Difference between revisions of "Template:FMB640 Trip/Odometer settings"

From Wiki Knowledge Base | Teltonika GPS
Line 3: Line 3:
 
[[Image:Fmb640_trip_settings.png|300px|right]]
 
[[Image:Fmb640_trip_settings.png|300px|right]]
  
''Trip'' section offers user to configure the ''Trip'' feature. ''Start Speed'' defines the minimum GPS speed in order to detect ''Trip'' start.<br/>''Ignition OFF Timeout'' is the timeout value to detect ''Trip'' end once the Ignition (configured ignition source) is off.<br/>I/O Trip Odometer must be enabled to use ''Distance counting mode'' feature. When it is set to <span style=color:#F6A83E>Continuous</span>, ''Trip'' distance is going to be counted continuously (from ''Trip'' start to ''Trip'' end) and written to I/O ''Trip Odometer'' value field. When ''Trip'' is over and the next ''Trip'' begins, ''Trip Odometer'' value is reset to zero.<br/>When ''Mode'' is set to <span style=color:#F6A83E>Between Records</span>, the distance is going to be counted between every record made. This value is written to I/O ''Trip Odometer'' value field and is reset to zero every new record until the ''Trip'' ends. If later all Odometer values are summed up manually, the distance driven during the whole duration of the ''Trip'' can be obtained.<br/>
+
Trip window offers user to configure Trip feature. Trip customizable feature enables user extended monitoring of performed trips (from engine start at present location to engine stop at arrived location), log their start and stop points, view driven total distance. Event will be generated (included into send records) only when trip starts and finishes.
 +
Start Speed (km/h) – GPS speed has to be greater than the specified Start Speed in order to detect Trip Start.  
 +
Ignition OFF Timeout (s) – timeout to wait if ignition (configured ignition source) was off, to detect Trip stop.  
 +
Distance counting mode – Between Records or Continuous can be chosen. For this feature I/O Trip Odometer must be enabled.
 +
If I/O Trip Odometer is enabled and Continuous distance counting variable (Mode) is set to Continuous, Trip distance is going to be counted continuously (from Trip start to Trip stop). This value is written to I/O Trip Odometer value field. When Trip is over and next Trip begins, Trip Odometer value is reset to zero. When the next trip starts counting continuously starts from the beginning again.
 +
If I/O Trip Odometer is enabled and Continuous Distance Counting variable (Mode) is set “Between Records”, then the distance is going to be counted only between every record made. This value is written to I/O Trip Odometer value field and reset to zero every new record until Trip stops. If later all Odometer values are summed up manually, the user gets the distance driven during the whole period of the Trip.
  
 
[[Image:Fmb120_trip_mode.png|600px|center]]
 
[[Image:Fmb120_trip_mode.png|600px|center]]
Line 11: Line 16:
 
{{{pic_advtrip|[[Image:Fmb640_advtrip_settings.png|300px|right]]}}}
 
{{{pic_advtrip|[[Image:Fmb640_advtrip_settings.png|300px|right]]}}}
  
Advanced trip settings allow configuring a number of ''Eco Score allowed Events'' per 100 km{{{txt_ibutton| and enabling/disabling iButton remembering functionality}}}.<br/>I/O Eco score must be enabled to get the value onto the server. ECO scoring is differentiated by separate Trips.<br/>
 
There are six Eco evaluation events:
 
* Harsh acceleration.
 
* Harsh braking.
 
* Harsh cornering.
 
* Over-speeding (will only count events with value 1 (start) and ignore value 0 (end)).
 
* Excessive Idling (will only count events with value 1 (start) and ignore value 0 (end)).
 
* High RPM.<br/>
 
Eco score value can range from 10 (excellent) to 0.00 (very bad):
 
* Excellent 8.00 – 10
 
* Good 6.00 – 7.99
 
* Not Good 4.00 – 5.99
 
* Bad 2.00 – 3.99
 
* Very Bad 0 – 1.99<br/>
 
Score evaluation is calculated the following way:<br/>Eco score = 10/((Total events)/((Trip distance in km)*(Allowed events per km))).<br/>Allowed events per km = (''Eco Score Allowed Events'')/100.
 
 
{| class="wikitable" style="border-style: solid; border-width: 0px"
 
|+
 
|-
 
| style="text-align: left; background: #F6F6FB;"        | [[Image:Bw_nb.png|50px]]
 
| style="text-align: left; background: #F6F6FB;"        | When Total events < 1, we ignore the formula and then Eco Score is equal to 10.<br/>If ''Eco Score Allowed Events'' value is configured as 0, then Eco score can have only two values: 0 (when total events > 0) or 10 (when total events = 0).
 
|-
 
| style="text-align: left; background: #F6F6FB;"        | [[Image:Bw_nb.png|50px]]
 
| style="text-align: left; background: #F6F6FB;"        | Score is updated every 1 km driven or every 5 minutes of ''Trip'' duration.
 
|}
 
{{{txt_ibutton|
 
 
'''Remember iButton functionality.''' If ''Remember iButton'' and ''Trip'' parameters are enabled, ignition is on and iButton is attached then {{{model|FMB640}}} remembers iButton ID. iButton ID is saved and sent to the server with every record. If new iButton is attached during the ''Trip'', {{{model|FMB640}}} remembers new iButton ID. {{{model|FMB640}}} forgets iButton ID after ignition is off and ignition timeout is reached.}}}
 
'''Remember iButton functionality.''' If ''Remember iButton'' and ''Trip'' parameters are enabled, ignition is on and iButton is attached then {{{model|FMB640}}} remembers iButton ID. iButton ID is saved and sent to the server with every record. If new iButton is attached during the ''Trip'', {{{model|FMB640}}} remembers new iButton ID. {{{model|FMB640}}} forgets iButton ID after ignition is off and ignition timeout is reached.}}}
 
==Odometer==
 
 
{{{pic_odometer|[[Image:FMB640_odometer.png|300px|right]]}}}
 
{{{par_src|''Calculation Source'' allows to choose Odometer calculation source between <span style=color:#F6A83E>GNSS</span>{{{txt_lvcan|, <span style=color:#F6A83E>LVCAN</span>}}} or <span style=color:#F6A83E>OBD</span>.<br/>}}}''Odometer Value'' sets the starting total odometer value.
 

Revision as of 14:09, 28 May 2018

Trip Settings

Fmb640 trip settings.png

Trip window offers user to configure Trip feature. Trip customizable feature enables user extended monitoring of performed trips (from engine start at present location to engine stop at arrived location), log their start and stop points, view driven total distance. Event will be generated (included into send records) only when trip starts and finishes. Start Speed (km/h) – GPS speed has to be greater than the specified Start Speed in order to detect Trip Start. Ignition OFF Timeout (s) – timeout to wait if ignition (configured ignition source) was off, to detect Trip stop. Distance counting mode – Between Records or Continuous can be chosen. For this feature I/O Trip Odometer must be enabled. If I/O Trip Odometer is enabled and Continuous distance counting variable (Mode) is set to Continuous, Trip distance is going to be counted continuously (from Trip start to Trip stop). This value is written to I/O Trip Odometer value field. When Trip is over and next Trip begins, Trip Odometer value is reset to zero. When the next trip starts counting continuously starts from the beginning again. If I/O Trip Odometer is enabled and Continuous Distance Counting variable (Mode) is set “Between Records”, then the distance is going to be counted only between every record made. This value is written to I/O Trip Odometer value field and reset to zero every new record until Trip stops. If later all Odometer values are summed up manually, the user gets the distance driven during the whole period of the Trip.

Fmb120 trip mode.png

Advanced Trip Settings

Fmb640 advtrip settings.png

Remember iButton functionality. If Remember iButton and Trip parameters are enabled, ignition is on and iButton is attached then FMB640 remembers iButton ID. iButton ID is saved and sent to the server with every record. If new iButton is attached during the Trip, FMB640 remembers new iButton ID. FMB640 forgets iButton ID after ignition is off and ignition timeout is reached.}}}