Steve Etter
Lifetime Supporting Member + Moderator
I am having an interesting problem with an Ethernet IP connection between two CompactLogix Controllers that I am hoping someone has some ideas about.
The two processors I have are a 1769-L32E and a 1769-L35E. They are connected via an Ethernet network and I am communicating between them via Produced and Consumed tags. The problem I am having is that the communications on the L32E is showing an error code 16#0203: "Communications Time Out" for the L35E processor. The really interesting thing about this problem is that sometimes I can get the communications to work for a couple of minutes (witnessed by monitoring handshake logic between the two processors) and then it will drop out. For note, there is no error displayed in the L35E processor.
FYI - I have the same communications working between this L32E processor and a 1756-L61 processor already. I have no problems with it.
So far I have:
1) rewritten both of the produced and consumed tags in the L32E processor (this actually seemed to get the communications working again - once),
2) rebooted the L32E processor (this seemed to work once, too),
3) removed and recreated the processor in the L32E program's I/O configuration,
4) adjusted the RPI time as high as 500ms for the produced tag in the L32E processor, and
5) verified the logic and tag configuration in both processors. So far, the handshake monitoring is all that is affected in either PLC by this fault.
I am not at liberty to randomly reboot or modify the tags and program in the L35E since it is a running machine at this time and I need to have a pretty good idea how to resolve the problem before doing so.
Anybody have any ideas?
Steve
The two processors I have are a 1769-L32E and a 1769-L35E. They are connected via an Ethernet network and I am communicating between them via Produced and Consumed tags. The problem I am having is that the communications on the L32E is showing an error code 16#0203: "Communications Time Out" for the L35E processor. The really interesting thing about this problem is that sometimes I can get the communications to work for a couple of minutes (witnessed by monitoring handshake logic between the two processors) and then it will drop out. For note, there is no error displayed in the L35E processor.
FYI - I have the same communications working between this L32E processor and a 1756-L61 processor already. I have no problems with it.
So far I have:
1) rewritten both of the produced and consumed tags in the L32E processor (this actually seemed to get the communications working again - once),
2) rebooted the L32E processor (this seemed to work once, too),
3) removed and recreated the processor in the L32E program's I/O configuration,
4) adjusted the RPI time as high as 500ms for the produced tag in the L32E processor, and
5) verified the logic and tag configuration in both processors. So far, the handshake monitoring is all that is affected in either PLC by this fault.
I am not at liberty to randomly reboot or modify the tags and program in the L35E since it is a running machine at this time and I need to have a pretty good idea how to resolve the problem before doing so.
Anybody have any ideas?
Steve