# OPC Device Connections unstable

**URL:** <https://forum.inductiveautomation.com/t/opc-device-connections-unstable/90336>\
**Category:** Ignition\
**Tags:** opcua, modbus\
**Created:** [May 13, 2024, 11:49pm UTC](https://forum.inductiveautomation.com/t/opc-device-connections-unstable/90336 "2024-05-13T23:49:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nebul0us](https://avatars.discourse-cdn.com/v4/letter/n/82dd89/32.png) [@Nebul0us](https://forum.inductiveautomation.com/u/Nebul0us)\
**Post date:** [May 13, 2024, 11:49pm UTC](https://forum.inductiveautomation.com/t/opc-device-connections-unstable/90336/1 "2024-05-13T23:49:03Z")

</div>

Hey all,

We have a lot of OPC connections that are unstable. Most are using Modbus/TCP drivers, and they will connect sometimes. But often they cycle between "connecting, disconnected," or "ReconnectWait." At the same time several of our Modbus driver connections are working just fine. I am a lesser experienced Ignition user so might need a bit of walk through in troubleshooting this issue. With these two devices in particular, I can reboot the sensor and the connection will reestablish for about a week. I'm not even sure where to begin to be honest. Are there some troubleshooting tools in Ignition for this? Using Ignition 8.1.33 currently. Thanks for the help in advance!

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/6/1691d09fea65335ce80fd4d07e8c28bfef146530.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:** [May 14, 2024, 11:29am UTC](https://forum.inductiveautomation.com/t/opc-device-connections-unstable/90336/2 "2024-05-14T11:29:29Z")

</div>

> [@Nebul0us](#):
>
> in Ignition for this?

No, not really. I recommend collecting a wireshark capture from the gateway during one of these events. Use a capture filter for the target IP address, typically `host w.x.y.z`

Perhaps, use Wireshark's "ring buffer" mode to continuously capture with file rollover (for a known length of past time).

Whatever is happening will be pretty clear in a packet capture.
