I’ve been having issues with the DNP3 device connecting to MicroLogix 1400 when the network connection between the two is broken. When the connection is resumed the device will show connected but the tag will show a bad quality until the device is disabled/enabled or just saved. This is periodically…

[image] declan1: I’ve been having issues with the DNP3 device connecting to MicroLogix 1400 when the network connection between the two is broken. When the connection is resumed the device will show connected but the tag will show a bad quality until the device is disabled/enabled or just saved.…

I am having the same problem. The device is connected, but the tag shows bad quality. I'm using Ignition Edge 7.9.20. What should be the workaround for this? Thanks in advance!

I too have been having the same issue with Edge 8.0.6 and 8.0.17. I haven't found any way to recover from this state other than to edit/save the device, bounce the DNP driver, or bounce OPC-UA. Since we only work with DNP/3 outstations, this is a debilitating bug that greatly reduces the value of …

Have you tried v8.1? (I recall some DNP3 improvements in the relatively recent past.) V8.0 is end-of-life, and therefore will receive no more fixes.

Thanks for the note. I'm planning on giving 8.1 a try.

Hi. It seems that the bug is still in version 4.1.27 of the DNP3.0 driver. I'm using Ignition 8.1.27. [dnp30 error] The error is critical for us as we are in the process of finishing a big SCADA project for PV monitoring using DNP3.0 protocol. Does the Ignition DNP3.0 driver only support applic…

Exact same issue here. This is quite debilitating. After the fragment timer, warning, we get an exception and failed write errors, and then all tags from that device are of bad quality until a dnp3 driver restart. [image] We're on 7.9.17 but it sounds like this issue persists in 8.1? Hesitant abo…

It's tough to diagnose this without Wireshark captures. I don't know if anybody ever tried to run this issue through support and where that went. It's never made it's way to me, whatever the case. At this point it probably won't make much difference. There's a new DNP3 driver that is already done w…

Exciting to hear there will be a new DNP3 driver! It's our go-to for SEL RTAC to Ignition, at least until SEL/Codesys updates their OPC-UA metadata implementation or we decide to take the 61850 plunge. Any chance the new driver will allow bit-level DNP3 addressing similar to the Modbus implementati…

Bit level addressing isn’t planned, but I’d imagine the other issues are fixed. The new driver uses class-based polling by default, which is a significantly different (and more correct) approach than the current driver, which does explicit polled reads like a traditional PLC driver unless you’ve op…

Issues with DNP3 Driver reconnection

Ignition

Kevin.Herron October 27, 2023, 3:36am 16