Changes

MSP500 Features settings (view source)

Revision as of 16:29, 28 December 2023

2,921 bytes removed ,  16:29, 28 December 2023
m
Text replacement - "Bluetooth(?!®)" to "Bluetooth®"
Line 30: Line 30:  
         <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|MSP500}}} 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 60: Line 56:  
</table>
 
</table>
   −
{{{FMT100_eco|==Advanced Eco Driving==
  −
From 03.25.14.Rev.03 base firmware version new '''[[MSP500_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 '''[[MSP500_AVL_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>
  −
}}}
  −
<br>
  −
===Data output===
  −
----
  −
Data from accelerometer/GPS are continuously monitored and processed and are used to decide whether a harsh event has occurred. If either of three cases is satisfied, an event is generated and a record is saved and sent to the server (MSP500 must be properly configured in order to send the record). Event value is multiplied by 100 before sending/saving record to get more precision when displaying data.{{{text_dout|<br/>}}}<br/><youtube>RlkJELdVGRs</youtube>
  −
  −
===Auto calibration===
  −
----
  −
The auto-calibration process is following:
  −
  −
#The vehicle is stopped.
  −
#There is a straight road ahead.
  −
#Send SMS ''"auto_calibrate:set"'' to the {{{model_2|FMB}}} device.
  −
#Accelerate to >30 km/h for 5 sec.
  −
#{{{model_2|FMB}}} will send a response when calibration is completed successfully.
  −
  −
Calibration is saved to internal flash memory, which means it will stay after a reset.
  −
To check auto-calibration status send a following short text message to the {{{model_2|FMB}}} device: ''"auto_calibrate:get"''.
      
==Over Speeding==
 
==Over Speeding==
−
[[Image:Over_Speeding.gif|{{{general|size}}}|right]]
+
[[Image:MSP500_Over_Speeding.gif|{{{general|size}}}|right]]
 
Over speeding scenario functionality has been modified for the MSP500 hardware.<br />
 
Over speeding scenario functionality has been modified for the MSP500 hardware.<br />
 
Over speeding scenario supports multiple speed sources:
 
Over speeding scenario supports multiple speed sources:
 
     * GNSS
 
     * GNSS
−
     * OBDII (Bluetooth)
+
     * OBDII (Bluetooth®)
 
     * Pulse counter input (vehicle speed sensor signal on AIN wire)
 
     * Pulse counter input (vehicle speed sensor signal on AIN wire)
    
Speed source can be chosen in the configurator Features tab inside Over Speeding box.
 
Speed source can be chosen in the configurator Features tab inside Over Speeding box.
   −
Over speeding activates intermittent buzer sound when vehicles’ speed reaches 95% of set maximum speed to warn the driver. If speed keeps increasing and reaches set maximum speed record is generated & output control may be started. Records are generated the same way as they are in the base over speeding functionality. If output control is enabled set output starts toggling in on and off time periods set in configurator “DOUT ON Duration” & “DOUT OFF Duration” fields. DOUT control and buzzer are canceled when vehicles’ speed decreases to below calculated speed value. This speed value is calculated using configured hysteresis percentage parameter which sets speed drop in percents regarding to set maximum speed (maximum speed value - hysteresis).
+
Over speeding activates intermittent buzer sound when vehicles’ speed reaches 95% of set maximum speed to warn the driver.<br>
−
<br />
+
If speed keeps increasing and reaches set maximum speed record is generated & output control may be started. Records are generated the same way as they are in the base over speeding functionality. If output control is enabled set output starts toggling in on and off time periods set in configurator “DOUT ON Duration” & “DOUT OFF Duration” fields. DOUT control and buzzer are canceled when vehicles’ speed decreases to below calculated speed value. This speed value is calculated using configured hysteresis percentage parameter which sets speed drop in percents regarding to set maximum speed (maximum speed value - hysteresis).
 +
<br>
 
In this example maximum speed value is 80 km/h & hysteresis value is 28%. When actual speed reaches 76 km/h (80 km/h - (80 * 0,05)) buzzer is started. If speed is lowered buzzer stops. If speed keeps increasing set output is activated when max speed is reached. Relay control & buzzer are kept enabled until speed decreases to at least 57 km/h (80 km/h - (80 * 0,28)).
 
In this example maximum speed value is 80 km/h & hysteresis value is 28%. When actual speed reaches 76 km/h (80 km/h - (80 * 0,05)) buzzer is started. If speed is lowered buzzer stops. If speed keeps increasing set output is activated when max speed is reached. Relay control & buzzer are kept enabled until speed decreases to at least 57 km/h (80 km/h - (80 * 0,28)).
 
<br /><br />
 
<br /><br />
Retrieved from "https://wiki.teltonika-gps.com/view/Special:MobileDiff/64312...94423"

Navigation menu