Template:FMA1 Trip and Odometer settings - Revision history

Artur.tomasevski: /* Trip */

2018-09-06T10:33:09Z

Trip

← Older revision		Revision as of 13:33, 6 September 2018
Line 24:		Line 24:
	<br><br>		<br><br>
	[[File:FM36YX_Continuous_distance.png]]<br><br>		[[File:FM36YX_Continuous_distance.png]]<br><br>
	Continuous odometer calculates the distance if Total Distance I/O element is enabled. Odometer Value is constantly saved to flash memory every 30 seconds, but counted every second. After power is turned off, odometer value saved in flash does not reset. Start odometer value with can be set using configurator („set“ button) or SMS/GPRS (setparam/getparam) commands. This parameter can not be configured via TCP config. If this value is not set, ~~FMA110~~ starts counting from 0. Continuous odometer works irrespective of the Trip functionality.		Continuous odometer calculates the distance if Total Distance I/O element is enabled. Odometer Value is constantly saved to flash memory every 30 seconds, but counted every second. After power is turned off, odometer value saved in flash does not reset. Start odometer value with can be set using configurator („set“ button) or SMS/GPRS (setparam/getparam) commands. This parameter can not be configured via TCP config. If this value is not set, {{{model\|FM36YX}}} starts counting from 0. Continuous odometer works irrespective of the Trip functionality.

Artur.tomasevski at 06:26, 23 August 2018

2018-08-23T06:26:30Z

← Older revision		Revision as of 09:26, 23 August 2018
Line 12:		Line 12:
	\|}		\|}

	[[File:~~Trip_configuration~~.png]]<br><br>		[[File:FMA_Trip_configuration.png]]<br><br>
	~~Trip window offers user to configure Trip feature.~~ If Trip is enabled ~~configuration of~~ parameters are ~~enabled. <br>~~		If Trip is enabled following parameters are configurable:
	Start Speed – ~~GNSS~~ speed has to be greater than the specified Start Speed in order to detect Trip Start. ~~<br>~~		* Start Speed – GPS speed has to be greater than the specified Start Speed in order to detect Trip Start.
	Ignition Off Timeout – timeout to wait if ignition was off, to detect Trip stop. ~~<br>~~		* Ignition Off Timeout – timeout to wait if ignition (configured Ignition Source) was off, to detect Trip stop.
	~~Distance Mode~~ – ~~Between records, Continuous trip~~ or Continuous can be chosen. For this feature I/O ~~Odometer~~ must be enabled (~~see Figure above~~). <br>		* Continuous distance counting – Not or Continuous can be chosen. For this feature I/O Trip distance must be enabled.
	If I/O ~~Odometer~~ is enabled and ~~Distance Mode~~ variable is set to ~~“Continuous trip”~~, ~~'''~~Trip distance~~'''~~ is going to be counted continuously ~~'''~~(from Trip start to Trip stop)~~'''~~. This value is written to I/O ~~Odometer~~ value field. When Trip is over and next Trip begins, ~~Odometer~~ value is reset to zero. When the next trip starts counting continuously starts from the beginning again. <br>		* Remember iButton ID – devices remembers connected iButtons id(While trip is detected) and sends it to server along with periodical records.
	If I/O ~~Odometer~~ is enabled and Distance ~~Mode~~ variable is set ~~“Between records”~~, then the distance is going to be counted only between every record made. This value is written to I/O ~~Odometer~~ value field and reset to zero every new record until Trip stops. ~~<br>~~		<br/>
	If ~~I/O Odometer is enabled and Distance Mode variable is set “Continuous”, '''~~Trip distance~~'' is going to be counted continuously (Starting from trip start~~, ~~trip~~ distance ~~is saved to flash memory, see Figure below). <br>~~		If I/O Trip distance is enabled and Continuous distance counting variable 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 distance value field. When Trip is over and next Trip begins, Trip distance value is reset to zero. When the next trip starts counting continuously starts from the beginning again. <br/> <br/>
	~~Continuous Odometer Value – gives ability to set starting value~~ of the ~~“Continuous” trip~~. ~~<br>~~		If I/O Trip distance is enabled and Continuous Distance Counting variable is set “Not”, then the distance is going to be counted only between every record made. This value is written to I/O Trip distance value field and reset to zero every new record until Trip stops. If later all Trip distance values are summed up manually, the user gets the distance driven during the whole period of the Trip.
	~~Remember iButton ID – devices remembers connected iButtons id(While trip is detected) and sends it to server along with periodical records.~~
	<br><br>		<br><br>
	[[File:FM36YX_Continuous_distance.png]]<br><br>		[[File:FM36YX_Continuous_distance.png]]<br><br>
			Continuous odometer calculates the distance if Total Distance I/O element is enabled. Odometer Value is constantly saved to flash memory every 30 seconds, but counted every second. After power is turned off, odometer value saved in flash does not reset. Start odometer value with can be set using configurator („set“ button) or SMS/GPRS (setparam/getparam) commands. This parameter can not be configured via TCP config. If this value is not set, FMA110 starts counting from 0. Continuous odometer works irrespective of the Trip functionality.

Artur.tomasevski: Created page with "===Virtual Odometer=== Virtual odometer is used to calculate traveled distance in {{{model|FM36YX}}} as a separate I/O element. When {{{model|FM36YX}}} detects movement, it st..."

2018-08-23T06:20:30Z

Created page with "===Virtual Odometer=== Virtual odometer is used to calculate traveled distance in {{{model|FM36YX}}} as a separate I/O element. When {{{model|FM36YX}}} detects movement, it st..."

New page

===Virtual Odometer===
Virtual odometer is used to calculate traveled distance in {{{model|FM36YX}}} as a separate I/O element. When {{{model|FM36YX}}} detects movement, it starts counting distance using GNSS signal: every second it checks current location and calculates distance between current and previous point. It keeps adding these intervals until it is time to make a record, then {{{model|FM36YX}}} records its location and adds odometer value, which is equal to the sum of all distances, measured every second. When record is made, odometer resets to zero and distance calculation starts all over again. Virtual odometer as an I/O element can be also used with [[{{{model|FM36YX}}}_Features_settings#Trip|Trip]].
 
===Trip===
Trip customizable feature enables user extended monitoring of performed trips (from engine start at present location to engine stop at arrived location), log their start and stop points, view driven total distance. Event will be generated (included into send records) only when trip starts and finishes. This feature is available on all {{{model|FM36YX}}} hardware versions without limitations.
 
{| 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;" | Note: Scenarios and Trip features are activated (DOUTs are activated) only if DIN1 = 1 (ignition is on).
|}

[[File:Trip_configuration.png]] 
Trip window offers user to configure Trip feature. If Trip is enabled configuration of parameters are enabled. 
Start Speed – GNSS speed has to be greater than the specified Start Speed in order to detect Trip Start. 
Ignition Off Timeout – timeout to wait if ignition was off, to detect Trip stop. 
Distance Mode – Between records, Continuous trip or Continuous can be chosen. For this feature I/O Odometer must be enabled (see Figure above). 
If I/O Odometer is enabled and Distance Mode variable is set to “Continuous trip”, '''Trip distance''' is going to be counted continuously '''(from Trip start to Trip stop)'''. This value is written to I/O Odometer value field. When Trip is over and next Trip begins, Odometer value is reset to zero. When the next trip starts counting continuously starts from the beginning again. 
If I/O Odometer is enabled and Distance Mode variable is set “Between records”, then the distance is going to be counted only between every record made. This value is written to I/O Odometer value field and reset to zero every new record until Trip stops. 
If I/O Odometer is enabled and Distance Mode variable is set “Continuous”, '''Trip distance'' is going to be counted continuously (Starting from trip start, trip distance is saved to flash memory, see Figure below). 
Continuous Odometer Value – gives ability to set starting value of the “Continuous” trip. 
Remember iButton ID – devices remembers connected iButtons id(While trip is detected) and sends it to server along with periodical records.
 
[[File:FM36YX_Continuous_distance.png]]