USER MANUAL
STM 550X / EMSIX
–
ENOCEAN MULTI-SENSOR
© 2020 EnOcean | www.enocean.com F-710-017, V1.0
STM 550x / EMSIx User Manual | v1.0 | February 2020 | Page 30/79
4.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 … Bit
7. 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.
4.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.
4.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.
4.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 19 below.
UTE RORG
0xD4
BYTE0
BYTE1
BYTE2
BYTE3
BYTE4
BYTE5
UTE DATA
CTRL
CHANNEL
MANUFACTURER_ID
FUNC
TYPE
BYTE0
RORG
BYTE5
Figure 19
–
UTE Telegram Structure