# Control Logix Bridge to SLC connection issues

**URL:** <https://forum.inductiveautomation.com/t/control-logix-bridge-to-slc-connection-issues/7808>\
**Category:** Ignition\
**Created:** [January 9, 2014, 10:49am UTC](https://forum.inductiveautomation.com/t/control-logix-bridge-to-slc-connection-issues/7808 "2014-01-09T10:49:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![njsd](https://avatars.discourse-cdn.com/v4/letter/n/54ee81/32.png) [@njsd](https://forum.inductiveautomation.com/u/njsd)\
**Post date:** [January 9, 2014, 10:49am UTC](https://forum.inductiveautomation.com/t/control-logix-bridge-to-slc-connection-issues/7808/1 "2014-01-09T10:49:41Z")

</div>

Hi,

Running Ignition 7.6, routing through a control logix chassis:

Ethernet-\>ENBT: IP=10.1.178.11-\>Slot6: DH/RIO Card-\>SLC 5/04 at node 21

I have an OPC-UA Device (Allen Bradley SLC) pointed to 10.1.178.11 with communication path:

```auto
1,6,2,21
```

I have added ~15 tags that reference both int values and I/O bools in the SLC.

The int tags work just fine, but the boolean tags that point to the input bits fault out in a blinking manner. Half the time the tags work, and are the appropriate value for the physical I/O, but half the time they are bad quality. The blink cycle also seems to be tied to the scan rate: If I increase the scan rate slow time, they blink slower.

When I first set up this device driver, I didn’t see this problem. But then I deleted the driver, and had to re-enter it. Now the tags constantly blink.

---

<div class="post-metadata">

**Author:** ![witman](https://avatars.discourse-cdn.com/v4/letter/w/d2c977/32.png) [@witman](https://forum.inductiveautomation.com/u/witman)\
**Post date:** [January 9, 2014, 7:48pm UTC](https://forum.inductiveautomation.com/t/control-logix-bridge-to-slc-connection-issues/7808/2 "2014-01-09T19:48:14Z")

</div>

Increasing timeout in device settings on gateway doesn’t help anything does it? This is the only thing I can imagine might have changed from your old device settings to the recreated ones, though it seems unlikely it would affect only the bits if this was the issue.

---

<div class="post-metadata">

**Author:** ![Dravik](https://avatars.discourse-cdn.com/v4/letter/d/e274bd/32.png) [@Dravik](https://forum.inductiveautomation.com/u/Dravik)\
**Post date:** [January 10, 2014, 2:33pm UTC](https://forum.inductiveautomation.com/t/control-logix-bridge-to-slc-connection-issues/7808/3 "2014-01-10T14:33:32Z")

</div>

I’ve run into this before w/ SLC(and Micros)

Per [http://inductiveautomation.com/forum/viewtopic.php?f=72&t=9212&p=31526&hilit=slc+input#p31526](http://inductiveautomation.com/forum/viewtopic.php?f=72&t=9212&p=31526&hilit=slc+input#p31526) you may want to remap the input bits to Bs instead.

---

<div class="post-metadata">

**Author:** ![witman](https://avatars.discourse-cdn.com/v4/letter/w/d2c977/32.png) [@witman](https://forum.inductiveautomation.com/u/witman)\
**Post date:** [January 10, 2014, 3:59pm UTC](https://forum.inductiveautomation.com/t/control-logix-bridge-to-slc-connection-issues/7808/4 "2014-01-10T15:59:18Z")

</div>

Good to know about I/O points. I’ve worked with a similar setup as far as connection goes (SLC 5/04s via ControlLogix bridge), but we always map I/O points to N or B files which may be why we haven’t seen this behaviour.

---

<div class="post-metadata">

**Author:** ![njsd](https://avatars.discourse-cdn.com/v4/letter/n/54ee81/32.png) [@njsd](https://forum.inductiveautomation.com/u/njsd)\
**Post date:** [January 10, 2014, 4:22pm UTC](https://forum.inductiveautomation.com/t/control-logix-bridge-to-slc-connection-issues/7808/5 "2014-01-10T16:22:57Z")

</div>

Thank you Dravik, I read the post, and I will take that advice.