Changes

[[Image:Fmb120_trip_settings.png|300px|right]]

[[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'' 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 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 stops. If later all Odometer values are summed up manually, the user obtains the distance driven during the whole duration of the Trip.<br/>

''Trip'' section offers user to configure the ''Trip'' feature. ''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:Fmb120_trip_mode.png|600px|center]]

[[Image:Fmb120_trip_mode.png|600px|center]]

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.

* Harsh braking.

* Harsh braking.

* 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 – 1.99<br/>

 

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"

|-

|-

| 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 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;"        | 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 as 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 every 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 and Trip parameters are enabled, ignition is on and iButton is attached, then {{{model|FMB1YX}}} remembers iButton ID. iButton ID is saved and sent to the server with every record. If new iButton is attached during the Trip, {{{model|FMB1YX}}} remembers new iButton ID. {{{model|FMB1YX}}} forgets iButton ID after ignition is off and ignition timeout is reached.

'''Remember iButton functionality.''' If ''Remember iButton'' and ''Trip'' parameters are enabled, ignition is on and iButton is attached then {{{model|FMB1YX}}} remembers iButton ID. iButton ID is saved and sent to the server with every record. If new iButton is attached during the ''Trip'', {{{model|FMB1YX}}} remembers new iButton ID. {{{model|FMB1YX}}} forgets iButton ID after ignition is off and ignition timeout is reached.

==Odometer==

==Odometer==