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 support@radixiot.com.
GUI Add-Remove Datapoints
-
Hello,
I've been using the Mango HMI software for a little while now on an energy project. Essentially, I have Mango poll the energy meter every hour, for a value that increments on power consumption. This way I can roll up the datapoints over a 24 hours period and see the accumulated usage on a daily basis. I've set it up, and it works well.
The problem I'm having, is periodically the network will go down for a day or so and Mango will miss updates. When the connection is finally reestablished, the newest datapoint has all the accumulated consumption from the period of time the communication was down. The side effect of this, is that it looks like a huge zig-zag on the line diagram. If the communications are down long enough, it can cause the Y axis on the line diagrams to stretch out of hand.
In my application, it is acceptable to smooth out these anomalies for the purposes of reporting.
So far the only way I've found to "smooth" this line is to log into the old interface (v2), export the datapoints over the relevant period, do the math myself, and manually insert an estimated "fake" reading at the halfway point. This works, but it is time consuming and not something I can delegate to someone less technically inclined.
Is there a simpler way to do this?
-
You could manually download the Data in CSV format, manipulate it and then upload it again.
If you need to have it automated I have a feeling you could write a metadata point script that would determine if data is being lost by looking at the last time data was logged and then average the spiked reading over the time the data was lost.
What are the logging settings you are using on the Data Point?
