# 7.6.6 -- resetting Allen Bradley Driver fixes problem

**URL:** <https://forum.inductiveautomation.com/t/7-6-6-resetting-allen-bradley-driver-fixes-problem/10897>\
**Category:** General Discussion\
**Created:** [December 9, 2015, 9:59pm UTC](https://forum.inductiveautomation.com/t/7-6-6-resetting-allen-bradley-driver-fixes-problem/10897 "2015-12-09T21:59:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eric\_G](https://avatars.discourse-cdn.com/v4/letter/e/258eb7/32.png) [@Eric\_G](https://forum.inductiveautomation.com/u/Eric_G)\
**Post date:** [December 9, 2015, 9:59pm UTC](https://forum.inductiveautomation.com/t/7-6-6-resetting-allen-bradley-driver-fixes-problem/10897/1 "2015-12-09T21:59:34Z")

</div>

Ignition 7.6.6 (b2014040112) | 64-bit  
Allen-Bradley Drivers 1.6.6 (b2014040112)  
Windows Server 2008 R2 SP1

We had a PLC ( ControlLogix 1756-L61/B ) worked on and when the programmer put the PLC back into remote run the gateway still saw the device in program mode.

We switched the PLC from REM to RUN and still the gateway refused. We restarted the fiber connection and nothing.

Clicking restart on the Allen Bradley Driver module from the gateway configuration pages is what fixed it, even though the other AB PLCs (a mix of Control, Compact, and Micro Logix) were all shown correctly in Remote Run.

Any ideas? I don’t like the idea of restarting the AB module being a fix since now this makes me the first guy to call when a problem occurs.

---

<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:** [December 9, 2015, 10:05pm UTC](https://forum.inductiveautomation.com/t/7-6-6-resetting-allen-bradley-driver-fixes-problem/10897/2 "2015-12-09T22:05:16Z")

</div>

I suspect in 7.6.6 the mode was read upon connecting and never again, which is why restarting the module caused it to later read correctly…

You also probably could have just edit/saved that one device, forcing it to reconnect.

---

<div class="post-metadata">

**Author:** ![Eric\_G](https://avatars.discourse-cdn.com/v4/letter/e/258eb7/32.png) [@Eric\_G](https://forum.inductiveautomation.com/u/Eric_G)\
**Post date:** [December 9, 2015, 10:30pm UTC](https://forum.inductiveautomation.com/t/7-6-6-resetting-allen-bradley-driver-fixes-problem/10897/3 "2015-12-09T22:30:56Z")

</div>

Okay, that’s good info, thank you.

---

<div class="post-metadata">

**Author:** ![Eric\_G](https://avatars.discourse-cdn.com/v4/letter/e/258eb7/32.png) [@Eric\_G](https://forum.inductiveautomation.com/u/Eric_G)\
**Post date:** [December 9, 2015, 10:35pm UTC](https://forum.inductiveautomation.com/t/7-6-6-resetting-allen-bradley-driver-fixes-problem/10897/4 "2015-12-09T22:35:28Z")

</div>

Another question, is there a way to do this from scripting? So I can put a button out there on our PLC pages.