TeSys T LTMR Ethernet communication loss don't work.

[Nurali]

Hellow everybody. 
I have a problem whith LTMR27EFM, when we change to remote control (I.6 input ON) with Ethernet IP from PLC CompacLogix is working (run, O.1, O.2 e.t.c) but when I physicaly imitate communication loss with disconecting the wire UTP, the outputs motor start LO.1 and LO.2 are not Shout down or not swhitching but LO.1 and LO.2 are state "ON" (comand from CompacLogix).

• Parametr network port fallback action setting = LO1, LO2 off
• Network protocol = Ethernet IP 
• Network port trip enable = enable 

[NeiB · Accepted solution]

Hi Nurali,

Wish you are very well.

It seems to me that what is missing is the primary IP address as indicated on the user manual page 26 and 29 from the link as follow:

https://download.schneider-electric.com/files?p_Doc_Ref=DOCA0129EN&p_enDocType=User+guide&p_File_Nam... 

Hope this help. If the problem persists, I suggest that you open a technical case with Schneider at your country and include the complete SoMove file exported for a deeper investigation.

Best Regards, 

Neide

[palani84]

Hi Neide,

I hope you're doing well.

I’d like to raise a concern regarding the Tesys LTMR behavior following a communication loss with the PLC. After a COM LOSS event, the remote start command (bit 704.0) retains its last value, even though the motor stops as per the configured fail-safe response. However, once communication with the primary PLC IP is restored, the LTMR immediately executes the retained start command, causing the motor to restart unexpectedly. It then resumes following PLC commands thereafter.

This behavior poses a significant safety risk in the field, as the unintended motor restart could lead to hazardous conditions.

Is there a recommended method or function to automatically clear or reset bit 704.0 upon communication loss, to prevent this scenario? Any guidance or best practices to ensure safe recovery behavior would be greatly appreciated.

Best regards, 

Palanikumar