# Modbus TCP - Moore / Siemens 353 **URL:** \ **Category:** Ignition\ **Tags:** modbus\ **Created:** [September 13, 2024, 6:53pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-moore-siemens-353/95970 "2024-09-13T18:53:52Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![Stephen\_Lasley](https://avatars.discourse-cdn.com/v4/letter/s/a3d4f5/32.png) [@Stephen\_Lasley](https://forum.inductiveautomation.com/u/Stephen_Lasley)\ **Post date:** [September 13, 2024, 6:53pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-moore-siemens-353/95970/1 "2024-09-13T18:53:52Z")
I have a new installation with a Moore / Siemens 353 controller using Modbus TCP. It all works great for the first 15 or so minutes - then, it just times-out and cycles from connecting/disconnecting/etc. If I disable/enable, it starts to work again - for 15 minutes. Is there some obvious setting that I can change to correct this behavior? ---
**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:** [September 13, 2024, 6:59pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-moore-siemens-353/95970/2 "2024-09-13T18:59:06Z")
Have you set up some tags yet? It is common for Modbus TCP devices to cut off idle connections. (Sometimes in as little as ten seconds.) ---
**Author:** ![Stephen\_Lasley](https://avatars.discourse-cdn.com/v4/letter/s/a3d4f5/32.png) [@Stephen\_Lasley](https://forum.inductiveautomation.com/u/Stephen_Lasley)\ **Post date:** [September 13, 2024, 7:41pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-moore-siemens-353/95970/3 "2024-09-13T19:41:39Z")
Yes, I have 4 tags configured. The opc quick client at a 1000ms refresh updates without issue... until about 15 minutes... sometimes shorter.. ---
**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:** [September 13, 2024, 7:47pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-moore-siemens-353/95970/4 "2024-09-13T19:47:55Z")
Maybe you can get a Wireshark capture of an entire cycle of this, from connect until it stops responding, but I'm not sure how much help it will be. Sounds like this device is buggy/broken. ---
**Author:** ![Stephen\_Lasley](https://avatars.discourse-cdn.com/v4/letter/s/a3d4f5/32.png) [@Stephen\_Lasley](https://forum.inductiveautomation.com/u/Stephen_Lasley)\ **Post date:** [September 14, 2024, 3:53am UTC](https://forum.inductiveautomation.com/t/modbus-tcp-moore-siemens-353/95970/5 "2024-09-14T03:53:31Z")
So... looks like the Modbus/TCP transaction identifier counts up to 1024 - and, then, poof. I don't think these devices like anything over 1023. Is there some sort of way to make ignition start over at 512 or 1023? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/7/973b9a3c4be93642d86a671650271b1d6af63c7f.png) ---
**Author:** ![Stephen\_Lasley](https://avatars.discourse-cdn.com/v4/letter/s/a3d4f5/32.png) [@Stephen\_Lasley](https://forum.inductiveautomation.com/u/Stephen_Lasley)\ **Post date:** [September 14, 2024, 4:43am UTC](https://forum.inductiveautomation.com/t/modbus-tcp-moore-siemens-353/95970/6 "2024-09-14T04:43:04Z")
Also referenced here... [I/A Series G3 Modbus TCP communications to Siemens Moore 353 controller stops updating after a period of time after ENC/JACE ... - Schneider Electric Community](https://community.se.com/t5/Building-Automation-Knowledge/I-A-Series-G3-Modbus-TCP-communications-to-Siemens-Moore-353/ta-p/4382) ---
**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:** [September 14, 2024, 11:51am UTC](https://forum.inductiveautomation.com/t/modbus-tcp-moore-siemens-353/95970/7 "2024-09-14T11:51:48Z")
There’s no configuration for this, no. ---
**Author:** ![Stephen\_Lasley](https://avatars.discourse-cdn.com/v4/letter/s/a3d4f5/32.png) [@Stephen\_Lasley](https://forum.inductiveautomation.com/u/Stephen_Lasley)\ **Post date:** [September 14, 2024, 2:32pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-moore-siemens-353/95970/8 "2024-09-14T14:32:29Z")
So, the options are 1) don't use ignition 2) replace all 353s with something else 3) find an OPCua that would support it or 4) use the SDK to write my own driver? ---
**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:** [September 14, 2024, 2:46pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-moore-siemens-353/95970/9 "2024-09-14T14:46:53Z")
I suppose I could make an option for this in my alternate driver. ---
**Author:** ![Stephen\_Lasley](https://avatars.discourse-cdn.com/v4/letter/s/a3d4f5/32.png) [@Stephen\_Lasley](https://forum.inductiveautomation.com/u/Stephen_Lasley)\ **Post date:** [September 14, 2024, 2:58pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-moore-siemens-353/95970/10 "2024-09-14T14:58:47Z")
You add, I'll buy. 🙂 ---
**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:** [September 14, 2024, 10:42pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-moore-siemens-353/95970/11 "2024-09-14T22:42:15Z")
Phil's driver is a good option as long as you aren't using Edge, which doesn't allow custom / 3rd party modules to be installed. ---
**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:** [September 15, 2024, 10:50am UTC](https://forum.inductiveautomation.com/t/modbus-tcp-moore-siemens-353/95970/12 "2024-09-15T10:50:29Z")
After ICC. I have a couple other items needing attention in that driver. ---
**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:** [October 1, 2024, 2:58pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-moore-siemens-353/95970/13 "2024-10-01T14:58:54Z")
This has now been implemented, via a new driver setting. > [@Automation Professionals' Advanced Modbus Driver](https://forum.inductiveautomation.com/t/automation-professionals-advanced-modbus-driver/41312/68): > > Automation Professionals is pleased to announce a new production release of the Advanced Modbus Module. For Ignition v8.1.x: [v1.1.7.242701819](https://www.automation-pros.com/ignition/Advanced%20Modbus%20Driver-1.1.7.242701819-v81.modl) This includes a bugfix for the driver status problem mentioned in [comment #63](https://forum.inductiveautomation.com/t/automation-professionals-advanced-modbus-driver/41312/63) above. This includes the constrained Transaction ID feature requested in this topic: Also note the announcement over there that this module of mine is now available in Edge.