USER MANUAL
PTM 215B – BLUETOOTH
®
PUSHBUTTON TRANSMITTER MODULE
© 2019 EnOcean | www.enocean.com
F-710-017, V1.0
PTM 215B User Manual | v1.9 | June 2019 | Page 70/85
A.
Parsing PTM 215B radio telegrams
This appendix is intended as an example of how start to parse received PTM 215B radio
telegrams. Please refer to chapter 4 first for a description of the BLE frame structure
Data telegram example
We consider the following raw data telegram data captured from an EnOcean PTM 215B
device:
D6 BE 89 8E 42 13 9F 1B 00 00 15 E2 0C FF DA 03 69 01 00 00 10 8A D6 C1 7E 16 EE 23
A.1.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):
0x1342
Size of source a payload: 0x13 (19 byte)
Telegram type: Non-connectable Advertising
BLE Source Address (6 byte):
0xE21500001B9F
Length of payload (1 byte):
0x0C (12 byte)
Type of payload (1 byte):
0xFF (manufacturer-specific data)
Manufacturer ID (2 byte):
0x03DA (EnOcean GmbH)
EnOcean Payload (9 byte):
69 01 00 00 10 8A D6 C1 7E
CRC (3 byte):
16 EE 23
A.1.2
EnOcean data telegram payload structure
The EnOcean data telegram payload can now be parsed as follows:
Sequence Counter (4 byte):
0x00000169
Switch Status:
10 (Release of button B1)
Telegram Signature:
C7 24 EA F0
