# Communication to Modbus/TCP elements drops down every 40-60 seconds **URL:** \ **Category:** Ignition\ **Tags:** ignition81, ignition79, ignition80\ **Created:** [July 5, 2023, 12:50pm UTC](https://forum.inductiveautomation.com/t/communication-to-modbus-tcp-elements-drops-down-every-40-60-seconds/75932 "2023-07-05T12:50:03Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![ilan](https://avatars.discourse-cdn.com/v4/letter/i/ecae2f/32.png) [@ilan](https://forum.inductiveautomation.com/u/ilan)\ **Post date:** [July 5, 2023, 12:50pm UTC](https://forum.inductiveautomation.com/t/communication-to-modbus-tcp-elements-drops-down-every-40-60-seconds/75932/1 "2023-07-05T12:50:03Z")
Hello all we are having approx. project of 15 (Phoenix contact) Modbus converters - behind them groups of 30 RTU elements each. 4 of the converters readings are not stable: every 40-60 seconds it drops down for 1-2 seconds/ We slowed down the timeout of the device gateway up to 10000 - no success. Any ideas? ---
**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:** [July 5, 2023, 1:00pm UTC](https://forum.inductiveautomation.com/t/communication-to-modbus-tcp-elements-drops-down-every-40-60-seconds/75932/2 "2023-07-05T13:00:11Z")
Do you know what the Phoenix Contact converters have as an idle timeout? If you don't have at least one subscription item guaranteed to read that fast (for each), the converter may be the piece that is timing out. This would be visible in Wireshark captures. ---
**Author:** ![ilan](https://avatars.discourse-cdn.com/v4/letter/i/ecae2f/32.png) [@ilan](https://forum.inductiveautomation.com/u/ilan)\ **Post date:** [July 5, 2023, 1:30pm UTC](https://forum.inductiveautomation.com/t/communication-to-modbus-tcp-elements-drops-down-every-40-60-seconds/75932/3 "2023-07-05T13:30:48Z")
Thank you ! How would you suggest to filter with Wireshark. and which result to expect. ---
**Author:** ![ilan](https://avatars.discourse-cdn.com/v4/letter/i/ecae2f/32.png) [@ilan](https://forum.inductiveautomation.com/u/ilan)\ **Post date:** [July 5, 2023, 1:48pm UTC](https://forum.inductiveautomation.com/t/communication-to-modbus-tcp-elements-drops-down-every-40-60-seconds/75932/4 "2023-07-05T13:48:54Z")
We set the Phoenix Contact converter timeout from 100 up to20000ms. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [July 5, 2023, 2:01pm UTC](https://forum.inductiveautomation.com/t/communication-to-modbus-tcp-elements-drops-down-every-40-60-seconds/75932/5 "2023-07-05T14:01:47Z")
You may also want to set the "Reconnect After Consecutive Timeouts" setting on the driver to `false`. ---
**Author:** ![ilan](https://avatars.discourse-cdn.com/v4/letter/i/ecae2f/32.png) [@ilan](https://forum.inductiveautomation.com/u/ilan)\ **Post date:** [July 6, 2023, 2:30pm UTC](https://forum.inductiveautomation.com/t/communication-to-modbus-tcp-elements-drops-down-every-40-60-seconds/75932/6 "2023-07-06T14:30:16Z")
Problem solved! I increased the Idle Force Timeout Characters to 100 (default = 10). Thanks!!! ---
**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:** [July 6, 2023, 3:15pm UTC](https://forum.inductiveautomation.com/t/communication-to-modbus-tcp-elements-drops-down-every-40-60-seconds/75932/7 "2023-07-06T15:15:20Z")
> [@ilan](#): > > I increased the Idle Force Timeout Characters to 100 Eww! That kind of tweak should not be needed for Modbus TCP. Are you using Modbus RTU over TCP? That is quite different. What model converter is this?