Hello all!
Quick run down of situation before i ask my question. Currently have a project replacing 35 1305 over remote I/O with PF525 via the AN-X2 prosoft controller.
Everything with the conversion going well except communicating to the 525 over Ethernet after initial set up of 4 drive group. This is my process:
This has been consistent on four groups of four drives set up with the same switch (N-tron 108TX) and E-net cables (certified not homemade). All were changed out on the last group and the issue persists.
So after all of that my question is. Do any of you see something I'm doing wrong with CCW not reconnecting? I know it seems like a minor thing but there is a common RsLink file stored on our source control server that is universal to everyone. I want to make it as easy as possible for our techs to get connected without this kind of issue. just pull the files and go.
I almost think its a windows issue but have no way to prove it. Could just as easily be CCW or linx as well. CCW version 8.01.00 and Rslinx gateway version 3.71
Anyone else had this issue? Checked RA knowledge base and didn't find anything but could have missed something.
Any suggestions appreciated.
Quick run down of situation before i ask my question. Currently have a project replacing 35 1305 over remote I/O with PF525 via the AN-X2 prosoft controller.
Everything with the conversion going well except communicating to the 525 over Ethernet after initial set up of 4 drive group. This is my process:
- Wire power and Ethernet up on the bench (4 drives that's all the AN-X2 supports per unit.)
- Apply power
- Used GUI to change IP to AN-X2
- Use DHCP to assign IP addresses to 525 drives
- Add address ranges to RsLinx driver
- Download drive configuration with CCW establishing linx driver.
- Configure AN-X2 module
- Download test program for RIO control from RsLogix 500 over serial connection.
- Connect RIO 230.4K with resistor.
- control drives with test program.
- connect to drives with CCW through same driver.
- Put drives in idle state with 500 test program
- disconnect computer from test program and drives
- remove power for 15 minutes+
- shut all programs down.
- repeat steps 2,10 successfully
- step 11 fails to connect to the drives with CCW.
This has been consistent on four groups of four drives set up with the same switch (N-tron 108TX) and E-net cables (certified not homemade). All were changed out on the last group and the issue persists.
So after all of that my question is. Do any of you see something I'm doing wrong with CCW not reconnecting? I know it seems like a minor thing but there is a common RsLink file stored on our source control server that is universal to everyone. I want to make it as easy as possible for our techs to get connected without this kind of issue. just pull the files and go.
I almost think its a windows issue but have no way to prove it. Could just as easily be CCW or linx as well. CCW version 8.01.00 and Rslinx gateway version 3.71
Anyone else had this issue? Checked RA knowledge base and didn't find anything but could have missed something.
Any suggestions appreciated.