Page 2
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 7
STM 550 will report immediately if the status (open / closed) of the magnet contact changes or if a change in acceleration measured by the acceleration sensor exceeds a user-defined threshold for the first time.
Page 9
Dimensions (EMSI finished product) 49 mm x 49 mm x 13 mm Note 1: STM 550 is designed for indoor use only and should only be used in the environmental conditions specified below Note 2: Minimum light level required for self-supplied operation with the default product configuration.
Page 10
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS Packaging information 1.5.1 STM 550 STM 550 is delivered in a box of 100 units packed onto 10 trays of 10 units each. Packaging Unit 100 units Packaging Method 10 modules per tray, 10 trays per box...
Page 11
EnOcean Alliance Security Specification. The user interface of STM 550 consists of one button for simple configuration tasks and one LED to provide user feedback. Configuration of STM 550 parameters is also possible via an integrated NFC (ISO 14443) interface.
Page 12
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS 2.2.1 Front side (STM 550) Figure 2 below shows the external interfaces on the front side of the STM 550 module. Figure 2 – STM 550 product interface (front side) 2.2.2...
Page 13
2.2.3 Back side (STM 550) Figure 4 below shows the external interfaces on the back side of the STM 550 module. The orientation indicator points towards the side where the magnet contact is located. Figure 4 – STM 550 product interface (back side) 2.2.4...
Page 14
2.3.2 Standby (Sleep) mode Standby (sleep) mode is the lowest power mode of STM 550 and is the out of the box state of STM 550 upon delivery. It is intended to be used during extended periods without operation such as device storage or transport. In standby mode, STM 550 stops operation and con- serves as much energy as possible.
Page 15
STM 550 can be set into function test mode via the LRN button as described in chapter 5.2 or via the MODE field of the FUNCTIONAL_MODE NFC register as described in chapter 9.8.11.
Page 16
2.3.7 Factory reset mode STM 550 can be reset to its standard settings using factory reset mode. Upon entering this mode, STM 550 will reset all configuration registers to their default settings and then restart operation in standard operation mode.
Page 17
By default, the reporting interval is 60 seconds, i.e. STM 550 will measure and report its status approximately once per minute. STM 550 is designed to add a random timing offset of up to 10% to the configured reporting interval to increase transmission reliability and meet regulatory requirements.
Page 18
Figure 7 – Illumination-controlled reporting interval STM 550 can use either the light level at the solar cell (harvested energy) or the light level at the ambient light sensor to trigger a higher update rate. To enable this feature, use the following steps: 1.
Page 19
Figure 8 below illustrates the use of the temperature-controlled reporting interval. Figure 8 – Temperature-controlled reporting interval STM 550 can use the temperature measured by the temperature and humidity sensor to trigger a higher update rate. To enable this feature, use the following steps: 1.
Page 20
Figure 9 below illustrates the use of the humidity-controlled reporting interval. Figure 9 – Humidity-controlled reporting interval STM 550 can use the humidity measured by the temperature and humidity sensor to trigger a higher update rate. To enable this feature, use the following steps: 1.
Page 21
STANDARD_TX_INTERVAL Figure 10 – Acceleration-controlled reporting interval STM 550 can use acceleration events detected by the acceleration sensor to trigger a higher update rate. To enable this feature, use the following steps: 1. Make sure that the EEP selected using the EEP register as described in chapter 9.8.8 reports acceleration 2.
Page 22
Figure 11 below illustrates the use of the magnet contact sensor-controlled reporting interval. Figure 11 – Magnet contact sensor-controlled reporting interval STM 550 can use the status of the magnet contact to trigger a higher update rate. To enable this feature, use the following steps: 1.
Page 23
3.1.1 Light level STM 550 uses an integrated solar cell which is optimized for indoor lighting conditions. It is designed to achieve best performance for light levels between 50 lux and 2000 lux. Table 1 below provides a summary of the minimum required light level for typical work and school areas in Germany as a reference for typical light levels.
Page 24
Understanding the energy consumption is important to determine the energy balance. STM 550 is designed to operate for one full day (24 hours) based on 200 lux of ambient light available for 6 hours. This means that 6 hours of available light will provide enough energy for 24 hours (6 hours with light, 18 hours without light) of operation.
Page 25
Figure 12 – Spectrum response of the light level sensor Solar cell STM 550 can use SIGNAL telegrams - as described in chapter A.5.2.5 - to report the energy generated by the solar cell. Reporting of the solar cell energy generation level can be enabled and disabled via the SIGNAL register of the NFC interface as described in chapter 9.8.9.
Page 26
+-0.3 °C throughout the entire operation temperature range and an accuracy of better than +-0.2 °C for the typical indoor temperature range. Figure 13 below shows the typical accuracy of the STM 550 temperature sensor as a function of the ambient temperature. Figure 13 – Temperature sensor accuracy To determine the overall system accuracy, the quantization error (reporting step size) de- termined by the selected EnOcean Equipment Profile (EEP) has to be added to this value.
Page 27
(acceleration vector changes). Examples use cases causing such small vibrations include asset utilization (e.g. a motor to which STM 550 is attached is run- ning) or asset movement (e.g. an asset to which STM 550 is attached changes its location).
Page 28
Table 2 – Acceleration sensor parameters Note that increasing the sampling rate will proportionally increase the power con- sumption of STM 550. The sampling rate should only be increased if sufficient ambi- ent light is available or if a backup battery is used.
Page 29
Refer to Chapter 2.2 for the location of the magnet contact sensor within STM 550 and to Chapter 11.7 for mounting instructions. The STM 550 installation kit includes a block magnet suitable for use with its magnet contact sensor. Figure 16 shows the outer appearance of this magnet.
Page 30
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS User interface The STM 550 product interface contains an LED, a LRN button and a backup battery interface as described in chapter 2.2. STM 550 contains an indication LED used to provide user feedback. By default, the LED will blink shortly whenever a telegram is transmitted.
Page 31
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS Backup battery STM 550 provides a backup battery interface to mount a CR1632 battery for cases with insufficient ambient light. The backup battery has to be installed with the negative pole point- ing upwards (i.e.
Page 32
Each STM 550 module contains a product label with a commissioning QR code. Figure 18 shows the STM 550 product label. STM 550U and STM 550J use the same label structure. Note the commissioning QR code (described in chapter 8.2) on the bottom left side.
Page 33
ERP2 (ISO 14543-3-11) standard. Refer to Appendix A for a description of EnOcean Radio Protocol and EnOcean Equipment Profiles. Supported EEP STM 550 supports a wide range of EEP suitable for different use cases. Table 5 below lists the supported EEP. For details about the data format used by these EEP, see: http://tools.enocean-alliance.org/EEPViewer/#1...
Page 34
6.1.1 Default EEP The default EEP used by STM 550 is D2-14-41 (VLD with 9 byte payload). It is possible to select another one of the supported EEP via the EEP register of the NFC configuration interface described in chapter 9.8.8.
Page 35
For backwards compatibility with legacy systems, it is possible to select via NFC a legacy mode using a 3 byte sequence counter to generate a 3 byte signature. STM 550 will use secure chained telegrams (SEC_CDM) if high security mode is used and the telegram payload (including rolling code and CMAC) exceeds 14 byte.
Page 36
The following two tasks are required in this process: Device identification ◼ The receiver needs to know how to uniquely identify this specific STM 550 device. This is achieved by using a unique 48 Bit ID (Source Address) for each STM 550 de- vice. Security parameter exchange ◼...
Page 37
Radio-based commissioning is used to associate STM 550 with other devices by sending a dedicated radio telegram (a so-called commissioning telegram). To do so, STM 550 can transmit a dedicated teach-in telegram identifying its relevant pa- rameters. Transmission of the teach-in telegram is triggered by pressing the LRN button or via the NFC interface by setting the function mode to Learn Mode as described in chapter 9.8.11.
Page 38
NFC interface parameters The NFC interface of STM 550 uses NFC Forum Type 2 Tag functionality as specified in the ISO/IEC 14443 Part 2 and 3 standards. It is implemented using an NXP NT3H2111 Mifare Ultralight tag.
Page 39
NFC functionality is available in certain Android (e.g. Samsung Galaxy S7 or newer) and iOS (iPhone7 or newer, firmware version 13 or newer) smartphones. EnOcean provides the configuration app “EnOcean Tool” for these devices which can be downloaded directly from the respective app store.
Page 40
STM 550 does not use this area and does not interpret its content in any way. The organization of the STM 550 NFC memory map is shown in Table 8 below.
Page 41
The NDEF area contains a device identification string using the NDEF (NFC Data Exchange Format) standard that is readable by most NFC-capable reader devices (including smartphones). An example device identification string from the NDEF area of STM 550 could be: 6PENO+30S000012345678+1P000B0000004C+30PS6221-K516+2PDB06+12Z01234567891234 +3C31+01000000 This NDEF string encodes the parameters shown in Table 9 below.
Page 42
LENGTH ◼ This field identifies the length of the NFC header. For STM 550, this field is set to 0x0A since the header structure is 10 bytes long VERSION ◼ This field identifies the major revision and is set to 0x01 currently ◼...
Page 43
Before making any changes to the default configuration, be sure to familiarize yourself with the functionality of the device and the effect of the intended changes. STM 550 will not ac- cept the setting of non-valid values for its parameters. If any parameter is non-valid then all changes made will be rejected and the previous configuration will be restored.
Page 44
The EnOcean Alliance Product ID uniquely identifies each product within the EnOcean Alli- ance ecosystem. The Product ID consists of a 2 byte manufacturer identification code (as- signed by EnOcean Alliance) and a 4 byte product identification code (assigned by the man- ufacturer.
Page 45
The register SECURITY_KEY_MODE allows selecting if FACTORY_KEY or USER_KEY should be used to encrypt and authenticate STM 550 radio telegrams in high security mode. In ad- dition, it allows disabling the transmission of Secure Teach-in telegrams in order to protect- ing the security key.
Page 46
0b10, 0b11 Table 11 – SECURE LRN TELEGRAM bit field encoding 9.8.7 SECURITY_MODE The register SECURITY_MODE identifies the security settings used by STM 550. Figure 24 below shows the structure of the SECURITY_MODE register. SECURITY_MODE (Default: 0x00) Bit 7 Bit 6...
Page 47
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS 9.8.8 The EEP register determines the EnOcean Equipment Profile (EEP) used by STM 550 for the transmission of data telegrams. Figure 25 below shows the structure of the EEP register.
Page 48
(MID 0x0D) and backup battery status (MID 0x10) is disabled. STM 550 allows additionally to configure at what rate each enabled SIGNAL telegram will be sent using the TRANSMISSION RATE bit field as shown in Table 15 below. If more than one SIGNAL telegram is enabled, then this rate will apply to all enabled telegrams.
Page 51
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS 9.8.12 STANDARD_TX_INTERVAL STM 550 uses a standard reporting interval which can be automatically adjusted based on sensor readings as described in chapter 2.4. The standard reporting interval is set by the register STANDARD_TX_INTERVAL shown in Figure 29 below.
Page 52
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS 9.8.13 THRESHOLD_CFG1 STM 550 can reduce the reporting interval based on the illumination of the solar cell, the light illumination of the light level sensor, the temperature or the humidity as described in chapter 2.4.
Page 54
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS 9.8.14 THRESHOLD_CFG2 STM 550 can reduce the reporting interval based on the acceleration sensor status and the magnet contact status as described in chapter 2.4. The use of these reduced reporting intervals is enabled by the THRESHOLD_CFG2 register shown in Figure 31 below.
Page 55
9.8.15 LIGHT_SENSOR_CFG STM 550 allows the user to select if the reported light level is the one measured by the am- bient light sensor or the one measured by the solar cell. Refer to chapter 4.1 for a descrip- tion of the ambient light sensor and to chapter 4.2 for a description of the solar cell func- tionality.
Page 56
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS 9.8.16 ACC_SENSOR_CFG The operation parameters of the acceleration sensor in STM 550 can be configured using the ACC_SENSOR_CFG registers shown in Figure 33 below. Refer to chapter 4.5 for a de- scription of the acceleration sensor function.
Page 68
9.8.28 ILLUMINATION_TEST_RESULT If STM 550 has executed an illumination test as described in chapter 2.3.5 then the result (the measured average light level at the solar cell) will be stored in the ILLUMINA- TION_TEST_RESULT register shown in Figure 45 below.
Page 73
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS 10.2 Housing The STM 550 installation kit provides a housing for integration of the STM 550 module. Figure 51 below shows the mechanical interface of this housing. Figure 51 – Mechanical interface of STM 550 in housing The housing can be attached to a variety of surfaces using the provided adhesive pad.
Page 74
STM 550 and its correct operation should be verified. To do so, follow these steps: 1. Place STM 550 under bright light (daylight or bright light source) for 5 minutes to provide an initial charge 2. Press the LRN button once so that STM 550 will start operation 3.
Page 75
STM 550 should not be used on fast moving or strongly vibrating parts. ◼ If used as a door sensor, STM 550 should be attached to the stationary door frame Additional, application-specific guidance (for specific use cases) is provided in subsequent chapters.
Page 76
Avoid mounting the sensor in niches or slots with little air flow. When designing your own housing around an STM 550 module, consider the location of the ventilation slots (there are four of them in total) as shown in Figure 54.
Page 77
Figure 55 below. This illustration assumes that STM 550 is placed flat onto a surface parallel to the earth surface (e.g. a table). Figure 55 – Acceleration vector based on device orientation Note that it is not possible to distinguish cases where STM 550 is rotated but its orientation relative to the direction of earth gravity remains the same.
Page 78
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS Figure 57 below illustrates this issue in a practical use case: The position of the window in the left case (window tilt) could be detected if STM 550 ◼ is attached to the window part that is tilted since the orientation of STM 550 relative...
Page 79
In both cases, STM 550 should be attached to the object for which location or utilization shall be monitored. The following chapter gives general guidelines how to do so.
Page 80
11.6 Illumination measurement STM 550 offers the option to measure the ambient light level either via the ambient light sensor or via the solar cell. This can be configured using the LIGHT_SENSOR_CFG register of the NFC interface as described in chapter 9.8.15. By default, the ambient light sensor is used.
Page 81
STM 550 is designed to operate self-supplied with its standard parameters based on 200 lux of illumination at its solar cell for at least 6 hours per day. STM 550 can operate for 4 days without available energy after being exposed to 200 lux for 2 days.
Page 82
Updating the device configuration via the NFC interface requires that STM 550 has sufficient energy to read and process the new parameters. It is therefore recom- mended to provide an initial charge to STM 550 by placing it under bright light for 5 minutes before starting the configuration process.
Page 83
12.1.1 Declaration of conformity Hereby, EnOcean GmbH, declares that this radio equipment is in compliance with the essen- tial requirements and other relevant provisions of Directive 2014/53/EU. A copy of the Dec- laration of Conformity can be obtained from the product webpage at www.enocean.com...
Page 85
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS 12.2.2 FCC OEM requirements In order to use EnOcean’s FCC ID number, OEM integrating STM 550U into own products must ensure that the following conditions are met: The Original Equipment Manufacturer (OEM) must ensure that FCC labeling require- ◼...
Page 90
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS A. Introduction to EnOcean radio protocol This chapter gives a high-level introduction to key aspects of the EnOcean radio protocol to help the understanding of STM 550 radio transmission features. Refer to the EnOcean Radio Protocol 1 (ERP1) specification and the EnOcean Radio Protocol 2 (ERP2) specification for detailed information.
Page 91
CRC is used to verify the integrity of the telegram ◼ A.3 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.
Page 92
A.3.1 Subtelegram timing EnOcean Radio Protocol 1 (ERP1) and EnOcean Radio Protocol 2 (ERP2) uses a repeater-level dependent time slot mechanism for the subtelegram timing during transmission. The sender of a radio telegram will transmit the first telegram immediately upon receiving the request for transmission.
Page 94
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...
Page 96
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS A.5 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 97
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS A.5.2 Common RORG Within EnOcean radio telegrams, the RORG field identifies the telegram type as described in the previous chapter. Table 43 below lists common RORG used for communication in EnOcean systems.
Page 100
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
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 104
This chapter gives a high-level introduction to key aspects of the security protocol used in EnOcean radio networks to help the understanding of security-related features of STM 550. Refer to the EnOcean Alliance Security Specification for a detailed up to date description of all features.
Page 105
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. EnOcean radio systems do not support asymmetric key algorithms.
Page 108
STM 550 / EMSI – ENOCEAN MULTISENSOR FOR IOT APPLICATIONS EnOcean radio systems use an approach where the RLC is used to change the security ma- terial (specifically, the initialization vector – often called Nonce - used by the security algo- rithms together with the security key) to ensure that the encrypted telegram payload and the telegram signature change even when the content of the telegram itself stays the same.
Need help?
Do you have a question about the STM 550 and is the answer not in the manual?
Questions and answers