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 17/68
4.6
Payload
The payload of data telegrams is 13 … 17 bytes long (depending on the size of the Optional
Data field) and consists of the following fields:
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 / 1 / 2 or 4
byte).
The resulting Length setting would be 12 / 13 / 14 or 16 byte (
0x0C
/
0x0D
/
0x0E
/
0x10
) respectively
Type (1 byte)
The Type field identifies the data type used for this telegram. For PTM 215B data
telegrams, this field is always set to
0xFF
to designate manufacturer-specific data
field
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.
The Manufacturer ID can be changed via the NFC configuration interface as de-
scribed in chapter 6.7.4.
Sequence Counter (4 byte)
The Sequence Counter is a continuously incrementing counter used for security
processing. It is initialized to
0
at the time of production and incremented for each
telegram (data telegram or commissioning telegram) sent.
Switch Status (1 byte)
The Switch Status field reports the button action. The encoding of this field is de-
scribed in chapter 4.7.
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 de-
scribed in chapter 6.7.6.
Security Signature (4 byte)
The Security Signature is used to authenticate ExRPB radio telegrams as described
in chapter 4.8
Figure 13 below illustrates the data telegram payload.
Figure 13 – Data telegram payload structure