# Modbus OPC tag disconnecting constantly

**URL:** <https://forum.inductiveautomation.com/t/modbus-opc-tag-disconnecting-constantly/28355>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [September 18, 2019, 4:55pm UTC](https://forum.inductiveautomation.com/t/modbus-opc-tag-disconnecting-constantly/28355 "2019-09-18T16:55:06Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![jlam](https://avatars.discourse-cdn.com/v4/letter/j/839c29/32.png) [@jlam](https://forum.inductiveautomation.com/u/jlam)\
**Post date:** [September 18, 2019, 4:55pm UTC](https://forum.inductiveautomation.com/t/modbus-opc-tag-disconnecting-constantly/28355/1 "2019-09-18T16:55:06Z")

</div>

Hi,

I’ve been connecting to a Modbus device to gather data measurements and the data comes through from OPC tags for ~10 seconds (data is updating), but then it stops.

The logs show this message: **ReadHoldingRegistersRequest** , **Request failed. FailureType==DISCONNECTED**

I’ve been playing around with my tag groups and their common Rate (~10,000) and custom opcRate (~10,000). Should I be using both of these rates with the same value? I have been using two different values.

Is this the same case as ([Modbus TCP Request Failed](http://forum.inductiveautomation.com/t/modbus-tcp-request-failed/21147))? Could you direct me to the fixes that were mentioned here ([[bug-14313]Direct Tag Group running on Leased/Driven rate](http://forum.inductiveautomation.com/t/bug-14313-direct-tag-group-running-on-leased-driven-rate/27158/2))?

Detailed message below:  
java.lang.Exception: RequestCycle stopped.  
at com.inductiveautomation.xopc.driver.api.BasicRequestCycle.shutdown(BasicRequestCycle.java:281)  
at com.inductiveautomation.xopc.driver.api.AbstractDriver.createNewRequestCycle(AbstractDriver.java:763)  
at com.inductiveautomation.xopc.driver.api.AbstractDriver.notifyDisconnectDone(AbstractDriver.java:722)  
at com.inductiveautomation.xopc.driver.api.AbstractIODelegatingDriver.notifyDisconnectDone(AbstractIODelegatingDriver.java:71)  
at com.inductiveautomation.xopc.driver.api.AbstractIODelegatingDriver.disconnect(AbstractIODelegatingDriver.java:43)  
at com.inductiveautomation.xopc.driver.api.AbstractIODelegatingDriver.reconnect(AbstractIODelegatingDriver.java:93)  
at com.inductiveautomation.xopc.drivers.modbus2.AbstractModbusDriver.access$000(AbstractModbusDriver.java:97)  
at com.inductiveautomation.xopc.drivers.modbus2.AbstractModbusDriver$2.notifyCommunicationTimeout(AbstractModbusDriver.java:138)  
at com.inductiveautomation.xopc.drivers.modbus2.requests.AbstractModbusRequest.fail(AbstractModbusRequest.java:169)  
at com.inductiveautomation.xopc.drivers.modbus2.requests.AbstractModbusReadRequest.fail(AbstractModbusReadRequest.java:121)  
at com.inductiveautomation.xopc.driver.api.requests.TimedRequest.fail(TimedRequest.java:44)  
at com.inductiveautomation.xopc.driver.api.BasicRequestCycle$TimeoutDaemon.failRequests(BasicRequestCycle.java:374)  
at com.inductiveautomation.xopc.driver.api.BasicRequestCycle$TimeoutDaemon.run(BasicRequestCycle.java:329)  
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)  
at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source)  
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)  
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)  
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)  
at java.base/java.lang.Thread.run(Unknown Source)

---

<div class="post-metadata">

**Author:** ![WillMT10](https://avatars.discourse-cdn.com/v4/letter/w/7feea3/32.png) [@WillMT10](https://forum.inductiveautomation.com/u/WillMT10)\
**Post date:** [September 18, 2019, 5:00pm UTC](https://forum.inductiveautomation.com/t/modbus-opc-tag-disconnecting-constantly/28355/2 "2019-09-18T17:00:07Z")

</div>

Looks like this post may be a similar issue to what you’re seeing: [modbus connection toggling between connected disconnected](http://forum.inductiveautomation.com/t/modbus-connection-toggling-between-connected-disconnected/28041)

---

<div class="post-metadata">

**Author:** ![jlam](https://avatars.discourse-cdn.com/v4/letter/j/839c29/32.png) [@jlam](https://forum.inductiveautomation.com/u/jlam)\
**Post date:** [September 26, 2019, 3:05pm UTC](https://forum.inductiveautomation.com/t/modbus-opc-tag-disconnecting-constantly/28355/3 "2019-09-26T15:05:38Z")

</div>

Hmm I tried changing the poll rates, having some tags with a 5s scan rate and the rest around 7s but still no luck. If I make the scan rate extremely small, it seems to just timeout faster (from 2min to 1min).

Looking at all of the log messages, is LegacyScripting[system\_util\_tag] relevant to the disconnection?

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/f/f0f64ef6ea948b0b02f9c147f35c4d0016af6d5f.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:** [September 26, 2019, 3:19pm UTC](https://forum.inductiveautomation.com/t/modbus-opc-tag-disconnecting-constantly/28355/4 "2019-09-26T15:19:50Z")

</div>

What loading is showing on the diagnostics page for that device?

---

<div class="post-metadata">

**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 26, 2019, 3:20pm UTC](https://forum.inductiveautomation.com/t/modbus-opc-tag-disconnecting-constantly/28355/5 "2019-09-26T15:20:22Z")

</div>

There’s a setting on the Modbus driver called “Reconnect After Consecutive Timeouts”. Try disabling this.

---

<div class="post-metadata">

**Author:** ![jlam](https://avatars.discourse-cdn.com/v4/letter/j/839c29/32.png) [@jlam](https://forum.inductiveautomation.com/u/jlam)\
**Post date:** [September 26, 2019, 3:41pm UTC](https://forum.inductiveautomation.com/t/modbus-opc-tag-disconnecting-constantly/28355/6 "2019-09-26T15:41:26Z")

</div>

Sorry, I wasn’t sure if you meant the Execution or Threads page, so I’ve taken some screenshots of both, related to this device

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/a/a7b337f558e88e821e3dc1a13316ec4a27926bdc.png)

---

<div class="post-metadata">

**Author:** ![jlam](https://avatars.discourse-cdn.com/v4/letter/j/839c29/32.png) [@jlam](https://forum.inductiveautomation.com/u/jlam)\
**Post date:** [September 26, 2019, 3:50pm UTC](https://forum.inductiveautomation.com/t/modbus-opc-tag-disconnecting-constantly/28355/7 "2019-09-26T15:50:17Z")

</div>

Now my device is connected, but the data does not come through once it has a timeout

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/1/1a3264acef0beb61128b80a394cb4150018c9b21.png)

Perhaps an unrelated question, but what is the differenc between the Common Rate and Custom OPCrate matter? Should they be the same? I’ve tried setting them \<10s to avoid device inactivity
