CtrlX Core X3 boot error because of Modbus fiedbus

[Hugues]

Hello,

I'm having two similar problems about a CtrlX Core X3 communicating with a speed variator drive (EFC5610) by the Modbus TCP App.

So in the first case, the CtrlX won't boot properly while having a Modbus communication plugged on its XF51 port. The indicator lights vary between red and blue so it means that it activated the rescue system (from the status displays document). Nothing changes unless I unplug the cable on the XF51 port. The CtrlX then boots normally and works correctly after I plug again on the XF51 port.

Same configuration with a different CtrlX Core X3, this time the CtrlX boots and starts properly. But the Modbus communication doesn't start unless I unplug and then re-plug the XF51 port.

So that makes two very similar situation and it is quite disturbing having to physically interact with the system everytime it restarts. So I'm wondering what could be the cause of it ? Could it be an app version issue or else ?

I'm using a CtrlX Core X3 in 1.20 version and the Modbus TCP app in 1.20.1 version. I also don't think that the problem comes from the bus configuration because the bus works well after the quick cable handling.

Thank you in advance.

[Hugues]

UPDATE : I tried an other Modbus communication using function blocks in PLC Engineering. The problem remains the same.  I also observed that the sequence of booting the Core with the drive being off first (and then power it right after) works just fine. Is it possible that there is a conflict in some way between the booting and the Modbus communication ?

[cc2go]

Hello,
is XF10 and XF51 in same subnet and at same switch or how is your IP-address configuration, can you give an example.
in any case you should update your software and apps to the current release 1.20 (RM 23.03.5), that is available by our collaboration room. Pls check if issue remains.

If remain, pls attach a system report, to see which additional apps you use.