User's Manual

USER MANUAL PREVIEW

PTM 535BZ – BLUETOOTH AND ZIGBEE GREEN POWER PUSHBUTTON TRANSMITTER

C. Parsing of PTM 535BZ BLE radio telegrams

This appendix is intended as an example of how start to parse received PTM 535BZ radio

telegrams. Please refer to Chapter 3 for a description of the BLE frame structure.

C.1 Data telegram example

We consider the following raw data telegram data captured from a PTM 535BZ device:

D6 BE 89 8E 42 13 06 00 00 10 15 E2 0C FF DA 03 40 00 00 00 01 B0 56 1C 03 89 F4 6E

C.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 (Advertising)

BLE Frame Control (2 byte): 0x1342

Size of source address + payload: 0x13 (19 byte)

Telegram type: Non-connectable Advertising

BLE Source Address (6 byte): 0xE21510000006

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): 40 00 00 00 01 B0 56 1C 03

CRC (3 byte): 89 F4 6E

C.1.2 EnOcean data telegram payload structure

The EnOcean data telegram payload can now be parsed as follows:

Sequence Counter (4 byte): 0x00000040

Input Status (1 byte): 01 (ECO 200 Press, INPUT1 and INPUT2 disconnected)

Telegram Signature (4 byte): B0 56 1C 03