Hi,
I am testing Modbus TCP. I am able to read and write without any issues but on the logs, it keeps on going into a read timeout.
And the values in the tag browser goes in to bad_stale.
I have the force reconnect turned off as it constantly disconnects and reconnects.
I have set up the modbus addressing for two holding registers.
Could anyone point me in the right direction?
Thank you.
It’s hard to tell if those are really the device not responding or possible caused by the frequent clock drifts you’re experiencing.
Can you do a Wireshark capture to see if the device is responding or not?
Yes. I did a Wireshark capture and I can see the read requests and response from the device.
When I change the value of the tag, I can see the write request and the value changes on my PLC.
Can you upload your logs and Wireshark capture somewhere so we can take a look?
Those clock drift messages shouldn’t be ignored either.
It means either your system clock is constantly changing or your server is overloaded and freezing for 7-8 seconds at a time, frequently.
Yes. I have an ongoing issue (high CPU usage and high memory usage) and Technical support advised to do a java dump so they can check what is causing this.
Is that the only way to go?
Please see the attached link for the wireshark and igntion logs
There’s no Modbus traffic in your capture 
Your timeouts appear to be legit… you have the default driver timeout of 2 seconds set and according to Wireshark all the responses are coming back in a little over 2 seconds.
Oh Gotcha. So I made my Timeout to be 10 seconds but I see the read timeout on the logs.
It is also coming up with the clock drift with more than 10 seconds.
Changed the timeout to 60s and I don’t get the read timeout in the logs anymore.
Thank you very much.
