• 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 4 Documentation Website Mango 5 Documentation Website Radix IoT LinkedIn

    Modbus points 4-byte float swapped displays zero but Point locator test shows good values

    Scheduled Pinned Locked Moved User help
    3 Posts 2 Posters 1.7k Views 2 Watching
    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.
    • P Offline
      Pedro
      last edited by

      When using the "Point locator test" on the Modbus datasource configuration page, a good value is displayed after clicking on "Read." However, if that point is added as a regular point, 0 is displayed when mousing over the grey building block in the "Data points" list. Similarly, /point_details.shtm displays zero live and in the "Real-time history."

      • "Discard extreme values" is not selected
      • Register range is "Holding register"
      • None of the "numeric" points are working, but binary points are working with the same datasource
      • "Modbus read data" box shows non-zero hex values.
      • The datasource log file displays outgoing and incoming Modbus packets, even when only one problematic point is selected.
      • mango/logs/ma.log shows nothing
      • There are no related datasource "Event alarm levels" generated.
      • Disabling/enabling the source or the point does not fix the problem.
      • core 2.7.2 build 465

      Has anyone seen this problem before? What is the work-around? Were any changes made to the core or to the Modbus module that may fix this?

      1 Reply Last reply Reply Quote 0
      • C Offline
        craig
        last edited by

        do you have other holding register points on the data source? what if there is only the one?

        Also try the "contiguous batches only" check box, some slaves will throw an exception if you you try to read a register that doesn't exist that may be between two blocks of defined registers.

        1 Reply Last reply Reply Quote 0
        • P Offline
          Pedro
          last edited by Pedro

          Craig, I noticed on the point_details.shtm page that it would display zero when the device was polled every five seconds, but when I clicked the green refresh icon, it would display the correct floating point value. After I checked the "contiguous batches only" check box, everything worked properly. Thanks for your help!

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • First post
            Last post