|
|
| (36 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| == Fall Down Detection ==
| | {{Template:Test-A|model=FTC305}} |
| Fall down detection is a feature which is used to detect when a two-wheeler vehicle has fallen over. The scenario uses a combination of accelerometer sensor and GNSS data to determine whether the physical orientation of the vehicle changed in such a way, that would indicate a fall down event.
| |
| | |
| The feature allows to improve safety of the end user, by sending events to the fleet tracking platform indicating that the equipment has fallen over. It can help business meet safety regulations while also helping to keep riders and their equipment safe.
| |
| | |
| This is achieved by the device acquiring a base vector, which will serve as a reference point for when the two-wheeler is upright. This vector is acquired by measuring the accelerometer readings when the GNSS fix is available, GNSS ground speed is 0 and no movement is detected. Once the base vector is acquired, the device will constantly monitor the readings of the accelerometer to calculate the current vector. If the difference in angle between the base vector and the current vector exceed the configured values, a fall down event will be generated and sent to the server.
| |
| | |
| === <u>Prerequisites and Important Settings </u> ===
| |
| | |
| * All accelerometer-related features, including fall down detection depend on secure device mounting to function properly. See “Mounting recommendations” [link].
| |
| * Movement source settings are vital for proper functioning of the feature, since base vector will only be calculated when movement, according to movement source is not detected.
| |
| * It is important to note, that a valid GNSS fix is also neccessery for proper base vector acquiring. Due to this reason, it is not possible for the device to acquire a base vector indoors, for example, inside a garage.
| |
| * If the device is remounted to another vehicle, the base vector will have to be recalculated. Base vector recalculation can be initiated via the SMS/GPRS command '''fall_down_reset'''.
| |
| | |
| === <u> Basic Operation </u> ===
| |
| | |
| * Once the feature is enabled, the device waits until the conditions for base vector calculation are met.
| |
| * Once a valid GNSS fix is available, ground speed is 0 m/s and no movement, according to the configured movement source is detected, the device initiates base vector calculation.
| |
| * The device continuously reads IMU acceleration vectors, until a sufficient number of measurements have been taken.
| |
| * Once the base vector is established, the device will continuously read the current vector and compare it to the base vector.
| |
| * Once the base vector is established, the device will continuously read the current vector and compare it to the base vector.
| |
| If a the angle difference is greater than the configured Activation Angle for more seconds than the configured Activation Timeout, a fall down event will be generated.
| |
| * Once the base vector is established, the device will continuously read the current vector and compare it to the base vector.
| |
| Once the angle difference returns to a value below the configured Activation Angle, the fall down event is considered over. The device returns to the monitoring state.
| |
| | |
| === <u> Parameters list </u>===
| |
| ''Will be added soon''.
| |
| | |
| == Network Jamming Extension with DOUT Control ==
| |
| The Jamming Detection scenario identifies instances of active GSM signal jamming on the device. The modem performs continuous jamming detection and reports any suspicious activity back to the main device.
| |
| | |
| Network jamming detection serves as a useful tool, which provides the crucial benefits of preventing cargo or vehicle theft, ensuring driver safety, and maintaining uninterrupted data flow.
| |
| | |
| When GSM signal jamming is detected, Network Jamming scenario activates. Then it starts a configurable jamming detection delay before generating jamming event. It is intended to reduce false positives. After the timeout ends, the device generates an event record. SMS notification Additionally, if digital output is configured, it activates already installed measures to inform driver or disrupt thieves ( like buzzer, LED indication, locking all doors etc. ).
| |
| | |
| === <u>Prerequisites and Important Settings </u> ===
| |
| * The modem has jamming detection enabled at all times.
| |
| * Network Jamming won’t work with Deep Sleep and Power off sleep modes turned ON. Make sure to check information in Power saving settings.
| |
| | |
| === <u> Basic operation </u> ===
| |
| * The modem continuously always monitors the network, scanning for potential jamming events.
| |
| * Network Jamming detection scenario activates when GSM signal jamming is detected.
| |
| * When GSM signal Jamming is detected, Time until jamming reporting (s) counter starts. It can be configured by user. It is intended to reduce false positives of jamming events.
| |
| * If detected jamming event lasts after entire delay period, device creates a High or Low priority record labeled “Jamming started”. Additionally, if output control is configured, it will activates already installed measures to inform driver or disrupt thieves (like buzzers, LED indication, locking all doors etc.).
| |
| * As soon as jamming stops (after a “Jamming started” record was generated), the device creates a “Jamming ended” record. It is sent immediately if priority level is set to High.
| |
| * Eventual records function lets user choose between sending eventual records of Jamming when enabled. And if disabled – eventual and periodic records are being sent bout Jamming.
| |
| * After jamming event has ended, modem continues monitoring for further jamming events.
| |
| | |
| === <u> Parameters list </u>===
| |
| ''Will be added soon''.
| |
| | |
| == Auto Geofence ==
| |
| The Auto Geofence feature automatically creates a circular geofence zone around a vehicle's last known location after it has been stationary for a specified period. The system then generates alarm events if the vehicle moves outside this zone, or if it moves for a sustained period without a valid GNSS signal.
| |
| | |
| This functionality offers a dynamic layer of security against theft, particularly unauthorized towing, as it arms itself automatically based on vehicle behavior rather than ignition status. It is highly valuable for asset protection where vehicles make frequent, unscheduled stops. The ability to trigger an alarm even without a GNSS fix provides a crucial advantage in scenarios where a signal might be intentionally jammed or lost.
| |
| | |
| The feature operates in two main states. In its "Wait State," it monitors for the vehicle to become stationary with a valid GNSS fix. Once this condition is met for a configured timeout, it creates the geofence and enters the "Active State." In the Active State, it monitors for breaches. The feature can be deactivated and returned to the Wait State by various configurable triggers, such as a change in voltage, a digital input, or the presentation of an authorized iButton.
| |
| | |
| === <u>Prerequisites and Important Settings </u> ===
| |
| * The device must have a reliable GNSS signal and be able to detect its movement status for the feature to arm correctly.
| |
| * If using a deactivation source such as a Digital Input (DIN) or iButton, the corresponding hardware (e.g., ignition connection, iButton reader) must be properly installed and configured.
| |
| | |
| === <u> Basic Operation </u> ===
| |
| The feature's logic is divided into two distinct operational states: Wait State and Active State.
| |
| * '''Entering the Wait State (Arming Process)''':
| |
| ** The system starts in the '''Wait State'''. It continuously checks for two conditions to be met simultaneously: the device must have a valid GNSS fix, and the vehicle must be stationary.
| |
| ** Once both conditions are met, an "Activation timeout" timer begins. If the vehicle moves or loses its GNSS fix at any point, the timer resets.
| |
| ** When the timer successfully completes, the device creates a circular geofence of a configured "Radius" centered on its current location.
| |
| ** Depending on the configuration, an "On Enter" event record can be generated at this point. The system then transitions to the Active State.
| |
| * '''Active State (Monitoring and Alarm Trigger):'''
| |
| ** While in the '''Active State''', the geofence is armed. The system monitors for two primary breach conditions:
| |
| *** '''Condition A:''' The device has a valid GNSS fix, and its current position is outside the created geofence.
| |
| *** '''Condition B:''' The device does not have a GNSS fix, but it detects continuous movement for the duration of the "Activation timeout".
| |
| ** If either of these conditions is met, an "On Exit" event record is generated (if configured), and the system returns to the Wait State.
| |
| * '''Deactivation:'''
| |
| ** The armed geofence can be deactivated, returning the system to the Wait State without generating an alarm. This is achieved when a configured "Deactivate by" source is triggered (e.g., Digital Input 1 becomes active).
| |
| | |
| | |
| === <u> Parameters list </u>=== | |
| ''Will be added soon''.
| |
| | |
| === <u> Limitations, Edge Cases & Additional Notes </u> ===
| |
| * '''Stuck in Wait State:''' The feature will never arm if the conditions are not met. This can happen if the vehicle is constantly moving or if it is parked in a location with no GNSS signal (e.g., an underground garage).
| |
| * '''Movement without GNSS:''' A key capability of this feature is generating an "On Exit" alarm if the vehicle moves for a sustained period without a GNSS fix. This is a critical security measure against signal jamming or loss.
| |
| * '''Deactivation Source:''' The chosen deactivation source is the only way to disarm the feature without triggering an alarm (aside from staying within the geofence). Ensure the source aligns with the intended use case (e.g., using a Digital Input connected to the ignition).
| |
