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.

Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website

Device disconnect and data logging


  • Hi all,
    I'm building a Mango website to monitor some power meter via Ethenet. Below is my data point logging setting.
    0_1586186844940_41f2adfa-0b02-4144-94cd-3c875b94b3bf-image.png

    Today, my server disconnect or the meter disconnect, the server keeps logging last data value (see photo below)

    0_1586187008229_45e98c85-7016-4db9-ab9e-bbb05aac62a9-image.png
    From 3PM to 9PM, the server is disconnected so I expect the value should be 0.

    Is there are any setting so I can make sure the logging value is 0 if server/power meter disconnected, therefore I or anyone can realize the abnormal and check the server/meter?

    Thank you.


  • I believe because your mango instance is logging, it will continue to use the same previous value if a new one hasn't come in. The very same thing happens with virtual datapoints and serial.
    If you change your logging type to all data or on change, you won't get these automatic point value inserts and thus can use an event detector to fire once the data hasn't been updated after a given period of time.

    Fox


  • @tungthanh500 said in Device disconnect and data logging:

    From 3PM to 9PM, the server is disconnected so I expect the value should be 0.
    Is there are any setting so I can make sure the logging value is 0 if server/power meter disconnected, therefore I or anyone can realize the abnormal and check the server/meter?

    Setting a point that is unhealthy to zero. would have a lot of unwanted consequences and create a lot of noise in your data when doing analytics on it... The point does indicate that it is unhealthy, just not on the chart. The live value will have an exclamation mark next to it.

    Also even if you do not log the point when it is unhealthy, your chart will still have the same shape... IF you want to be get notified when the point goes unhealthy you can set a "has not updated" event detector on the point and link the detector to an email event handler.