I was trying Ignition for the first time, and the first thing I wanted to know was it it is capable to handle DNP3 properly.
So I'm just polling data from a DNP3 Slave table on an Eaton SMP4 gateway.
There is a discrepancy between my source tag/event and what Ignition OPC is showing, probably that the time stamp is the server time (4 seconds right now). And when I reset the trial mode, it goes straight to the OPC server time, which make no sense. Furthermore, I didn't find a way to display the msec.
The time stamp in DNP3 should be the exact same thing as the source.
Am I missing something or Ignition just poorly handle DNP3?
There's actually a new DNP3 driver being released with 8.1.36, it would be a lot better if you waited to evaluate and ask any follow up questions once that is available and you're using it instead.
"it would be a lot better if you waited to evaluate and ask any follow up questions once that is available and you're using it instead."
I just said I'm brand new to this software, what did trigger this passive-aggressive answer? How should have known that a new driver was about to be released and that "maybe" it could fix my specific issue?
Why didn't you just answer the question? Let start over:
-Do you work for Inductive Automation?
-Do you know if that new driver would fix the issue I'm talking about or not?
-Is that a known issue?
-How many other DNP3 revisions should I wait before you allow me to ask a simple question?
From my understanding, DNP3 driver didn't just appear with version 8.
No, you didn't hurt my feelings. Are you projecting something on my response?
Yes
Probably, but you didn't provide enough detail in your original post to be certain.
The current driver, by default, is implemented using either explicit reads or unsolicited messaging. The new driver uses class-based polling by default instead. This can have some influence on whether source timestamps are available.
I don't know - maybe? I don't know exactly what the problem you described is - that resetting the trial didn't preserve your original timestamp?
I'm just letting you know the new driver fixes a number of outstanding issues with the way the current/old one was implemented.
@Kevin.Herron off topic, but related to the latest DNP3 driver release. Documentation says it does not support secure authentication. Do you know if that is on the roadmap?
It's not, unless DNP3-SA v6 comes along and fixes the outstanding issues with v5 and prior, and the vendor of the DNP3 library we're using implements it.
edit: for posterity, things that are on the roadmap: