EnOcean TCM 515 User Manual
  1. Manuals
  2. Brands
  3. EnOcean Manuals
  4. Control Unit
  5. TCM 515
  6. User manual

EnOcean TCM 515 User Manual

Transceiver gateway module
Hide thumbs Also See for TCM 515:
Table of Contents

Advertisement

Quick Links

Download this manual
USER MANUAL
TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE
TCM 515 EnOcean Transceiver Gateway Module
31.07.2020
Observe precautions! Electrostatic sensitive devices!
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
© 2020 EnOcean | www.enocean.com
F-710-017, V1.0
TCM 515 User Manual | v1.16 | July 2020 | Page 1/114

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the TCM 515 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for EnOcean TCM 515

Summary of Contents for EnOcean TCM 515

  • Page 1 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 © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 1/114...
  • Page 2 Published by EnOcean GmbH, Kolpingring 18a, 82041 Oberhaching, Germany www.enocean.com, info@enocean.com, phone +49 (89) 6734 6890 © EnOcean GmbH, All Rights Reserved © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 2/114...
  • Page 3 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.

  • Page 4: Table Of Contents

    RADIO_ERP2 packet for received telegrams (TCM 515U only) ......29 Wait for RX maturity time ................30 Transparent mode ..................31 RSSI test mode ................... 32 Telegram transmission ................. 34 © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 4/114...
  • Page 5 11.1 Recommended PCB Footprint ..............67 11.2 Device outline ..................68 11.3 Soldering information ................69 11.4 Packaging information ................70 © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 5/114...
  • Page 6 TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE 11.5 Layout recommendations ................. 71 11.6 Power supply requirements ..............72 11.7 Using an SAW Filter with TCM 515 (868 MHz version only) ......72 11.8 Low noise design considerations ............... 73 11.9 Suggested Reset circuit ................74 11.10 Test interface ..................
  • Page 7 B.5 Secure telegram types ................113 B.5.1 Secure teach-in telegram ............... 113 B.5.1.1 Teach-in Info .................... 114 B.5.1.2 Security level format (SLF) ................. 114 © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 7/114...

  • Page 8: General Description

    ◼ 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.

  • Page 9: Technical Data

    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.

  • Page 10: Physical Dimensions

    Packaging Unit / Method 250 units / Tape and reel Ordering information Type Ordering Code TCM 515 S3003-K515 TCM 515U S3053-K515 © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 10/114...

  • Page 11: Functional Information

    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].

  • Page 12: 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.

  • Page 13: Device Interface

    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.

  • Page 14: Power Supply

    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.

  • Page 15: Reset

    TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE 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 –...

  • Page 16: Power-Up, Initialization And System Operation

    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.

  • Page 17: Typical Operation Sequence For Transmit-Only Mode

    TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE 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 tele- gram as described in chapter 5 and inform the host once the transmission of a telegram has been completed.

  • Page 18: Telegram Reception

    After start-up, TCM 515 will enter receive state unless TX-only mode is active as discussed in chapter 5.7. 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 ◼...

  • Page 19: Telegram Filtering

    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 ◼...

  • Page 20: 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 tele- gram) is evaluated. This filter type can for instance be used in actuators which only accept input from certain devices (e.g.

  • Page 21: Filter Condition

    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 ◼...

  • Page 22: Filter Combination

    / 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).

  • Page 23: Filter Enabling

    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. © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 23/114...

  • Page 24: Filter Reading

    COMMAND Code 0x0F 0x0F: CO_RD_FILTER CRC8D 0xnn Table 4 – 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 Sync. byte...

  • Page 25: Filter Deletion

    Packet Type 0x05 0x05: COMMON_COMMAND CRC8H 0xnn Data COMMAND Code 0x0D 0x0D: CO_WR_FILTER_DEL_ALL CRC8D 0xnn Table 7 – Syntax for CO_WR_FILTER_DEL_ALL command © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 25/114...

  • Page 26: Filter Examples

    = 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) © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 26/114...

  • Page 27: Repeater Filter Examples

    = 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) © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 27/114...

  • Page 28: Radio_Erp1 Packet For Received Telegrams

    CRC8 Data byte; calculated checksum for DATA and OPTIONAL_DATA fields Table 8 – Syntax of the RADIO_ERP1 packet for received messages © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 28/114...

  • Page 29: Radio_Erp2 Packet For Received Telegrams (Tcm 515U Only)

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

  • Page 30: Wait For Rx Maturity Time

    TCM 515 can be configured to wait for the RX maturity time (100 ms) after reception of a subtelegram in order to determine the number of received subtelegrams. TCM 515 will in that case report the actual number of received subtelegrams to the external host.

  • Page 31: Transparent Mode

    Transparent mode In certain applications all higher level protocol handling (encryption, decryption, authentica- tion, telegram chaining) is executed by the external host and TCM 515 is used as simple transmitter / receiver only. Starting with product version DC, TCM 515 can be configured to operate in transparent mode to disable all higher-level protocol handling in TCM 515.

  • Page 32: Rssi Test Mode

    (if filter criteria have been configured). If this is the case and RSSI Test Mode is enabled, then TCM 515 will report the signal strength and the repeater level for each received telegram using a SIGNAL telegram with MID (type) 0x0A. The payload format for a SIGNAL telegram with MID=0x0A is shown in Table 14 below.
  • Page 33 0b0010: Two-time repeated telegrams received peater level 0b0011 … 0b1110: Reserved 0b1111: Maximum repeater level unknown Table 14 – Syntax for SIGNAL 0x0A © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 33/114...

  • Page 34: Telegram Transmission

    TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE Telegram transmission TCM 515 will enter transmit state if it receives radio telegrams for transmission from the external host via the ESP3 interface or if repeating is enabled and a telegram is received that has to be repeated based on the defined conditions.

  • Page 35: Radio_Erp1 Packet For Telegram Transmission

    Table 15 – ESP3 structure for RADIO_ERP1 packet used for transmission TCM 515 will respond to the RADIO_ERP1 command immediately with the RESPONSE mes- sage 00: RET_OK if TCM 515 can transmit the message (correct format used in the command and duty cycle limit not active).

  • Page 36: Radio_Erp2 Packet For Telegram Transmission (Tcm 515U Only)

    The structure of the RADIO_ERP2 packet is shown in Table 16 below. It is only supported for TCM 515U (902 MHz ERP2). Trying to use the RADIO_ERP2 packet with TCM 515 (868 MHz ERP1) will result in response 02: RET_NOT_SUPPORTED.

  • Page 37: Radio_Message Packet For Telegram Transmission

    14 byte (broadcast) / 9 byte (addressed) of payload. Using RADIO_MESSAGE therefore allows using the same command for telegram transmission on all TCM 515 products irrespective of the payload length and the radio protocol that is used. The structure of the RADIO_MESSAGE packet is shown in Table 17 below.

  • Page 38: Using Base Id For Transmission

    Table 18 – CO_WR_IDBASE Alignment is automatically enforced within TCM 515, i.e. if a non-aligned address is provided in the ESP3 command then TCM 515 will use the next lower aligned address as start address of the Base ID range.

  • Page 39: Duty Cycle Limit

    European radio regulation mandates that the duty cycle limits of radio transmitters have to be enforced by technical means. TCM 515 (868.3 MHz ERP1) therefore implements a hard- ware duty cycle monitor which enforces the regulatory duty cycle limit of 1% per hour.

  • Page 40: Determining Available Transmission Time

    0xnn Table 19 – CO_RD_DUTYCYCLE_LIMIT The response from TCM 515 will specify both the already used percentage of available trans- mission time within the current time slot (0% … 100%) and the remaining time (in seconds) until the start of the next time slot as shown in Table 20.

  • Page 41: Transmit-Only Mode

    Sleep state in the same way as if it had received a CO_WR_SLEEP command with parameter 0x0000. TCM 515 will remain in Sleep state until it is woken up again via an ESP3 command. Please refer to chapter 8 for a detailed description of Sleep state.

  • Page 42: Telegram Repeating

    5.7. If TCM 515 is configured to act as repeater and it receives a radio telegram that it has to repeat, then TCM 515 will automatically transition from receive to transmit state to re-trans- mit (repeat) this telegram.

  • Page 43: Configuration Of Telegram Repeating

    USER MANUAL TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE Configuration of telegram repeating The telegram repeating functionality of TCM 515 is configured using the ESP3 command CO_WR_REPEATER as shown in Table 22 below. Group Offset Size Field Value hex Description Sync.

  • Page 44: Security Processing

    32 remote devices using its secure link table. For each such connection, TCM 515 maintains separate security keys and rolling codes for the communication to the remote device (outbound, transmission using KEY1 and RLC1) and for communication from the remote device (inbound, reception using KEY2 and RLC2) as discussed in chapter B.4.1.

  • Page 45: Telegram Processing Flow

    7.7. If a high security radio telegram is received from a device that has not been teched-in then TCM 515 will report forward the high security telegram without processing to the host for further analysis. Figure 11 below illustrates the high-level processing flow for received EnOcean high security radio telegrams.

  • Page 46: Secure Link Table

    TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE Secure link table TCM 515 stores all required information for secure communication with a remote device in the secure link table. The secure link table can store up to 32 entries in order to manage secure connection to up to 32 remote devices.

  • Page 47: Secure Link Table Parameters

    515 can communicate based on the parameters for this entry Security Key ◼ This field contains the security key used by TCM 515 to transmit telegrams to the remote device (KEY_O) and the security key used by the remote device to transmit telegrams to TCM 515 (KEY_I) ◼...
  • Page 48 USER MANUAL TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE The security processing in TCM 515 supports both secure messages that specify the original telegram type (RORG) and those who don’t. Table 23 below summarizes the different RORG supported by TCM 515 security processing.

  • Page 49: Telegram Encryption And Decryption

    TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE Telegram encryption and decryption TCM 515 used the AES-128 algorithm together with a 16 byte security key and an RLC to encrypt and decrypt radio telegrams as described in chapter B.2. TCM 515 supports both VAES and AES-CBC modes of the AES-128 algorithm. The mode which is used can be selected using the ENCRYPTION_ALGO field in the SLF described in chapter B.5.1.2.

  • Page 50: Rlc Support

    TCM 515 supports the use of RLC generated by a monotonously incrementing sequence coun- ter as described in chapter B.4. TCM 515 supports RLC sizes of 16 bit, 24 bit and 32 bit according to the setting of the RLC_MODE field in the SLF as described in chapter B.5.1.2.

  • Page 51: Rlc Roll-Over

    Roll-over allowed in 24 bit explicit RLC mode (SLF = 0b101), consecutive RLC must be within RLC WINDOW CRC8D 0xnn Table 24 – CO_WR_RLC_LEGACY_MODE © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 51/114...

  • Page 52: Rlc Backup

    0xnn Table 25 –CO_WR_RLC_SAVE_PERIOD Using a Save Period of 0 in this command will result in TCM 515 backing up all RLC values in its link table to non-volatile memory leaving the RLC backup interval otherwise un- changed. This is intended for cases of expected power down where volatile data should be stored before power loss.

  • Page 53: Teach-In Of Secure Devices

    It is used to encrypt, decrypt and authenticate telegrams. For the case of transmission, TCM 515 defines the security key that will be used to secure communication. It has to be generated by the external host using a suitable random number generation algorithm.

  • Page 54: Secure Teach-In Procedure

    7.7.2 Secure teach-in procedure Secure teach-in can be performed in two different ways: Using a secure teach-in telegram if TCM 515 is in teach-in mode (see chapter 7.7.3) ◼ TCM 515 can automatically derive the required parameters for telegram encryption, decryption and authentication from such secure teach-in telegram.

  • Page 55: Reception Of A Secure Teach-In Telegram (Teach-In Mode)

    If TCM 515 is not in teach-in mode and it receives a valid (same key, same SLF, same Teach-in Info) secure teach-in telegram then it will adjust its inbound RLC to the RLC speci- fied within this secure teach-in telegram as described in chapter 7.7.3.3.

  • Page 56: Handling Of Secure Teach-In Telegrams If Teach-In Mode Is Not Active

    7.7.3.3 Handling of secure teach-in telegrams if teach-in mode is not active If TCM 515 is not in teach-in mode, then secure teach-in telegrams from unknown senders are ignored. If TCM 515 receives a secure teach-in telegram from a known (previously teched-in) sender containing the correct security key, then the sequence counter information in the TCM 515 secure link table is updated to the value specified in the telegram.

  • Page 57: Teach-In Of Secure Devices Using Esp3

    The security parameters required for secure communication with a remote device can also be setup by the external host via the ESP3 interface. This approach is always used for the case of outbound communication (from TCM 515 to the remote device).
  • Page 58 USER MANUAL TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE Due to the recent addition of the option for using 4 byte rolling code size into the EnOcean Alliance Security Specification, the new command CO_WR_SECUREDEVICEV2_ADD has been defined. This command is supported starting with product revision DB-09 and uses the structure shown in Table 30 below.

  • Page 59: Reporting Of Security-Related Events

    USER MANUAL TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE Reporting of security-related events TCM 515 can report to the host the following security-related events by means of a CO_EVENT_SECUREDEVICES event using the structure shown below. Group Offset Size Field Value hex Description Sync.

  • Page 60: Low Power Sleep Mode

    TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE Low power sleep mode TCM 515 can be set into a low power sleep mode for a defined period of time by means of the CO_WR_SLEEP command shown in Table 32 below. After expiry of the requested sleep period, TCM 515 will automatically wake-up and transition back to receive mode.

  • Page 61: Esp3 Interface

    Gateway Controller is a 3-wire full duplex UART / RS-232 connection (RX, TX, GND). The standard UART baud rate is 57600 baud per second. TCM 515 supports a higher baud rate of 460800 baud per second which can be selected using the command CO_SET_BAU- DRATE as shown in Table 33 below.

  • Page 62: Esp3 Packet Structure

    The Data field encodes the ESP3 command together with the required parameter data. For some commands, the Optional Data field is used to provide additional parameter data. The maximum length of an ESP3 packet in TCM 515 is 255 byte. © 2020 EnOcean | www.enocean.com F-710-017, V1.0...

  • Page 63: Supported Esp3 Commands

    CO_RD_SECUREDEVICE_COUNT to read the number of devices in a link table CO_RD_SECUREDEVICE_BY_INDEX to read a link table entry using its index © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 63/114...
  • Page 64 Messages with up to 255 byte of payload Type 9 Radio Message (ERP1 or ERP2) ◼ Messages with up to 255 byte of payload. TCM 515 will automatically chain (segment) / de-chain (reassemble) messages as needed based on the maxi- mum payload size of EnOcean radio telegrams Type 10: ERP2 Radio Telegram (TCM 515U only, use for reception selected using ◼...

  • Page 65: Persistent Versus Not Persistent Configuration Settings

    TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE Persistent versus not persistent configuration settings TCM 515 will store certain configuration settings in persistent memory, i.e. those settings will be maintained even after a power cycle. There are three classes of persistent settings: 1.

  • Page 66: Remote Management

    TCM 515 provides a transparent radio channel also for remote management messages with a message length of up to 255 bytes. This enables an external micro controller connected to TCM 515 to handle remote management request from external devices or to control other devices via remote management.

  • Page 67: Device Integration

    USER MANUAL TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE Device Integration TCM 515 is designed for integration onto a host PCB. Detailed Gerber data of the device footprint is available from EnOcean. 11.1 Recommended PCB Footprint Figure 14 below shows the recommended PCB footprint for TCM 515.

  • Page 68: Device Outline

    TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE 11.2 Device outline Figure 15 below shows the device outline of TCM 515. Figure 15 – Device outline © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 68/114...

  • Page 69: Soldering Information

    Figure 16 – Recommended soldering profile TCM 515 shall be handled according to Moisture Sensitivity Level MSL4 which means a floor time of 72 h. TCM 515 may be soldered only once, since one time is already consumed at production of the module itself.

  • Page 70: Packaging Information

    TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE 11.4 Packaging information TCM 515 is delivered in Tape & Reel packaging with 250 units per reel. Figure 17 below illustrates the dimensions. Figure 17 – Tape & Reel dimensions of TCM 515 Figure 18 below shows the positioning of TCM 515 in the Tape &...

  • Page 71: Layout Recommendations

    If distortion / radiated noise cannot be minimized to acceptable levels then consider also using the adjustable internal noise filter. See chapter 11.8. © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 71/114...

  • Page 72: Power Supply Requirements

    Radiated emissions from power supply inductors (especially DCDC inductors) towards the TCM 515 RF input must be minimized as they impact RF performance. Place such inductors as much as possible away from TCM 515 or – if this is not possible – consider using switched capacitor designs.

  • Page 73: Low Noise Design Considerations

    11.8 Low noise design considerations For best performance, HW design of TCM 515 systems has to minimize radiated or conducted noise that interferes with the correct reception of RF signals. Strong emphasis should there- fore be placed onto good RF and power supply design to eliminate or minimize the level of noise introduced into the RF path.

  • Page 74: Suggested Reset Circuit

    In order to avoid spurious reset events, it is recommended to filter the input signals by means of a small capacitor which is placed as close as possible to the TCM 515 nRESET pin as shown in Figure 20 below.

  • Page 75: Test Interface

    COMMAND Code 0x27 0x27: CO_GET_STEPCODE Data CRC8D 0xnn Table 36 – CO_GET_STEPCODE TCM 515 will respond to this command with a response as shown in Table 37 below. Group Offset Size Field Value hex Description Sync. byte 0x55 Data Length...

  • Page 76: Antenna Options

    TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE Antenna options This chapter outlines options for antenna that can be used with TCM 515. Note that this chapter is for guidance purposes only, please consult with an authorized certification body for specific information.

  • Page 77: Whip Antenna

    TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE 12.1.1 Whip antenna TCM 515 modules have been certified for use with a whip antenna under EU (RED) regula- tions. Figure 21 below shows key whip antenna parameters. Figure 21 – Whip antenna parameters...

  • Page 78: Antenna Options For 902 Mhz (Us / Canada)

    Minimum distance space: 10 mm ◼ 12.2.2 Helical antenna TCM 515U has been certified for use with the ANT 300 helix antenna from EnOcean which uses the following parameters (see Figure 22): Shape according to drawing below ◼ Minimum GND plane: 35 mm x 30 mm ◼...

  • Page 79: Chip Antenna (Supplier: Mitsubishi Material, Type Am11Dp-St01T)

    Figure 23 – Required layout for AM11DP-ST01T For any further questions or chip antenna quotes, please refer to Mitsubishi Materials website www.mmea.com or email to electroniccomponents@mmus.com. © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 79/114...

  • Page 80: Dipole Antenna (Ant-916-Cw-Hwr-Rps)

    Figure 24 below shows ANT-916-CW-HWR-RPS from Linx. Figure 24 – ANT-916-CW-HWR-RPS Figure 25 below shows RP-SMA- Female from Linx. Figure 25 – RP-SMA-Female © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 80/114...

  • Page 81: Application Information

    The distance between the receiver and other transmitting devices such as computers, WiFi routers, audio and video equipment that also emit high-frequency signals should be at least 0.5 m. © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 81/114...

  • Page 82: Maximum Input Power

    TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE 13.2 Maximum input power The rated maximum input power for TCM 515 is -23 dBm in line with EnOcean Alliance air interface specification. Under ideal conditions (free line of sight connection between two fully stretched whip an- tennas without any housing damping or obstruction) this input power level is equivalent to approximately 10 cm of distance between transmitter and receiver.

  • Page 83: Regulatory Information

    At the time of writing, the text of the RED legislation was available from this link: http://eur-lex.europa.eu/eli/dir/2014/53/oj Dolphin radio modules such as TCM 515 are components which are delivered to OEM manu- facturers for their use in final or combined products.

  • Page 84: Red Attestation Of Conformity For Tcm 515

    USER MANUAL TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE 14.1.1 RED Attestation of Conformity for TCM 515 © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 84/114...

  • Page 85: Fcc (United States)

    TCM 515U has been tested against and is in compliance with FCC Part 15 Subpart B Class B. 14.2.1 FCC Grant Of Equipment Authorization © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 85/114...

  • Page 86: Fcc Usage Conditions

    Because this may depend on the details of how the mod- ule is integrated within the host, EnOcean will provide any guidance to the host manufacturer if needed for the final product for ensuring compliance with the Part 15 Subpart B require- ments.

  • Page 87: Oem Requirements

    TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE 14.2.3 OEM Requirements In order to use EnOcean’s FCC ID number, the OEM must ensure that the following conditions are met: End users of products, which contain the module, must not have the ability to alter ◼...

  • Page 88: Module Activation

    © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 88/114...

  • Page 89: Ised (Former Industry Canada) Certification

    ISED (former Industry Canada) Certification TCM 515U has been tested and meets the requirements of Industry Canada’s license-exempt RSSs. 14.3.1 ISED Technical Acceptance Certificate © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 89/114...

  • Page 90: Ised Usage Conditions

    (2) l'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en compromettre le fonctionnement. In order to use EnOcean’s IC number, the OEM must ensure that the following conditions are met: Labeling requirements for ISED are similar to those required by the FCC. The ◼...

  • Page 91: Repeater Function (Fcc/Ic)

    FCC ID:SZV-STM300U IC:5713A-STM300U ◼ TCM 320U FCC ID:SZV-TCM320U IC:5713A-TCM320U ◼ TCM 330U FCC ID:SZV-STM300U IC:5713A-STM300U ◼ TCM 515U FCC ID:SZV-TCM515U IC:5713A-TCM515U ◼ © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 91/114...

  • Page 92: References

    USER MANUAL TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE References Please use below references for an in-depth description of features supported by TCM 515. EnOcean Serial Protocol 3 EnOcean Radio Protocol 1 (ERP1) EnOcean Radio Protocol 2 (ERP2) Security of EnOcean Radio Networks...

  • Page 93: Product History

    USER MANUAL TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE Product history Table 38 below outlines the product history of TCM 515 and indicates key changes made between different revisions. Revision Release Key features / changes - First product prototypes for lead customer evaluation...

  • Page 94: Introduction To Enocean Radio Protocol

    902.875 MHz radio systems in the US / Canada and 928.35 MHz radio systems in Japan. Note that EnOcean radio transceivers such as TCM 310 or TCM 515 will by default convert received ERP1 and ERP2 telegrams into the same RADIO_ERP1 packet type so that the dif- ference between ERP1 and ERP2 is transparent to the connected host.

  • Page 95: Erp2 Telegram Format

    ◼ Subtelegrams EnOcean radio systems use the concept of redundant subtelegrams in order to increase the communication reliability. In addition to using redundant transmissions, first and second level repeaters can be used to increase communication distance and reliability as described in chapter 6.

  • Page 96: Subtelegram Timing

    20 ms and 29 ms. Both first and second level repeaters do not transmit a third subtelegram. The standard sub- telegram timing is summarized in Table 39 below. It is used both by TCM 515 and TCM 515U. Time Offset [ms]...

  • Page 97: Tx Maturity Time

    Identical subtelegrams from the same sender are considered to belong to the same telegram if they are received within the RX maturity time. In EnOcean radio systems, the RX maturity time is 100 ms. © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 97/114...

  • Page 98: Addressing

    Telegrams where the intended receiver is designated are called Addressed Data Tele- gram or ADT in short. Telegrams where the intended receiver is not designated are called Broadcast Telegrams. Different types of addresses can be used to designate sender and receiver of an EnOcean radio telegram. A.4.1 Address types...

  • Page 99: Eurid (Radio Id)

    Note also that the use of Base ID is not defined within the scope of secure communication. TCM 515 applications shall not use the Base ID functionality for telegrams where TCM 515 is handling the security processing. TCM 515 supports Base ID for the purpose of backwards compatibility.

  • Page 100: Data Payload

    TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE Data payload EnOcean radio systems encode the data using so called EEP (EnOcean Equipment Profile). Each transmitter might choose one (or sometimes several) EEP for data transmission de- pending on the type of transmitted data.

  • Page 101: Common Rorg

    USER MANUAL TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE A.5.2 Common RORG Within EnOcean radio telegrams, the RORG field identifies the telegram type as described in the previous chapter. Table 41 below lists common RORG used for communication in EnOcean systems.

  • Page 102: Data Payload Size

    TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE A.5.3 Data payload size The maximum telegram data payload size used by EnOcean radio telegrams is 14 byte of data payload for the case of standard broadcast telegrams. For the case of standard ad- dressed telegrams, the maximum length of the data payload is 9 byte.

  • Page 103: Telegram Chaining For Broadcast Telegrams

    The theoretical maximum DATA length within a chain of telegrams is 766 byte (63 * 12 byte + 1 * 10 byte). Note that in TCM 515 the maximum length is limited by the maximum size of an ESP3 command accepted by TCM 515 which is 255 byte.

  • Page 104: Telegram Chaining For Secure Telegram (Sec_Cdm)

    (if the data exactly fits into the previous telegram in the chain). Figure 37 – Structure of the last telegram in a chain of secure telegrams © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 104/114...

  • Page 105: Telegram Chaining For Addressed Secure Telegram (Adt Sec_Cdm)

    The last SEC_CDM telegram might therefore be split into two ad- dressed SEC_CDM telegrams due to the addition of the RORG and DESTINATION EURID ad- dressing fields resulting in a telegram size larger than the maximum size of EnOcean radio telegrams.

  • Page 106: Introduction To Enocean Security Protocol

    This chapter gives a high-level introduction to key aspects of the security protocol used in EnOcean radio networks to help the understanding of TCM 515 features. Refer to the EnOcean Alliance Security Specification [4] for a detailed up to date description of all features.

  • Page 107: Telegram Encryption

    If different security keys are used for encryption at the sender and decryption at the receiver then this is called an asymmetric key algorithm or a public key algorithm. Public / private key algorithms such as PGP, GPG or TLS fall into this category. TCM 515 does not support asymmetric key algorithms.
  • Page 108 Figure 42 below illustrates the concept of telegram authorization via a telegram signature. Figure 42 – Telegram authentication via telegram signature © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 108/114...

  • Page 109: Replay Protection

    RLC. Figure 43 below shows the concept of adding an RLC to the telegram data. Figure 43 – Addition of an RLC to the telegram data © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 109/114...
  • Page 110 USER MANUAL TCM 515 – ENOCEAN TRANSCEIVER GATEWAY MODULE TCM 515 uses an approach where the RLC is used to change the security material (specifi- cally, the initialization vector – often called Nonce - used by the security algorithms together with the security key) to ensure that the encrypted telegram payload and the telegram sig- nature change even when the content of the telegram itself stays the same.

  • Page 111: Rlc And Security Key In Bi-Directional Communication

    RLC2 and Key2 together with the address of Device1 in its outbound secure link table. Figure 45 below illustrates that. Figure 45 – Security key and RLC usage in bi-directional communication © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 111/114...

  • Page 112: Rlc Synchronization Between Sender And Receiver

    RLC used by the sender. For systems using TCM 515, this can be done either via a dedicated secure teach-in telegram as described in chapter 7.7.3 or via the ESP3 interface as described in chapter 0.

  • Page 113: Secure Telegram Types

    The 128 bit security key is used by the sender to encrypt and authenticate the trans- mitted telegram and by the receiver to decrypt and authenticate the received telegram © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 113/114...

  • Page 114: Teach-In Info

    Others: RFU 0b110: 32 bit RLC (24 bit transmitted) 0b111: 32 bit RLC (32 bit transmitted) Figure 48 – SLF structure © 2020 EnOcean | www.enocean.com F-710-017, V1.0 TCM 515 User Manual | v1.16 | July 2020 | Page 114/114...

Table of Contents