• 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

    Send publisher when datasource modbus fail

    How-To
    3
    3
    357
    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.
    • J
      jcaballeroa
      last edited by

      Currently, we have Mango 3 in our projects, and we are testing the new version of Mango 5 for the next one we are going to implement. In Mango 3, we usually use many Modbus I/P type datasources for communication with peripherals. To determine if the devices are out of communication, we have MetadaSource that checks every minute the last time values were received for each measurement. If that time exceeds 2 minutes, we set a virtual DataPoint to a value of 0, which triggers an HTTP Publisher to an endpoint on a server that manages the corresponding JSON to indicate that this measurement is out of communication. Before that, we used event management through the "Poll aborted" option, but we stopped doing so because sometimes there were communication drops and the event did not trigger correctly, so we were unaware of the issue.

      We would like to know if there is a better option in Mango 5 for sending a publisher if a Modbus I/P datasource stops communicating with the corresponding peripheral. We have seen significant changes in event management at the DataPoints level, allowing customization, but we only see information being sent via email, Slack, or other methods, not through a Publisher.

      MattFoxM 1 Reply Last reply Reply Quote 0
      • MattFoxM
        MattFox @jcaballeroa
        last edited by

        @jcaballeroa given that the changes implemented appear to be mainly ui focused, I do not think you'll find a better way at this stage.

        Fox

        Do not follow where the path may lead; go instead where there is no path.
        And leave a trail - Muriel Strode

        1 Reply Last reply Reply Quote 0
        • K
          kellybrook
          last edited by

          thanks for creating this topic

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