• Recent
    • Tags
    • Popular
    • Register
    • Login

    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 Mango 5 Documentation Website

    Event detector with duration

    User help
    2
    6
    2.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • W
      wave1234
      last edited by

      I'm having trouble setting up a new event detector. If I set the duration to anything other than 0 seconds, it never detects an event despite being in the proper state. I have tried High limit alarms for a numeric Point and a State alarm for a Binary point. I must be missing something simple. Help?

      1 Reply Last reply Reply Quote 0
      • M
        mlohbihler
        last edited by

        Not sure - it works for me. Can you provide the configuration of the detector, and the point history for comparison? Also, what logging settings are you using?

        Best regards,
        Matthew

        1 Reply Last reply Reply Quote 0
        • W
          wave1234
          last edited by

          Here is an example. I have two event detectors monitoring the same point. Both are low limit detectors with an information alarm level and a limit of 5. One is set with duration 0 seconds. The other with duration 1 second.

          When the following point history passed by:

          [list]Value Time Annotation
          8.2% 13:18:43
          1.2% 13:18:13
          0.5% 13:17:43
          0.6% 13:17:13
          0.9% 13:16:43
          2.5% 13:16:13
          6.7% 13:15:43
          7.0% 13:15:13
          7.1% 13:14:43
          7.0% 13:14:13
          7.1% 13:13:13
          7.0% 13:12:13
          6.8% 13:11:43
          7.0% 13:11:13
          7.1% 13:10:13
          7.0% 13:09:43
          7.1% 13:09:13
          7.0% 13:07:43
          7.1% 13:06:13
          6.9% 13:05:13
          7.1% 13:04:13
          6.9% 13:03:13
          7.1% 13:01:43
          6.8% 13:00:43
          7.1% 12:59:43[/list]

          Only the 0 second event tripped.

          Logging settings are when point value changes by 0.1, no discarding extreme values, and cache size 1.

          Had the same problem with version 1.10 and 1.11.

          1 Reply Last reply Reply Quote 0
          • M
            mlohbihler
            last edited by

            Thanks. We found the problem. A fix will be in the next release.

            Best regards,
            Matthew

            1 Reply Last reply Reply Quote 0
            • W
              wave1234
              last edited by

              Great. I'm looking forward to it.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post