Issues with DNP3 Driver reconnection

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 implementation? Right now we have to pull in the register in as a counter and then break it apart into binary expression tags with getBit() which can be a performance drag.

We haven't seen the specific bug mentioned here, but we have encountered two other DNP3 oddities in the past:

  • We route bitpacked registers from RTACs to Ignition as counter objects since we were getting floating point error even when the object type was an int.
  • A colleague was reminding me earlier today about how Ignition's DNP3 polling is all over the map in no discernable order - they are not clean requests to inspect in wireshark like we'd have from most other DNP3 devices.