USER MANUAL PREVIEW
PTM 535BZ
–
BLUETOOTH AND ZIGBEE GREEN POWER PUSHBUTTON TRANSMITTER
© 2021 EnOcean | www.enocean.com
F-710-017, V1.0
PTM 535BZ User Manual | v1.0 | May 2021 | Page 26/112
3.4.3
Commissioning telegram payload
The payload of commissioning telegrams is 30 bytes long and consists of the following fields:
◼
Length (1 byte)
The Length field specifies the combined length of the following fields. For PTM 535BZ
commissioning telegrams, this field is always set to
0x1D
to indicate that 29 byte of
manufacturer-specific data follow.
◼
Type (1 byte)
The Type field identifies the data type used for this telegram. This field is always set
to
0xFF
to indicate a “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. This field is by default set to
0x03DA
(EnOcean GmbH) but can
be reconfigured using the NFC interface.
◼
Sequence Counter (4 byte)
The Sequence Counter is a continuously incrementing counter used for security pro-
cessing. It is initialized to
0x00000000
at the time of production and incremented for
each telegram (data telegram or commissioning telegram) sent.
◼
Security Key (16 byte)
Each PTM 535BZ device contains its own 16 byte device-unique random security key
(SECURITY_KEY1) which is generated and programmed during manufacturing. It is
transmitted during commissioning to enable the receiver to authenticate PTM 535BZ
data telegrams and used as IRK for the case of resolvable private address mode.
◼
Static Source Address (6 byte)
The Static Source Address is used to uniquely identify each BLE device. It is transmit-
ted as part of the BLE frame as described in
Chapter 3.3.5
. Some receiver devices
(most notably iOS-based products) however do not directly expose this address to
their applications but rather assign a random value instead. The Static Source Address
is therefore also transmitted as part of the commissioning telegram payload so that
receivers can identify the source address of the sender.
below illustrates the commissioning telegram payload.
Figure 19
–
Commissioning telegram payload structure