FMB125 Accelerometer Based Features
Accelerometer Calibration
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle‘s axes (see Picture below). Vehicles axes are as follows:
1. X is front.
2. Y is left.
3. Z is down.
Once vehicle‘s axes are calculated, device is considered calibrated.
Note: moving forward along any axis will generate negative values. This means acceleration will generate -X values, accordingly breaking will generate X values. Same goes for other axes.
Configurable parameters can be found at System Settings Accelerometer Auto Calibration
Commands that can be used during calibration:
| Command | Response | Description |
|---|---|---|
| auto_calibrate:set | Yes | Request auto calibration task start |
| auto_calibrate:get | Yes | Request calibration info (time, ground vector, side vector) |
| auto_calibrate:clear | Yes | Request calibration clear from flash and stop calibration task |
| auto_calibrate:status | Yes | Request calibration status and calibration task status |
Auto-calibration
Auto calibration task is launched on one of these conditions (assume calibration is enabled in configuration):
1. Every time device turns on, it checks whether it was previously calibrated and has calibration stored in flash. If device has no calibration in flash, auto calibration task is started.
2. Device calibration was previously disabled by configuration and now is enabled.
3. SMS “auto_calibrate:set” is received. Note: SMS response is sent after calibration has been acquired.
This SMS triggers an SMS response to be sent. Response is sent when calibration is acquired. When 1 hour passes without successful calibration, failed SMS response is sent.
4. Calibrated device’s mean axes of set interval differ more than set amount from desired (0,0,1) calibration is considered inaccurate. Calibration is deleted from flash and auto calibration task started.
After auto calibration task has been started, it will go on indefinitely until satisfactory calibration is acquired.
Data Required
Auto calibration needs to fill two buffers to calibrate the device:
1. All accelerometer data – buffer which collects all data from accelerometer at 10Hz frequency. To fill this buffer set seconds of data samples are needed. When buffer is full, oldest data is dumped and new data is placed into the buffer.
2. Straight accelerometer data – buffer which collects straight accelerations data from accelerometer at 10Hz frequency. To fill this buffer set seconds of data samples (set times Hz samples) are needed. When buffer is full, oldest data is dumped and new data is placed into the buffer. Algorithm rules to acquire these samples:
2.1. GPS fix is present.
2.2. Ignition is on.
2.3. GPS speed is more than 5 km/h.
2.4. GPS heading is equal to last GPS heading (+/-1 degree) at GPS sample rate 1Hz.
2.5. GPS speed more then 5 km/h from last sample (accelerating).
Once both buffers are full, auto calibration is attempted. If calibrated values pass calibration quality threshold, calculated calibration is written to flash as current calibration – device is calibrated.
Note: If GPS fix is lost or ignition is turned off, buffers’ data is dumped and must be gathered from 0 again.
At this point calibration is successfully ended as indication device sends an SMS/GPRS message with Device is calibrated, to recalibrate send:auto_calibrate:set.
Note: SMS/GPRS message will be sent only if auto calibration functionality was triggered by SMS/GPRS message.
For user convenience in case auto calibration functionality fails then notification message will be sent. For exact messages, check algorithm section.
Note: SMS/GPRS message will be sent only if auto calibration functionality was triggered by SMS/GPRS message.
To get current calibration status auto_calibrate:get SMS/GPRS command must be sent to the device. If device is calibrated it will respond with Calibration state: calibrated or otherwise Calibration state: not calibrated. Also this command returns saved Ground and Side vectors.
Re-Calibration
When calibration is present, device checks for re-calibration every 60s indefinitely. Re-calibration requires fix and ignition to run also re-calibration is turned off when vehicle is stopped for more than 15s until conditions are satisfied again. When calibrated device’s mean axes of set interval(calibrated accelerometer data) differ more than set amount from desired (0,0,1) (perfect vehicle’s axes) calibration is considered inaccurate, or device’s position has changed and re-calibration is needed. Calibration is cleared from flash and auto calibration task is started.
Note: turning device around calibrated Z axis will not trigger re-calibration, after turning device around Z axis manual re-calibration is advised. After calibration if quality value is less than 0.80, calibration update functionality is run. Calibration update constantly tries calibrating device in background until 0.80 quality is reached. Calibration update functionality does not change calibration if calculated new calibration quality is less than 0.80.
Towing Detection
Towing Detection is a feature that detects and notifies about unexpected movements of a stationary vehicle, such as towing or theft attempts.
Towing detection is useful in industries like fleet management, vehicle rental, car sharing, automotive insurance, where it is critical to monitor towing, unauthorized use, theft, and similar activities.
Towing detection monitors various acceleration, angle, and duration values to identify unexpected vehicle movements. Timeouts filter out normal behavior, such as getting in and out of the vehicle. The device looks for changes in reference vector values over a certain duration, and a towing event is generated. SMS and call notifications can be made. Additionally, programmable output control can be used to operate external devices such as LEDs and buzzers. The feature also allows you to register more data during the event by changing the “Data Acquisition” mode.
Prerequisites and Important Settings
- All accelerometer-related features depend on proper device mounting, see “Mounting recommendations” [link].
- To send SMS messages and/or make calls, at least one number must be predefined in the “GSM Predefined Numbers” list (“SMS / Call Settings” menu).
- In the “System” menu:
- Pay attention to “Accelerometer Delay Settings” – "Movement Stop Delay” is one of the ways to define when the device exits Towing Detection scenario.
Basic Operation
- You park the vehicle and turn off the ignition.
- The Activation timeout starts. After this timeout, towing detection starts.
- The device monitors whether acceleration and angle values exceed thresholds for the pre-configured duration.
- When thresholds are exceeded, the device reports a towing event. Notifications are made as configured (SMS, call, outputs).
- Event Timeout prevents generating an event if thresholds are exceeded, but the ignition is turned on during this time.
- If configured, “Data Acquisition” mode changes to “Ignition OFF - Moving”.
- Towing detection scenario ends when ignition is turned on, or the device stops moving and does not move for “Movement Stop Delay” duration.
Parameters
Attention! The following parameters depend on hardware/firmware – you may not see them in software:
- Output control
- DOUT ON Duration (ms)
- DOUT OFF Duration (ms)
Where applicable, the table also shows AVL ID values that are directly related to a certain parameter (in parentheses). Always double-check the AVL IDs in the page of your device.
| PARAMETER NAME | PARAMETER ID (RELATED AVL ID) | DESCRIPTION | VALUES |
|---|---|---|---|
| Scenario Settings | 11600 (246) |
Sets the scenario priority level. |
0 = Disable Disable scenario. |
| Eventual Records | 11601 | Toggle appending scenario status to eventual records. | 0 = Disable When enabled, scenario status will be appended only to eventual records. 1 = Enable When disabled, scenario status will be appended in each AVL record. |
| Activation Timeout (min) | 11602 | Sets the timeout after which this scenario is activated. | Minimum value = 0 Maximum value = 65535 |
| Event Timeout (s) | 11603 | Sets a timeout to filter out redundant events (e.g. to ignore movement while entering the vehicle). This parameter delays the checking of Ignition state after "Threshold" and "Angle" values are reached - towing events during this time are ignored. |
Minimum value = 0 Maximum value = 600 |
| Threshold (g) | 11605 | Sets the acceleration threshold value to detect the event. | Minimum value = 0.1 Maximum value = 5 |
| Angle (deg) | 11606 | Sets the angle value used to detect towing when ignition is OFF. | Minimum value = 0.1 Maximum value = 30 |
| Duration (ms) | 11607 | Sets the minimal time period for how long the acceleration and angle values should be higher than "Threshold" to trigger the event. | Minimum value = 1 Maximum value = 5000 |
| Output Control | 60300 | Configures the digital output to be activated when this scenario is entered. | 0 = None DOUTs are disabled in this scenario.
1 = DOUT1 DOUT1 is enabled in this scenario. |
| DOUT ON Duration (ms) | 11609 | Duration for which the selected DOUT signal is ON when the device enters this scenario. Value in milliseconds.
Works together with "DOUT OFF Duration" (for most parameters) - after one duration elapses, the other starts, until the scenario is exited. |
Minimum value = 100 Maximum value = 60000 |
| DOUT OFF Duration (ms) | 11610 | Duration for which the selected DOUT signal is OFF when the device enters this scenario. Value in milliseconds.
Works together with "DOUT ON Duration" - after one duration elapses, the other starts, until the scenario is exited. |
Minimum value = 0 Maximum value = 60000 |
| Make Call to | 11604 | Select the GSM number for the device to make a call upon event. | Number selected from “GSM Predefined Numbers” list in menu “SMS / Call Settings” |
| Send SMS to | 7035 | Sets the GSM number of SMS event recipient. | Number selected from “GSM Predefined Numbers” list in menu “SMS / Call Settings” |
| SMS Text | 8035 | Sets the SMS text that will be sent to SMS recipient when the event is triggered. | Maximum text length = 160 symbols |
| Data Acquisition Change | 11611 | Toggles the option to change "Data Acquisition" mode after a towing event is detected. | 0 = DisableThe device will not change the "Data acquisition" mode. 1 = Enable When towing event is detected, "Data Acquisition" mode will change to "Ignition Off - Moving". |
Excessive Idling
Excessive Idling is a feature that automatically detects if a vehicle is stopped for a prolonged time with a running engine.
Excessive idling detection is essential in industries like logistics and fleet management in general, where fuel consumption efficiency and minimizing environmental impacts are critical.
The Excessive Idling feature combines information from three sources – movement data, ignition status, and delays to enter/exit scenario – to indicate an excessive idling event. When the vehicle remains stationary with the ignition on for longer than “Delay To Enter Idle”, the device generates an event. Additionally, programmable output control can be used to operate external devices such as LEDs and buzzers. The scenario remains active until the vehicle moves for “Delay To Exit Idle” duration, or ignition is turned off.
Prerequisites and Important Settings
- All accelerometer-related features depend on proper device mounting, see “Mounting recommendations” [link].
- To send SMS messages and/or make calls, at least one number must be predefined in the “GSM Predefined Numbers” list (“SMS / Call Settings” menu).
- If you use “GNSS” as “Movement Source”, and there is no GNSS fix, the system defaults to using accelerometer data for movement source.
- In the “System” menu:
- Select the desired “Movement Source” and “Ignition Source”. This influences the basic functionality of the feature.
- Do not set “Movement source” to “Ignition” - this prevents the feature from working correctly, as ignition itself is used to determine excessive idling.
- Pay attention to “Accelerometer Delay Settings” – this can affect the functioning of excessive idling if “Movement Source” is set to “Accelerometer”.
Basic Operation
- You enable the feature and configure the delays to enter/exit the scenario.
- The device constantly checks movement and ignition status.
- When the vehicle stops moving and is idling (movement is 0 and ignition is ON), the device waits for “Delay To Enter Idle” amount of time.
- If the vehicle moves before the “Delay To Enter Idle” elapses, excessive idling is not detected.
- If “Delay To Enter Idle” elapses, excessive idling is detected, and a record is generated. It is sent based on your eventual and periodic record settings. SMS can also be sent. Additionally, digital outputs can be controlled, e.g., to notify the driver by LED or buzzer.
- As the vehicle excessively idles, it may at some point start to move (the driver starts driving again). If it moves for longer than “Delay To Exit Idle”, the device exits the scenario – excessive idling ends. I.e., “Delay To Exit Idle” prevents the vehicle from exiting the scenario due to short bursts of vehicle movement.
Parameters
The availability of the following parameters depends on device hardware and firmware:
- Output control
- DOUT ON Duration (ms)
- DOUT OFF Duration (ms)
- Buzzer
Where applicable, the table also shows AVL ID values that are directly related to a certain parameter (in parentheses). Always double-check the AVL IDs in the page of your device.
| PARAMETER NAME | PARAMETER ID (RELATED AVL ID) | DESCRIPTION | VALUES |
|---|---|---|---|
| Scenario Settings | 11200 (251) |
Sets the scenario priority level. |
0 = Disable Disable scenario. |
| Eventual Records | 11203 | Toggle appending scenario status to eventual records. | 0 = Disable When enabled, scenario status will be appended only to eventual records. 1 = EnableWhen disabled, scenario status will be appended in each AVL record. |
| Delay To Enter Idle (s) | 11205 | Delay before entering the excessive idling state. Defines how long a vehicle with Ignition ON (configured in System>Ignition settings) should not move to enter the excessive idling state. | Minimum value = 0 Maximum value = 3600 |
| Delay To Exit Idle (s) | 11206 | Delay before exiting the excessive idling state. Defines how long a vehicle should be moving with Ignition ON (configured in System>Ignition settings) to exit the excessive idling state. | Minimum value = 0 Maximum value = 3600 |
| Output Control | 11024 | Configures the digital output to be activated when this scenario is entered. | 0 = None DOUTs are disabled in this scenario.
1 = DOUT1 DOUT1 is enabled in this scenario. |
| DOUT ON Duration (ms) | 11201 | Duration for which the selected DOUT signal is ON when the device enters this scenario. Value in milliseconds.
Works together with "DOUT OFF Duration" (for most parameters) - after one duration elapses, the other starts, until the scenario is exited. |
Minimum value = 100 Maximum value = 5000 |
| DOUT OFF Duration (ms) | 11202 | Duration for which the selected DOUT signal is OFF when the device enters this scenario. Value in milliseconds.
Works together with "DOUT ON Duration" - after one duration elapses, the other starts, until the scenario is exited. |
Minimum value = 0 Maximum value = 5000 |
| Buzzer | 11209 | Toggles use of buzzer for event indication. This parameter is available only for devices with integrated buzzer. In such cases, it replaces the “Output control” and related parameters. |
0 = None Buzzer is disabled for this scenario. 1 = Buzzer Buzzer is enabled for this scenario. |
| Send SMS to | 7037 | Sets the GSM number of SMS event recipient. | Number selected from “GSM Predefined Numbers” list in menu “SMS / Call Settings”. |
| SMS Text | 8037 | Sets the SMS text that will be sent to SMS recipient when the event is triggered. | Maximum text length = 160 symbols |
Crash Detection
Crash Detection is a feature that automatically detects crash events by continuously monitoring device accelerometer data.
Crash detection is essential for such applications as fleet management, emergency response, and insurance, where detailed data and immediate notification of vehicle incidents are critical.
A crash is detected when acceleration exceeds the threshold value for a predefined duration. The device then generates detailed event records and can send SMS notifications. The system includes crash counting, classification, and filtering to distinguish between genuine crashes and false positives (such as potholes or sudden braking), using GNSS speed analysis to verify the authenticity of detected events.Crash tracing functionality allows the device to capture comprehensive acceleration, GNSS, and I/O data before, during, and after the crash for detailed analysis.
Prerequisites and Important Settings
- All accelerometer-related features depend on proper device mounting, see “Mounting recommendations” [link].
- To send SMS messages and/or make calls, at least one number must be predefined in the “GSM Predefined Numbers” list (“SMS / Call Settings” menu).
- To get higher quality accelerometer data (accurate direction, not only magnitude) it is recommended to enable “Accelerometer auto calibration” in the “System” menu.
- GNSS fix is required to detect fake crashes – without the fix, the device cannot verify speed changes to distinguish genuine crashes from false positives. Also, GNSS fix is required if you use position-related scenarios.
- To properly receive crash trace data, data protocol in the “System Settings” group (“System” menu) must be set to any protocol except “Codec 8” (e.g., Codec 8 Extended or Codec JSON). This helps to optimize sending crash trace data from device to server.
- To correlate a crash event record to its trace (in the management system you use), enable both "Crash Counter" and "Crash Trace".
- To receive the desired I/O element data with the crash event record: in “I/O” menu(s) of the Configurator, under the “Event Only” column, set the element to “Crash”.
Basic Operation
Basic crash detection
- The device continuously reads accelerometer data, and checks if threshold and duration are exceeded.
- When the configured threshold is exceeded for the specified duration, crash event generation is triggered.
- The device classifies and verifies the crash using various criteria (accelerometer calibration state, GNSS speed dynamics).
Crash trace
- If “Trace Full” is enabled, the device gathers additional information about the crash.
- Acceleration magnitude and direction along X, Y, Z axes. Use “Trace filter” parameter to filter acceleration data.
- GNSS data.
- Any I/O element data configured in the “I/O” menus.
- When “Trace Changes” is selected, the device records data only when acceleration changes exceed 50 mG.
- The device processes data (filtering, resampling, timestamping, etc.).
- The crash end is detected.
- Crash event record is generated and sent.
Crash trace with IMU
This is an optional scenario, for devices with an IMU (gyroscope).
- If “Gyroscope crash trace” is enabled, the device gathers additional information about the crash from the IMU (inertial measurement unit).
- An additional record is generated and sent.
Crash counter
- If “Crash counter” is enabled, the device adds AVL ID 317 to both the crash event packet and the related trace data packets.
Parameters
Attention! The following parameters depend on hardware/firmware – you may not see them in software:
- Threshold (16 g) (mG)
- Accel Duration (s)
- Gyroscope crash trace
- IMU trace duration before crash (s)
- IMU trace duration after crash (s)
Where applicable, the table also shows AVL ID values that are directly related to a certain parameter (in parentheses). Always double-check the AVL IDs in the page of your device.
| PARAMETER NAME | PARAMETER ID (RELATED AVL ID) | DESCRIPTION | VALUES |
|---|---|---|---|
| Scenario Settings | 111400 (247) |
Sets the scenario priority level. |
0 = Disable Disable scenario. |
| Duration (ms) | 11401 | Sets the minimal time period for how long the acceleration value should be higher than "Threshold" to trigger the event. | Minimum value = 0 Maximum value = 1000 |
| Threshold (mG) | 11402 | Sets the acceleration threshold value to detect the event. | Minimum value = 100 Maximum value = 6000 |
| Threshold (16 g) (mG) | 11416 | Acceleration threshold (applicable for devices with max 16 g range accelerometer) | Minimum value = 100 Maximum value = 14000 |
| Send SMS to | 7037 | Sets the GSM number of SMS event recipient. | Number selected from “GSM Predefined Numbers” list in menu “SMS / Call Settings”. |
| SMS Text | 8037 | Toggle filtering of accelerometer data in the crash trace. IF enabled, data is passed through EMA filter with 0.4 beta value (can be changed through serial command). | Maximum text length = 160 symbols |
| Trace Filter | 11412 | Toggle filtering of accelerometer data in the crash trace. IF enabled, data is passed through EMA filter with 0.4 beta value (can be changed through serial command). | 0 = Disable 1 = Enable |
| Crash Trace | 11406 (257) |
Enable tracing of crash events to get additional data about the crash. Related parameters: "Trace ODR", "Accel duration", "GNSS duration". | 0 = Disable Generates only an eventual crash record. 1 = Trace Changes Records timestamps, GNSS data and acceleration values ONLY WHEN acceleration values change my 50 mG or more (saves mobile data). |
| Crash Counter | 11415 (317) |
Toggle crash counter. This allows relating the eventual record of a particular crash with its trace packets by adding IO ID 317 to both. “Crash Counter“ and “Crash Trace“ must be enabled. The first crash will send an eventual record with IO ID 317 value 1. Subsequent crashes will add 1 to the value, overflowing at 255 and starting again from 0. | 0 = Disable 1 = Enable |
| Trace ODR (Hz) | 11410 | Sets the output data rate (frequency) of crash event data recording. | Minimum value = 20 Maximum value = 200/400
|
| Accel Duration (s) | 11407 | Sets monitoring duration of linear accelerometer values before and after crash event. This parameter is available for trackers without a gyroscope (IMU). |
Minimum value = 2 Maximum value = 15 |
| GNSS Duration (s) | 11408 | Sets monitoring duration of GNSS data before and after the crash event. | Minimum value = 2 Maximum value = 30 |
| Gyroscope crash trace | 78112 (1422) |
Gyroscope data is collected and processed simultaneously with accelerometer data. If enabled, collected data will be included in accelerometer + gyroscope crash trace, AVL ID 1422. This parameter is available for trackers that have a gyroscope (IMU) |
0 = Disable 1 = Enable |
| IMU trace duration before crash (s) | 78100 | Accelerometer and gyroscope crash trace duration before the crash. Sum of crash trace durations (before and after the crash) cannot be more than 20 seconds.
This parameter is available for trackers that have a gyroscope (IMU) |
Minimum value = 2 Maximum value = 15
|
| IMU trace duration after crash (s) | 78101 | Accelerometer and gyroscope crash trace duration after the crash. Sum of crash trace durations (before and after the crash) cannot be more than 20 seconds. This parameter is available for trackers that have a gyroscope (IMU) |
Minimum value = 2 Maximum value = 11
|
Unplug Detection
Unplug Detection is a feature that notifies when the device is disconnected from its external power source, and again when reconnected. This feature is available for devices that have an internal battery.
Unplug detection is useful in all industries and applications where uninterrupted tracking and notifications about unplugging are essential, e.g. to detect tampering with the device or disconnection attempts by a person.
The Unplug Detection feature monitors the voltage level of the external power source, e.g. of a car battery to which the tracker is connected. If the voltage level drops below a device-specific value for longer than Unplug Delay, an event is generated and notifications can be sent (SMS, calls). The Speed Threshold parameter helps prevent unwanted unplug events in vehicles with smart alternators.
Prerequisites and Important Settings
- This feature is available for devices that have an internal battery.
- All accelerometer-related features depend on proper device mounting, see “Mounting recommendations” [link].
- To send SMS messages and/or make calls, at least one number must be predefined in the “GSM Predefined Numbers” list (“SMS / Call Settings” menu).
Basic Operation
If Unplug detection scenario is enabled, conditions to determine unplug state are checked every second. Initially external power is checked to set device to appropriate unplug state. If external power is less than 5.25 volts, unplugged state is set, on the other hand, if external power is higher than or equal 5.25 volts, plugged state is set.
It is required 1 to 3 seconds to determine the power loss of a device. Consequently, if a device is not being moved any more after few seconds after removing it from the power source, no event will be generated. This can happen, if a device is quickly throwed on the ground after ripping it off.
Simple mode
- Unplug detection constantly monitors external power source voltage.
- Unplug scenario changes states from plugged to unplugged, when external power is less than 5.25 volts and Unplug delay counter reaches its limit.
- Active Unplug event is recorded and SMS notifications are sent.
- Unplug scenario changes states from unplugged to plugged, when external power is higher than or equal 5.25 volts. It resets Unplug delay counter. Plugged event is generated again and SMS notifications are sent accordingly.
Advanced mode
- Unplug detection constantly monitors external power source voltage and accelerometer source for movement changes.
- Unplug scenario changes states from plugged state to unplugged, when unplugged state detected by accelerometer flag is set to true.
- If Speed Threshold is not exceeded, then unplugged event detected by accelerometer, flag is set to true when external power is less than 5.25 volts and measured accelerometer threshold exceeds 0.31 mg.
Once accelerometer threshold exceeds 0.31 mg it is not going to be measured again until external power will be higher or equal to 5.25 volts.
- Active Unplug event is recorded and SMS notifications are sent.
- Unplug scenario changes states from unplugged state to plugged, when external power is higher than or equal 5.25 volts. Plugged event is recorded and SMS notifications are sent.
Unplug Status After Reset
When Unplug Detection Mode is configured as Advanced, Unplug status is saved to flash memory every time when Unplug status is changed. On the first run after soft/hard reset Unplug status is retrieved from flash memory. After configuration change, if previous Unplug Detection Mode was Simple and current alarm sensor ripped off Unplug Detection Mode is Advanced – Unplug status persists from previous mode. This does not work the other way around when configuration changes from Advanced to Simple.
Unplug Detection with Low Power Mode
When Unplug Detection is being used together with Low Power Mode (LPM), depending on configured Sleep mode it will or will not send Unplug Detection record, make a call, or send SMS message.
In Deep Sleep mode record and SMS will be created but they will not be sent, because entering LPM device immediately enters sleeping mode without checking any of the conditions. Since modem is disabled in Deep Sleep, record and SMS will be sent when device will wake up according to LPM conditions. Call will not be made.
In Online Deep Sleep mode record and SMS will be created and sent as well as call will be made since modem is not being turned off. Link will be closed immediately after sending is completed.
Parameters
Where applicable, the table also shows AVL ID values that are directly related to a certain parameter (in parentheses). Always double-check the AVL IDs in the page of your device.
| PARAMETER NAME | PARAMETER ID (RELATED AVL ID) | DESCRIPTION | VALUES |
|---|---|---|---|
| Scenario Settings | 11500 (252) |
Sets the scenario priority level. |
0 = Disable Disable scenario. |
| Eventual Records | 11501 | Toggle appending scenario status to eventual records. | 0 = Disable When enabled, scenario status will be appended only to eventual records. 1 = Enable When disabled, scenario status will be appended in each AVL record. |
| Detection Mode | 11502 | Toggle between simple and advanced unplug detection modes. | 0 = Simple Detects unplugging according to change in external voltage. Event created when external voltage drops below minimum operating voltage of this device. 1 = Advanced Detects unplugging according to changes in external voltage and accelerometer data. Event created when the accelerometer detects movement and external voltage drops below minimum operating voltage of this device. |
| Speed Threshold (km/h) | 11510 | Sets the speed over which unplug events are ignored. | Minimum value = 0. Maximum value = 5000.
|
| Unplug Delay (s) | 11511 | Sets the value by which to delay an Unplug event. Record is generated only if the unplug event is detected and persists for the delay period. If the unplug state keeps changing during the delay period, the unplug event is ignored. | Minimum value = 0. Minimum value = 3600.
|
| Make Call to | 11503 | Select the GSM number for the device to make a call upon event. | Number selected from “GSM Predefined Numbers” list in menu “SMS / Call Settings”. |
| Send SMS to | 7036 | Sets the GSM number of SMS event recipient. | Number selected from “GSM Predefined Numbers” list in menu “SMS / Call Settings". |
| SMS Text | 8036 | Sets the SMS text that will be sent to SMS recipient when the event is triggered. | Maximum text length = 160 symbols. |
Limitations, Edge Cases
Unplug event may not be generated in Advanced detection mode when GNSS signal quality is poor:
- When the GNSS signal quality is poor, speed values may be incorrectly reported, e.g. non-zero values when the vehicle is actually stationary.
- If, during a real unplug event, this incorrect speed value is higher than the configured Speed Threshold, the unplug event will not be registered.
- In such cases, we recommend setting a higher Speed Threshold value.