F 8627X (0650)
382
The following ReadDevice ID Codes are supported:
(1) Read Basic device identification (stream access)
(2) Read regular device identification (stream access)
(3) Read extended device identification (stream access)
(4) Read one specific identification object (inidividual access)
For further information about MODBUS TCP, refer to "Modbus Application Protocol Specifica-
tion" www.modbus.org.
6.4.5 Error codes
Note The function codes 03, 04 and 16 support data type Word (2 bytes)
and any other data types. The interpretation of the two MODBUS mas-
ter request parameters (start address, number) is done as follows:
Start address
describes the index of the first variable to be transmitted.
Number
determines the size of the area to be transmitted:
2*number bytes must be transmitted, provided the area ends directly
at a variable boundary.
Error code Description
0x01
(Invalid Code)
If MODBUS TCP master sends a telegram with an unknown function
code, MODBUS TCP slave responds with error code 0x01 (invalid code).
0x02
(Invalid Data)
If MODBUS TCP master's telegram does not match with the MODBUS
TCP slave's configuration (e.g. the request telegram does not end "even"
at a variable border), MODBUS TCP slave responds with error code 0x02
(invalid data).
0x03
(Invalid Value)
If MODBUS TCP master sends a telegram with faulty values (e.g. length
field), MODBUS TCP slave respons with error code 0x03 (invalid value).
0x0B No reply for a MODBUS Request is possible.
In case of Port 502
No F 865x central module is reachable.
In case of Port 8896
No active MODBUS TCP slave on the F 8627X is reachable.
Note: The function code "0x0B" is based on a gateway function.
Please refer to the Modbus specification at page modbus.org
To Next Page