Jump to content

Template:FTX Bluetooth: Difference between revisions

From Teltonika Telematics Wiki
No edit summary
Tag: Reverted
No edit summary
 
(10 intermediate revisions by 2 users not shown)
Line 3: Line 3:
| FTM305
| FTM305
| FTC134
| FTC134
| FTM134
| FTC924
| FTC927
| FTM927
| FTC965
| FTC887
| FTC887
| FTM887 =
| FTM887
| FTC308
| FTM308 =


==Eye-Sensor activity monitoring scenario==
==Eye-Sensor activity monitoring scenario==
Line 46: Line 53:
* The device must be configured to '''log periodic records''' for accurate activity tracking.
* The device must be configured to '''log periodic records''' for accurate activity tracking.
* Ensure the system has sufficient '''storage capacity''' for storing sensor data.
* Ensure the system has sufficient '''storage capacity''' for storing sensor data.
}}


{{#switch: {{{model}}}
 
| FTC305
| FTM305
| FTC134
| FTC887
| FTM887 =
==Eye-Sensor Temperature/Humidity monitoring scenario==
==Eye-Sensor Temperature/Humidity monitoring scenario==


Line 96: Line 97:
* '''IO element updates''' to reflect the latest sensor readings.
* '''IO element updates''' to reflect the latest sensor readings.


{{#switch: {{{model}}}
| FTC305
| FTM305
| FTC134
| FTC887
| FTM887 =
==Eye-Sensor magnet detection scenario==
==Eye-Sensor magnet detection scenario==


Line 134: Line 129:
* The scenario is '''enabled by default''', but users can '''manually enable or disable''' it as needed.
* The scenario is '''enabled by default''', but users can '''manually enable or disable''' it as needed.


==Identification scenario==
===Parameter Description===
'''Authorized Devices List'''
* Maintains a list of devices that have been authenticated and are permitted to connect or be recognized without further checks.
* When a new device is approved, it’s added to this list.
'''Scenario functionality can be divided into 5 states:'''
* '''Idle'''
** Waits for detection or expiration events.
** If a device detected event occurs, transitions to Authorization.
** If a device expired event occurs, transitions to Device Expired.
* '''Authorization'''
** Triggered when a new device is detected.
** Checks if the device is authorized:
*** If not authorized, it returns to Idle (no record generated).
*** If authorized and first occurrence, transitions to Device Online.
*** If authorized and subsequent occurrence, transitions to Device Update.
* '''Device Online'''
** Generates a "Device Online" record (e.g., AVL) for an authorized device’s first recognition.
** Moves the device to the “already authorized devices” list.
** Returns to Idle.
* '''Device Update'''
** Reached if the device is authorized and not in its first occurrence.
** Updates the device record to reflect the new detection time or any changes in state.
** Returns to Idle.
* '''Device Expired'''
** Triggered if the device’s authorization has ended (e.g., time limit expired or device removed from the system).
** If the device is still in the authorization list, generates a “Device Expired” record and removes the device from the authorized list.
** Returns to Idle.
'''Record Generation'''
* Periodic or Eventual: Records related to device detection can be configured with different priorities—Low (periodic) or High (immediate).
* Record Types
** Device Online
** Device Update
** Device Expired
[[Category:{{{model}}} Configuration]]
}}
}}

Latest revision as of 08:54, 2 June 2026