# Creating Totalizer for OPC Float Tags on Ignition **URL:** \ **Category:** Ignition\ **Created:** [January 23, 2026, 4:01pm UTC](https://forum.inductiveautomation.com/t/creating-totalizer-for-opc-float-tags-on-ignition/113515 "2026-01-23T16:01:33Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![ian.begg](https://avatars.discourse-cdn.com/v4/letter/i/71e660/32.png) [@ian.begg](https://forum.inductiveautomation.com/u/ian.begg)\ **Post date:** [January 23, 2026, 4:01pm UTC](https://forum.inductiveautomation.com/t/creating-totalizer-for-opc-float-tags-on-ignition/113515/1 "2026-01-23T16:01:33Z")
Hello, I am wanting to make a totalizer for a few OPC float tags on ignition 8.1.40. I was thinking about creating a memory tag and then writing an expression to sum the required tags to this one. Is this an ok way to do this or could it be done more efficiently. The reason is due to needing to trend lots of these tags in the historian which sometimes doesn’t load or takes a substantial amount of time to do so. Thanks! ---
**Author:** ![Nol](https://avatars.discourse-cdn.com/v4/letter/n/8e8cbc/32.png) [@Nol](https://forum.inductiveautomation.com/u/Nol)\ **Post date:** [January 23, 2026, 4:21pm UTC](https://forum.inductiveautomation.com/t/creating-totalizer-for-opc-float-tags-on-ignition/113515/2 "2026-01-23T16:21:53Z")
If it's possible I'd build the totalizer in the PLC instead and then read the accumulated tags across into Ignition. The PLC can have a task set to a fixed scan rate so it more accurately accumulates the total. Otherwise trying to use Ignition's polling rate you're going to have a much greater degree of rounding errors. ---
**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\ **Post date:** [January 23, 2026, 4:23pm UTC](https://forum.inductiveautomation.com/t/creating-totalizer-for-opc-float-tags-on-ignition/113515/3 "2026-01-23T16:23:57Z")
A few of points: > I am wanting to make a totalizer for a few OPC float tags... A totalizer is usually an instrument that measures or displays the **cumulative total** of a variable — such as fluid flow, volume, or mass—over a specific period. Is this really what you want, or do you mean you want to periodically log the **sum** of tag readings? > The reason is due to needing to trend lots of these tags in the historian ... Historian doesn't do trends. The chart components do that. ... which sometimes doesn’t load or takes a substantial amount of time to do so. Show your binding and describe in more detail what the problem is. Also, what is the frequency of logging to the historian? In general, it's better to store the individual counts as they may prove useful in later analysis. ---
**Author:** ![ian.begg](https://avatars.discourse-cdn.com/v4/letter/i/71e660/32.png) [@ian.begg](https://forum.inductiveautomation.com/u/ian.begg)\ **Post date:** [January 23, 2026, 4:34pm UTC](https://forum.inductiveautomation.com/t/creating-totalizer-for-opc-float-tags-on-ignition/113515/4 "2026-01-23T16:34:15Z")
Ok thank you I’ll give that a try. ---
**Author:** ![ian.begg](https://avatars.discourse-cdn.com/v4/letter/i/71e660/32.png) [@ian.begg](https://forum.inductiveautomation.com/u/ian.begg)\ **Post date:** [January 23, 2026, 4:39pm UTC](https://forum.inductiveautomation.com/t/creating-totalizer-for-opc-float-tags-on-ignition/113515/5 "2026-01-23T16:39:30Z")
> [@Transistor](#): > > A totalizer is usually an instrument that measures or displays the **cumulative total** of a variable — such as fluid flow, volume, or mass—over a specific period. Is this really what you want, or do you mean you want to periodically log the **sum** of tag readings? Ah ok I’m very new to the industry so figuring out exactly what I want based on process requirements has been a learning process. A sum of tag readings is what I’m looking for as its a total of multiple flows from different meters. > [@Transistor](#): > > Show your binding and describe in more detail what the problem is. Also, what is the frequency of logging to the historian? The trend is for the sum of total flows over the last month to be generated on the first of each month. ---
**Author:** ![ian.begg](https://avatars.discourse-cdn.com/v4/letter/i/71e660/32.png) [@ian.begg](https://forum.inductiveautomation.com/u/ian.begg)\ **Post date:** [January 23, 2026, 4:42pm UTC](https://forum.inductiveautomation.com/t/creating-totalizer-for-opc-float-tags-on-ignition/113515/6 "2026-01-23T16:42:25Z")
Thank you both, I’m going to sum them in the PLC then just add that tag to the historian so they can trend it as needed. ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [January 24, 2026, 9:35pm UTC](https://forum.inductiveautomation.com/t/creating-totalizer-for-opc-float-tags-on-ignition/113515/7 "2026-01-24T21:35:16Z")
Also to note that you should not use floats for a totaliser. Due to how the datatype stores numbers in binary, once the value gets high enough, adding a small value to it may not actually change the value at all. This means that your totaliser might work till 65,000,000.0 litres then adding 1.0 litre to it does nothing at all, you would have to add maybe 5.0 litres to it in order for it to change value. This is why totalisers are normally based on Integers, as they don't suffer this issue. In summary, the suggestion is that you do the float totalisation on the PLC, then each time the totaliser reaches a whole number, increment a counter that shows the total whole values. If you need the part values, expose those as a float that never goes over the whole value and add the two values in the HMI/Ignition.