F 037 300 069 (2013.05.21)
47
Response CIMS -> MASTER
Byte Contents Value
2 MEI Type - Read Device Identification 0Eh
3 Conformity Level - Extended Identification (Individual Access) 83h
4 More Follows 00h
5 Next Object Id 00h
6 Number of Objects 01h
7 Object ID - MODBUS Interface Version A2h
8 Object Length 07h
9 Payload
Coding: ASCII string
Length: 7 Byte
Format: 'V' + 2 digits Major Version + '.' + 3 digits Minor Version
Example: 'V01.024'
XXh
... ...
15 XXh
16 CRC XXh
17 XXh
C.5 SENSOR EVENT MANAGEMENT
To use the Event Management services the MODBUS function Read Holding Registers 03h is
used as described in [2]. To clear the Event Memory the MODBUS function Write Multiple
Registers 10h is used as described in [2]. In contrast to this specification, the Starting Address is
not used as a physical address, but more as a Service ID.
The CIMS Sensor supports only access to one Service ID (Address) at one request.
C.5.1 POSSIBLE ERROR MESSAGES
Error CIMS -> MASTER
Byte Contents Value
0 Slave Address A2h
1 Error Function Code (Function Code + 80h) FC+80h
2
Exception Code
0x04 - Slave Device Failure - If the syntax of the request is wrong.
XXh
3 CRC XXh
4 XXh
C.5.2 GET LAST DEBUG DETAIL (10H, E0FEH)
This service is more a debug feature. It gives back more detail to the last occurred debug event,
e.g. a MODBUS communication error. It is not direct related to the event memory feature.
Request MASTER -> CIMS
Byte Contents Value
0 Slave Address A2h
1 Function Code - Read Holding Registers 03h
2 Starting Address / Service ID - Get Last Debug Detail E0h
3 FEh
4 Quantity of Registers 00h
5 05h
6 CRC XXh
7 XXh
To Next Page
Loading...
