• 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

    Haystack Point Status

    User help
    haystack niagara nhaystack reliability status
    2
    2
    1.3k
    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.
    • D
      ddiezperez
      last edited by

      When doing a Haystack Point Import from a Niagara 4 server (using the nHaystack RESTful API servlet) Mango can see both the curStatus value and the axStatus. However when mapping the columns to create Mango points, we can only map to Mango point properties: HaystackID, DeviceName, PointName, PointXID, Settable and Unit.

      Is it possible to see the curStatus and axStatus properties for the Haystack points once they are added to Mango as Data Points?

      If at all helpful, I listed the possible values I see for the two properties we care the most about.

      The possible curStatus values are:

      • disabled
      • down
      • fault
      • ok

      The possible axStatus value are:

      • disabled
      • down,stale
      • fault
      • fault,overriden
      • ok
      • overriden
      • unackedAlarm
      • Alarm

      Thanks,
      David

      1 Reply Last reply Reply Quote 0
      • Jared WiltshireJ
        Jared Wiltshire
        last edited by

        The data source only supports reading the curValue into a data point. It does check if curStatus is ok, if it is not OK the data point is marked as being "unreliable". You should see the unreliable status as a little red warning icon next to any point value displays in the UI. The unreliable status is not trended however.

        Developer at Radix IoT

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