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 33/97
5.2.3 1BS telegram
1 Byte Sensor (1BS) telegrams are identified by the RORG field being set to 0xD5 which is
followed by one byte of payload (Bit0 … Bit7. 1BS telegrams are used exclusively to encode
the status (open / closed) of a binary contact (typically a magnet contact)
The payload of 1BS telegrams encodes either the contact status (1BS Data Telegram) dur-
ing normal operation or identifies a teach-in telegram (1BS Teach-in Telegram).
The distinction between data and teach-in telegrams is made based on the status of Bit4. If
this bit is set to 0 then the telegram is a 1BS Teach-in Telegram; if this bit is set to 1 then
the telegram is a 1BS Data Telegram.
5.2.4 4BS telegram
4 Byte Sensor (4BS) telegrams are identified by the RORG field being set to 0xA5 which is
followed by four bytes of payload (Bit0 … Bit31.
The payload of 4BS telegrams encodes either the sensor status (4BS Data Telegram) dur-
ing normal operation or identifies EEP and manufacturer of the device during teach-in (4BS
Teach-in Telegram).
The distinction between data and teach-in telegrams is made based on the status of Bit28.
If this bit is set to 0 then the telegram is a 4BS Teach-in Telegram; if this bit is set to 1
then the telegram is a 4BS Data Telegram.
5.2.5 VLD telegram
Variable Length Data (VLD) telegrams are identified by the RORG field being set to 0xD2.
They carry a variable length payload which can be between 1 and 14 byte long.
5.2.6 UTE (Universal Teach-in) telegram
Variable Length Data (VLD) telegrams carry a variable length payload, therefore it is not
possible to use one bit at a pre-defined location to distinguish between data and teach-in
telegrams.
Devices communicating using VLD data telegrams therefore use the generic Universal
Teach-in with EEP (UTE) format when transmitting a teach-in telegram. The format of such
UTE telegram is shown in Figure 20 below.
UTE RORG
0xD4
BYTE0 BYTE1 BYTE2 BYTE3 BYTE4 BYTE5
UTE DATA
CTRL CHANNEL MANUFACTURER_ID FUNC TYPE
BYTE0
RORG
BYTE5
Figure 20 – UTE Telegram Structure