3 Basics | LXM32M |
|
|
3.4.5"Function Code" 43 (Encapsulated Interface Transport)
This "Function Code" 43 / 14 (Read Device Identification) allows you to read
Modbus request Structure of the Modbus request:
Field | Bytes | Value | Meaning |
|
|
|
|
Function Code | 1 | 43 = 2Bh | Encapsulated Interface Transport |
|
|
|
|
Modbus Encapsula- | 1 | 14 = 0Eh | Fixed value 14 (Read Device Identification) |
ted Interface Type |
|
|
|
|
|
|
|
Read Device ID | 1 | 01 | Read all objects |
Code |
|
|
|
|
|
|
|
Object ID | 1 | 0x00 | Object ID |
|
|
|
|
Modbus response Structure of the positive Modbus response:
Field | Bytes | Value | Meaning |
|
|
|
|
Function Code | 1 | 43 = 2Bh | Encapsulated Interface Transport |
|
|
|
|
Modbus Encapsula- | 1 | 14 = 0Eh | Fixed value 14 (Read Device Identification) |
ted Interface Type |
|
|
|
|
|
|
|
Read Device ID | 1 | 01 | Corresponds to the Modbus request |
Code |
|
|
|
|
|
|
|
Conformity Level | 1 | 02 | Fixed value |
|
|
|
|
More Follows | 1 | 00 | Fixed value |
|
|
|
|
Next Object ID | 1 | 00 | Fixed value |
|
|
|
|
Number Of Objects | 1 | 03 | Number of objects |
|
|
|
|
Object ID | 1 |
| Object ID, see table |
|
|
|
|
Object Length | 1 |
| Object length |
|
|
|
|
Object Value |
| (various) | Object data (various) |
|
|
|
|
Structure of the negative Modbus response
Field | Bytes | Value | Meaning |
|
|
|
|
Function Code | 1 | 2Bh + 80h = ABh | Encapsulated Interface Transport |
|
|
|
|
Exception Code | 1 | 01h ... 04h | See chapter |
|
|
| "3.3.2 Modbus response to a Modbus request" |
|
|
|
|
Object ID The following object IDs are available:
Object ID | Object name | Value |
|
|
|
00h | vendor name | Manufacturer name |
|
|
|
01h | product code | „xxxxxxxxxxxx“ (see type code) |
|
|
|
03h | revision | "Vxx.yyy" (e.g. "V02.001") |
|
|
|
0198441113843, V1.01, 01.2012
32 |
