User's Manual
© 2020 EnOcean | www.enocean.com PTM 210 / PTM 215 / PTM 215U / PTM 215J User Manual August 2020 | Page 31/45
USER MANUAL
PTM 210 / PTM 215 / PTM 215U / PTM 215J
DC Step code and later
5.3.4.5 NEXT OEPRATION IS TEACH IN
The module will send a Security Teach-in telegram the next time it is triggered. The module
must first be set to the desired security level. After the secure Teach in telegram was send
this flag is reset to default state. Following values can be set
0b00000000: OFF (default): Normal operation.
0b00000001: ON: Next telegram will be a Security Teach-in telegram.
0b0000 0010 – 0b1111 1111: RFU
5.3.4.6 PRODUCT ID
The EnOcean Alliance Product ID uniquely identifies each product within the EnOcean Alliance
ecosystem. The Product ID consists of a 2-byte manufacturer identification code (assigned
by EnOcean Alliance) and a 4-byte product identification code (assigned by the manufacturer.
EnOcean has been assigned the manufacturer identification code 0x000B. EnOcean has as-
signed the following product identification codes to PTM 215:
PTM 215: 0x00000053
PTM 215U: 0x00000055
PTM 215J: 0x00000057
The PRODUCT ID register contains the Product ID in ASCII format (12 characters) and allows
changing both manufacturer and product identification. Changing the PRODUCT ID will also
cause the PRODUCT ID field in the NDEF string (described in chapter 5.3.1) to be updated.
Figure 17 below shows the structure of the PRODUCT ID register. This register contains the
sequence of 12 ASCII characters (1 byte each) starting with CH0 and ending with CH11.
PRODUCT_ID
CH0
CH1
CH2
CH3
CH4
CH5
CH6
CH7
CH8
CH9
CH10
CH11
Manufacturer (“000B”)
Product ID (“00000053”, “00000055” or “00000057”)
Figure 17 – PRODUCT_ID
5.3.4.7 USER_KEY
Each PTM 215 module is pre-programmed at the factory with a randomly generated 128-bit
security key. This key will by default be used to encrypt and authenticate PTM 215 radio
telegrams when operating in security mode. This key is also encoded inside the QR code on
the label of the product.
In certain applications or situations, it might be desirable to assign a different (user-defined)
security key. This can be done by writing the user-defined security key to the USER_KEY.