jshiepe
Member
Hi folks,
Had a strange one happen last night and I can't seem to figure out exactly what the cause was. A SLC 5/05 just seemed to stop communicating from the Channel 1 port(ethernet). The CPU was not faulted and the ENET light on the CPU was solid green, but neither the I/O server I'm using(Wonderware's DASABCIP, which has been very reliable) nor RSLinx from my programming node could see it. It was almost like a cable had been unplugged, but all were checked and were plugged in solid.
It gets a little stranger.....
I had the techs cycle power while I watched RSWho in Linx from my programming terminal and waited to see the CPU come back online. The techs told me it was powered up and I should be able to see it, but I couldn't see it in RSWho.........BUT I could ping it! I was also able to reconnect the DASABCIP server, and everything seemed to return to normal, except for this issue with RSWho. The only way I could see it again was by shutting down and restarting RSLinx(Classic version, 2.5).
I guess I have two questions:
1. What caused the original problem of comms on channel 1 to just stop without any type of CPU fault?
2. Why did I have to cycle RSLinx to see the CPU again? I've never had to do that before....
Any input would be greatly appreciated.
Thanks,
Jeff
Had a strange one happen last night and I can't seem to figure out exactly what the cause was. A SLC 5/05 just seemed to stop communicating from the Channel 1 port(ethernet). The CPU was not faulted and the ENET light on the CPU was solid green, but neither the I/O server I'm using(Wonderware's DASABCIP, which has been very reliable) nor RSLinx from my programming node could see it. It was almost like a cable had been unplugged, but all were checked and were plugged in solid.
It gets a little stranger.....
I had the techs cycle power while I watched RSWho in Linx from my programming terminal and waited to see the CPU come back online. The techs told me it was powered up and I should be able to see it, but I couldn't see it in RSWho.........BUT I could ping it! I was also able to reconnect the DASABCIP server, and everything seemed to return to normal, except for this issue with RSWho. The only way I could see it again was by shutting down and restarting RSLinx(Classic version, 2.5).
I guess I have two questions:
1. What caused the original problem of comms on channel 1 to just stop without any type of CPU fault?
2. Why did I have to cycle RSLinx to see the CPU again? I've never had to do that before....
Any input would be greatly appreciated.
Thanks,
Jeff