Modbus RTU over TCP Timeout Issue

Hello ,
Ignition version 8.0.1 and Ignition 7.9 (Both)

I am first time doing interface of PLC over MODBUS RTU over TCP in ignition . I am using Mitsubishi MT91 card for Modbus communication and verified Modbus communication with MODSCAN32 application . It is working perfectly fine , getting data over Modbus . But when I tired same interfacing with ignition , getting time out error. I increased thresholds also but getting same response . I changed configuration of 125 to 10 as I needed to read only 10 holding register from 400001 to 10 .

Logger Time Message
TimeoutDaemon 20May2019 12:55:49 ScheduledRequest[com.inductiveautomation.xopc.drivers.modbus2.requests.ReadHoldingRegistersRequest@302ed88b] request with key “java.lang.Object@2395d66e” failed due to timeout.
ReadHoldingRegistersRequest 20May2019 12:55:49 Request failed. FailureType==TIMEOUT
TimeoutDaemon 20May2019 12:55:19 ScheduledRequest[com.inductiveautomation.xopc.drivers.modbus2.requests.ReadHoldingRegistersRequest@302ed88b] request with key “java.lang.Object@2395d66e” failed due to timeout.
ReadHoldingRegistersRequest 20May2019 12:55:19 Request failed. FailureType==TIMEOUT
ReadHoldingRegistersRequest 20May2019 12:54:48 Uncaught Throwable handling response. key=java.lang.Object@2395d66e, req=[ ], rsp=[ 01 03 00 00 00 ]
TimeoutDaemon 20May2019 12:54:48 ScheduledRequest[com.inductiveautomation.xopc.drivers.modbus2.requests.ReadHoldingRegistersRequest@302ed88b] request with key “java.lang.Object@2395d66e” failed due to timeout.
ReadHoldingRegistersRequest 20May2019 12:54:48 Request failed. FailureType==TIMEOUT
ReadHoldingRegistersRequest 20May2019 12:54:15 Request failed. FailureType==DISCONNECTED
ReadHoldingRegistersRequest 20May2019 12:54:15 Request failed. FailureType==DISCONNECTED
TimeoutDaemon 20May2019 12:54:15 ScheduledRequest[com.inductiveautomation.xopc.drivers.modbus2.requests.ReadHoldingRegistersRequest@7222a9f7] request with key “java.lang.Object@2395d66e” failed due to timeout.

Please help me !! thanks in advance !!!

Maybe you need to set the unit/slave id on your Ignition tags?

It defaults to 0 in Ignition, so try addresses like [MyDevice]1.HR1 to try unit 1, etc…

If that doesn’t work, a comparison of Ignition and Modscan traffic via Wireshark would help.

It’s 1 only in my configuration.and i tried both methods of addressing but not happening . Is there any limitations for modbus in ignition trail version ? I hope that’s not the case.

Can you share basic configuration needed to communicate with modbus to read 10 holding register only. working at you end .

Thanks