User's Manual
Table Of Contents
- 1 General description
- 2 Functional overview
- 2.1 Product description
- 2.2 Functional modes
- 2.3 Reporting interval
- 2.3.1 Energy considerations
- 2.3.2 Standard reporting interval
- 2.3.3 Illumination-controlled reporting interval
- 2.3.4 Temperature-controlled reporting interval
- 2.3.5 Humidity-controlled reporting interval
- 2.3.6 Acceleration-controlled reporting interval
- 2.3.7 Magnet contact sensor-controlled reporting interval
- 2.3.8 Arbitration between reporting intervals
- 3 Sensor functionality
- 4 Product interface
- 5 Radio communication
- 6 Security
- 7 Commissioning
- 8 NFC interface
- 9 NFC registers
- 9.1 NFC memory areas
- 9.2 Device identification NDEF
- 9.3 User information NDEF
- 9.4 NFC HEADER
- 9.5 CONFIGURATION
- 9.5.1 Using the NFC configuration functionality
- 9.5.2 CONFIGURATION area structure
- 9.5.3 NFC_PIN_CODE
- 9.5.4 PRODUCT_ID
- 9.5.5 USER_KEY
- 9.5.6 SECURITY_KEY_MODE
- 9.5.7 SECURITY_MODE
- 9.5.8 EEP
- 9.5.9 SIGNAL
- 9.5.10 LED_MODE
- 9.5.11 FUNCTIONAL_MODE
- 9.5.12 STANDARD_TX_INTERVAL
- 9.5.13 THRESHOLD_CFG1
- 9.5.14 THRESHOLD_CFG2
- 9.5.15 LIGHT_SENSOR_CFG
- 9.5.16 ACC_SENSOR_CFG
- 9.5.17 SOLAR_THRESHOLD
- 9.5.18 SOLAR_TX_INTERVAL
- 9.5.19 LIGHT_THRESHOLD
- 9.5.20 LIGHT_TX_INTERVAL
- 9.5.21 ACCELERATION_THRESHOLD
- 9.5.22 ACCELERATION_TX_INTERVAL
- 9.5.23 TEMPERATURE_THRESHOLD
- 9.5.24 TEMPERATURE_TX_INTERVAL
- 9.5.25 HUMIDITY_THRESHOLD
- 9.5.26 HUMIDITY_TX_INTERVAL
- 9.5.27 MAGNET_CONTACT_TX_INTERVAL
- 9.5.28 ILLUMINATION_TEST_RESULT
- 9.6 USER DATA
- 10 Mechanical interface
- 11 Installation recommendations
- 12 Regulatory notes
- 13 Product history
USER MANUAL
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS
© 2020 EnOcean | www.enocean.com F-710-017, V1.0 STM 550 / EMSI User Manual | v1.4 | November 2020 | Page 30/97
5 Radio communication
STM 550 devices communicate using radio telegrams encoded according to the EnOcean
Equipment Profile (EEP) specification and the EnOcean Alliance Signal Telegram specification
on a radio link according to the EnOcean Alliance Radio Protocol (ERP).
STM 550 uses the ERP1 standard (ISO 14543-3-10) while STM 550U and STM 550J use the
ERP2 (ISO 14543-3-11) standard.
5.1 Radio Frame format
As described above, STM 550 uses ERP1 as radio link while STM 550U and STM 550J use
ERP2.
Note that EnOcean radio transceivers such as TCM 310 or TCM 515 will convert both ERP1
and ERP2 into the same EnOcean Serial Protocol (ESP3) format so that this difference is
normally not noticeable.
5.1.1 ERP1 frame format
The ERP1 radio frame format is shown in Figure 17 below.
RORG DATA SENDER EURID STATUS CRC
Figure 17 – ERP1 Frame Format
The most relevant fields of the ERP1 frame are the following:
◼ RORG (containing the EEP or SIGNAL RORG)
◼ SENDER EURID (Device address of the sender)
◼ DATA (Telegram payload containing the EEP)
5.1.2 ERP2 frame format
The ERP2 radio frame format is shown in below.
LENGTH HEADER EXT_HEADER SENDER EURID DATA CRC
Figure 18 – ERP2 Frame Format
The most relevant fields of the ERP2 frame are the following:
◼ HEADER (including the EEP or SIGNAL RORG)
◼ SENDER EURID (Device address of the sender)
◼ DATA (Telegram payload containing the EEP)