# Allen Bradley timeout

**URL:** <https://forum.inductiveautomation.com/t/allen-bradley-timeout/81383>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [November 2, 2023, 1:43pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-timeout/81383 "2023-11-02T13:43:00Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alfredo\_Egmo](https://avatars.discourse-cdn.com/v4/letter/a/ccd318/32.png) [@Alfredo\_Egmo](https://forum.inductiveautomation.com/u/Alfredo_Egmo)\
**Post date:** [November 2, 2023, 1:43pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-timeout/81383/1 "2023-11-02T13:43:00Z")

</div>

I have a DH+ network with AllenBradley , I am using an AllenBradley gateway to read the DH+ plcs throught ethernet, but I have many timeout errors in IGNITION from those PLCs, any idea?  
thanks

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/1/615d616158848cdc1e49b992b2776a808b09626d.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:** [November 2, 2023, 1:50pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-timeout/81383/2 "2023-11-02T13:50:10Z")

</div>

How many tags are involved? Have you looked at the device's diagnostics page?

{ Timeouts often mean "badly overloaded comms", which is really easy to do with old, very slow protocols, like DH+.)

---

<div class="post-metadata">

**Author:** ![Alfredo\_Egmo](https://avatars.discourse-cdn.com/v4/letter/a/ccd318/32.png) [@Alfredo\_Egmo](https://forum.inductiveautomation.com/u/Alfredo_Egmo)\
**Post date:** [November 2, 2023, 1:55pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-timeout/81383/3 "2023-11-02T13:55:09Z")

</div>

Around 500 tags  
is there a way to fix this "Overloaded comms"?

---

<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:** [November 2, 2023, 2:07pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-timeout/81383/4 "2023-11-02T14:07:53Z")

</div>

See this comment about throttled SLC 5/05 traffic, the 5/04 has similar throttles:

> [@Typical Performance between Ignition and AB SLC 5/05](https://forum.inductiveautomation.com/t/typical-performance-between-ignition-and-ab-slc-5-05/17262/3):
>
> Check “Comms Servicing Selection” and “MSG Servicing Selection” for channel 1 (S:2/15 & S:33/7). If either is set, it will crush your throughput, as only one request will be processed per scan (Comms) or per certain control flow instructions (MSG).

If those aren't your problem, then you should check if you are running your DH+ at 230k. If not, you can get a 4x improvement by converting (all devices on the channel must be capable of this, and be configured together).

Other than that, no. You'll just have to go slower. (Tag group rate.) You can only fit so much [expletive] in a one-pound bag. (The normal euphemism is ten pounds in a five-pound bag, but DH+ is a much smaller "bag".)

---

<div class="post-metadata">

**Author:** ![Alfredo\_Egmo](https://avatars.discourse-cdn.com/v4/letter/a/ccd318/32.png) [@Alfredo\_Egmo](https://forum.inductiveautomation.com/u/Alfredo_Egmo)\
**Post date:** [November 2, 2023, 2:12pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-timeout/81383/5 "2023-11-02T14:12:49Z")

</div>

thanks

---

<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:** [November 2, 2023, 2:15pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-timeout/81383/6 "2023-11-02T14:15:04Z")

</div>

I just noticed that your OP indicates **plural**"PLCs". If there are multiple PLCs on a single DH+ channel, a couple other factors to consider:

- The bandwidth is shared. So the number of tags that matter is the number across **all** of the PLCs on a channel.

- Throttling in any of the PLCs will cause a response to be delayed, delaying **all** of the PLCs.

- Any PLC that is powered down will not respond for its turn, timing out and affecting all other PLCs on the channel. It is imperative that the Ignition device be disabled when its PLC is unresponsive.

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [November 2, 2023, 2:17pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-timeout/81383/7 "2023-11-02T14:17:19Z")

</div>

> [@pturmel](#):
>
> You can only fit so much [expletive] in a one-pound bag. (The normal euphemism is ten pounds in a five-pound bag, but DH+ is a much smaller "bag".)

My new quote for the week.
