# Troubleshooting Modbus Timeout

**URL:** <https://forum.inductiveautomation.com/t/troubleshooting-modbus-timeout/99595>\
**Category:** Ignition\
**Created:** [December 9, 2024, 5:02pm UTC](https://forum.inductiveautomation.com/t/troubleshooting-modbus-timeout/99595 "2024-12-09T17:02:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marshall\_Tickner](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@Marshall\_Tickner](https://forum.inductiveautomation.com/u/Marshall_Tickner)\
**Post date:** [December 9, 2024, 5:02pm UTC](https://forum.inductiveautomation.com/t/troubleshooting-modbus-timeout/99595/1 "2024-12-09T17:02:06Z")

</div>

Any advice for chasing down warnings like the ones here? The device reads data fine most of the time but occasionally will throw one of these warnings.

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/b/fbba908e2eba55635baeffc7ba3f16b4841bcf76.png)

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [December 9, 2024, 5:19pm UTC](https://forum.inductiveautomation.com/t/troubleshooting-modbus-timeout/99595/2 "2024-12-09T17:19:26Z")

</div>

The first thing I'd look for is Clock Drift Warnings at the same time. Java GC pauses that are longer than your timeout (or overlap the timeout) can cause this.

Otherwise, look at your network. (Wireshark, perhaps.)