USER MANUAL
EMDCB
–
BLUETOOTH LOW ENERGY MOTION AND ILLUMINATION SENSOR
© 2019 EnOcean | www.enocean.com
EMDCB User Manual | v1.3 | August 2019 | Page 59/67
A
Parsing EMDCB telegrams
This chapter provides examples of EMDCB telegrams and shows how to interpret them.
A.1
Data telegram example
We consider the following raw data (excluding CRC) captured from an EMDCB device:
D6 BE 89 8E 42 1C C4 00 00 00 00 E5 15 FF DA 03 57 E2 01 00 02 AA 44 D6 00 45 35 00
20 02 C8 CC 57 12
A.1.1
BLE advertising frame structure
The message above can be parsed according to the Bluetooth standard for advertising mes-
sages as shown in Table 21 below.
Field
Length
Data
Interpretation
BLE Access Address
4 byte
0x8E89BED6
Constant (always used)
BLE Frame Control
2 byte
0x1C42
Length = 28 byte
BLE Source Address
6 byte
0xE500000000C4
Device-unique address
Length of payload
1 byte
0x15
21 byte of payload follow
Type of payload
1 byte
0xFF
Manufacturer-specific data
Manufacturer ID
2 byte
0x03DA
EnOcean GmbH
Payload
18 byte
57 E2 01 00 02 AA 44 D6 00 45 35 00 20 02 C8 CC 57 12
Table 21
–
Advertising message parsing
A.1.2
Data telegram payload
The EnOcean payload can be parsed as shown in Table 22 below.
Field
Length
Data
Interpretation
Sequence Counter
4 byte
0x0001E257
Incrementing message counter
Sensor Data
10 byte
02 AA 44 D6 00 45 35 00 20 02
Telegram Signature
4 byte
0xC8CC5712
Authentication signature
Table 22
–
EnOcean data telegram payload parsing
A.1.3
Sensor data
The sensor data can be parsed as shown in Table 23 below.
Descriptor Data Length
Type
Data
Value
0x02
0b00
(8 bit)
0b000010
(Energy Level)
0xAA
85 %
0x44
0b01
(16 bit)
0b000100
(Solar Cell Illuminance)
0x00D6
214 lx
0x45
0b01
(16 bit)
0b000101
(Sensor Illuminance)
0x0035
53 lx
0x20
0b00
0b100000 (Occupancy)
0x02
Occupied
Table 23
–
Sensor data parsing