EnOcean TCM 515 User Manual

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

Patent protected:

WO98/36395, DE 100 25 561, DE 101 50 128, WO 2004/051591, DE 103 01 678 A1, DE 10309334, WO 04/109236, WO 05/096482, WO 02/095707, US 6,747,573, US 7,019,241

Observe precautions! Electrostatic sensitive devices!

TCM 515

EnOcean Transceiver Gateway Module

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

REVISION HISTORY

The following major modifications and improvements have been made to this document:

Version

Author

Reviewer

Date

Major Changes

1.0

MKA

MK, CB

12.05.2017

First public release

1.1

MKA

22.05.2017

Added detailed antenna information

1.2

MKA

MH, MK

22.06.2017

Added receiver class due to RED requirement

1.3

OS

MKA

08.08.2017

Added FCC grant and regulatory information for FCC and ISED; Added maximum input power

1.4

MKA

31.08.2017

Added Tape & Reel specification

1.5

MKA

19.09.2017

Added detailed description of filtering functionality

1.6

MKA

25.10.2017

Added maximum number of filters

1.7

MKA

10.01.2018

Extensive update for production version. Added detailed description of telegram processing, security operations and noise filtering.

1.8

MKA

30.01.2018

Added product revision history Added maximum input power and RSSI accuracy. Added current during start-up.

1.9

MKA

30.04.2018

Added DA-7 to product history

1.10

MKA

31.07.2018

Added DB-8 to product history, extended description of ESP3 interface, telegram filtering and BaseID functionality

1.11

MKA

08.01.2019

Added application info for SAW circuit

1.12

MKA

05.02.2019

Added note regarding test points and regarding RLC storage.

1.13

MKA

08.08.2019

Update with new features in product version DB-09

1.14

MKA

28.01.2020

Corrected list of supported secure RORG

1.15

MKA

18.03.2020

Added information about ESP3 command for transmission

1.16

MKA

31.07.2020

Added new features in product version DC, Added introduction to EnOcean radio in Appendix A and EnOcean security in Appendix B

1.17

MKA

08.12.2020

Added PCB parameters for whip antenna Added description of product label

Published by EnOcean GmbH, Kolpingring 18a, 82041 Oberhaching, Germany www.enocean.com, info@enocean.com, phone +49 (89) 6734 6890

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

Disclaimer

This user manual describes the type of component and shall not be considered as assured characteristics. No responsibility is assumed for possible omissions or inaccuracies. Circuitry and specifications are subject to change without notice. For the latest product specifications, refer to the EnOcean website: http://www.enocean.com.

As far as patents or other rights of third parties are concerned, liability is only assumed for modules, not for the described applications, processes and circuits.

EnOcean does not assume responsibility for use of modules described and limits its liability to the replacement of modules determined to be defective due to workmanship. Devices or systems containing RF components must meet the essential requirements of the local legal authorities.

The modules must not be used in any relation with equipment that supports, directly or indirectly, human health or life or with applications that can result in danger for people, animals or real value.

Components of the modules are considered and should be disposed of as hazardous waste. Local government regulations are to be observed.

Packing: Please use the recycling operators known to you.

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

TABLE OF CONTENT

1 General description ........................................................................................ 8

1.1 Basic functionality ......................................................................................... 8

1.2 Technical data ............................................................................................... 9

1.3 Physical dimensions ..................................................................................... 10

1.4 Environmental conditions ............................................................................. 10

1.5 Packaging information .................................................................................. 10

1.6 Ordering information ................................................................................... 10

2 Functional information ................................................................................. 11

2.1 High-level functionality ................................................................................ 11

2.2 Functional states ......................................................................................... 12

2.3 Device interface .......................................................................................... 13

2.3.1 Pin-out ............................................................................................... 13

2.4 Power supply .............................................................................................. 14

2.5 Antenna ..................................................................................................... 14

2.6 UART interface ............................................................................................ 14

2.7 Reset ......................................................................................................... 15

2.8 Test interface (TP1, TP2, TP3) ....................................................................... 15

2.9 Product label ............................................................................................... 15

2.9.1 QR code ............................................................................................. 16

3 Power-up, initialization and system operation ................................................. 17

3.1 Typical operation sequence for transmit and receive mode ............................... 17

3.2 Typical operation sequence for transmit-only mode ......................................... 18

4 Telegram reception ...................................................................................... 19

4.1 Telegram reception flow ............................................................................... 19

4.2 Telegram filtering ........................................................................................ 20

4.2.1 Filter type ........................................................................................... 21

4.2.2 Filter value .......................................................................................... 21

4.2.3 Filter condition .................................................................................... 22

4.2.4 Filter action ......................................................................................... 22

4.2.5 Filter combination ................................................................................ 23

4.2.6 Filter definition .................................................................................... 23

4.2.7 Filter enabling ..................................................................................... 24

4.2.8 Filter reading ....................................................................................... 25

4.2.9 Filter deletion ...................................................................................... 26

4.2.10 Filter examples .................................................................................... 27

4.2.10.1 Forwarding (ESP3 to host) filter examples ............................................ 27

4.2.10.2 Repeater filter examples .................................................................... 28

4.3 RADIO_ERP1 packet for received telegrams .................................................... 29

4.4 RADIO_ERP2 packet for received telegrams (TCM 515U only) ........................... 30

4.5 Wait for RX maturity time ............................................................................. 31

4.6 Transparent mode ....................................................................................... 32

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

4.7 RSSI test mode ........................................................................................... 33

5 Telegram transmission ................................................................................. 35

5.1 Transmission flow ........................................................................................ 35

5.2 RADIO_ERP1 packet for telegram transmission ............................................... 36

5.3 RADIO_ERP2 packet for telegram transmission (TCM 515U only) ....................... 37

5.4 RADIO_MESSAGE packet for telegram transmission ......................................... 38

5.5 Using Base ID for transmission ..................................................................... 39

5.6 Duty cycle limit ........................................................................................... 40

5.6.1 Determining available transmission time ................................................. 41

5.7 Transmit-only mode .................................................................................... 42

6 Telegram repeating ..................................................................................... 43

6.1 Configuration of telegram repeating ............................................................... 44

7 Security processing ..................................................................................... 45

7.1 TCM 515 security architecture ....................................................................... 45

7.2 Telegram processing flow ............................................................................. 46

7.3 Secure link table ......................................................................................... 47

7.3.1 Secure link table parameters ................................................................. 48

7.4 Telegram encryption and decryption .............................................................. 50

7.5 Telegram authentication ............................................................................... 50

7.6 RLC support ................................................................................................ 51

7.6.1 Explicit and implicit rolling code support ................................................. 51

7.6.2 RLC roll-over ....................................................................................... 52

7.6.3 RLC backup ......................................................................................... 53

7.7 Teach-in of secure devices ............................................................................ 54

7.7.1 Security parameters ............................................................................. 54

7.7.1.1 Security key ..................................................................................... 54

7.7.1.2 RLC ................................................................................................. 54

7.7.2 Secure teach-in procedure .................................................................... 55

7.7.3 Teach-in of secure devices with secure teach-in telegram ......................... 55

7.7.3.1 Transmission of a secure teach-in telegram .......................................... 55

7.7.3.2 Reception of a secure teach-in telegram (Teach-in mode) ...................... 56

7.7.3.3 Handling of secure teach-in telegrams if teach-in mode is not active ....... 57

7.7.4 Teach-in of secure devices using ESP3 ................................................... 58

7.8 Reporting of security-related events .............................................................. 60

8 Low power sleep mode ................................................................................. 61

9 ESP3 interface ............................................................................................ 62

9.1 ESP3 physical interface ................................................................................ 62

9.2 ESP3 packet structure .................................................................................. 63

9.3 Supported ESP3 commands .......................................................................... 64

9.4 Persistent versus not persistent configuration settings ..................................... 66

10 Remote management ................................................................................... 67

11 Device integration ....................................................................................... 68

11.1 Recommended PCB Footprint ................................................................... 68

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

11.2 Device outline ........................................................................................ 69

11.3 Soldering information .............................................................................. 70

11.4 Packaging information ............................................................................. 71

11.5 Layout recommendations ......................................................................... 72

11.6 Power supply requirements ...................................................................... 73

11.7 Using an SAW Filter with TCM 515 (868 MHz version only) .......................... 73

11.8 Low noise design considerations ............................................................... 74

11.9 Suggested Reset circuit ........................................................................... 75

11.10 Test interface ...................................................................................... 76

11.11 Identifying the TCM 515 product revision ................................................ 76

12 Antenna options .......................................................................................... 77

12.1 Antenna options for 868 MHz (European Union) ......................................... 77

12.1.1 Whip antenna ...................................................................................... 78

12.2 Antenna options for 902 MHz (US / Canada) .............................................. 79

12.2.1 Whip antenna ...................................................................................... 79

12.2.2 Helical antenna .................................................................................... 79

12.2.3 Chip antenna (Supplier: Mitsubishi Material, Type AM11DP-ST01T) ............ 80

12.2.4 Dipole antenna (ANT-916-CW-HWR-RPS)................................................ 81

13 Application information ................................................................................ 82

13.1 Transmission range ................................................................................. 82

13.2 Maximum input power ............................................................................. 83

13.3 RSSI reporting ....................................................................................... 83

14 Regulatory information ................................................................................. 84

14.1 RED (European Union) ............................................................................ 84

14.1.1 RED Attestation of Conformity for TCM 515 ............................................. 85

14.2 FCC (United States) ................................................................................ 86

14.2.1 FCC Grant Of Equipment Authorization ................................................... 86

14.2.2 FCC Usage Conditions .......................................................................... 87

14.2.3 OEM Requirements .............................................................................. 88

14.2.4 Module Activation ................................................................................ 89

14.3 ISED (former Industry Canada) Certification .............................................. 90

14.3.1 ISED Technical Acceptance Certificate .................................................... 90

14.3.2 ISED Usage Conditions ......................................................................... 91

14.4 Repeater Function (FCC/IC) ..................................................................... 92

15 References ................................................................................................. 93

16 Product history ............................................................................................ 94

A. Introduction to EnOcean radio protocol .......................................................... 95

A.1 ERP1 telegram format .................................................................................. 95

A.2 ERP2 telegram format .................................................................................. 96

A.3 Subtelegrams ............................................................................................. 96

A.3.1 Subtelegram timing ................................................................................. 97

A.3.2 TX maturity time ..................................................................................... 98

A.3.3 RX maturity time ..................................................................................... 98

A.4 Addressing ................................................................................................. 99

A.4.1 Address types ......................................................................................... 99

A.4.2 EURID (Radio ID) ...................................................................................... 100

A.4.3 Broadcast ID ............................................................................................. 100

A.4.4 Base ID .................................................................................................... 100

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

A.5 Data payload ............................................................................................ 101

A.5.1 EnOcean Equipment Profiles (EEP) structure ............................................. 101

A.5.2 Common RORG ..................................................................................... 102

A.5.3 Data payload size .................................................................................. 103

A.6 Telegram chaining ..................................................................................... 103

A.6.1 Telegram chaining for broadcast telegrams ............................................... 104

A.6.2 Telegram chaining for addressed telegrams (ADT) ..................................... 104

A.6.3 Telegram chaining for secure telegram (SEC_CDM) ................................... 105

A.6.4 Telegram chaining for addressed secure telegram (ADT SEC_CDM) ............. 106

B. Introduction to EnOcean security protocol .................................................... 107

B.1 Goals of secure radio communication ........................................................... 107

B.2 Telegram encryption .................................................................................. 108

B.3 Telegram authentication ............................................................................. 108

B.4 Replay protection ...................................................................................... 110

B.4.1 RLC and security key in bi-directional communication ................................ 112

B.4.2 RLC synchronization between sender and receiver ..................................... 113

B.5 Secure telegram types ............................................................................... 114

B.5.1 Secure teach-in telegram ....................................................................... 114

B.5.1.1 Teach-in Info ............................................................................................ 115

B.5.1.2 Security level format (SLF) ......................................................................... 115

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

1 General description

1.1 Basic functionality

TCM515 is an addition to the existing TCM 300 / 310 / 320 transceiver module family consisting of the following products:

◼ TCM 515

868.3 MHz ASK, EnOcean Radio Protocol version 1, main market Europe

◼ TCM 515U

902.875 MHz FSK, EnOcean Radio Protocol version 2, main market US and Canada

The term “TCM 515” in this document refers to all members of the TCM 515 family unless noted differently.

TCM 515 products are limited to OEM installation ONLY.

TCM 515 is optimized for application requiring smallest possible size and integrated security handling such as line-powered actuators or controllers. For applications requiring highest radio performance - such as gateways or access points covering larger areas – consider using TCM 310 which provides the highest possible sensitivity and noise immunity due to an integrated SAW filter.

TCM 515 provides a radio link between EnOcean radio devices and an external host connected via UART interface using the standardized EnOcean Serial Protocol V3 (ESP3) communication protocol.

TCM 515 receives and transmits radio telegrams based on a 50 Ohm or whip antenna connected to the host PCB. It forwards received radio telegrams to an external host processor or host PC via the ESP3 interface. Messages received from an external host via the ESP3 interface will be transmitted by TCM 515 as EnOcean radio telegrams according to the chosen frequency.

TCM 515 is implemented as 31 pin reflow-solderable module with optimized form factor for size constrained applications. It is not pin compatible with existing TCM 310 products. Figure 1 below shows TCM 515.

Figure 1 – TCM 515

This document describes the features of TCM 515 (868.3 MHz ERP1) and TCM 515U (902.875 MHz ERP2).

In addition, this document provides an introduction to EnOcean radio networks in Appendix

A and an introduction to EnOcean security architecture in Appendix B.

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

1.2 Technical data

Antenna

50 Ohm whip antenna (connected at host board)

Supported Radio Frequencies

TCM 515: 868.3 MHz ASK TCM 515U: 902.875 MHz FSK

Data Rate

125 kbps

Receiver Sensitivity

(1)

TCM 515: 868.3 MHz ASK: -92 dBm TCM 515U: 902.875 MHz FSK: -98 dBm

Maximum Input Power

(1) (2)

-17 dBm (for product version DC)

Receiver Blocking Performance

Class 2 according to EN 300 220-1

Radiated RF Immunity

3 V / m according to EN 301 489-3

Transmit Power

TCM 515: 868.3 MHz ASK: +10 dBm TCM 515U: 902.875 MHz FSK: +1 dBm

Supply Voltage (min / max / typ)

2.0 V / 3.6 V / 3.3 V

Supply Current RX State

25 mA

Supply Current TX State

(3)

25 mA

Supply Current Idle State

(4)

5 mA

Supply Current Sleep Mode

0.05 mA

Power-up to Ready State Timing

50 ms

Ready State to RX State Delay

(5)

200 ms (default setting, adjustable via ESP3)

Supply Current between Power-up and RX

12 mA

TX to RX switching time

(6)

< 1 ms

Serial Interface To Host

UART according to ESP3 Standard (TURBO option)

Note: All figures are typical values at 25°C unless otherwise specified

Note 1: Sensitivity and Maximum Input Power figures are based on 0.1% telegram error rate for the combination of 3 received sub-telegrams

Note 2: Maximum Input Power is -17 dBm for product revision DC onwards. For previous revisions, it is -23 dBm

Note 3: ASK modulation encodes the bit status (0 or 1) using different radio power levels where 0 is encoded with a high-power level and 1 with a low power level. The TX current therefore depends on the ration between bits with the value 0 and bits with the value 1 in the bit stream. The figure given here is for a PN9 sequence.

Note 4: Idle Mode is used when TCM 515 operates in transmit-only mode while no telegram is transmitted. Transmit-only mode is supported in TCM 515 starting with product revision DC.

Note 5: During start-up, TCM 515 waits for a configurable additional delay before transitioning to RX state to allow for power supply stabilization and start-up of the external host.

The default value for this delay is 200 ms; this is adjustable via ESP3

Note 6: TX to RX switch over time is measured from the transmission of the last bit (end of frame) of a radio frame until the receiver is ready to receive the first bit (preamble) of a radio frame

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

1.3 Physical dimensions

Module Dimensions

19.0 mm x 14.7 mm x 3.0 mm (all +- 0.3 mm)

Module Weight

1 g

1.4 Environmental conditions

Operating Temperature

-40°C ... +85°C

Storage Temperature

-40°C ... +85°C

Humidity

0% to 95% r.h. (non-condensing)

1.5 Packaging information

Packaging Unit / Method 250 units / Tape and reel

1.6 Ordering information

Type

Ordering Code

TCM 515 TCM 515U

S3003-K515 S3053-K515

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

2 Functional information

2.1 High-level functionality

TCM 515 is a fully integrated radio transceiver family which enables communication with other devices implementing the EnOcean Radio Protocol (ERP).

TCM 515 uses EnOcean Radio Protocol 1 as described in the EnOcean Radio Protocol 1 (ERP1) specification [2] while TCM 515U and TCM 515J use EnOcean Radio Protocol version 2 as described in the EnOcean Radio Protocol 2 (ERP2) specification [3].

TCM 515 is used to exchange (send and / or receive) radio telegrams with external sensors, switches or actuators.

TCM 515 is connected to an external host which for instance could be a microprocessor, a controller or a gateway via the EnOcean Serial Protocol v3 (ESP3) interface. ESP3 commands are listed within this document for information purposes only; for details about ESP3 commands refer to the ESP3 specification [1].

Figure 2 below shows the integration of TCM 515 into a typical system environment.

Figure 2 – TCM 515 system environment

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

2.2 Functional states

TCM 515 implements the following functional states:

◼ Power-up and system initialization (with user-configurable delay)

This state is described in chapter 3

◼ RX state (telegram reception with security processing, filtering, repeating as required)

This state is described in chapter 4

◼ TX state (telegram transmission with security processing as required)

This state is described in chapter 5

◼ Sleep state (low power state to conserve energy)

This state is described in chapter 8

The transition between these functional states is shown in Figure 3 below.

Figure 3 – TCM 515 functional states

Note that starting with revision DC-10 it is possible to configure TCM 515 to operate as transmit-only device which disables receive functionality. If TCM 515 is configured to operate as transmit-only device, then RX state is replaced by Idle state where TCM 515 will wait for ESP3 commands. Transmit-only functionality is described in chapter 5.7.

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

2.3 Device interface

TCM 515 implements a 31 pin reflow-solderable interface. Solder mask data is available on request from EnOcean.

2.3.1 Pin-out

The pin assignment (as seen from the top of the TCM 515 device) is shown in Figure 4 below. Solder mask and mechanical data is available from EnOcean.

Figure 4 – TCM 515 device interface

Table 1 below summarizes the signal assignment.

NAME

1

GND

12

NC

23

GND 2 RF_50 (50Ω antenna)

13

NC

24

nRESET (Reset input, active low)

3

GND

14

NC

25

TP1 (Test Interface)

4

NC

15

GND

26

TP2 (Test Interface)

5

NC

16

NC

27

TP3 (Test Interface)

6

GND

17

NC

28

NC

7

NC

18

NC

29

NC

8

NC

19

NC

30

NC

9

NC

20

UART_RX (Input to TCM 515)

31

nTURBO (UART speed, active low)

10

NC

21

UART_TX (Output from TCM 515)

11

NC

22

VDD

Table 1 - TCM 515 pin assignment

Signals marked with “NC” are reserved for production test and future device variants and must not be connected in the design.

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

2.4 Power supply

TCM 515 is supplied by the VDD and GND Pins and supports a supply voltage range between

2.0 V and 3.6 V. For best radio performance it is very important to minimize noise on the supply voltage lines. Please see chapter 11.5 and 11.6.

If TCM 515 is operated close to the minimum supply voltage of 2.0 V then care has to be taken in the power supply design to ensure that the supply voltage does not drop to below 2.0 V during load transients such as start-up or wake-up from Sleep state.

2.5 Antenna

TCM 515 receives and transmits data based on a 50Ω whip antenna connected to its RF_50 input (Pin 2). Please see chapter 12.

2.6 UART interface

TCM 515 communicates with the external host using the standard ESP3 serial (UART) interface based on the signals UART_TX (Pin 21, direction from TCM 515 to external host) and UART_RX (Pin 20, direction from external host to TCM 515).

It is strongly recommended that the PCB design provides the ability to connect to these signals – e.g. by means of providing suitable test point pads on the PCB - for the purpose of analysis, debug and firmware update.

The default interface speed of the ESP3 interface is 57600 bit per second and data is transmitted using 8 data bits, 1 STOP bit and no parity (8N1).

It is possible to select faster communication speeds during operation using the ESP3 CO_SET_BAUDRATE command (see chapter 9.1). The following interface speeds are supported by TCM 515:

◼ 57600 bit per second

◼ 460800 bit per second

Additionally, it is possible to change the default ESP3 interface speed at power up from

57.600 bit per second to 460.800 bit per second by connecting the nTURBO input (Pin 31, active low) to Ground.

Subsequent modification of the interface speed during operation using the CO_SET_BAUDRATE command is always possible irrespective of the state of the TURBO input pin.

Care should be taken not to select a UART interface speed which cannot be supported

by the connected host processor as this would prevent subsequent communication.

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

2.7 Reset

TCM 515 can be reset by pulling the nRESET pin (Pin 24, active low) to Ground. Please see chapter 11.9 for reset circuit recommendations.

It is strongly recommended that the PCB design provides the ability to connect to this signal – e.g. by means of providing a suitable test point pad on the PCB - for the purpose of analysis, debug and firmware update.

2.8 Test interface (TP1, TP2, TP3)

TCM 515 provides a test interface (TP1, TP2 and TP3). The intended use of this interface is for analysis and debugging of customer products by EnOcean.

It is strongly recommended that customer PCB design provides the ability to connect external devices to these signals – e.g. by means of providing suitable test point pads on the PCB - for the purpose of analysis, debug and firmware update.

2.9 Product label

Each TCM 515 contains a product label as shown in Figure 5 below.

Figure 5 – TCM 515 product label

The label shown above identifies the following parameters in writing:

◼ Product name (TCM 515)

◼ Order number (S3003-K515)

◼ Product revision (DC-10)

◼ Manufacturing date (week 35, 2020)

◼ Manufacturer traceability code (592001002206)

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

2.9.1 QR code

The TCM 515 product label contains an automatically readable QR code in the lower right corner which encodes certain product parameters according to the ANSI/MH10.8.2-2013 standard as listed in Table 2 below.

Data Identifier

Data Length (excluding identifier)

Data Content

30S

8 characters (hexadecimal)

EnOcean Radio ID (EURID)

30P

10 characters (alphanumeric)

Ordering Code

2P

4 characters (alphanumeric)

Step Code and Revision

S

14 characters (decimal)

Serial Number (starts with 01)

Table 2 – TCM 515 product QR code structure

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

3 Power-up, initialization and system operation

After power-up, TCM 515 executes the following steps:

◼ Initialization of the system

TCM 515 initializes all system components and peripherals. After that, TCM 515 transitions to Ready state

◼ Wait for pre-configured delay

This delay allows the power supply to stabilize and the external host to initialize the system. The default value of this delay is 200 ms; this is configurable This delay can be configured as persistent parameter (maintained after power down) using the ESP3 command CO_WR_STARTUP_DELAY.

After that, TCM 515 is in ready for operation depending on the selected TCM 515 operation mode (transmit and receive mode or transmit-only mode).

3.1 Typical operation sequence for transmit and receive mode

The default configuration of TCM 515 is transmit and receive mode. In this mode, TCM 515 is continuously scan for EnOcean radio telegrams in RX state unless it receives a request from the host to transmit a telegram.

If TCM 515 receives a valid EnOcean radio telegram, then it will process this as described in chapter 4 and forward it to the host via ESP3.

If TCM 515 receives a request from the host to transmit a telegram, then it will transition to TX state and transmit the telegram as described in chapter 5. After that, it will automatically transition back to RX state and continue to scan for EnOcean radio telegrams.

Figure 6 below shows a typical operation sequence for transmit and receive mode with manual sleep entry and exit.

Figure 6 – Operation sequence for transmit and receive mode with manual sleep

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

3.2 Typical operation sequence for transmit-only mode

In transmit-only mode, TCM 515 will wait in Idle state until an ESP3 command from the host requesting the transmission of a telegram has been received. It will then transmit the telegram as described in chapter 5 and inform the host once the transmission of a telegram has been completed.

After completion of the telegram transmission, TCM 515 will either transition back to Idle state waiting for the next command from the host (default configuration) or automatically enter Sleep state waiting for a wake-up via ESP3 command (Auto Sleep configuration).

Figure 7 below shows a typical operation sequence for transmit-only mode with automatic sleep entry (Auto Sleep). See chapter 5.7 for a detailed description of transmit-only mode.

Figure 7 – Operation sequence for transmit-only mode with Auto Sleep

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

4 Telegram reception

After start-up, TCM 515 will enter receive state unless TX-only mode is active as discussed in chapter 5.7.

4.1 Telegram reception flow

While in receive state, TCM 515 will wait for valid EnOcean radio telegrams and then performs the following functions:

◼ RX telegram processing

Received data bitstream is processed (detection and removal of preamble, start of frame, end of frame and redundant bits, CRC check, subtelegram merge) and formatted as EnOcean radio telegrams

◼ Repeater handling

Received telegrams are checked if they should be repeated based on the repeater mode configured at TCM 515 (L1 Repeater, L2 Repeater, Selective Repeater) and the repeater information reported as part of the radio telegram. If the received telegram should be repeated, then it will be inserted into the transmission queue. See chapter

5.7 for details on the repeater functionality.

◼ Telegram filtering

Received telegrams can be classified according to user-defined characteristics so that only telegrams matching these characteristics will be processed and forwarded to the external host via the ESP3 interface. See chapter 4.2 for details.

◼ Security processing

Telegrams from senders using high security mode can be automatically decrypted and authenticated according to their security parameters stored in the inbound secure link table. See chapter 7 for details.

◼ ESP3 formatting and telegram forwarding

Processed telegrams will be formatted as ESP3 packet (RADIO_ERP1 or RADIO_ERP2) and forwarded to the external host via the ESP3 interface. See chapter 9 for details.

Figure 8 below shows the processing flow for received telegrams.

Figure 8 – Telegram Reception Flow

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

4.2 Telegram filtering

By default, TCM 515 will forward all valid telegrams received by it (including such that are addressed to a different receiver) to the host via its ESP3 interface.

Additionally, TCM 515 will repeat all received telegrams if repeating is enabled.

Filtering allows the host to configure via the ESP3 interface conditions based on which telegrams are forwarded to the host or repeated. Telegram filtering is based on the following parameters:

◼ Filter type

The filter type defines based on what property TCM 515 should evaluate in received telegrams, e.g. if it should check the source address, the destination address, the telegram type or the signal strength

◼ Filter value

The filter value defines the reference value against which TCM 515 will compare the property of the received telegram

◼ Filter condition

The filter condition defines the desired relation between the defined filter value and the corresponding property of the received telegram. For the case of source address, destination address and RORG, the filter condition can be Equal (e.g. the source address of received telegram is the same as the defined filter value) or Not Equal (e.g. the RORG of the received telegram is not the same as the defined filter value). For the case of signal strength, the filter condition can be Lower Than Or Equal (the received signal strength is lower than the defined value or equal to it) or Higher Than (the received signal strength is higher than the defined value).

◼ Filter action

The filter action defines what TCM 515 should do if the filter condition is true, e.g. if it should forward the telegram to the host or if it should forward the telegram to the host and repeat the telegram

◼ Filter combination

The filter combination defines what happens if more than one filter condition is defined for a specific set filter action, e.g. if the filters controlling telegram forwarding to the host should be combined in a logic OR fashion or a logic AND fashion.

The following chapters describe these parameters in more detail.

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

4.2.1 Filter type

TCM 515 supports the following filter types:

◼ Source EURID Filter

The source EURID (EnOcean Universal Radio ID = EURID of the sender of the telegram) is evaluated. This filter type can for instance be used in actuators which only accept input from certain devices (e.g. switches) identified by their EURID

◼ Destination EURID Filter

The destination EURID (EnOcean Universal Radio ID = EURID of the intended receiver of the telegram) is evaluated. This filter type can for instance be used by a receiver to not repeat radio telegrams that are directly addressed to it (and therefore do not need to be received by other devices).

◼ Telegram Type (RORG) Filter

The telegram type of the received telegram is evaluated. This filter type can be used for instance be used in actuators which should react only to switch telegrams (RPS Telegram Type).

◼ Received signal strength (RSSI) Filter

The received signal strength (RSSI) of the received telegram is evaluated. This filter type can for instance be used during learn-in if an actuator should only accept teach-in telegrams from devices close to the receiver. Alternatively, this filter type could also be used in repeaters so that only telegrams with weak signal strength (low RSSI value) would be repeated in order to limit radio congestion.

4.2.2 Filter value

The filter value field contains the value against which the corresponding property of the received telegram is compared. The filter value field is 4 byte long and – depending on the configured filter type - contains the following:

◼ 32 bit Source EURID (radio address of the sender)

◼ 32 bit Destination EURID (radio address of the intended receiver)

◼ 8 bit RORG

The RORG value has to be allocated in the least significant byte and the remaining 3 byte of the value field should be set to 0x000000

◼ 8 bit RSSI

The RSSI value has to be allocated in the least significant byte and the remaining 3 byte of the value field should be set to 0x000000. The absolute value of the desired RSSI shall be entered, i.e. an RSSI threshold of -80 dBm is desired then the value 80 shall be entered

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

4.2.3 Filter condition

TCM 515 supports the following filter conditions for Source ID, Destination ID and RORG:

◼ Is Equal

The value in the received telegram is the same as the defined filter value

◼ Is Not Equal

The value in the received telegram is different from the defined filter value

TCM 515 supports the following filter conditions for signal strength (RSSI):

◼ Is Less Than Or Equal (used instead of the Is Equal condition for RSSI)

If the defined signal strength (RSSI) value is -50 dBm then received telegrams with signal strength – 50 dBm, -51 dBm, …, -98 dBm will all match this condition. Note that TCM 515 cannot receive signals with a signal strength below the specified RX sensitivity.

◼ Is Greater Than (used instead of the Is Not Equal condition for RSSI)

If the defined signal strength (RSSI) value is -50 dBm then received telegrams with signal strength -49 dBm, -48 dBm, … -17 dBm will all match this condition. Note that TCM 515 cannot receive signals with a signal strength above the specified maximum input power.

4.2.4 Filter action

TCM 515 supports two types of filter actions:

◼ Forward the received telegram to the host via ESP3 function

This filter is ignored for the repeater function

◼ Forward the received telegram to the host via ESP3 interface and

Repeat (retransmit) the received telegram if selective repeating is enabled

Note that the filter action for telegram repeating is only considered if the repeater functionality is configured for Selective Repeating as described in chapter 6.1.

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

4.2.5 Filter combination

For each of the two actions (telegram forwarding to the host, telegram repeating) it is possible to define one or several filters.

The combination between the defined filters for the same filter action can either be a logical AND (all filter conditions must be true in order to execute the filter action) or a logical OR (one of the filter conditions must be true in order to execute the filter action). For the case of selective repeating, filters with condition / action codes 0x00 and 0x40 will be ignored when evaluating the defined filters.

TCM 515 support the definition of up to 30 individual filters in total. Attempting to define more than 30 filters will result in the response 01: RET_ERROR (memory space full).

4.2.6 Filter definition

Telegram filters are defined using the CO_WR_FILTER_ADD command as shown in Table 3 below.

Group

Offset

Size

Field

Value hex

Description

- 0 1

Sync. byte

0x55

Header

1

2

Data Length

0x0007

7 bytes

3

1

Optional Length

0x00

0 byte

4

1

Packet Type

0x05

0x05: COMMON_COMMAND

- 5 1

CRC8H

0xnn

Data

6

1

COMMAND Code

0x0B

0x0B: CO_WR_FILTER_ADD

7

1

Filter type

0x00…0x03

Telegram property that will be evaluated 0x00: Source EURID 0x01: Telegram type (RORG) 0x02: Received signal strength (RSSI, in dBm) 0x03: Destination EURID

8

4

Filter value

0xnnnnnnnn

Value to compare against

- Source EURID (4 byte)

- RORG (1 byte)

- Signal strength (1 byte, interpreted as negative of this value, e.g. 85 means -85 dBm)

- Destination EURID (4 byte)

12

1

Filter condition and action

0x00 0x80 0x40 0xC0

0x00: Forward to host if condition is false Ignore this filter for selective repeating 0x80: Forward to host if condition is true Ignore this filter for selective repeating 0x40: Forward to host if condition is false Repeat telegram if condition is false 0xC0: Forward to host if condition is true Repeat telegram if condition is true

-

13

1

CRC8D

0xnn

Table 3 – Syntax for CO_WR_FILTER_ADD

Note that if the filter value is only 8 bit long (for RORG or RSSI filters) then the remaining bits of the filter value field should bet set to 0x000000.

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

4.2.7 Filter enabling

Once all filters have been defined, the CO_WR_FILTER_ENABLE command shown in Table 4 below has to be used to select the logical relation between the defined filters (logical AND versus logical OR) and to enable the filtering mechanism for telegram forwarding via ESP3.

Note that the combination between the defined filters can be set independently for the host filters determining if a received telegram will be forwarded to the host via the ESP3 interface and the repeater filters determining if a received telegram will be repeated.

Group

Offset

Size

Field

Value hex

Description

- 0 1

Sync. byte

0x55

Header

1

2

Data Length

0x0003

3 bytes

3

1

Optional Length

0x00

0 byte

4

1

Packet Type

0x05

0x05: COMMON_COMMAND

- 5 1

CRC8H

0xnn

Data

6

1

COMMAND Code

0x0E

0x0E: CO_WR_FILTER_ENABLE = 14

7

1

Forward Filter ON/OFF

0x00 0x01

0x00: Forwarding filter disabled 0x01: Forwarding filter enabled

8

1

Filter Operator

0x00 0x01 0x08 0x09

0x00: OR connection between all filters 0x01: AND connection between all filters 0x08: OR connection between host filters AND connection between repeater filters 0x09: AND connection between host filters OR connection between repeater filters

- 9 1

CRC8D

0xnn

Table 4 – Syntax for CO_WR_FILTER_ENABLE command

The use of the defined filters for the repeater is enabled separately by means of the CO_WR_REPEATER command shown in Table 23 in chapter 446.1. There, REP_ENABLE has to be set to 0x02 to enable selective repeating based on the defined filters.

Note that if a filter is set to be ignored for the cases of repeating (filter condition / action 0x00 or 0x80), then this filter will not be evaluated and the result of the evaluation of the other filters (not set to be ignored) will not be influenced by it.

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

4.2.8 Filter reading

It is possible to read the currently defined filters using the CO_RD_FILTER command shown in Table 5 below.

Group

Offset

Size

Field

Value hex

Description

- 0 1

Sync. byte

0x55

Header

1

2

Data Length

0x0001

1 byte

3

1

Optional Length

0x00

0 byte

4

1

Packet Type

0x05

0x05: COMMON_COMMAND

- 5 1

CRC8H

0xnn

Data

6

1

COMMAND Code

0x0F

0x0F: CO_RD_FILTER

- 7 1

CRC8D

0xnn

Table 5 – Syntax for CO_RD_FILTER

TCM 515 will reply to the CO_RD_FILTER command with a response containing all defined filters as shown in below.

Group

Offset

Size

Field

Value hex

Description

- 0 1

Sync. byte

0x55

Header

1

2

Data Length

0xnnnn

1 + 5*f bytes (f = number of filters)

3

1

Optional Length

0x00

0 byte

4

1

Packet Type

0x02

0x02: RESPONSE

- 5 1

CRC8H

0xnn

Data

6

1

Return Code

0x00

0x00: RET_OK

7+5*f

1

Filter type

0xnn

Telegram property that will be evaluated 0x00: Source EURID 0x01: Telegram type (RORG) 0x02: Received signal strength (RSSI, in dBm) 0x03: Destination EURID

8+5*f

4

Filter value

0xnnnnnnnn

Value to compare against

- Source EURID (4 byte)

- RORG (1 byte)

- Signal strength (1 byte, interpreted as negative of this value, e.g. 85 means -85 dBm)

- Destination EURID (4 byte)

-

12+5*f

1

CRC8D

0xnn

Table 6 – Syntax of the response to CO_RD_FILTER_ENABLE command

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

4.2.9 Filter deletion

Filters can be deleted individually using the CO_WR_FILTER_DEL command as shown in Table 7 below.

Group

Offset

Size

Field

Value hex

Description

- 0 1

Sync. byte

0x55

Header

1

2

Data Length

0x0007

7 bytes

3

1

Optional Length

0x00

0 byte

4

1

Packet Type

0x05

0x05: COMMON_COMMAND

- 5 1

CRC8H

0xnn

Data

6

1

COMMAND Code

0x0C

0x0C: CO_WR_FILTER_DEL

7

1

Filter type

0x00…0x03

Telegram property that will be evaluated 0x00: Source EURID 0x01: Telegram type (RORG) 0x02: Received signal strength (RSSI, in dBm) 0x03: Destination EURID

8

4

Filter value

0xnnnnnnnn

Value to compare against

- Source EURID (4 byte)

- RORG (1 byte)

- Signal strength (1 byte, interpreted as negative of this value, e.g. 85 means -85 dBm)

- Destination EURID (4 byte)

12

1

Filter action and condition

0x00 0x80 0x40 0xC0

0x00: Forward to host if condition is false Ignore this filter for selective repeating 0x80: Forward to host if condition is true Ignore this filter for selective repeating 0x40: Forward to host if condition is false Repeat telegram if condition is false 0xC0: Forward to host if condition is true Repeat telegram if condition is true

-

13

1

CRC8D

0xnn

Table 7 – Syntax for CO_WR_FILTER_DEL command

It is possible to delete all configured filters using the CO_WR_FILTER_DEL_ALL command as shown in Table 8 below. It is strongly recommended to use this command to clear the filter table from existing entries before starting the filter table configuration.

Group

Offset

Size

Field

Value hex

Description

- 0 1

Sync. byte

0x55

Header

1

2

Data Length

0x0001

1 byte

3

1

Optional Length

0x00

0 byte

4

1

Packet Type

0x05

0x05: COMMON_COMMAND

- 5 1

CRC8H

0xnn Data

6

1

COMMAND Code

0x0D

0x0D: CO_WR_FILTER_DEL_ALL

-

13

1

CRC8D

0xnn

Table 8 – Syntax for CO_WR_FILTER_DEL_ALL command

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

4.2.10 Filter examples

4.2.10.1 Forwarding (ESP3 to host) filter examples

The examples below show common filter conditions for the telegram forwarding of received telegrams to the external host via the ESP3 interface.

// Do not forward telegrams sent from the specified ID // All telegrams will be forwarded except those from the specified ID Filter_type = 0x00 (Sender EURID matches specified value) Filter_value = 0x12345678 (device source ID) Filter_action = 0x00 (Forward to host via ESP3 if condition is false)

// Forward telegrams sent from the specified ID // Only telegrams from the specified ID will be forwarded Filter_type = 0x00 (Sender EURID matches specified value) Filter_value = 0x12345678 (device source ID) Filter_action = 0x80 (Forward to host via ESP3 if condition is true)

// Do not forward telegrams having the specified R-ORG // All telegrams will be forwarded except those having the specified R-ORG Filter_type = 0x01 (R-ORG matches specified value) Filter_value = 0x000000A5 (4BS) Filter_ action = 0x00 (Forward to host via ESP3 if condition is true)

// Forward telegrams with the specified R-ORG // Only telegrams with the specified R-ORG will be forwarded Filter_type = 0x01 (R-ORG matches specified value) Filter_value = 0x00000A5 (4BS) Filter_ action = 0x80 (Forward to host via ESP3 if condition is true)

// Do not forward telegrams with a signal strength below -70dBm (ignore weak telegrams) // Only telegrams with a signal strength greater than -70dBm will be forwarded Filter_type = 0x02 (RSSI is less than or equal the specified value) Filter_value = 0x00000046 (decimal: 70) Filter_ action = 0x00 (Forward to host via ESP3 if condition is false)

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

4.2.10.2 Repeater filter examples

The examples below show possible filter conditions for the telegram repeating of received telegrams (selective repeating). Note that repeating always works in conjunction with forwarding of a telegram to the host, i.e. you can not specify an individual filter to repeat a telegram but not forward it to the host.

// Repeat telegrams sent from the specified EURID (requires REP_ENABLE = 0x02) // Telegrams sent from other senders (with different EURID) will not be repeated Filter_type = 0x00 (Sender EURID matches specified value) Filter_value = 0x12345678 (sender EURID) Filter_action = 0xC0 (Forward to host via ESP3 and repeat telegram if condition is true)

// Repeat telegrams with an RORG other than 0xA5 (requires REP_ENABLE = 0x02) // Telegrams with R-ORG 0xA5 will not be repeated Filter_type = 0x01 (R-ORG matches specified value) Filter_value = 0x000000A5 (4BS) Filter_action = 0x40 (Forward to host via ESP3 and repeat telegram if condition is false)

// Repeat telegrams with a signal strength <= -70dBm (requires REP_ENABLE = 0x02) // Telegrams with a signal strength above -70dBm will not be repeated Filter_type = 0x02 (RSSI is less than or equal the specified value) Filter_value = 0x00000046 (decimal: 70) Filter_action = 0xC0 (Forward to host via ESP3 and repeat telegram if condition is true)

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

4.3 RADIO_ERP1 packet for received telegrams

The telegram payload of received telegrams is forwarded to the external host using the RADIO_ERP1 packet with the structure shown in Table 9 below.

The Data field of the RADIO_ERP1 packet contains the ERP1 telegram (excluding the Hash field used for data verification) as shown in Table 9 below.

Group

Offset

Size

Field

Value hex

Description

- 0 1

Sync. Byte

0x55

Header

1

2

Data Length

0xnnnn

Variable length of radio telegram

3

1

Optional Length

0x07

7 fields fixed

4

1

Packet Type

0x01

RADIO_ERP1 = 1

- 5 1

CRC8H

0xnn

Data

6

x

... ...

Radio telegram without checksum/CRC x = variable length / size

Optional

Data

6+x

1

SubTelNum

0xnn

Number of received subtelegrams If “wait for maturity time” is disabled, then this field will be set to 0 (not applicable)

7+x

4

Destination ID

0xnnnnnnnn

Broadcast: Broadcast ID (FF FF FF FF) ADT: Destination EURID

11+x

1

dBm

0xnn

Highest (best) RSSI value of all received subtelegrams. Value is expressed as positive decimal number (60 means – 60 dBm)

12+x

1

Security Level

0x0n

0x00: Telegram not processed by TCM 515 0x01: Obsolete (old security concept) 0x02: Telegram decrypted by TCM 515 0x03: Telegram authenticated by TCM 515 0x04: Telegram decrypted + authenticated

-

13+x

1

CRC8D

0xnn

CRC8 Data byte; calculated checksum for DATA and OPTIONAL_DATA fields

Table 9 – Syntax of the RADIO_ERP1 packet for received messages

USER MANUAL

TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE

4.4 RADIO_ERP2 packet for received telegrams (TCM 515U only)

TCM 515U uses EnOcean Radio Protocol 2 (ERP2) for radio communication as described in appendix A.2.

To ensure compatibility between TCM 515 (using ERP1) and TCM 515U (using ERP2) from serial interface (ESP3) perspective, TCM 515U by default uses RADIO_ERP1 packets for forwarding received telegrams to the external host via the ESP3 interface.

It is possible to change from this default setting to using RADIO_ERP2 packets using the CO_WR_MODE command as shown in Table 10 below. Note that this command is only supported for TCM 515U; trying to use this command with TCM 515 will result in a response 0x02: RET_NOT_SUPPORTED.

Group

Offset

Size

Field

Value hex

Description

- 0 1

Sync. Byte

0x55

Header

1

2

Data Length

0x0002

2 bytes

3

1

Optional Length

0x00

0 byte

4

1

Packet Type

0x05

COMMON_COMMAND = 5

- 5 1

CRC8H

0xnn

Data

6

1

COMMAND Code

0x1C

CO_WR_MODE = 28

6

1

Mode

0xnn

0x00: Use Radio_ERP1 packets (default) 0x01: Use Radio_ERP2 packets

- 7 1

CRC8D

0xnn

Table 10 – Syntax of CO_WR_MODE (TCM 515U only)

If the use of RADIO_ERP2 packets is selected, then received telegrams will be forwarded to the external host using the Radio_ERP2 packet format shown in Table 11 below.

Group

Offset

Size

Field

Value hex

Description

- 0 1

Sync. Byte

0x55

Header

1

2

Data Length

0xnnnn

Variable length of radio telegram

3

1

Optional Length

0x02

2 fields fixed

4

1

Packet Type

0x0A

RADIO_ERP2 = 10

- 5 1

CRC8H

0xnn

Data

6

x

Raw data

... ...

ERP2 telegram without the first Length byte

Optional

Data

6+x

1

SubTelNum

0xnn

Number of received subtelegrams

If “wait for maturity time” is disabled, then

this field will be set to 0 (not applicable)

7+x

1

dBm

0xnn

Highest (best) RSSI value of all received subtelegrams. Value is expressed as positive decimal number (60 means – 60 dBm)

8+x

1

Security Level

0x0n

0x00: Telegram not processed by TCM 515 0x01: Obsolete (old security concept) 0x02: Telegram decrypted by TCM 515 0x03: Telegram authenticated by TCM 515 0x04: Telegram decrypted + authenticated

-

8+x

1

CRC8D

0xnn

CRC8 checksum

Table 11 – ESP3 structure for RADIO_ERP2 command used for transmission

EnOcean TCM 515 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

1 General description

1.1 Basic functionality

1.2 Technical data

1.3 Physical dimensions

1.4 Environmental conditions

1.5 Packaging information

1.6 Ordering information

2 Functional information

2.1 High-level functionality

2.2 Functional states

2.3 Device interface

2.3.1 Pin-out

2.4 Power supply

2.5 Antenna

2.6 UART interface

2.7 Reset

2.8 Test interface (TP1, TP2, TP3)

2.9 Product label

2.9.1 QR code

3 Power-up, initialization and system operation

3.1 Typical operation sequence for transmit and receive mode

3.2 Typical operation sequence for transmit-only mode

4 Telegram reception

4.1 Telegram reception flow

4.2 Telegram filtering

4.2.1 Filter type

4.2.2 Filter value

4.2.3 Filter condition

4.2.4 Filter action

4.2.5 Filter combination

4.2.6 Filter definition

4.2.7 Filter enabling

4.2.8 Filter reading

4.2.9 Filter deletion

4.2.10 Filter examples

4.2.10.1 Forwarding (ESP3 to host) filter examples

4.2.10.2 Repeater filter examples

4.3 RADIO_ERP1 packet for received telegrams

4.4 RADIO_ERP2 packet for received telegrams (TCM 515U only)