09-20-2012 06:42 PM
Hello
I have read previous posts on this error and none seem to provide a fix for this situation
I have three SLC5/05 CPUs on a private network. They are addressed as PLC1 (192.168.1.11), PLC2 (192.168.1.12), PLC3 (192.168.1.13). PLCs are connected via a fibre optic switch, at the end of the fibre is a fibre to UTP router (non managed). PLC1 and PLC2 are on one fibre optic link, PLC3 is on a seperate fibre. I connect a LabVIEW computer to the fibre switch and I can communicate to PLC3 using SLC500 Read Float.vi. I read File Number = 8, Element = 0, Number of Elements = 1. PLC3 returns valid data. When I try to request data from PLC1 and PLC2 the Error -251723767 is returned. I am entering the 192.168.1.11 ip address directly into the Network Path field but have also tried 192.168.1.11,1,0. All CPU's are in slot 0 on all PLC backplanes
From the LabVIEW computer I can ping PLC1 and PLC2.
From another computer on the private network on can run RSLINX 5000 and communicate to PLC1, PLC2 and PLC3
I have installed the EthernetIP package on a laptop and took the laptop down to the fibre to UTP router on PLC1 and PLC2 and connected directly to the router. I still get the above error but can still communicate to PLC3 from anywhere on the private network
I have swapped the PLC1 and PLC2 router with another just to check no firewall was impeding PLC1 and PLC2 communications (even though it is un-managed, getting desperate) with the same error being returned.
So I am now totally confused with why PLC1 and PLC2 are not communicating. Is there a setting to turn off PCCC communications in a SLC5/05? What other things could be configured in a PLC to not allow these vi's to work?
Any help would be greatly appreciated
Cheers
Michael
10-24-2012 12:29 AM
I found the solution for this problem
I was communicating to an SLC5/05 with the following OS and Firmware Revision - OS501 Series A FRN 3.
I found a note on the web suggesting that CPPP was not implemented till OS 501 Series A FRN 5
I have now upgraded to OS501 Series C FRN 11 and communications with LabVIEW is working
Cheers
Michael