Changes

no edit summary
Line 2: Line 2:  
==Trip Settings==
 
==Trip Settings==
   −
[[Image:FMC800_trip_settings.png|300px|right]]
+
[[Image:Fmb120_trip_settings.png|300px|right]]
    
''Trip'' section offers user to configure the ''Trip'' feature. ''Trip'' starts when Ignition according ''Ignition source'' is ON and Movement according ''Movement source'' is ON and also 'Start Speed' is exceeded. ''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'' section offers user to configure the ''Trip'' feature. ''Trip'' starts when Ignition according ''Ignition source'' is ON and Movement according ''Movement source'' is ON and also 'Start Speed' is exceeded. ''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/>
   −
[[Image:FMC800_trip_mode.png|600px|none]]
+
[[Image:Fmb120_trip_mode.png|600px|none]]
    
==Advanced Trip Settings==
 
==Advanced Trip Settings==
   −
{{{pic_advtrip|[[Image:FMC800_advtrip_settings.png|300px|right]]}}}
+
{{{pic_advtrip|[[Image:Fmb001_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 score is dependent on overspeeding, Eco/Green driving (harsh acceleration, braking, cornering), excessive idling and high RPM events (latter one requires OBD BT dongle). If less of parameters/scenarios are activated - it is easier to have higher Eco score. ECO scoring is differentiated by separate Trips.<br/>
 
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 score is dependent on overspeeding, Eco/Green driving (harsh acceleration, braking, cornering), excessive idling and high RPM events (latter one requires OBD BT dongle). If less of parameters/scenarios are activated - it is easier to have higher Eco score. ECO scoring is differentiated by separate Trips.<br/>

Navigation menu