Modbus Bad due to TimeOut

Ignition
1

Hi all,
I'm currently testing Ignition by using Docker container. On the project, I create a Modbus Device linked to a local Modbus Simulator (pyModSlave).
The device has a connected status.
I create then a new tag but it gets a Bad status. I can see on pyModSlave the Rx and Tx activity. On ignition logs, I can find:

java.lang.Exception: Request failed by TimeoutDaemon due to timeout: ScheduledRequest[com.inductiveautomation.xopc.drivers.modbus2.requests.ReadCoilsRequest@70b3b116]

at com.inductiveautomation.xopc.driver.api.BasicRequestCycle$TimeoutDaemon.failRequests(BasicRequestCycle.java:376)

at com.inductiveautomation.xopc.driver.api.BasicRequestCycle$TimeoutDaemon.run(BasicRequestCycle.java:328)

at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source)

at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.base/java.lang.Thread.run(Unknown Source)

I cannot find where should I change/check the Timeout settings for this modbus connection. Except if I'm wrong, there is nothing on the Tag Group or the device connection settings.

If someone can help please.

Thanks,

Martial

2

The timeout setting is not likely the problem.

Usually this means the slave isn’t responding at all. Most often because you have an invalid address and/or slave/unit id specified.

Ignition defaults to requesting id 0 unless you prepend another to the address.

3

Thanks Kevin.

I used this path on the tags:
[ModSim]1.C01
[ModSim]1.C02

I have to use [ModSim]1.C1 and 1.C2

Regards,

Martial