Template:FMB640 Data acquisition settings - Revision history

Gintare.Slizyte: /* On Demand Tracking */

2021-11-08T09:04:50Z

On Demand Tracking

← Older revision		Revision as of 12:04, 8 November 2021
Line 45:		Line 45:

	Tracking on demand can be triggered by multiple IO Events. To enable functionality at least one activation source must be selected and an appropriate IO Event (in I/O tab) should be enabled (Low/High/Panic priority, the operand must NOT be “Monitoring”). When IO Event is generated and if the event is enabled in activation sources, tracking on demand will be started. THE new IO event will not interrupt or restart tracking on-demand until the Duration period has expired. If tracking on demand is already running, SMS/GPRS command will restart tracking on demand.		Tracking on demand can be triggered by multiple IO Events. To enable functionality at least one activation source must be selected and an appropriate IO Event (in I/O tab) should be enabled (Low/High/Panic priority, the operand must NOT be “Monitoring”). When IO Event is generated and if the event is enabled in activation sources, tracking on demand will be started. THE new IO event will not interrupt or restart tracking on-demand until the Duration period has expired. If tracking on demand is already running, SMS/GPRS command will restart tracking on demand.
	If tracking the on-demand period is lower than the normal record acquisition period, only high priority records will be created. If tracking the on-demand period is larger than the normal record acquisition period, low priority records will be created according to data acquisition configuration and high priority records will be created after configured tracking on-demand period. Some new [[Template:~~FMB_Device_Family_Parameter_list~~#Tracking_on_Demand\|Tracking on Demand parameters]] are introduced in devices.		If tracking the on-demand period is lower than the normal record acquisition period, only high priority records will be created. If tracking the on-demand period is larger than the normal record acquisition period, low priority records will be created according to data acquisition configuration and high priority records will be created after configured tracking on-demand period. Some new [[Template:FMB640_Device_Family_Parameter_list#Tracking_on_Demand\|Tracking on Demand parameters]] are introduced in devices.

	[[image:FMx640_on_demand_tracking_(1).gif]]		[[image:FMx640_on_demand_tracking_(1).gif]]

	There are three available options for the activation source of tracking on demand - DIN/AIN or both (devices that support multiple DINs/AINs allow choosing which DINs/AINs to use). Note that, these inputs will work as buttons, rather than switches, and are used to trigger the functionality, the duration of tracking on demand will not be extended if the activation source status is high for a period of time.		There are three available options for the activation source of tracking on demand - DIN/AIN or both (devices that support multiple DINs/AINs allow choosing which DINs/AINs to use). Note that, these inputs will work as buttons, rather than switches, and are used to trigger the functionality, the duration of tracking on demand will not be extended if the activation source status is high for a period of time.

Gintare.Slizyte: /* On Demand Tracking */

2021-10-11T06:17:50Z

On Demand Tracking

← Older revision		Revision as of 09:17, 11 October 2021
Line 33:		Line 33:
	==On Demand Tracking==		==On Demand Tracking==

	This functionality was added to FMX640 series devices from 01.00.05. Tracking on Demand can be activated using commands. After device receives [[~~FMB~~ SMS/GPRS ~~Commands~~\|SMS/GPRS]] command "'' [[~~FMB SMS~~/~~GPRS Commands~~#~~Commands Related to Features~~\|on_demand_trackingX]]''" where ''X'' is a number from 0 to 2.		This functionality was added to FMX640 series devices from 01.00.05. Tracking on Demand can be activated using commands. After device receives [[FMB640 SMS/GPRS command list\|SMS/GPRS]] command "'' [[FMB640_SMS/GPRS_command_list#Commands_related_to_features\|on_demand_trackingX]]''" where ''X'' is a number from 0 to 2.

	Possible X values are:		Possible X values are:
Line 42:		Line 42:

	After that, the device starts to generate high priority records and initiate data sending to the server. This		After that, the device starts to generate high priority records and initiate data sending to the server. This
	feature is configurable via [[~~FMB~~ SMS/GPRS ~~Commands~~\|SMS/GPRS]] commands only.<br />		feature is configurable via [[FMB640 SMS/GPRS command list\|SMS/GPRS]] commands only.<br />

	Tracking on demand can be triggered by multiple IO Events. To enable functionality at least one activation source must be selected and an appropriate IO Event (in I/O tab) should be enabled (Low/High/Panic priority, the operand must NOT be “Monitoring”). When IO Event is generated and if the event is enabled in activation sources, tracking on demand will be started. THE new IO event will not interrupt or restart tracking on-demand until the Duration period has expired. If tracking on demand is already running, SMS/GPRS command will restart tracking on demand.		Tracking on demand can be triggered by multiple IO Events. To enable functionality at least one activation source must be selected and an appropriate IO Event (in I/O tab) should be enabled (Low/High/Panic priority, the operand must NOT be “Monitoring”). When IO Event is generated and if the event is enabled in activation sources, tracking on demand will be started. THE new IO event will not interrupt or restart tracking on-demand until the Duration period has expired. If tracking on demand is already running, SMS/GPRS command will restart tracking on demand.
	If tracking the on-demand period is lower than the normal record acquisition period, only high priority records will be created. If tracking the on-demand period is larger than the normal record acquisition period, low priority records will be created according to data acquisition configuration and high priority records will be created after configured tracking on-demand period. Some new [[Template:FMB_Device_Family_Parameter_list#Tracking_on_Demand\|Tracking on Demand parameters]] are introduced in devices.		If tracking the on-demand period is lower than the normal record acquisition period, only high priority records will be created. If tracking the on-demand period is larger than the normal record acquisition period, low priority records will be created according to data acquisition configuration and high priority records will be created after configured tracking on-demand period. Some new [[Template:FMB_Device_Family_Parameter_list#Tracking_on_Demand\|Tracking on Demand parameters]] are introduced in devices.

	[[image:~~On demand Tracking~~.gif]]		[[image:FMx640_on_demand_tracking_(1).gif]]

	There are three available options for the activation source of tracking on demand - DIN/AIN or both (devices that support multiple DINs/AINs allow choosing which DINs/AINs to use). Note that, these inputs will work as buttons, rather than switches, and are used to trigger the functionality, the duration of tracking on demand will not be extended if the activation source status is high for a period of time.		There are three available options for the activation source of tracking on demand - DIN/AIN or both (devices that support multiple DINs/AINs allow choosing which DINs/AINs to use). Note that, these inputs will work as buttons, rather than switches, and are used to trigger the functionality, the duration of tracking on demand will not be extended if the activation source status is high for a period of time.

Gintare.Slizyte at 11:50, 7 September 2021

2021-09-07T11:50:48Z

← Older revision		Revision as of 14:50, 7 September 2021
Line 30:		Line 30:

	[[Image:Fmb120_daq_mode_basis.png\|800px\|centre]]		[[Image:Fmb120_daq_mode_basis.png\|800px\|centre]]

			==On Demand Tracking==

			This functionality was added to FMX640 series devices from 01.00.05. Tracking on Demand can be activated using commands. After device receives [[FMB SMS/GPRS Commands\|SMS/GPRS]] command "'' [[FMB SMS/GPRS Commands#Commands Related to Features\|on_demand_trackingX]]''" where ''X'' is a number from 0 to 2.

			Possible X values are:

			*X = 0 – Stops Tracking on Demand functionality.
			*X = 1 – Starts Tracking on Demand functionality.
			*X = 2 – Generates one high priority record and initiates data sending to the server.

			After that, the device starts to generate high priority records and initiate data sending to the server. This
			feature is configurable via [[FMB SMS/GPRS Commands\|SMS/GPRS]] commands only.<br />

			Tracking on demand can be triggered by multiple IO Events. To enable functionality at least one activation source must be selected and an appropriate IO Event (in I/O tab) should be enabled (Low/High/Panic priority, the operand must NOT be “Monitoring”). When IO Event is generated and if the event is enabled in activation sources, tracking on demand will be started. THE new IO event will not interrupt or restart tracking on-demand until the Duration period has expired. If tracking on demand is already running, SMS/GPRS command will restart tracking on demand.
			If tracking the on-demand period is lower than the normal record acquisition period, only high priority records will be created. If tracking the on-demand period is larger than the normal record acquisition period, low priority records will be created according to data acquisition configuration and high priority records will be created after configured tracking on-demand period. Some new [[Template:FMB_Device_Family_Parameter_list#Tracking_on_Demand\|Tracking on Demand parameters]] are introduced in devices.

			[[image:On demand Tracking.gif]]

			There are three available options for the activation source of tracking on demand - DIN/AIN or both (devices that support multiple DINs/AINs allow choosing which DINs/AINs to use). Note that, these inputs will work as buttons, rather than switches, and are used to trigger the functionality, the duration of tracking on demand will not be extended if the activation source status is high for a period of time.

Linas.zaldokas at 08:17, 28 May 2018

2018-05-28T08:17:59Z

← Older revision		Revision as of 11:17, 28 May 2018
Line 1:		Line 1:
	Data Acquisition modes are an essential part of {{{model\|FMB640}}} device, they are also highly configurable.<br/>Through configuration user defines how records will be saved and sent. There are three different modes: Home, Roaming and Unknown. All these modes with configured data acquisition and report frequencies depend on current GSM Operator defined in the Operator list (see section {{{ctrGsm\|[[Template:FMB GSM Operators settings]]}}}) and are switched when GSM operator changes (e.g. vehicle passes through a country border).<br/>If current GSM operator is defined as Home Operator, device will work in Home Data Acquisition mode, if current operator is defined as Roaming Operator, device will work in Roaming Data Acquisition mode, and if current operator code is not written in the Roaming Operator list, device will work in Unknown mode.<br/>This functionality allows having different AVL records to acquire and send parameter values when object is moving or standing still. Vehicle moving or stop state is defined by Stop Detection Source parameter~~. There are {{{txt_num\|4}}} ways for {{{model\|FMB640}}} to switch between Vehicle on Stop and Vehicle Moving modes, please refer to the first table in {{{ctrSystem\|[[Template:FMB System settings]]}}}~~.<br/>{{{model\|FMB640}}} has 6 different modes. Operational logic is shown in the figure below.		Data Acquisition modes are an essential part of {{{model\|FMB640}}} device, they are also highly configurable.<br/>Through configuration user defines how records will be saved and sent. There are three different modes: Home, Roaming and Unknown. All these modes with configured data acquisition and report frequencies depend on current GSM Operator defined in the Operator list (see section {{{ctrGsm\|[[Template:FMB GSM Operators settings]]}}}) and are switched when GSM operator changes (e.g. vehicle passes through a country border).<br/>If current GSM operator is defined as Home Operator, device will work in Home Data Acquisition mode, if current operator is defined as Roaming Operator, device will work in Roaming Data Acquisition mode, and if current operator code is not written in the Roaming Operator list, device will work in Unknown mode.<br/>This functionality allows having different AVL records to acquire and send parameter values when object is moving or standing still. Vehicle moving or stop state is defined by Stop Detection Source parameter.<br/>{{{model\|FMB640}}} has 6 different modes. Operational logic is shown in the figure below.

	{\| class="wikitable" style="border-style: solid; border-width: 0px"		{\| class="wikitable" style="border-style: solid; border-width: 0px"

Linas.zaldokas at 08:15, 28 May 2018

2018-05-28T08:15:57Z

← Older revision		Revision as of 11:15, 28 May 2018
Line 8:		Line 8:
	\|}		\|}

	[[Image:~~FMB640_daq_mode_logic~~.png\|800px\|centre]]<br/>		[[Image:Fmb120_daq_mode_logic.png\|800px\|centre]]<br/>

	Operator search is performed every 15 minutes. Depending on current GSM operator Home, Roaming or Unknown mode can be changed faster than every 15 minutes. This process is separate from operator search. Movement criteria are checked every second.		Operator search is performed every 15 minutes. Depending on current GSM operator Home, Roaming or Unknown mode can be changed faster than every 15 minutes. This process is separate from operator search. Movement criteria are checked every second.
Line 29:		Line 29:
	* Speed based data acquisition (''Min Speed Delta'') – records are acquired when the speed difference between last recorded coordinate and current position is greater than a defined value. Entering zero disables data acquisition based on speed.		* Speed based data acquisition (''Min Speed Delta'') – records are acquired when the speed difference between last recorded coordinate and current position is greater than a defined value. Entering zero disables data acquisition based on speed.

	[[Image:~~FMB640_daq_mode_basis~~.png\|800px\|centre]]		[[Image:Fmb120_daq_mode_basis.png\|800px\|centre]]

Linas.zaldokas: Created page with "Data Acquisition modes are an essential part of {{{model|FMB640}}} device, they are also highly configurable.
Through configuration user defines how records will be saved..."

2018-05-28T08:14:05Z

Created page with "Data Acquisition modes are an essential part of {{{model|FMB640}}} device, they are also highly configurable. Through configuration user defines how records will be saved..."

New page

Data Acquisition modes are an essential part of {{{model|FMB640}}} device, they are also highly configurable. Through configuration user defines how records will be saved and sent. There are three different modes: Home, Roaming and Unknown. All these modes with configured data acquisition and report frequencies depend on current GSM Operator defined in the Operator list (see section {{{ctrGsm|[[Template:FMB GSM Operators settings]]}}}) and are switched when GSM operator changes (e.g. vehicle passes through a country border). If current GSM operator is defined as Home Operator, device will work in Home Data Acquisition mode, if current operator is defined as Roaming Operator, device will work in Roaming Data Acquisition mode, and if current operator code is not written in the Roaming Operator list, device will work in Unknown mode. This functionality allows having different AVL records to acquire and send parameter values when object is moving or standing still. Vehicle moving or stop state is defined by Stop Detection Source parameter. There are {{{txt_num|4}}} ways for {{{model|FMB640}}} to switch between Vehicle on Stop and Vehicle Moving modes, please refer to the first table in {{{ctrSystem|[[Template:FMB System settings]]}}}. {{{model|FMB640}}} has 6 different modes. Operational logic is shown in the figure below.

{| 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;" | If home operator is written to roaming operator list, it will still be detected as home operator.
|}

[[Image:FMB640_daq_mode_logic.png|800px|centre]] 

Operator search is performed every 15 minutes. Depending on current GSM operator Home, Roaming or Unknown mode can be changed faster than every 15 minutes. This process is separate from operator search. Movement criteria are checked every second.

{{{fmb_picture|[[Image:FMB640_daq_mode_config.png|800px|centre]]}}} 

''Min Saved Records'' defines minimum number of coordinates and I/O data that should be transferred within a single connection to the server. If {{{model|FMB640}}} does not have enough coordinates to send to the server, it will check again after a time interval defined in ''Send Period'' field. ''Send period'' controls the frequency of GPRS data being sent to server. Module makes attempts to send collected data to the server every defined period of time. If it does not have enough records (depends on the parameter ''Min. Saved Records'' described above), it tries again after the defined time interval.

{| 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;" | Keep in mind that {{{model|FMB640}}} operates in GMT:0 time zone, without daylight saving.
|}

{{{model|FMB640}}} is able to collect records using four methods at the same time: time, distance, angle and speed based data acquisition:
* Time based data acquisition (''Min Period'') – records are acquired every time when a defined interval of time passes. Entering zero disables data acquisition based on time.
* Distance based data acquisition (''Min Distance'') – records are acquired when the distance between previous coordinate and current position is greater than a defined parameter value. Entering zero disables data acquisition based on distance.
* Angle based data acquisition (''Min Angle'') – records are acquired when the angle difference between last recorded coordinate and current position is greater than a defined value. Entering zero disables data acquisition based on angle.
* Speed based data acquisition (''Min Speed Delta'') – records are acquired when the speed difference between last recorded coordinate and current position is greater than a defined value. Entering zero disables data acquisition based on speed.

[[Image:FMB640_daq_mode_basis.png|800px|centre]]

Template:FMB640 Data acquisition settings - Revision history

Gintare.Slizyte: /* On Demand Tracking */

Gintare.Slizyte: /* On Demand Tracking */

Gintare.Slizyte at 11:50, 7 September 2021

Linas.zaldokas at 08:17, 28 May 2018

Linas.zaldokas at 08:15, 28 May 2018

Linas.zaldokas: Created page with "Data Acquisition modes are an essential part of {{{model|FMB640}}} device, they are also highly configurable.Through configuration user defines how records will be saved..."

Linas.zaldokas: Created page with "Data Acquisition modes are an essential part of {{{model|FMB640}}} device, they are also highly configurable.
Through configuration user defines how records will be saved..."