About Modbus TCP Communication

[Chirag03]

Hello,

I have third party HMI which is connected to ctrlx core XF10 port. Now i want to configure HMI button via ModbusTCP communication .

1)So i need to purchase Modbus TCP Licesnse from ctrlX store .

2)Is there any possibility to connect via plc . if that possible then how can i do that?

Thanks in advance

[TheCodeCaptain · Accepted solution]

Hi Chiragkumar,

here is an example how to do it from the PLC:
Solved: ModBus RTU on CORE (boschrexroth.com)

Regards

[Chirag03]

Hello,

Thank you for your answer.

I have to configure  third party device via Modbus TCP . But how can i do via Modbus RTU?

For modbus TCP communication, Which port of ctrlX core i have to use?

[TheCodeCaptain]

Hi,

for Modbus TCP you can use XF10 or XF51.

Here are some possible ways to communicate via Modbus TCP:
Solved: Looking for a Modbus TCP example program (boschrexroth.com)

In the PLC library you can find some examples as well.

PLCModbus TCP

[Chirag03]

Hi,  

Thank you for your reply.

I try it but my device not reconginze.

So for that i have to buy license from ctrlX store?

[TheCodeCaptain]

Hi,

License is only needed for our Modbus TCP App.

If you do it on your own via PLC Libraries you do not need the Modbus License.

[MauroRiboniMX]

Sorry to interrupt you guys but is the HMI that should read the data in ctrlX right? In that case the ctrlX modbus TCP app is useless since it is just a client. the only feaible way is to create a server in the PLC like @TheCodeCaptain said.

[Chirag03]

Hi,

Thank you fro your reply.

Now i am able to communicate modbus via PLC libraries. I cofigured modubus as separate task in PLC program  with cycle time 1ms. But when i press button from HMI , robot start moving but it take delay . Is any possibility to reduce this delay ? 

[MauroRiboniMX]

Hello, 

Modbus TCp is not famous to be a really performant protocol. The ctrlX core is just a server it waits for communications so the bottleneck should be your HMI. Consider to move to OPCUA.

Mauro