• 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

    Addressing issue

    Modbus4J general discussion
    2
    5
    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.
    • B
      bharti
      last edited by

      I am new to Modbus4J howerever i have used jamod which supports addressing of the slave in the range of 0-255 and not beyond that.
      can i use Modbus4J for connecting to devices of 16bit addresse.
      thnx very much.

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

        Actually, as per the spec a slave id must be between 1 and 240. (0 is the broadcast id.)

        It would be easy enough to circumvent the slave id range checks, but you'd be violating the specification. All devices would need to agree to use 16 bit addresses before this would work.

        Best regards,
        Matthew

        1 Reply Last reply Reply Quote 0
        • B
          bharti
          last edited by

          Thanks very much for your prompt reply.
          Hardware config is done. only issue is thru software i want to access a slave having 2 bytes address.
          how do i do this thru modbus4j?

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

            Simplest is to make the appropriate changes to the Modbus4J code.

            Best regards,
            Matthew

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