Difference between revisions of "Template:FMB Trip/Odometer settings"
From Wiki Knowledge Base | Teltonika GPS
Atabasnikov (talk | contribs) |
|||
| (43 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
==Trip Settings== | ==Trip Settings== | ||
| − | [[Image: | + | [[Image:Fmb120_trip_settings.png|300px|right]] |
| − | + | Trip window offers user to configure the Trip feature. If Trip is enabled, configuration of Trip parameters is enabled.<br/>''Start Speed'' (km/h) defines the minimum GPS speed in order to detect Trip Start.<br/>''Ignition OFF Timeout'' is the timeout value to detect Trip Stop once the Ignition (configured ignition source) is off.<br/>To use feature ''Distance counting mode'' I/O Trip Odometer must be enabled. When it is set to <span style=color:#F6A83E>Continuous</span>, Trip distance is going to be counted continuously (from Trip start to Trip stop) and is written to I/O ''Trip Odometer'' value field. When Trip is over and next Trip begins, ''Trip Odometer'' value is reset to zero.<br/>When ''Mode'' is set <span style=color:#F6A83E>Between Records</span>, the distance is going to be counted only 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 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| | + | [[Image:Fmb120_trip_mode.png|600px|center]] |
==Advanced Trip Settings== | ==Advanced Trip Settings== | ||
| − | + | [[Image:Fmb120_advtrip_settings.png|300px|right]] | |
| + | |||
| + | 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: | ||
| − | |||
| − | |||
* Harsh acceleration. | * Harsh acceleration. | ||
* Harsh braking. | * Harsh braking. | ||
| 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 | + | Eco score value can be 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 – 1.99 | + | * Very Bad 0.00 – 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). | ||
{| class="wikitable" style="border-style: solid; border-width: 0px" | {| class="wikitable" style="border-style: solid; border-width: 0px" | ||
| Line 50: | 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 | + | | 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]] | ||
| − | | style="text-align: left; background: #F6F6FB;" | | + | | 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 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== | ||
| − | + | [[Image:Fmb120_odometer.png|300px|right]] | |
| − | + | ''Calculation Source'' allows to choose Odometer calculation source between <span style=color:#F6A83E>GNSS</span>, <span style=color:#F6A83E>OBD</span> or <span style=color:#F6A83E>LVCAN</span>.<br/>''Odometer Value'' sets the starting total odometer value. | |
Revision as of 14:13, 12 April 2018
Trip Settings
Trip window offers user to configure the Trip feature. If Trip is enabled, configuration of Trip parameters is enabled.
Start Speed (km/h) defines the minimum GPS speed in order to detect Trip Start.
Ignition OFF Timeout is the timeout value to detect Trip Stop once the Ignition (configured ignition source) is off.
To use feature Distance counting mode I/O Trip Odometer must be enabled. When it is set to Continuous, Trip distance is going to be counted continuously (from Trip start to Trip stop) and 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 Mode is set Between Records, the distance is going to be counted only 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 stops. If later all Odometer values are summed up manually, the user gets the distance driven during the whole period of the Trip.
Advanced Trip Settings
Advanced trip settings allow configuring a number of Eco Score allowed Events per 100 km and enabling/disabling iButton remembering functionality.
I/O Eco score must be enabled to get the value onto the server. ECO scoring is differentiated by separate Trips.
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.
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 the following way:
Eco score = 10/((Total events)/((Trip distance in km)*(Allowed events per km))).
Allowed events per km = (Eco Score allowed events/100).
|
When Total events < 1, we ignore the formula and then Eco score is equal to 10. 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). |
|
|
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 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
Calculation Source allows to choose Odometer calculation source between GNSS, OBD or LVCAN.
Odometer Value sets the starting total odometer value.
