![EnOcean EASYFIT EMDCB Скачать руководство пользователя страница 60](http://html1.mh-extra.com/html/enocean/easyfit-emdcb/easyfit-emdcb_user-manual_2413682060.webp)
USER MANUAL
EMDCB
–
BLUETOOTH LOW ENERGY MOTION AND ILLUMINATION SENSOR
© 2019 EnOcean | www.enocean.com
EMDCB User Manual | v1.3 | August 2019 | Page 60/67
A.2
Commissioning telegram example
We consider the following advertising data (excluding CRC) captured from the same EMDCB
device as in the previous chapter:
D6 BE 89 8E 42 25 C4 00 00 00 00 E5 1E FF DA 03 56 E2 01 00 3E 9E 0D E9 C2 53 86 B6
C4 F0 70 64 2E 19 E0 36 80 C4 00 00 00 00 E5
A.2.1
BLE advertising data
The advertising data given above can be parsed according to the Bluetooth standard for
advertising frames as shown in Table 24 below.
Field
Length
Data
Interpretation
BLE Access Address
4 byte
0x8E89BED6
Constant (always used)
BLE Frame Control
2 byte
0x2542
Length = 37 byte
BLE Source Address
6 byte
0xE500000000C4
Device-unique address
Length of payload
1 byte
0x1E
30 byte of payload follow
Type of payload
1 byte
0xFF
Manufacturer-specific data
Manufacturer ID
2 byte
0x03DA
EnOcean GmbH
Payload
27 byte
56 E2 01 00 3E 9E 0D E9 C2 53 86 B6 C4 F0 70 64 2E 19
E0 36 80 C4 00 00 00 00 E5
Table 24
–
Advertising data parsing
A.2.2
Commissioning telegram payload
The payload of the commissioning telegram can be parsed as shown in Table 25 below.
Field
Length
Data
Interpretation
Sequence Counter
4 byte
0001E256
Incrementing message counter
Field Identfier
1 byte
0x3E
Commissioning Telegram (22 byte)
Device Key
16 byte
9E0DE9C25386B6C4F070642E19E03680
Source Address
6 byte
0xE500000000C4
Table 25
–
Commissioning telegram payload parsing