Changes

m
Line 11: Line 11:  
[[Image:Fmb120_advtrip_settings.png|300px|right]]
 
[[Image:Fmb120_advtrip_settings.png|300px|right]]
   −
Advanced trip settings allow configure number of Eco Score allowed events in 100 km and enable or disable iButton remember functionality.<br/>Eco Score allowed events – how much ECO events is allowed in 100 km. I/O Eco score must be enabled to get value into server. ECO scoring is differentiated by separate Trips.<br/>
+
Advanced trip settings allow configuring a number of ''Eco Score allowed Events'' per 100 km 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:
 
There are six ECO evaluation events:
   Line 17: Line 17:  
* Harsh braking.
 
* Harsh braking.
 
* Harsh cornering.
 
* Harsh cornering.
* Over-speeding (count only events with value 1 (start) and ignore value 0(end)).
+
* Over-speeding (will only count events with value 1 (start) and ignore value 0 (end)).
* Excessive Idling (count only 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/>
 
* High RPM.<br/>
 
Eco score value can be from 10 (excellent) to 0.00 (very bad):
 
Eco score value can be from 10 (excellent) to 0.00 (very bad):
Line 27: Line 27:  
* Very Bad 0.00 – 1.99
 
* Very Bad 0.00 – 1.99
   −
Score evaluation is calculated like this:<br/>Eco score =10/((Total events)/(Trip distance in km* Allowed events per km)).<br/>Allowed events per km = (Eco Score allowed events/100).
+
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"
 
{| class="wikitable" style="border-style: solid; border-width: 0px"
Line 33: Line 33:  
|-
 
|-
 
| style="text-align: left; background: #F6F6FB;"        | [[Image:Bw_nb.png|50px]]
 
| style="text-align: left; background: #F6F6FB;"        | [[Image:Bw_nb.png|50px]]
| style="text-align: left; background: #F6F6FB;"        | When Total events < 1, we ignore formula and then Eco score is equal to 10.<br/>If Eco Score allowed events is configured to 0, then Eco score value can have only two values: 0 (when total events > 0) or 10 (when total events = 0).
+
| 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 is configured to 0, then Eco score value 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;"        | [[Image:Bw_nb.png|50px]]
Line 39: Line 39:  
|}
 
|}
   −
'''Remember iButton functionality.''' If Remember iButton ID while trip detected and Trip parameters are enabled, ignition is on and iButton is attached, then FMB120 remembers iButton ID. iButton ID is saved and sent to server with every record. If new iButton is attached during the trip, FMB120 remembers new iButton ID. FMB120 forgets iButton ID after ignition is off and trip ignition off timeout is reached.
+
'''Remember iButton functionality.''' If Remember iButton ID while trip detected and Trip parameters are enabled, ignition is on and iButton is attached, then FMB120 remembers iButton ID. iButton ID is saved and sent to the server with every record. If new iButton is attached during the trip, FMB120 remembers new iButton ID. FMB120 forgets iButton ID after ignition is off and ignition off timeout is reached.
    
==Odometer==
 
==Odometer==