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.
Alarm Annoyances
-
is there any way to clear the flashing information flag alarm?
-
Depends on the alarm. You can acknowledge it if it doesn't return to normal on its own. You can fix the problem that is keeping it from returning to normal. Or, you often can change the event's alarm level so that it's not an alarm.
-
there is no option to acknowledge, it's just letting me know I logged in.
-
User login alarms return to normal when you log out. If you are using the commercial version you can set the alarm level of user logins to "none". The open version doesn't have that feature.
-
ok, I'm now running the commercial version, and I changed the user login alarm level to none :)
one of my points (humidity probe) exceeded a threshold I defined on last Friday. It is no longer at that point however it still shows up in the active alarms section without an acknowledge check box. Also, the graphical display shows an exclamation point icon next to the data point. How do I clear this alarm?
-
There's probably a problem with the data source. Is there a message when you hover over the exclamation? Also, in the alarms list is there anything that suggests a data source or point problem?
-
No message on hover
Here's a screen capture of my alarm page.
http://joshua.t.sullivan.googlepages.com/mango_actAlarm_001.bmpAnd here's one of the data source:
http://joshua.t.sullivan.googlepages.com/mango_dataSource_001.bmp -
Can you send a screen shot of the point details page? Preferably showing the history of events and values since the time the point went into alarm.
-
I meant to post a reply earlier but I forgot. I rebooted the server and it went away. It must have been some kind of persistent little fluke because I had tried that already.
