# DNP3 tag quality bad **URL:** \ **Category:** Ignition\ **Tags:** ignition80\ **Created:** [September 9, 2020, 3:14pm UTC](https://forum.inductiveautomation.com/t/dnp3-tag-quality-bad/38523 "2020-09-09T15:14:47Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![rbalderrama](https://avatars.discourse-cdn.com/v4/letter/r/f14d63/32.png) [@rbalderrama](https://forum.inductiveautomation.com/u/rbalderrama)\ **Post date:** [September 9, 2020, 3:14pm UTC](https://forum.inductiveautomation.com/t/dnp3-tag-quality-bad/38523/1 "2020-09-09T15:14:47Z")
I have setup DNP3 to get data from a AB Micrologix 1400 PLC: 1. Binary tags works good except for time stamp showing incorrect on alarm journal. I have seen a post about this issue been solved on a previous release but not sure how. 2. Analog input tags show values but have BAD quality. I have changed configuration parameters on the DNP3 driver but still having problems. Any help will be appreciated. ---
**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:** [September 9, 2020, 3:22pm UTC](https://forum.inductiveautomation.com/t/dnp3-tag-quality-bad/38523/2 "2020-09-09T15:22:07Z")
Can you set the log level for logger “drivers.dnp3.Requests.Read.StaticData” to DEBUG and/or get a Wireshark capture? ---
**Author:** ![rbalderrama](https://avatars.discourse-cdn.com/v4/letter/r/f14d63/32.png) [@rbalderrama](https://forum.inductiveautomation.com/u/rbalderrama)\ **Post date:** [September 9, 2020, 3:31pm UTC](https://forum.inductiveautomation.com/t/dnp3-tag-quality-bad/38523/3 "2020-09-09T15:31:36Z")
Hi, I have found that decreasing the Integrity Poll Interval to 3600 alleviates the problem with the quality tag. The time stamp is still a problem. I know it has to do with the UTC time parameter but cant figured out how to compensate for it. Will try to do wire-shark captures. Thanks