USER MANUAL
ESRPB / EDRPB - EASYFIT BLUETOOTH® SINGLE / DOUBLE ROCKER PAD
© 2018 EnOcean | www.enocean.com
F-710-017, V1.0
ESRPB / EDRPB User Manual | v1.3 | Jan 2018 | Page 57/68
A.2
Commissioning telegram example
We consider the following raw commissioning telegram data captured from an EnOcean
PTM 215B device:
D6 BE 89 8E 42 24 9F 1B 00 00 15 E2 1E FF DA 03 71 01 00 00 AB 4B 9A 91 85 2B 70 B8
A6 52 A0 5E 92 BB 12 A0 9F 1B 00 00 15 E2 9E 6D 7C
A.2.1
BLE frame structure
The message shown above can be parsed into the following components (keep in mind the
little endian byte order):
BLE Access Address (4 byte):
0x8E89BED6
BLE Frame Control (2 byte):
0x2442
Size of source a payload: 0x24 (36 byte)
Telegram type: Non-connectable Advertising
BLE Source Address (6 byte):
0xE21500001B9F
Length of payload (1 byte):
0x1E (30 byte)
Type of payload (1 byte):
0xFF (manufacturer-specific data)
Manufacturer ID (2 byte):
0x03DA (EnOcean GmbH)
EnOcean Payload (27 byte):
71 01 00 00 AB 4B 9A 91 85 2B 70 B8 A6 52 A0 5E 92
BB 12 A0 9F 1B 00 00 15 E2
CRC (3 byte):
0x7C6D9E
A.2.2
EnOcean commissioning telegram payload structure
The EnOcean commissioning telegram payload can now be parsed as follows:
Sequence Counter (4 byte):
0x00000171
Security Key:
AB 4B 9A 91 85 2B 70 B8 A6 52 A0 5E 92 BB 12 A0
Static Source Address:
0xE21500001B9F