0
edits
Changes
Template:FMB Trip/Odometer settings (view source)
Revision as of 10:31, 11 April 2018
, 10:31, 11 April 2018no edit summary
==Trip Settings==
==Trip Settings==
[[Image:Fmb120_trip_settings.png|300px|right]]
Trip window offers user to configure Trip feature. If Trip is enabled configuration of parameters are enabled.<br/>Start Speed (km/h) – GPS speed has to be greater than the specified Start Speed in order to detect Trip Start.<br/>Ignition OFF Timeout (s) – timeout to wait if ignition (configured ignition source) was off, to detect Trip stop.<br/>Distance counting mode – Between Records or Continuous can be chosen. For this feature I/O Trip Odometer must be enabled.<br/>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.<br/>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.<br/>
[[Image:Fmb120_trip_mode.png|600px|center]]
==Advanced Trip Settings==
==Advanced Trip Settings==
[[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/>
There are six ECO evaluation events:
* Harsh acceleration.
* Harsh braking.
* Harsh cornering.
* Over-speeding (count only events with value 1 (start) and ignore value 0(end)).
* Excessive Idling (count only events with value 1 (start) and ignore value 0(end)).
* High RPM.<br/>
Eco score value can be 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.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).
{| 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 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;" | Score is updated every 1 km driven or 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 FMB1YX remembers iButton ID. iButton ID is saved and sent to server with every record. If new iButton is attached during the trip, FMB1YX remembers new iButton ID. FMB1YX forgets iButton ID after ignition is off and trip ignition off timeout is reached.
==Odometer==
==Odometer==
[[Image:Fmb120_odometer.png|300px|right]]
Calculation Source – choose odometer calculation source of GNSS, OBD or LVCAN.<br/>Odometer Value –sets starting total odometer value.
