# Micrologix 1400 Strange Behavior

**URL:** <https://forum.inductiveautomation.com/t/micrologix-1400-strange-behavior/9837>\
**Category:** Archived Topics\
**Created:** [March 24, 2015, 2:17pm UTC](https://forum.inductiveautomation.com/t/micrologix-1400-strange-behavior/9837 "2015-03-24T14:17:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cgardella](https://avatars.discourse-cdn.com/v4/letter/c/f08c70/32.png) [@cgardella](https://forum.inductiveautomation.com/u/cgardella)\
**Post date:** [March 24, 2015, 2:17pm UTC](https://forum.inductiveautomation.com/t/micrologix-1400-strange-behavior/9837/1 "2015-03-24T14:17:37Z")

</div>

I have a Micro 1400 connected to Ignition 7.6.6. I developed my code in the office without experiencing this strange problem.

I have communication timers setup to monitor the connection quality of 6 remote PLC’s. I have a numeric control writing directly to the \_PRE of the timer and a numeric display reading directly from the \_ACC. Both connections to the tags are bi-directional.

When I was on the customer site yesterday installing the new SCADA system, I noticed the \_ACC value was appearing in my \_PRE tag in Ignition. I opened my developer, browsed to an unused timer in my OPC tree, dropped the \_PRE and \_ACC in my project tag tree. I then wrote a value in the unused timer \_ACC in my PLC and it appeared in the \_PRE value in Ignition.

I then found other odd things happening to BOOL tags. I would press a Reset button and I would see another tag for a disable command trigger.

I called Tech support and they suggested using 7.6.7 since there seems to be a fix to Micrologix issues.

Has anyone else experienced these issues in versions later then 7.6.7?

Thanks

Chris