# AB compactlogix Device Connection= Alternate connecting/Idle

**URL:** <https://forum.inductiveautomation.com/t/ab-compactlogix-device-connection-alternate-connecting-idle/12398>\
**Category:** General Discussion\
**Created:** [November 23, 2016, 7:26pm UTC](https://forum.inductiveautomation.com/t/ab-compactlogix-device-connection-alternate-connecting-idle/12398 "2016-11-23T19:26:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![fivecents](https://avatars.discourse-cdn.com/v4/letter/f/d9b06d/32.png) [@fivecents](https://forum.inductiveautomation.com/u/fivecents)\
**Post date:** [November 23, 2016, 7:26pm UTC](https://forum.inductiveautomation.com/t/ab-compactlogix-device-connection-alternate-connecting-idle/12398/1 "2016-11-23T19:26:01Z")

</div>

1769-L30ER/5530ER rev20.14 when added as device in gateway status alternates between connecting and Idle.  
Device shows up in ignition OPC-UA server but no tags?

---

<div class="post-metadata">

**Author:** ![accyroy](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/accyroy/32/3386_2.png) [@accyroy](https://forum.inductiveautomation.com/u/accyroy)\
**Post date:** [November 23, 2016, 7:47pm UTC](https://forum.inductiveautomation.com/t/ab-compactlogix-device-connection-alternate-connecting-idle/12398/2 "2016-11-23T19:47:40Z")

</div>

Are you using the Legacy Allen Bradley driver for versions 20 and prior? It is a different selection when you create the device.

---

<div class="post-metadata">

**Author:** ![fivecents](https://avatars.discourse-cdn.com/v4/letter/f/d9b06d/32.png) [@fivecents](https://forum.inductiveautomation.com/u/fivecents)\
**Post date:** [November 23, 2016, 7:50pm UTC](https://forum.inductiveautomation.com/t/ab-compactlogix-device-connection-alternate-connecting-idle/12398/3 "2016-11-23T19:50:34Z")

</div>

Yes I tried the legacy driver and logix driver.

I am also having the same issue with a 1769-L30ER/5370 Rev28.011

---

<div class="post-metadata">

**Author:** ![fivecents](https://avatars.discourse-cdn.com/v4/letter/f/d9b06d/32.png) [@fivecents](https://forum.inductiveautomation.com/u/fivecents)\
**Post date:** [November 23, 2016, 7:54pm UTC](https://forum.inductiveautomation.com/t/ab-compactlogix-device-connection-alternate-connecting-idle/12398/4 "2016-11-23T19:54:38Z")

</div>

There are 2 NAT devices in use. I am able to upload and download AB PLC and AB HMI program across both NAT’s.

---

<div class="post-metadata">

**Author:** ![fivecents](https://avatars.discourse-cdn.com/v4/letter/f/d9b06d/32.png) [@fivecents](https://forum.inductiveautomation.com/u/fivecents)\
**Post date:** [December 9, 2016, 9:11pm UTC](https://forum.inductiveautomation.com/t/ab-compactlogix-device-connection-alternate-connecting-idle/12398/5 "2016-12-09T21:11:46Z")

</div>

Public IP scheme on 1st NAT (192.168.1.#) similar to private IP scheme on 2nd NAT(192.168.1.#).  
Per conversation with NAT maker this isn’t a valid thing for me to do.

Resolution would require 1st NAT public IP modification or 2nd NAT private IP modification.