| Line 29: |
Line 29: |
| | <td style="width: 8%; text-align:left">Which source (GPS or accelerometer) data will be collected from.</td> | | <td style="width: 8%; text-align:left">Which source (GPS or accelerometer) data will be collected from.</td> |
| | </tr> | | </tr> |
| − | {{{txt_advanced|<tr>
| |
| − | <td style="width: 8%; text-align:left">[[{{{model|FMB1YX}}} Features settings#Advanced Eco Driving|Advanced Eco Driving]]</td>
| |
| − | <td style="width: 8%; text-align:left">When this parameter is enabled device uses an advanced Eco Driving algorithm and sends different IO (maximum, average) elements instead of IO to server. More details about this option is decribed below.</td>
| |
| − | </tr>}}}
| |
| | <tr> | | <tr> |
| | <td style="width: 8%; text-align:left">Eco/Green Driving Duration</td> | | <td style="width: 8%; text-align:left">Eco/Green Driving Duration</td> |
| Line 54: |
Line 50: |
| | </table> | | </table> |
| | | | |
| − | {{{FMT100_eco|==Advanced Eco Driving==
| |
| − |
| |
| − | From 03.25.14.Rev.03 base firmware version new '''[[FMB120_Parameter_list|parameter]]''' has been added (Eco Driving Maximum and Eco Driving Average) to '''[[FMT100]]''' device. This parameter is '''enabled''' by default.
| |
| − |
| |
| − | When this parameter is enabled device uses an advanced Eco Driving algorithm and sends different IO (maximum, average) elements instead of IO to server. When enabled, device does not send Green Driving value IO element '''[[FMT100_Teltonika_Data_Sending_Parameters_ID|254]]'''.
| |
| − | <table class="nd-othertables" style="width: 68%;">
| |
| − | <tr>
| |
| − | <th style="width: 10%; text-align:left; vertical-align:middle; color:black">Parameter name</th>
| |
| − | <th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td style="width: 8%; text-align:left;">Eco Driving Average</td>
| |
| − | <td style="width: 8%; text-align:left;">If Eco/Green driving is enabled and accelerometer is selected as the data source, enabling Eco Driving Average will cause records with Eco Driving event Average value to be saved and send to the server.</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td style="width: 8%; text-align:left;">Eco Driving Maximum</td>
| |
| − | <td style="width: 8%; text-align:left;">If Eco/Green driving is enabled and accelerometer is selected as the data source, enabling Eco Driving Maximum will cause records with Eco Driving event Maximum value to be saved and send to the server.</td>
| |
| − | </tr>
| |
| − | </table>}}}
| |
| | | | |
| | ===Data output=== | | ===Data output=== |
| Line 114: |
Line 91: |
| | For a more visual explanation, take a look at the video made by Teltonika explaining the use-case of Jamming Detection: '''[https://www.youtube.com/watch?v=otQd34WqL54 Teltonika Jamming Detection scenario]''' | | For a more visual explanation, take a look at the video made by Teltonika explaining the use-case of Jamming Detection: '''[https://www.youtube.com/watch?v=otQd34WqL54 Teltonika Jamming Detection scenario]''' |
| | | | |
| − | ==GNSS Jamming==
| |
| − |
| |
| − |
| |
| − | [[Image:GNSS_Jammingass.PNG|{{{general|size}}}|right]]
| |
| − |
| |
| − | GNSS Jamming is the transmission of radio signals that disrupts communications between tracker and satellites by decreasing the signal to noise ratio.
| |
| − | When a device detects GNSS signal jamming, it activates the GNSS Jamming scenario. The device then generates and sends a record to the server, depending on hardware model activates Digital Output and optionally sends SMS notification to configured GSM number. After device regains GNSS signal, Digital Output is immediately deactivated and a new record is sent to the server. This Digital Output activation can be used to trigger measures to disrupt potential thieves using GNSS signal jamming to steal your vehicle.
| |
| − | GNSS Jamming record is stored in AVL ID 318 parameter and has 3 possible values:
| |
| − |
| |
| − | *0 - No Jamming,
| |
| − |
| |
| − | *1 - Jamming warning status, which means that signal and accuracy is disrupted but device is able to hold GPS fix for at least 5 seconds.
| |
| − |
| |
| − | *2 - Jamming critical status, which means that device is not able to acquire GPS fix.
| |
| − |
| |
| − | Worth mentioning, that Jamming Detection can go from any state to any other in 1 second intervals. It is completely dependent on received NMEA data by GNSS receiver. Therefore, it is possible in repeated jamming scenario for the state to rapidly go from 0 to 2 and backwards.
| |
| − | Also, GNSS Jamming functionality is capable to separate indoor areas (e.g. underground parking) from events when jamming is actually happening. This is possible because in-band jamming will affect internal PGA (Programmable Gain Amplifier) degrade, as a result, CNR (Carrier-to-noise ratio) will degrade as well. On the other hand, if CNR degrade is degraded only because of underground or signal covered, internal PGA gain will keep almost the same.
| |
| − |
| |
| − | Eventual Records parameter can be configured: when it is disabled scenario status value will appear in each AVL record, otherwise, it will be appended only to eventual records.
| |
| − |
| |
| − | '''Note:''' GNSS Jamming is only available since 03.28.03.Rev.03 or newer firmware version.
| |
| − |
| |
| − | '''Note:''' GNSS Jamming is not available on 3.80, 3.82 but available on 5.10, 5.1.5, 5.1.8 or newer GNSS module firmware versions. GNSS module version can be checked by SMS\GPRS command - getver
| |
| | | | |
| − | '''Note''' that this scenario will not work with [[{{{model|FMB1YX}}}_Sleep_modes#Deep_Sleep_mode|Deep Sleep]], [[{{{model|FMB1YX}}}_Sleep_modes#Ultra_Deep_Sleep_mode|Ultra Deep Sleep]] and [[{{{model|FMB1YX}}}_Sleep_modes#Online_Deep_Sleep_mode|Online Deep Sleep]] modes, since they disable the device's GNSS module to save power.
| |
| | ==DOUT Control Via Call== | | ==DOUT Control Via Call== |
| | | | |
