FMB640 I/O settings - Revision history

Sandra.Gasyte: Protected "FMB640 I/O settings" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2020-04-02T19:33:56Z

Protected "FMB640 I/O settings" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision		Revision as of 22:33, 2 April 2020
(No difference)

Kudalevas.da at 06:03, 21 October 2019

2019-10-21T06:03:52Z

← Older revision		Revision as of 09:03, 21 October 2019
Line 1:		Line 1:
	{{Template:FMB640_I/O_settings}}		{{Template:FMB640_I/O_settings}}

			[[Category:FMB640 Configuration]]

Gediminas.suminas: Replaced content with "{{Template:FMB640_I/O_settings}}"

2019-07-10T05:31:51Z

Replaced content with "{{Template:FMB640_I/O_settings}}"

← Older revision		Revision as of 08:31, 10 July 2019
Line 1:		Line 1:
	{{Template:FMB640_I/O_settings}}		{{Template:FMB640_I/O_settings}}
	* LVCAN

	~~LVCAN elements can be configured in same way like with normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command.~~

	* FMS IO

	FMS, or Fleet Management Systems Interface, is a sector to configure and manage events based on vehicle data of commercial vehicles. Vehicle data comes through CAN lines. Event configuring isn’t different from those in LVCAN and I/O sectors. The only difference is IDs.

	* Tachograph data

	Tachograph data can be taken from Tachograph via K-Line, ALLCAN, Tacho CAN or FMS. Data here is constantly refreshed. As the other elements’ windows, this one also has all the options to configure event generating.
	~~[[image:Vehicle_Data_priority_settings.png]]~~
	~~[[Category:FMB640 Configuration]]~~

Mantas.sestokas at 11:23, 30 April 2019

2019-04-30T11:23:49Z

← Older revision		Revision as of 14:23, 30 April 2019
Line 12:		Line 12:
	Tachograph data can be taken from Tachograph via K-Line, ALLCAN, Tacho CAN or FMS. Data here is constantly refreshed. As the other elements’ windows, this one also has all the options to configure event generating.		Tachograph data can be taken from Tachograph via K-Line, ALLCAN, Tacho CAN or FMS. Data here is constantly refreshed. As the other elements’ windows, this one also has all the options to configure event generating.
	[[image:Vehicle_Data_priority_settings.png]]		[[image:Vehicle_Data_priority_settings.png]]
			[[Category:FMB640 Configuration]]

Gediminas.suminas at 14:02, 5 December 2018

2018-12-05T14:02:41Z

← Older revision		Revision as of 17:02, 5 December 2018
Line 1:		Line 1:
	{{Template:FMB640_I/O_settings}}		{{Template:FMB640_I/O_settings}}
			* LVCAN

			LVCAN elements can be configured in same way like with normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command.

			* FMS IO

			FMS, or Fleet Management Systems Interface, is a sector to configure and manage events based on vehicle data of commercial vehicles. Vehicle data comes through CAN lines. Event configuring isn’t different from those in LVCAN and I/O sectors. The only difference is IDs.

			* Tachograph data

			Tachograph data can be taken from Tachograph via K-Line, ALLCAN, Tacho CAN or FMS. Data here is constantly refreshed. As the other elements’ windows, this one also has all the options to configure event generating.
			[[image:Vehicle_Data_priority_settings.png]]

Linas.zaldokas: Replaced content with "{{Template:FMB640_I/O_settings}}"

2018-06-04T07:27:12Z

Replaced content with "{{Template:FMB640_I/O_settings}}"

← Older revision		Revision as of 10:27, 4 June 2018
Line 1:		Line 1:
	When no I/O element is enabled, AVL packet comes with GNSS information only. After enabling I/O element(s) AVL packet contains current value(s) of enabled I/O element(s) along with GNSS information.<br/>If the device is connected to configurator all current I/O values are displayed in ''Current Value'' column.<br/>''Priority'' field allows enabling I/O elements and setting them a priority so they are added to the data packet, which is sent to the server. By default 12 I/O elements with low priority are enabled: ''Ignition'', ''Movement'', ''Data Mode'', ''GSM Signal'', ''Sleep Mode'', ''GNSS Status'', ''GNSS PDOP'', ''GNSS HDOP'', ''External Voltage'' and ''Speed''. ''Priority'' level (AVL packet priority) can be <span style=color:#F6A83E>Low</span>, <span style=color:#F6A83E>High</span> or <span style=color:#F6A83E>Panic</span>. All records made by {{{model\|FMB640}}} are regular, and regular packets are sent as low priority records. When ''Low priority'' event is triggered, {{{model\|FMB640}}} makes an additional record with an indication that the event was caused by an I/O element change (depending on ''Operand'' configuration). When ''High priority'' is selected, module makes an additional record with high priority flag and sends event packet immediately to the server using GPRS. ''Panic priority'' triggers same actions as ''High priority'', but if GPRS fails, it sends an AVL packet using SMS data if SMS data sending is enabled and the number is provided in ''SMS/Call Settings''.<br/>''High'' and ''Low'' levels define I/O value range. If I/O value enters or exits this range, {{{model\|FMB640}}} generates an event. ''Operand'' parameter defines when to generate event: ''On Exit'', ''On Entrance'', ''On Both'', ''On Hysteresis'' or ''On Delta Change''.<br/>When ''Event Only'' is selected, I/O element status value will be appended only to eventual records, otherwise I/O element status value will appear in each AVL record.		{{Template:FMB640_I/O_settings}}

	~~==Operands==~~

	~~===Operand On Exit===~~
	~~Record is generated when input value leaves a range between low and high level limits.~~
	~~[[Image:Fmb120_on_exit.png\|x150px\|center]]~~

	~~===Operand On Entrance===~~
	~~----~~
	~~Record is generated when input value enters a range between low and high level limits.~~
	~~[[Image:Fmb120_on_entrance.png\|x150px\|center]]~~

	~~===Operand On Both===~~
	~~----~~
	~~Record is generated by both On Exit and On Entrance operands' logic at same time.~~
	~~[[Image:Fmb120_on_both.png\|x150px\|center]]~~

	~~===Operand Monitoring===~~
	~~----~~
	~~No event at all. Values are recorded only when other triggers worked.~~
	~~[[Image:Fmb120_operand_monitoring.png\|x150px\|center]]~~

	~~===Operand On Hysteresis===~~
	~~----~~
	~~Record is generated when input value crosses the high limit value from below the low limit value or vice versa.~~
	~~[[Image:Fmb120_on_hysteresis.png\|350px\|center]]~~

	~~===Operand On Change===~~
	~~----~~
	~~Record is generated when input value changes.~~
	~~[[Image:Fmb120_on_change.png\|x150px\|center]]~~

	~~===Operand On Delta Change===~~
	~~----~~
	~~Record is generated when input value changes and the absolute change becomes equal to or higher than the limit value.~~
	~~[[Image~~:~~Fmb120_on_delta_change.png\|x150px\|center]]~~

	~~==Avg Const==~~
	If ''Avg Const'' value is 10, new value must be present for 1 second to register the change to a new value. Internal sampling is done every 40 ms, so 25 samples are taken per second. To configure 5 seconds of averaging multiply 10 by 5 yielding 50 as ''Avg Const'' value. The same logic works if the device is in Deep Sleep mode.<br/~~>Averaging follows RC exponential curves, see image below:~~
	~~[[Image:Fmb120_avg_const.png\|300px\|center]]~~
	~~For Boolean values of 5, values is used, that means value change is taken when new values is averaged to more than 99.3%.~~
	~~{{{section_fmb0\|~~
	~~{{{lvcan\|~~
	~~==LVCAN I/O,FMS IO and Tachograph data elements==~~
	~~''LVCAN'', ''FMS IO'' and ''Tachograph data'' sections shows I/O elements that can be obtained accordingly from external devices connected to {{{model\|FMB640~~}}~~} device. All I/O configuration is as described I/O elements~~

Linas.zaldokas at 11:13, 30 May 2018

2018-05-30T11:13:16Z

← Older revision		Revision as of 14:13, 30 May 2018
Line 39:		Line 39:
	==Avg Const==		==Avg Const==
	If ''Avg Const'' value is 10, new value must be present for 1 second to register the change to a new value. Internal sampling is done every 40 ms, so 25 samples are taken per second. To configure 5 seconds of averaging multiply 10 by 5 yielding 50 as ''Avg Const'' value. The same logic works if the device is in Deep Sleep mode.<br/>Averaging follows RC exponential curves, see image below:		If ''Avg Const'' value is 10, new value must be present for 1 second to register the change to a new value. Internal sampling is done every 40 ms, so 25 samples are taken per second. To configure 5 seconds of averaging multiply 10 by 5 yielding 50 as ''Avg Const'' value. The same logic works if the device is in Deep Sleep mode.<br/>Averaging follows RC exponential curves, see image below:
	[[Image:~~FMB640_avg_const~~.png\|300px\|center]]		[[Image:Fmb120_avg_const.png\|300px\|center]]
	For Boolean values of 5, values is used, that means value change is taken when new values is averaged to more than 99.3%.		For Boolean values of 5, values is used, that means value change is taken when new values is averaged to more than 99.3%.
	{{{section_fmb0\|		{{{section_fmb0\|

Linas.zaldokas at 11:12, 30 May 2018

2018-05-30T11:12:51Z

← Older revision		Revision as of 14:12, 30 May 2018
Line 5:		Line 5:
	===Operand On Exit===		===Operand On Exit===
	Record is generated when input value leaves a range between low and high level limits.		Record is generated when input value leaves a range between low and high level limits.
	[[Image:~~FMB120_on_exit~~.png\|x150px\|center]]		[[Image:Fmb120_on_exit.png\|x150px\|center]]

	===Operand On Entrance===		===Operand On Entrance===
	----		----
	Record is generated when input value enters a range between low and high level limits.		Record is generated when input value enters a range between low and high level limits.
	[[Image:~~FMB120_on_entrance~~.png\|x150px\|center]]		[[Image:Fmb120_on_entrance.png\|x150px\|center]]

	===Operand On Both===		===Operand On Both===
	----		----
	Record is generated by both On Exit and On Entrance operands' logic at same time.		Record is generated by both On Exit and On Entrance operands' logic at same time.
	[[Image:~~FMB120_on_both~~.png\|x150px\|center]]		[[Image:Fmb120_on_both.png\|x150px\|center]]

	===Operand Monitoring===		===Operand Monitoring===
	----		----
	No event at all. Values are recorded only when other triggers worked.		No event at all. Values are recorded only when other triggers worked.
	[[Image:~~FMB120_operand_monitoring~~.png\|x150px\|center]]		[[Image:Fmb120_operand_monitoring.png\|x150px\|center]]

	===Operand On Hysteresis===		===Operand On Hysteresis===
	----		----
	Record is generated when input value crosses the high limit value from below the low limit value or vice versa.		Record is generated when input value crosses the high limit value from below the low limit value or vice versa.
	[[Image:~~FMB120_on_hysteresis~~.png\|350px\|center]]		[[Image:Fmb120_on_hysteresis.png\|350px\|center]]

	===Operand On Change===		===Operand On Change===
	----		----
	Record is generated when input value changes.		Record is generated when input value changes.
	[[Image:~~FMB120_on_change~~.png\|x150px\|center]]		[[Image:Fmb120_on_change.png\|x150px\|center]]

	===Operand On Delta Change===		===Operand On Delta Change===
	----		----
	Record is generated when input value changes and the absolute change becomes equal to or higher than the limit value.		Record is generated when input value changes and the absolute change becomes equal to or higher than the limit value.
	[[Image:~~FMB120_on_delta_change~~.png\|x150px\|center]]		[[Image:Fmb120_on_delta_change.png\|x150px\|center]]

	==Avg Const==		==Avg Const==

Linas.zaldokas at 11:11, 30 May 2018

2018-05-30T11:11:18Z

← Older revision		Revision as of 14:11, 30 May 2018
Line 5:		Line 5:
	===Operand On Exit===		===Operand On Exit===
	Record is generated when input value leaves a range between low and high level limits.		Record is generated when input value leaves a range between low and high level limits.
	[[Image:~~FMB640_on_exit~~.png\|x150px\|center]]		[[Image:FMB120_on_exit.png\|x150px\|center]]

	===Operand On Entrance===		===Operand On Entrance===
	----		----
	Record is generated when input value enters a range between low and high level limits.		Record is generated when input value enters a range between low and high level limits.
	[[Image:~~FMB640_on_entrance~~.png\|x150px\|center]]		[[Image:FMB120_on_entrance.png\|x150px\|center]]

	===Operand On Both===		===Operand On Both===
	----		----
	Record is generated by both On Exit and On Entrance operands' logic at same time.		Record is generated by both On Exit and On Entrance operands' logic at same time.
	[[Image:~~FMB640_on_both~~.png\|x150px\|center]]		[[Image:FMB120_on_both.png\|x150px\|center]]

	===Operand Monitoring===		===Operand Monitoring===
	----		----
	No event at all. Values are recorded only when other triggers worked.		No event at all. Values are recorded only when other triggers worked.
	[[Image:~~FMB640_operand_monitoring~~.png\|x150px\|center]]		[[Image:FMB120_operand_monitoring.png\|x150px\|center]]

	===Operand On Hysteresis===		===Operand On Hysteresis===
	----		----
	Record is generated when input value crosses the high limit value from below the low limit value or vice versa.		Record is generated when input value crosses the high limit value from below the low limit value or vice versa.
	[[Image:~~FMB640_on_hysteresis~~.png\|350px\|center]]		[[Image:FMB120_on_hysteresis.png\|350px\|center]]

	===Operand On Change===		===Operand On Change===
	----		----
	Record is generated when input value changes.		Record is generated when input value changes.
	[[Image:~~FMB640_on_change~~.png\|x150px\|center]]		[[Image:FMB120_on_change.png\|x150px\|center]]

	===Operand On Delta Change===		===Operand On Delta Change===
	----		----
	Record is generated when input value changes and the absolute change becomes equal to or higher than the limit value.		Record is generated when input value changes and the absolute change becomes equal to or higher than the limit value.
	[[Image:~~FMB640_on_delta_change~~.png\|x150px\|center]]		[[Image:FMB120_on_delta_change.png\|x150px\|center]]

	==Avg Const==		==Avg Const==

Linas.zaldokas at 11:56, 28 May 2018

2018-05-28T11:56:41Z

← Older revision		Revision as of 14:56, 28 May 2018
Line 44:		Line 44:
	{{{lvcan\|		{{{lvcan\|
	==LVCAN I/O,FMS IO and Tachograph data elements==		==LVCAN I/O,FMS IO and Tachograph data elements==
	''LVCAN'', ''FMS IO'' and ''Tachograph data'' sections shows I/O elements that can be obtained accordingly from external devices connected to {{{model\|FMB640}}} device. All I/O configuration is as described ~~in {{{ctrIO\|[[FMB640_I/O_settings]]}}} section.<br/>Detailed description of LVCAN~~ I/O ~~element configuration is given in {{{ctrCAN\|[[Template:FMB640 CAN adapters]]}}}.}}}~~		''LVCAN'', ''FMS IO'' and ''Tachograph data'' sections shows I/O elements that can be obtained accordingly from external devices connected to {{{model\|FMB640}}} device. All I/O configuration is as described I/O elements
	~~}}}~~