# Why are there no Device Diagnostic Tags for devices implemented with the DNP3 Driver? **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [November 24, 2022, 12:24am UTC](https://forum.inductiveautomation.com/t/why-are-there-no-device-diagnostic-tags-for-devices-implemented-with-the-dnp3-driver/66875 "2022-11-24T00:24:39Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![tyler.bennett](https://avatars.discourse-cdn.com/v4/letter/t/f04885/32.png) [@tyler.bennett](https://forum.inductiveautomation.com/u/tyler.bennett)\ **Post date:** [November 24, 2022, 12:24am UTC](https://forum.inductiveautomation.com/t/why-are-there-no-device-diagnostic-tags-for-devices-implemented-with-the-dnp3-driver/66875/1 "2022-11-24T00:24:39Z")
Why are there no [Device Diagnostic Tags](https://docs.inductiveautomation.com/display/DOC81/OPC+UA+Drivers) for devices implemented with the DNP3 Driver?... Instead there are some [Internal Indicators](https://docs.inductiveautomation.com/display/DOC81/DNP3#DNP3-InternalIndicators) tags, but none of that provides the basic device connection health details that the [OPC UA Drivers](https://docs.inductiveautomation.com/display/DOC81/OPC+UA+Drivers) section of the manual suggest should be available for _ **all** _ the Ignition drivers. Some device connection health info is available under the [Gateway System Tags](https://docs.inductiveautomation.com/display/DOC81/System+Tags#SystemTags-GatewaySystemTags) **devices** folder (missing hostname or IP address) but I remain curious why that connection detail is not consistently available as [Device Diagnostic Tags](https://docs.inductiveautomation.com/display/DOC81/OPC+UA+Drivers) for all device drivers. Ideally I'd like to have at least the hostname (or IP address) and boolean Connection state (isConnected) for all configured devices available as diagnostic tags under each device in the OPC browser (like what exists for the Modbus TCP driver). Ignition v8.1.22 **Excerpt from the Manual:** ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/b/0b79bd4c445675d838c1f21d2c285dbfa89730f6.png) **Example of tags available from a DNP3 device driver:** ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/a/aa6f2b6f2eb5bca177ac30a800e2fd23b626923a.png) **Example of tags available from a Modbus TCP device driver:** ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/f/8fcce33f04c9528c809b480bc3d91cfffc58ae73.png) ---
**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:** [November 24, 2022, 1:38am UTC](https://forum.inductiveautomation.com/t/why-are-there-no-device-diagnostic-tags-for-devices-implemented-with-the-dnp3-driver/66875/2 "2022-11-24T01:38:49Z")
Hmm, seems like an omission, it should at least have the basic Connected, Hostname, etc… tags. It won’t ever have the “Sampling” tags because it’s not supposed to be polling/sampling-based like more traditional drivers (even if it does act that way in some ways right now…). ---
**Author:** ![tyler.bennett](https://avatars.discourse-cdn.com/v4/letter/t/f04885/32.png) [@tyler.bennett](https://forum.inductiveautomation.com/u/tyler.bennett)\ **Post date:** [November 24, 2022, 6:14am UTC](https://forum.inductiveautomation.com/t/why-are-there-no-device-diagnostic-tags-for-devices-implemented-with-the-dnp3-driver/66875/3 "2022-11-24T06:14:31Z")
Added associated entry to [Ignition Features and Ideas](https://inductiveautomation.canny.io/ignition-features-and-ideas/p/implement-device-diagnostic-tags-for-all-device-drivers) webpage. > **[Implement Device Diagnostic Tags for all device drivers | Voters | Inductive...](https://inductiveautomation.canny.io/ignition-features-and-ideas/p/implement-device-diagnostic-tags-for-all-device-drivers)** ---
**Author:** ![tyler.bennett](https://avatars.discourse-cdn.com/v4/letter/t/f04885/32.png) [@tyler.bennett](https://forum.inductiveautomation.com/u/tyler.bennett)\ **Post date:** [December 8, 2025, 5:47am UTC](https://forum.inductiveautomation.com/t/why-are-there-no-device-diagnostic-tags-for-devices-implemented-with-the-dnp3-driver/66875/4 "2025-12-08T05:47:25Z")
> [@Kevin.Herron](#): > > Hmm, seems like an omission, it should at least have the basic Connected, Hostname, etc… tags. @Kevin.Herron It seems then new DNP3 driver now includes the standard set of diagnostic tags omitted from the Legacy DNP3 driver, but now lacks some of the DNP3 specific diagnostic values (Internal Indicators) that were included in the Legacy DNP3 driver. I am hoping to monitor `Event Buffer Overflow` on my DNP3 connections. How is that achieved with the New DNP3 driver? ---
**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 8, 2025, 12:45pm UTC](https://forum.inductiveautomation.com/t/why-are-there-no-device-diagnostic-tags-for-devices-implemented-with-the-dnp3-driver/66875/5 "2025-12-08T12:45:37Z")
Hmm, I don't think these are accessible in the new driver. Seems like they probably should be, I'll make a ticket.