Changes

m
Line 12: Line 12:     
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/>
 
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:
    
* Harsh acceleration.
 
* Harsh acceleration.
Line 20: Line 20:  
* Excessive Idling (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/>
 
* High RPM.<br/>
Eco score value can be from 10 (excellent) to 0.00 (very bad):
+
Eco score value can range from 10 (excellent) to 0.00 (very bad):
 
* Excellent 8.00 – 10
 
* Excellent 8.00 – 10
 
* Good 6.00 – 7.99
 
* Good 6.00 – 7.99
 
* Not Good 4.00 – 5.99
 
* Not Good 4.00 – 5.99
 
* Bad 2.00 – 3.99
 
* Bad 2.00 – 3.99
* Very Bad 0.00 – 1.99
+
* Very Bad 0 – 1.99
   −
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).
+
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 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;"        | 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 to 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;"        | [[Image:Bw_nb.png|50px]]
| style="text-align: left; background: #F6F6FB;"        | Score is updated every 1 km driven or 5 minutes of trip duration.
+
| style="text-align: left; background: #F6F6FB;"        | Score is updated every 1 km driven or every 5 minutes of Trip duration.
 
|}
 
|}
   −
'''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.
+
'''Remember iButton functionality.''' If Remember iButton ID 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 timeout is reached.
    
==Odometer==
 
==Odometer==

Navigation menu