# Tag Historian Processing of DNP3 Sequence of Events (SOE)

**URL:** <https://forum.inductiveautomation.com/t/tag-historian-processing-of-dnp3-sequence-of-events-soe/114456>\
**Category:** Ignition\
**Tags:** ignition83\
**Created:** [March 12, 2026, 10:10am UTC](https://forum.inductiveautomation.com/t/tag-historian-processing-of-dnp3-sequence-of-events-soe/114456 "2026-03-12T10:10:45Z")\
**Posts on this page:** 1\
**Showing post:** 24

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [June 30, 2026, 2:55pm UTC](https://forum.inductiveautomation.com/t/tag-historian-processing-of-dnp3-sequence-of-events-soe/114456/24 "2026-06-30T14:55:07Z")

</div>

> [@vitor.dasilva.79](#):
>
> even though we captured the wireshark logs showing the "missing data" getting unloaded off the RTU.

What did Wireshark show was the object type of the dnp points? They need to include a timestamp to make it into the historian

> [@DNP3 Tags not backfilling data between class polls](https://forum.inductiveautomation.com/t/dnp3-tags-not-backfilling-data-between-class-polls/113858/33):
>
> I recently tested DNP3 comms with a simulator ([GitHub - stepfunc/dnp3: Rust implementation of DNP3 (IEEE 1815) with idiomatic bindings for C, .NET, C++, and Java · GitHub](https://github.com/stepfunc/dnp3)) to see what's required for backfilling. One thing that now jumps out at me from this screenshot is the wrong DNP3 data type: g32v5 = 32-bit (IEEE single-precision) floating-point numbers without a time stamp. For any DNP3 backfilling to work, I found the data types defined in the outstation must be set to vars that have tim…

Eg

> [@DNP3 Tags not backfilling data between class polls](https://forum.inductiveautomation.com/t/dnp3-tags-not-backfilling-data-between-class-polls/113858/33):
>
> - AnalogueInput:
> - g32v3 (32bit int + timestamp) or
> - g32v5 (float + timestamp)
> 
> - BinaryInput:
> - g2v3 (value + timestamp)
> 
> - BinaryOutput:
> - g11v2 (value + timestamp)
> 
> - AnalogueOutput:
> - g42v3 (32bit int + timestamp)
> - g42v7 (float + timestamp)

---

_[View the full topic](https://forum.inductiveautomation.com/t/tag-historian-processing-of-dnp3-sequence-of-events-soe/114456)._
