Changes

26 bytes removed ,  12:19, 30 November 2021
no edit summary
Line 27: Line 27:  
=== '''2. Configurate Tracker Security:'''===
 
=== '''2. Configurate Tracker Security:'''===
   −
====2.1. Set up Keyword: ====
+
====2.1. Set up Keyword:====
 
[[File:Keyword use.gif|thumb|480x480px|alt=|Set up keyword]]
 
[[File:Keyword use.gif|thumb|480x480px|alt=|Set up keyword]]
   Line 53: Line 53:       −
'''2.2. SMS security:'''
+
====2.2. SMS security:====
 
[[File:SMS Security.gif|left|alt=|border|frame|SMS security]]
 
[[File:SMS Security.gif|left|alt=|border|frame|SMS security]]
   Line 66: Line 66:       −
'''<big>2.3 FMBT App</big>'''
+
====2.3 FMBT App====
    
[[FMBT Mobile application]]
 
[[FMBT Mobile application]]
Line 77: Line 77:  
• I/O element status
 
• I/O element status
   −
'''<big>2.4 FOTA WEB</big>'''
+
====2.4 FOTA WEB====
    
To upgrade firmware or make configuration changes, you need to fill up a login and password in your browser that uses HTTPS protocol.  
 
To upgrade firmware or make configuration changes, you need to fill up a login and password in your browser that uses HTTPS protocol.  
Line 87: Line 87:       −
'''<big>2.5 BLE STANDARD AES-128</big>'''
+
====2.5 BLE STANDARD AES-128====
    
Since this version '''03.27.07''' there has been an implementation of BLE transferred data encryption with '''AES128 cipher'''. In '''Bluetooth 4.0 tab''' under '''Settings''' there is a field for a '''AES128 key'''. Which if left empty, the BLE outgoing data will not be ciphered and incoming data will not be decoded. AES128 key field settings showed below.
 
Since this version '''03.27.07''' there has been an implementation of BLE transferred data encryption with '''AES128 cipher'''. In '''Bluetooth 4.0 tab''' under '''Settings''' there is a field for a '''AES128 key'''. Which if left empty, the BLE outgoing data will not be ciphered and incoming data will not be decoded. AES128 key field settings showed below.

Navigation menu