Ability to ignore certain input values for totalizers

[mstjohn]

Hi Guys,

While you’re totalizing, check out this post, especially the warning in the middle re: QNANs because those will mess up your total, too!

Analog Totalizing 101: calculating watt-hours example

Measuring values over time - let the “brain” do the math! In [U]this OptoForum post[/U] we looked at digital totalizing, where we let the brain do the math to measure the On Time of a pump. But recently I got a “programming” question from a PAC/groov user measuring watts from a small solar system, who wanted to know wh (watt-hours). In particular, he wanted to know how much power his solar panels generated in a day. In the picture below, notice the yellow line; and also the totalized value on…

There’s also this discussion, which includes some sample code that might be helpful:

How to Create a Custom Totalizer

Hi Ben, I’m not sure where you’re getting that 0.5 second error assumption. But then, I wouldn’t use a timer for this either. Here’s how I would do it (just one option, hoping others will share their ideas): (OptoScript): while (1 == 1) // loop forever // Get Day & Seconds nSecondsSinceMidnight = GetSecondsSinceMidnight(); nDay = GetDay(); // See if the day changed since last we looked if (nDay <> nLastDay) then // Clear total fTotalMeasuredSoFarToday = 0; endif // …

Happy coding!

-Mary