Before I go too deep investigating this, are there any known issues with storing of DNP3 events into Ignition history with the correct timestamps/timezones?
We have some SEL protection relays talking DNP3 to Ignition using the new DNP3 driver, receiving buffered events via unsolicited messaging. The SEL devices seem to have the correct datetimes set inside the devices, but the timestamps being stored in Ignition history are out by -10 hours which corresponds to the timezone of the gateway which is GMT+1000. What it seems like is that the timestamps are coming in as UTC (GMT+0000) to Ignition which is being assumed as local time GMT+1000 and stored as such.
It seems like a bug to me (I'll reach out to support as well)
Check the clock and time zone of the outstation. Look at Wireshark. DNP3 timestamps are transmitted in UTC so pretty much the only reason they will seem wrong to you is if the outstation isn’t configured the way you expect.
2 Likes
This was captured on Sept 30th at 10:42 GMT+1000, so to me it seems like the SEL device isn't timezone aware. Their times are being set by an external time source, but to me it appears as though they're using this local datetime and their DNP3 code is assuming it's in UTC which is what is being sent through DNP3.
https://selinc.com/api/download/107040/
SEL recommend setting their devices to UTC.
Thanks Kevin, the issue does look like it's in the DNP3 outstations. Now to get all 15 changed over to UTC time 
2 Likes
