# Micrologix 1400 Tag Bad Quality \[Solved\]

**URL:** <https://forum.inductiveautomation.com/t/micrologix-1400-tag-bad-quality-solved/21479>\
**Category:** Ignition\
**Created:** [December 18, 2018, 5:28pm UTC](https://forum.inductiveautomation.com/t/micrologix-1400-tag-bad-quality-solved/21479 "2018-12-18T17:28:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jgooding](https://avatars.discourse-cdn.com/v4/letter/j/a88e4f/32.png) [@jgooding](https://forum.inductiveautomation.com/u/jgooding)\
**Post date:** [December 18, 2018, 5:28pm UTC](https://forum.inductiveautomation.com/t/micrologix-1400-tag-bad-quality-solved/21479/1 "2018-12-18T17:28:13Z")

</div>

I attempted to establish a connection to MicroLogix 1400. I can browse the tags in the PLC usign the designer and Quick Client. But I only get bad data from the PLC. The PLC is password protected. I can see the PLC from my machine and see values using RSLinx. One intersting thing is the connection to this PLC states: ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/3/3734cd5cc31f5080b72fb8211d618109eb5e21f8.png) versus Conneced Protocol :EIP for all my other 1400’s.

Ignition Version: 7.9.10 (b2018112821)  
Allen-Bradley Driver : 4.9.10 (b2018112813)  
OPC-UA : 4.9.10 (b2018112813)

When I use the Quick Client for a tag here is what I get:

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/d/d689b0568b8b790a48c764a11f2aafe3bcc38ecd.png)

Screen Shot of the Log File:

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/6/6d7249ccc904609fb863164471fcf3d4581e0a26.png)

---

<div class="post-metadata">

**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\
**Post date:** [December 19, 2018, 3:48pm UTC](https://forum.inductiveautomation.com/t/micrologix-1400-tag-bad-quality-solved/21479/2 "2018-12-19T15:48:25Z")

</div>

Try setting the connection path on the device

> [@PCCC protocol causing problems](http://forum.inductiveautomation.com/t/pccc-protocol-causing-problems/11651/15):
>
> Ah! I was thinking the driver was falling back to the direct protocol. You won’t be able to block PCCC access via Ethernet/IP without also blocking straight E/IP. Hmmm. Sounds like we need a new advanced setting in the driver. Maybe posting in [ideas.inductiveautomation.com](http://ideas.inductiveautomation.com) would help – I’d upvote it.