Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to

Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website

  • Hi Mango developers!

    I need to report minute averages for two data points. The first point "A" is acquired directly from a modbus device and the second "B" is the value of "A" * 46.006 / 24.5.
    So I've configured the modbus data point (A) to poll every second and to logg averages every minute. For "B" I've created a meta data point with "A" as context updater:

    return p20.value * 46.006 / 24.5;

    B is also logging average on a 1 minute interval.

    Well, this works fine, except that A and B minute averages values won't match. If I manually calculate the B minutes averages using A averages they are slightly different.
    This is because both averages were calculated in different times, e.g.:

    Averages for A values are calculated and logged over the PAST 60 seconds values at the 30th second every minute, while B averages are calculated at the 17th second. This result in values being shifted by 13 seconds, so the logged values can't be correlated using the formula.

    This 30 and 17 seconds are not random. They are related to the time I enabled the data point or data source. So Mango will logg the first value 60 seconds after the data point got enabled. This is fine but, in that case, average calculation should be done using the PREV method instead the PAST method, so averages are calculated over the data between the start and end of a particular period (quantized).

    A workaround for this may be enabling both data point at the same second of any minute, this result in much comparable values, but it will last just until the next system or data source / point restart.

    I think it would be nice to quantize, not only the polling time, but also the logging period.

  • Hi Alvaro,

    Thanks for the detailed explanation. This is something we will definitely take a look at.


  • Thanks Joel. I'll watch any news regarding this.

  • I second the need for synchronized logging data points.

  • A second workaround is to set the your poll every minute with quantize,and logtype on change,then the B,and a,B averages will log at the same time