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.
Suggestion - Don
-
Hi
When Mango is set to 'log point changes only' it becomes problematic when a value goes to zero, stays there, and then changes again:
In this example, the value changed to 0 at time A, then remained at 0 until a new value was recorded at time B.
This gives quite an ugly and perhaps misleading chart rendering. The only other option is to set Mango to 'log all data', but this - i assume - consumes DB space.It would be nice if there were some workaround in Mango for this. Something like 'discard intermediate values and record first and last values for repeating values'.
Or maybe there's a workaround that someone can suggest?
-
I had this too. I gave up on trying to fix this. I just set it to "interval" 1 min. For some reason I don't get zeros any more.
-
Am i understanded right? int fact,between time A and time B,have many points which values is 0,but they don't be store because they don't change. this is the logging rule,but we have one solution at query pointvalues from database,we can set up one interval option at query.
for example,between tim A and time B,assume have 60 seconds ,if the query interval is 2 second,we will get 30 pointvalues,we will copy the time A 'value 0 to 30times, until to time B, then we can restore really situation.
-
This is an interesting problem but it's probably more of an issue with how the Chart interprets the data something we can definitely look at. Thanks.
