• 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

    Using HTTP Retriever to retrieve data using HTTP GET

    User help
    2
    4
    2.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.
    • G
      glamprecht
      last edited by

      I have a logger that I can send a request for Modbus register value through a GET request in the form

      http://10.10.0.1?HoldingReg=43

      It is possible in Mango to setup a Publisher to issue this request periodically and a HTTP Receiver to log it to a datapoint.
      Another way is to use Mango HTTP Retriever instead with one data point to retrieve the register periodically.

      However I have 190 of these points per device to collect, so this means I have to create hundreds of Publishers or Retrievers data sources.

      Is there perhaps a way that I can set up one HTTP Retriever with 190 data points?

      thanks

      1 Reply Last reply Reply Quote 0
      • JoelHaggarJ
        JoelHaggar
        last edited by

        I can't think of how the Publisher and Receiver would work but this sounds pretty much exactly what the HTTP Retriever is meant for. Is there an option to make one request to the device and get all the register values back? If so then you could just use one data source for each device but as you say if it's a separate request for each register then you would need one data source for ever register.

        1 Reply Last reply Reply Quote 0
        • G
          glamprecht
          last edited by

          The way I understand the Retriever is that it sends ONE predetermined URL (setup in the data source) and then fills up all the data points based on a single response.

          I would do that by setting up Retriever URL as for example
          http://10.10.0.1?HoldingReg=43&HoldingReg=44&HoldingReg=45
          and then define a RegEx to look for the response containing the actual value for each one.

          However in this case the logger process a maximum of 5 data points at a time, so for every 5 I have to create a new Retriever?

          Is there perhaps a way that the Retriever will execute a request for ea of its data points and also append something to the URL based on that data point?

          1 Reply Last reply Reply Quote 0
          • JoelHaggarJ
            JoelHaggar
            last edited by

            Right, this works exactly as you describe so to work with that data logger you would need one data source per 5 data points.

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