DamianInRochester
Lifetime Supporting Member
We have two machines whose interface is Ethernet.
On one end is a ML1400 with built in Enet port
On the other end is an L35E with built in Enet port.
As a result of some bizarrely innapropriate saftey precautions being forced on manufacturing by HR, the machine controlled by the ML1400 must be turned off and locked out on a regular basis.
Every time this is done, it takes about 9 minutes (almost exactly and always consistent) for the L35E to re-stablish communication. Very occasionally you will get lucky and it will only take 30 seconds (much more tollerable).
The L35E is using message instructions CIP with SLC typed read and writes to N files on the ML1400. There is no logic on the ML1400 side for the communication, it is all on the L35E.
The error specifically is Code 1 "Connection Failure"
and Extended Code 204h "Unconnected message timeout"
The communication polling is being done by way of the MSG block handshaking signals (Not time based). When communication is lost or if a communication error exists, we re-start the MSG instruction at regular intervals (ie 10 seconds) until communication is re-stablished.
Generally, this all works fine. The communication, once up, does not miss a beat. If the L35E PLC is cycled, it also re-stablishes connection almost immediately.
It is only when the ML1400 goes down and comes back.
There seems to be some sort of timeout value in the L35E that refuses to re-initialize the connection. I have searched all the comm parameters on both the L35E, the MSG instructions, and the ML1400, and I can't find any timeouts that correlate to the 9 minutes (540 seconds) that I am experiencing.
Does anyone know of a way to force the L35E to close a connection so that it can be re-opened? This seems to be the source of my issues.
side note:
I have tried settting the {MSG_xxx}.EC "cached" bit both high and low. It has no effect. Having it set to low should cause to close the connection immediately after completion of the MSG instruction. It does not seem to do this.
On one end is a ML1400 with built in Enet port
On the other end is an L35E with built in Enet port.
As a result of some bizarrely innapropriate saftey precautions being forced on manufacturing by HR, the machine controlled by the ML1400 must be turned off and locked out on a regular basis.
Every time this is done, it takes about 9 minutes (almost exactly and always consistent) for the L35E to re-stablish communication. Very occasionally you will get lucky and it will only take 30 seconds (much more tollerable).
The L35E is using message instructions CIP with SLC typed read and writes to N files on the ML1400. There is no logic on the ML1400 side for the communication, it is all on the L35E.
The error specifically is Code 1 "Connection Failure"
and Extended Code 204h "Unconnected message timeout"
The communication polling is being done by way of the MSG block handshaking signals (Not time based). When communication is lost or if a communication error exists, we re-start the MSG instruction at regular intervals (ie 10 seconds) until communication is re-stablished.
Generally, this all works fine. The communication, once up, does not miss a beat. If the L35E PLC is cycled, it also re-stablishes connection almost immediately.
It is only when the ML1400 goes down and comes back.
There seems to be some sort of timeout value in the L35E that refuses to re-initialize the connection. I have searched all the comm parameters on both the L35E, the MSG instructions, and the ML1400, and I can't find any timeouts that correlate to the 9 minutes (540 seconds) that I am experiencing.
Does anyone know of a way to force the L35E to close a connection so that it can be re-opened? This seems to be the source of my issues.
side note:
I have tried settting the {MSG_xxx}.EC "cached" bit both high and low. It has no effect. Having it set to low should cause to close the connection immediately after completion of the MSG instruction. It does not seem to do this.