11. Modbus TCP server
11. 9. “Read Device Identification” (43 = 16#2B) function
Request format:
Byte | Meaning | With the VW3A3310d Ethernet card |
| ||
0 | Function Code = 16#2B | 16#2B |
| ||
1 | Type of MEI | 16#0E |
| ||
|
| 16#01: Basic |
| ||
2 | Read Device ID code | 16#02: Regular |
| ||
|
| 16#03: Extended |
| ||
3 | Object ID | 16#00 |
|
| |
Response format: |
|
|
|
| |
|
|
|
|
| |
Byte(s) | Meaning | With the VW3A3310d Ethernet card | |||
0 | Function code = 16#2B | 16#2B | |||
1 | Type of MEI | 16#0E | |||
2 | ReadDeviceId code | 16#01 |
|
| |
3 | Degree of conformity | 16#02 |
|
| |
4 | Number of additional frames | 16#00 (a single frame) | |||
5 | Next object ID | 16#00 |
|
| |
6 | Number of objects | 3 for Basic | |||
4 for Regular or Extended | |||||
|
| ||||
7 | Object no. 1 ID | 16#00 = Vendor Name | |||
8 | Length of object no. 1 (A) | 13 |
|
| |
9…21 | Value of object no. 1 (A ASCII characters) | “Telemecanique” | |||
22 | Object no. 2 ID | 16#01 = Product Code | |||
23 | Length of object no. 2 (B) | 11 (for the following example only) | |||
24…23+B | Value of object no. 2 (B ASCII characters) (1) | Example: “ATV71HU15M3” | |||
24+B | Object no. 3 ID | 16#02 = Major.Minor Revision | |||
25+B | Length of object no. 3 (C) | 4 |
|
| |
26+B…29+B | Value of object no. 3 (C ASCII characters) | Example: “0201” for version 2.1 | |||
30+B | Object no. 4 ID | 16#06 = Application Name (2) |
|
| |
31+B | Length of object no. 4 (D) | 8 (for the following example only) | for Regular and Extended | ||
32+B…31+B+D | Value of object no. 4 (D ASCII characters) (1) | Example: “MACHINE 4” |
|
| |
(1)The length of this field is variable. Use the “Length of object no. X” field associated with it to determine the length.
(2)In the case of the drive, this data item corresponds to [DEVICE NAME].
The response to a “drive identification” request does not cause an exception response.
39
