I'm struggling to find a way to clean historical data being shown in a table component.
I'm using a UDT to store a log of data at specific time. The whole UDT changes values at the same time (in PLC) but Ignition seems to log many different entries in the historian for every element of the UDT, so when queried, the dataset obtained has a lot of duplicate data.
I'm not sure if this is an issue on how I have the history set up for each element in the UDT, or if I'm querying the data wrong.
EDIT: Using Ignition 8.1; data comes from ControlLogix EtherNet/IP.
You should not use the historian for such storage. Use a triggered transaction group, and set it to "OPC Read" mode, so that everything other than the trigger is forced to read after the trigger.
(If you don't want to buy the SQL Bridge module, the equivalent can be scripted in a gateway timer event or gateway tag change event, using system.opc.readValues() to grab all the data.)
Sorry, I'm not very familiar with Ignition yet. So it would be a manual read of the UDT values upon a trigger event and that would log into the historian? or do I still have to also manually push an entry to the historian?
I see now what you mean, I don't have SQL Bridge. So I'll have to use a script on a tag change event.
Do I need to set the history properties of the UDT elements differently?
You don't push the values to the historian. You insert a row into a custom DB table.