User's Manual

USER MANUAL
PTM 215B – 2.4 GHZ Pusbutton Transmitter Module
© 2016 EnOcean | www.enocean.com F-710-017, V1.0 PTM 215B User Manual | v0.8 | September 2016 | Page 20/42
2.9.6 Payload
The payload structure is depending on the telegram type (data telegram or commissioning
telegram).
2.9.6.1 Data Telegram Payload
The payload of data telegrams is 13 … 17 bytes long and consists of the following fields:
n Length (1 byte)
The Length field specifies the combined length of the following fields. The content of the
field depends on the size of the Optional Data field (which can be 0 / 2 / 2 or 4 byte).
The resulting Length setting would be 12 / 13 / 14 or 16 byte (0x0C / 0x0D / 0x0E / 0x10)
respectively
n Type (1 byte)
The Type field identifies the data type used for this telegram. For PTM 215B data tele-
grams, this field is always set to 0xFF to designate manufacturer-specific data field
n Manufacturer ID (2 byte)
The Manufacturer ID field is used to identify the manufacturer of BLE devices based on
assigned numbers. EnOcean has been assigned 0x03DA as manufacturer ID code
n Sequence Counter (4 byte)
The Sequence Counter is a monotonously incrementing counter used for security pro-
cessing. It is initialized to 0 at the time of production and incremented for each telegram
(data telegram or commissioning telegram) sent.
n Switch Status (1 byte)
The Switch Status field reports the button action. The encoding of this field is described
in chapter 2.6.
n Optional Data (0 / 1 / 2 or 4 byte)
PTM 215B provides the option to transmit additional user-defined data within each data
telegram. This data can be used to identify user-specific properties.
The length of the Optional Data field is defined in the Configuration register as described
in chapter 2.11.4.2.
n Security Signature (4 byte)
The Security Signature is used to authenticate PTM 215B radio telegrams as described in
chapter 2.10
Figure 13 below illustrates the data telegram payload.