Operating Manual V8.2/03.2017
Non Invasive Road Sensor
G. Lufft Mess- und Regeltechnik GmbH, Fellbach, Germany
43
19.3.5 Status and Error Codes in Binary Protocol
If a measurement request delivers the <status> 00h, the sensor is working correctly. You can
find a complete list of additional codes in the description of the UMB protocol.
Extract from list:
<status>
Description
00h (0d)
Command successful; no error; all o.k.
10h (16d)
Unknown command; not supported by this device
11h (17d)
Invalid parameter
24h (36d)
Invalid channel
28h (40d)
Device not ready; e.g. initialization / calibration running
50h (80d)
Measurement variable (+offset) is outside the set display range
51h (81d)
52h (82d)
Measurement value (physical) is outside the measuring range (e.g. ADC over range)
53h (83d)
54h (84d)
Error in measurement data or no valid data available
55h (85d)
Device /sensor unable to carry out valid measurements due to ambient conditions
19.3.6 CRC Calculation
CRC is calculated according to the following rules:
Norm:
CRC-CCITT
Polynomial:
1021h = x16 + x12 + x5 + 1 (LSB first mode)
Start value:
FFFFh
You can find further information in the description of a CRC calculation in the UMB Protocol.
19.3.7 Recording of a Communication with the UMB Config Tool
The UMB Config Tool
uses the command ‘Online data request multiple channels’ (2Fh) for
the data request.
Example of request to 3 channels (100, 600 and 900):
Communication (in hex):
Request by UMB Config Tool:
01 10 01 50 16 F0 09 02 2F 10 03 64 00 58 02 84 03 03 D4 FA 04
Response from NIRS31-UMB Sensor:
01 10 16 F0 01 50 1C 02 2F 10 00 03 08 00 64 00 16 8F C2 45 41 08 00 58 02
16 9A 59 7B 43 05 00 84 03 10 02 03 28 A4 04