About cc2go

cc2go

I've heard a solution is found. And it's working with the ctrlX CORE. The robot is a Modbus Client, the ctrlX core must be a Modbus Server, it doesn't matter RTU or TCP. The CXA_Modbus Libs can be used.

cc2go

Hello, we tested the Modbus TCP App with the S20-ETH-BK. What I can see in your screenshot and your module you made a mistake. With the S20-DIDO-8/1 you will need just one register for the Inputs and another for the Outputs. The available registers you can find at the bus couplers webpage. When you use FC4 with register 8000 , quantity 1 and for FC16 with register 9000 or 9001 (check the webpage of BK), quantity 1 it should work. If it's not working, please send me a PN.

cc2go

Good news, we identified the issue, it will be solved with v1.18 of ctrlX Works. As I already mentioned, device is working properly, just ignore the red symbol, when using in current verison like v1.16

cc2go

This will work, but the IODD support is with the IFM tool, like Moneo or LR Device, only

cc2go

Yes, the ctrlX COREplus X3 or X7 with XB-EC-31 is possible. Have it with a ctrlX COREplus X3 running on my desk.

About cc2go

Re: Looking for a Modbus TCP example program

Re: Modbus TCP App issue.

Re: IO-Link error

Re: I/O Link Slave - I/O Engineering

Re: Support of EtherCAT junction and EtherCAT hub