# Modbus TCPIP driver issues **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [February 4, 2025, 8:08pm UTC](https://forum.inductiveautomation.com/t/modbus-tcpip-driver-issues/101866 "2025-02-04T20:08:50Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Dustin\_VanKeuren](https://avatars.discourse-cdn.com/v4/letter/d/b782af/32.png) [@Dustin\_VanKeuren](https://forum.inductiveautomation.com/u/Dustin_VanKeuren)\ **Post date:** [February 4, 2025, 8:08pm UTC](https://forum.inductiveautomation.com/t/modbus-tcpip-driver-issues/101866/1 "2025-02-04T20:08:50Z")
We have a field device that used Modbus TCPip. I may be not understanding how this is supposed to be set up. I configured the driver for the correct IP and port, but the statusshows connected for a few seconds then drops out. I have actually remove all the tags using the connection except for one. Any ideas? ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [February 4, 2025, 8:22pm UTC](https://forum.inductiveautomation.com/t/modbus-tcpip-driver-issues/101866/2 "2025-02-04T20:22:07Z")
Where are you seeing the drop out? Is it in the device status in the gateway or in the designer where the tags are going bad? There are a lot of very low power Modbus devices that have limits on speed of polling and maximum amount of registers able to be polled at a time, maybe you are approaching these limits? These are configurable in the driver. Generally if it is "Bad" tags, if you have a single tag on the unit that fails for some reason, it will force all tags of the same register type/polled in the same request to fail as well. Fix the one bad tag and all the surrounding tags work again. ---
**Author:** ![Dustin\_VanKeuren](https://avatars.discourse-cdn.com/v4/letter/d/b782af/32.png) [@Dustin\_VanKeuren](https://forum.inductiveautomation.com/u/Dustin_VanKeuren)\ **Post date:** [February 4, 2025, 8:53pm UTC](https://forum.inductiveautomation.com/t/modbus-tcpip-driver-issues/101866/3 "2025-02-04T20:53:43Z")
at the gateway level. I have only 1 tag pointing to the device (might have the address wrong for that tag) Trying to figure out the addressing at the moment. ---
**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:** [February 4, 2025, 8:55pm UTC](https://forum.inductiveautomation.com/t/modbus-tcpip-driver-issues/101866/4 "2025-02-04T20:55:52Z")
Many devices will drop an idle connection after ten seconds. If you've screwed up the addressing, there might not be an active poll happening. ---
**Author:** ![Dustin\_VanKeuren](https://avatars.discourse-cdn.com/v4/letter/d/b782af/32.png) [@Dustin\_VanKeuren](https://forum.inductiveautomation.com/u/Dustin_VanKeuren)\ **Post date:** [February 4, 2025, 8:58pm UTC](https://forum.inductiveautomation.com/t/modbus-tcpip-driver-issues/101866/5 "2025-02-04T20:58:17Z")
I guess that makes sense. ---
**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:** [February 4, 2025, 9:00pm UTC](https://forum.inductiveautomation.com/t/modbus-tcpip-driver-issues/101866/6 "2025-02-04T21:00:59Z")
If you share more details, we can probably help you with the addressing. ---
**Author:** ![Dustin\_VanKeuren](https://avatars.discourse-cdn.com/v4/letter/d/b782af/32.png) [@Dustin\_VanKeuren](https://forum.inductiveautomation.com/u/Dustin_VanKeuren)\ **Post date:** [February 4, 2025, 9:31pm UTC](https://forum.inductiveautomation.com/t/modbus-tcpip-driver-issues/101866/7 "2025-02-04T21:31:07Z")
The device is a Red Lion device. It was set up (supposedly) with the addresses that were in the device that the Red Lion replaced. I am not familiar with the device nor its predecessor. The old HMI communicated to the old device through the same protocol I believe. The address for the heartbeat tag for example was 413499. So I entered the address as ns=1;s=[Roads]413499 That does not work, I get a config error on the tag. after running across this page: > **[Modbus Addressing | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.1/ignition-modules/opc-ua/opc-ua-drivers/modbus/modbus-addressing)** > > Manually Addressing a Modbus Device I tried ns=1;s=[Roads]HRI413499 (the heartbeat is a 32 bit integer I was told) I get a Bad status with this as opposed to bad configuration. ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [February 4, 2025, 9:43pm UTC](https://forum.inductiveautomation.com/t/modbus-tcpip-driver-issues/101866/8 "2025-02-04T21:43:36Z")
Start with defining the Device ID: `ns=1;s=[Roads]1.HRI413499` Also that register ID looks like its got a function code on the front, so its likely that it should be: `ns=1;s=[Roads]1.HRI13499` See how those go. ---
**Author:** ![ryan.white](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan.white/32/73193_2.png) [@ryan.white](https://forum.inductiveautomation.com/u/ryan.white)\ **Post date:** [February 4, 2025, 9:45pm UTC](https://forum.inductiveautomation.com/t/modbus-tcpip-driver-issues/101866/9 "2025-02-04T21:45:36Z")
You may also need to mess around with the `zero based addressing` and `reverse word order` options in the driver configuration for the device. ---
**Author:** ![Dustin\_VanKeuren](https://avatars.discourse-cdn.com/v4/letter/d/b782af/32.png) [@Dustin\_VanKeuren](https://forum.inductiveautomation.com/u/Dustin_VanKeuren)\ **Post date:** [February 4, 2025, 9:49pm UTC](https://forum.inductiveautomation.com/t/modbus-tcpip-driver-issues/101866/10 "2025-02-04T21:49:50Z")
`ns=1;s=[Roads]1.HRI13499` This worked! I guess I need to figure out how to reconfigure the rest of them. ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [February 4, 2025, 10:02pm UTC](https://forum.inductiveautomation.com/t/modbus-tcpip-driver-issues/101866/11 "2025-02-04T22:02:22Z")
If you can, mark the post as a solution to help others with similar issues. ---
**Author:** ![Dustin\_VanKeuren](https://avatars.discourse-cdn.com/v4/letter/d/b782af/32.png) [@Dustin\_VanKeuren](https://forum.inductiveautomation.com/u/Dustin_VanKeuren)\ **Post date:** [February 4, 2025, 10:07pm UTC](https://forum.inductiveautomation.com/t/modbus-tcpip-driver-issues/101866/12 "2025-02-04T22:07:31Z")
Kudos also to [pturmel](https://forum.inductiveautomation.com/u/pturmel) for providing a possible explanation for the connection dropping out. Unfortunately I can only mark one solution.