![EnOcean B6221-K516 Скачать руководство пользователя страница 64](http://html1.mh-extra.com/html/enocean/b6221-k516/b6221-k516_user-manual_2413678064.webp)
USER MANUAL
STM 550B / EMSIB - EASYFIT MULTISENSOR FOR IOT APPLICATIONS (2.4 GHZ BLE)
© 2020 EnOcean | www.enocean.com
F-710-017, V1.0
STM 550B / EMSIB User Manual | v1.3 | June 2020 | Page 64 / 115
9.5.12
SECURITY_KEY
The register SECURITY_KEY identifies the 16 byte security key used to authenticate the
data telegrams of STM 550B.
Access to the SECURITY_KEY via this register or via its copy in the NDEF ore PUBLIC INFO
area can be disabled by the user via the SECURITY_KEY_ACCESS register described below.
9.5.13
SECURITY_KEY_ACCESS
The register SECURITY_KEY_ACCESS allows protecting access to the device-unique security
key via the SECURITY_KEY field of the NFC interface or via the transmission of a LRN tele-
gram as described in chapter 7.1.
Figure 45 below shows the structure of the SECURITY_KEY_ACCESS register.
SECURITY_KEY_ACCESS (Default Setting: 0x00)
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3
Bit 2
Bit 1
Bit 0
RFU
LRN_TEL_ACCESS
NFC_ACCESS
Figure 45
–
SECURITY_KEY_ACCESS register
The encoding for the NFC_ACCESS bit field is shown in Table 18 below.
NFC_ACCESS
Security key access via NFC
0b00 (Default)
Public NFC Access: Security key visible in NFC, No NFC PIN required
0b01
Private NFC Access: Security key visible in NFC, NFC PIN required
0b10
No NFC Access: Security key not visible in NFC
0b10
Reserved, do not use
Table 18
–
NFC_ACCESS bit field encoding
The encoding for the LRN_TEL_ACCESS bit field is shown in Table 19 below.
LRN_TEL_ACCESS
Security key access via LRN telegram
0b0 (Default)
LRN Telegram (containing security key) enabled
0b1
LRN Telegram (containing security key) disabled
Table 19
–
LRN_TEL_ACCESS bit field encoding