|
|
| (One intermediate revision by the same user not shown) |
| Line 235: |
Line 235: |
|
| |
|
| | #default = | | | #default = |
| | {{{excessive_idling| |
| | |
| ==Excessive Idling== | | ==Excessive Idling== |
| [[Image:FM Ver4 Excessive Idling Configurator panel.png|right]]
| |
| 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. | | {{{pic_idling|[[Image:Idling.gif|right]]}}} |
| | |
| | ===<u>Introduction</u>=== |
| | Excessive idling scenario is used to detect when a vehicle has stopped for a long time with a running engine. |
| | |
| | ===<u>How it works</u>=== |
| | When vehicle stops for a specific amount of time the scenario is activated, a record will be generated {{#switch: {{{model}}} |
| | | FMP100 | FMB010 | FMB020 | FMC800 | FMM800 | FMM80A | FMT100 | FMC880 | FMM880 | FMB001 |FMB003 |FMC003 |FMM003 |FMM00A = |
| | |
| | | #default = and digital output status will be changed to 1 when configured.}} |
| | You can configure the time it takes to turn on this scenario ('''Delay to Enter Idle'''). Scenario is activated until the vehicle starts moving (movement is detected '''only''' by the accelerometer) and keeps moving for the amount of time that it is configured. You can configure the time it takes to turn off this scenario ('''Time To Exit Idle'''). |
| | |
| | '''Note:''' When there is no GPS fix, the system uses accelerometer data to determine movement. |
| | |
| | *If the ignition is on and the accelerometer detects movement without a GPS fix, the vehicle is not considered idling. |
| | *If the ignition is on but the accelerometer indicates no movement without a GPS fix, the vehicle is considered idling. |
| | *If the ignition turns off during detected excessive idling, an (AVL ID 251) and Value: 0 will be generated. |
| | |
| | ===<u>Parameter description</u>=== |
|
| |
|
| 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.
| | '''Scenario Settings''' |
|
| |
|
| ===Prerequisites and Important Settings===
| | *<b>Disable</b> – Disable scenario |
| * All accelerometer-related features depend on proper device mounting, see “Mounting recommendations” [link]. | | *<b>Low Priority</b> – Device makes an additional record with indication of event cause. |
| * 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). | | *<b>Hight Priority</b> – Device makes an additional record with high priority flag and immediately sends an event packet to the server by GPRS. |
| * If you use “GNSS” as “Movement Source”, and there is no GNSS fix, the system defaults to using accelerometer data for movement source. | | *<b>Panic Priority</b> – Triggers same actions as High Priority, but if GPRS fails, the device sends an AVL packet via SMS (if enabled in SMS settings). |
| * In the “System” menu:
| | |
| ** Select the desired “Movement Source” and “Ignition Source”. This influences the basic functionality of the feature. | | '''Eventual Records''' |
| ** 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”.
| | *<b>Disable</b> – When disabled, scenario status will be appended in each AVL record. |
| | *<b>Enable</b> – When enabled, scenario status will be appended only to eventual records. |
| | |
| | '''Delay to Enter Idle (s)''' – Delay before entering the Excessive Idling state. Defines how long a vehicle with ignition ON should not move to enter the Excessive Idling state. Value in seconds. |
|
| |
|
| ===Basic Operation===
| | '''Delay to Exit Idle (s)''' – Delay before exiting the Excessive Idling state. Defines how long a vehicle with ignition ON should not move to exit the Excessive Idling state. Value in seconds. |
|
| |
|
| * You enable the feature and configure the delays to enter/exit the scenario.
| | {{#switch: {{{model}}} |
| * The device constantly checks movement and ignition status.
| | | FMP100 | FMB010 | FMB020 | FMC800 | FMM800 | FMM80A | FMT100 | FMC880 | FMM880 | FMB001 |FMB003 |FMC003 |FMM003 |FMM00A = |
| * 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.
| |
|
| |
|
| | | #default = |
|
| |
|
| ===Parameters===
| | '''Output Control''' |
|
| |
|
| The availability of the following parameters depends on device hardware and firmware:
| | *'''DOUT ON Duration (ms)''' – Duration for which the selected DOUT signal is ON when the device enters this scenario. Works together with “DOUT OFF Duration” (for most parameters) – after one duration elapses, the other starts, until the scenario exited. |
| * Output control
| | *'''DOUT OFF Duration (ms)''' – Duration for which the selected DOUT signal is ON when the device enters this scenario. Works together with “DOUT ON Duration” (for most parameters) – after one duration elapses, the other starts, until the scenario exited. |
| * 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.
| |
|
| |
|
| <table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
| | '''Note:''' Both DOUT ON and OFF Duration work together – after one duration elapses, the other starts, until the scenario exited. |
| <tr>
| | }} |
| <th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
| |
| <th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER ID (RELATED AVL ID)</th>
| |
| <th style="width:5%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
| |
| <th style="width:6%; vertical-align: middle; text-align: center;">VALUES</th>
| |
| </tr>
| |
| <tr>
| |
| <td style="vertical-align: middle; text-align: center;">Scenario Settings</td>
| |
| <td style="vertical-align: middle; text-align: center;">11200 <br> (251)</td>
| |
| <td style="vertical-align: middle; text-align: center;">Sets the scenario priority level.</td>
| |
| <td style="vertical-align: middle; text-align: left;">
| |
| '''0 = Disable''' Disable scenario.<br>
| |
| '''1 = Low priority''' Device makes an additional record with indication of event cause. <br>
| |
| '''2 = High priority''' Device makes an additional record with high priority flag and immediately sends an event packet to the server by GPRS. <br> | |
| '''3 = Panic priority''' Triggers the same actions as high priority, but if GPRS fails, the device sends an AVL packet via SMS (if enabled in SMS settings).
| |
| </td>
| |
| </tr>
| |
| <tr>
| |
| <td style="vertical-align: middle; text-align: center;">Eventual Records</td>
| |
| <td style="vertical-align: middle; text-align: center;">11203</td>
| |
| <td style="vertical-align: middle; text-align: center;">Toggle appending scenario status to eventual records.</td>
| |
| <td style="vertical-align: middle; text-align: left;">'''0 = Disable''' When enabled, scenario status will be appended only to eventual records.<br> '''1 = Enable'''When disabled, scenario status will be appended in each AVL record. </td>
| |
| </tr>
| |
| <tr>
| |
| <td style="vertical-align: middle; text-align: center;">Delay To Enter Idle (s)</td>
| |
| <td style="vertical-align: middle; text-align: center;">11205</td>
| |
| <td style="vertical-align: middle; text-align: center;">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.</td>
| |
| <td style="vertical-align: middle; text-align: left;">Minimum value '''= 0''' <br>
| |
| Maximum value '''= 3600''' </td>
| |
| </tr>
| |
| <tr>
| |
| <td style="vertical-align: middle; text-align: center;">Delay To Exit Idle (s)</td>
| |
| <td style="vertical-align: middle; text-align: center;">11206</td>
| |
| <td style="vertical-align: middle; text-align: center;">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.</td>
| |
| <td style="vertical-align: middle; text-align: left;">Minimum value '''= 0''' <br>
| |
| Maximum value '''= 3600''' </td>
| |
| </tr>
| |
| <tr>
| |
| <td style="vertical-align: middle; text-align: center;">Output Control</td>
| |
| <td style="vertical-align: middle; text-align: center;">11024</td>
| |
| <td style="vertical-align: middle; text-align: center;">Configures the digital output to be activated when this scenario is entered.</td>
| |
| <td style="vertical-align: middle; text-align: left;">'''0 = None''' DOUTs are disabled in this scenario.
| |
| '''1 = DOUT1''' DOUT1 is enabled in this scenario.<br>
| |
| '''2 = DOUT2''' DOUT2 is enabled in this scenario.<br> | |
| '''3 = DOUT3''' DOUT3 is enabled in this scenario.<br>
| |
| </td>
| |
| </tr>
| |
| <tr>
| |
| <td style="vertical-align: middle; text-align: center;">DOUT ON Duration (ms)</td>
| |
| <td style="vertical-align: middle; text-align: center;">11201</td>
| |
| <td style="vertical-align: middle; text-align: center;">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.
| |
| </td>
| |
| <td style="vertical-align: middle; text-align: left;"> Minimum value '''= 100''' <br>
| |
| Maximum value '''= 5000'''</td>
| |
| </tr>
| |
| <tr>
| |
| <td style="vertical-align: middle; text-align: center;">DOUT OFF Duration (ms)</td>
| |
| <td style="vertical-align: middle; text-align: center;">11202</td>
| |
| <td style="vertical-align: middle; text-align: center;">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.
| |
| </td>
| |
| <td style="vertical-align: middle; text-align: left;">Minimum value '''= 0''' <br>
| |
| Maximum value '''= 5000'''</td>
| |
| </tr>
| |
| <tr>
| |
| <td style="vertical-align: middle; text-align: center;">Buzzer</td>
| |
| <td style="vertical-align: middle; text-align: center;">11209</td>
| |
| <td style="vertical-align: middle; text-align: center;">Toggles use of buzzer for event indication.<br>
| |
| This parameter is available only for devices with integrated buzzer. In such cases, it replaces the “Output control” and related parameters.
| |
| </td>
| |
| <td style="vertical-align: middle; text-align: left;">'''0 = None''' Buzzer is disabled for this scenario.<br>
| |
| '''1 = Buzzer''' Buzzer is enabled for this scenario.</td>
| |
| </tr>
| |
| <tr>
| |
| <td style="vertical-align: middle; text-align: center;">Send SMS to</td>
| |
| <td style="vertical-align: middle; text-align: center;">7037</td>
| |
| <td style="vertical-align: middle; text-align: center;">Sets the GSM number of SMS event recipient.</td>
| |
| <td style="vertical-align: middle; text-align: left;">Number selected from “GSM Predefined Numbers” list in menu “SMS / Call Settings”.</td>
| |
| </tr>
| |
| <tr>
| |
| <td style="vertical-align: middle; text-align: center;">SMS Text</td>
| |
| <td style="vertical-align: middle; text-align: center;">8037</td>
| |
| <td style="vertical-align: middle; text-align: center;">Sets the SMS text that will be sent to SMS recipient when the event is triggered.</td>
| |
| <td style="vertical-align: middle; text-align: left;">Maximum text length = '''160 symbols'''</td>
| |
| </tr>
| |
| </table>
| |
|
| |
|
| | '''Send SMS to''' – Selects the GSM number of SMS event recipient from “GSM Predefined numbers” list. |
| | <br><br> |
| | '''SMS Text''' – Sets the SMS text that will be sent to SMS recipient when the event is triggered.}}} |
| }} | | }} |
|
| |
|
| Line 573: |
Line 504: |
| 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. | | 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. |
|
| |
|
| If Unplug Detection scenario priority is set to High or Panic and sleep mode is set to Deep Sleep, the device waits for 30 seconds before entering Deep Sleep in both Advanced and Simple modes, allowing the generated Unplug record to be sent or the call to be made. | | '''Note:''' If Unplug Detection scenario priority is set to High or Panic and sleep mode is set to Deep Sleep, the device waits for 30 seconds before entering Deep Sleep in both Advanced and Simple modes, allowing the generated Unplug record to be sent or the call to be made. |
|
| |
|
| ==== Simple mode ==== | | ==== Simple mode ==== |
