Uploaded image for project: 'OpenModbus TCP'
  1. OpenModbus TCP
  2. PSOMB-255

Unit Identifier should not be limited to 0-247

    Details

    • Type: Change
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: V2.5.19.0, V2.6.0.0
    • Component/s: None
    • Labels:
      None
    • Sprint:
      VARNA KW36 / 37, VARNA KW38 / 39, VARNA KW42 / 43
    • Account:
      SPC Open Modbus TCP (SPCOPENMODTCP)

      Description

      To fulfill the requirement of the specification MODBUS Messaging on TCP/IP Implementation Guide V1.0b Modbus-IDA (October 24, 2006) there should be no limit in the usable Unit identifier

      Excerpt from the specification:

      When addressing a MODBUS server connected directly to a TCP/IP network, it’s recommended not using a significant MODBUS slave address in the “Unit Identifier” field. In the event of a re-allocation of the IP addresses within an automated system and if a IP address previously assigned to a MODBUS server is then assigned to a gateway, using a significant slave address may cause trouble because of a bad routing by the gateway. Using a non-significant slave address, the gateway will simply discard the MODBUS PDU with no trouble. 0xFF is recommended for the “Unit Identifier" as non-significant value.
      Remark : The value 0 is also accepted to communicate directly to a MODBUS/TCP device.

        Attachments

          Expenses

            Activity

              Status Description

                People

                • Reporter:
                  ABe Andreas B [X] (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: