The beta module for the new DNP3 driver is available here.
It requires Ignition 8.1.33. It installs along side the existing DNP3 driver - it does not replace it, and it will not replace it in the future.
If you're familiar with DNP3 already there shouldn't be much of a learning curve here. The basic configuration settings look the same. The primary difference between this driver and the old driver is that it acquires data using class-based polling by default, as opposed to explicit READ function calls. This means you should be either dragging tags in from the "Points" folder, or manually addressing them using their generic point+index NodeIds, e.g. AnalogInput1.
The "gvi" syntax is also supported, e.g. g30v2i0, but any tag addressed in this manner will be read explicitly using the DNP3 READ function call.
The polling rate can be configured on a per-class basis. Unsolicited messaging is still supported, and can be enable on a per-class basis instead of all-or-nothing like the old driver.
Sequence of events can be maintained using either class-based polling or unsolicited messaging. Like the old driver, it requires some configuration in the Tag Groups as well. Make sure that under the OPC UA extended properties for the group:
Queue Size is set to some appropriate size (i.e. 100 and not 1)
Sampling Interval is set to 0 (in OPC UA this means the server can report by exception for an item rather than adhere to the sampling rules)
It's usually best to make a dedicated tag group for your DNP3 SoE tags.
Other things of note:
the scripting functions for this driver are located under system.dnp, not system.dnp3.
there is a new scripting function to issue a "Demand Poll"
the parameters used when operating an analog or binary output in response to a tag write are now configurable
whatever link layer confirmations the outstation decides to use should be supported
Kevin, I am still having issues pulling the events back with the new DNP3 driver. Is there any additional configuration I need to adjust in the tag group besides the "Queue Size" and "Sampling Interval"?
I am getting the live value when ignition polls the class but I am not getting the events that are stored between the polls. These events are building up on the RTU and will eventually cause the RTU to run out of memory. Let me know what additional information you will need.
Here is a screen shot of the "Floating Points Events" building up in the SCADAPack 470:
@ggross I am testing it on SCADAPack 470 if that helps. I will do some testing with Kepware to see if I am having the same issue, then I can rule if it's a outstation issue or not.
