User's Manual

USER MANUAL

PTM 210 / PTM 215 / PTM 215U / PTM 215J

DC Step code and later

For details on encrypted RPS telegrams please see the EnOcean Security specification [3].

4.2 ERP 2 Communication

The ERP2 frames are fully described by the ERP2 specification. In the ERP2, there are no ULP

frames defined and the PTM module uses the common definition. The ERP2 frame is defined

as follows:

The relevant fields are defined below, for other fields and details please consult the ERP2

specification. Optional Data is not used in any type of the PTM module telegram.

4.2.1 Normal Mode Telegram

HEADER

 ADDRESS CONTROL: 0b001: Originator-ID 32 bit; no Destination-ID

 EXT. HEADER: 0b0: No extended header

 TELERGAM TYPE: 0b0000: RPS telegram (0xF6)

DATA OF DATALINK LAYER

 Is defined as payload of the EEP, see chapter 2.3 for details on EEP.

4.2.2 Secure Mode Telegram

HEADER

 ADDRESS CONTROL: 0b001: Originator-ID 32 bit; no Destination-ID

 EXT. HEADER: 0b0: No extended header

 TELERGAM TYPE: 0111: Secure telegram (0x30)

DATA OF DATA LINK LAYER

 Is defined as payload of the EEP, see chapter 2.3 for details on EEP.