Template:FM3612 Data acquisition mode settings - Revision history

Marek.rakalovic at 07:34, 23 August 2018

2018-08-23T07:34:24Z

← Older revision		Revision as of 10:34, 23 August 2018
Line 22:		Line 22:


	[[Image:FM36_acquisition_conf.jpg\|700px\|none]]		{{{dataAcquisitionFoto\|[[Image:FM36_acquisition_conf.jpg\|700px\|none]]}}}

Marek.rakalovic at 07:30, 23 August 2018

2018-08-23T07:30:01Z

← Older revision		Revision as of 10:30, 23 August 2018
Line 14:		Line 14:
	</font>		</font>

	[[Image:FM36_Operator.jpg\|~~800px~~\|~~none~~]]		[[Image:FM36_Operator.jpg\|700px\|center]]

	==Data Acquisition Mode configuration==		==Data Acquisition Mode configuration==

Marek.rakalovic: /* Data Acquisition Mode configuration */

2018-08-23T07:28:51Z

Data Acquisition Mode configuration

← Older revision		Revision as of 10:28, 23 August 2018
Line 22:		Line 22:


	[[Image:FM36_acquisition_conf.jpg\|~~800px~~\|none]]		[[Image:FM36_acquisition_conf.jpg\|700px\|none]]

Marek.rakalovic at 07:28, 23 August 2018

2018-08-23T07:28:22Z

← Older revision		Revision as of 10:28, 23 August 2018
Line 50:		Line 50:
	</font>		</font>

	{{{model\|FM36YX}}} is able to collect records using four methods at the same time: time, distance, angle and speed based data acquisition:		{{{model\|FM36YX}}} is able to collect records using four methods at the same time: time, distance, angle and speed based data acquisition: <br/>
	Time based data acquiring (Min. period) – records are being acquired every time when defined interval of time passes. Entering zero disables data acquisition depending on time.		Time based data acquiring (Min. period) – records are being acquired every time when defined interval of time passes. Entering zero disables data acquisition depending on time.

Marek.rakalovic at 04:31, 13 August 2018

2018-08-13T04:31:16Z

← Older revision		Revision as of 07:31, 13 August 2018
Line 25:		Line 25:


	<span style=color:#~~F6A83E~~>Min Period</span> This parameter indicates time interval in seconds in order to acquire new record. If value is 0 it means no records by min period will be saved.		<span style=color:#0a0372>'''Min Period'''</span> This parameter indicates time interval in seconds in order to acquire new record. If value is 0 it means no records by min period will be saved.

	<span style=color:#~~F6A83E~~>Min Saved Records</span> defines minimum number of coordinates and I/O data that should be transferred with one connection to server. If {{{model\|FM36YX}}} does not have enough coordinates to send to server, it will check again after time interval defined in <span style=color:#~~F6A83E~~>Sending Period</span>		<span style=color:#0a0372>'''Min Saved Records'''</span> defines minimum number of coordinates and I/O data that should be transferred with one connection to server. If {{{model\|FM36YX}}} does not have enough coordinates to send to server, it will check again after time interval defined in <span style=color:#0a0372>'''Sending Period'''</span>

	<span style=color:#~~F6A83E~~>Send period</span> – GPRS data sending to server period. Module makes attempts to send collected data to server every defined period. If it does not have enough records (depends on parameter Min. Saved Records described above), it tries again after defined time interval.		<span style=color:#0a0372>'''Send period'''</span> – GPRS data sending to server period. Module makes attempts to send collected data to server every defined period. If it does not have enough records (depends on parameter Min. Saved Records described above), it tries again after defined time interval.

	==GPRS Week Time configuration==		==GPRS Week Time configuration==

	<span style=color:#~~F6A83E~~>GPRS Week Time tab</span> – most GSM billing systems charge number of bytes (kilobytes) transmitted per session. During the session, {{{model\|FM36YX}}} makes connection and transmits data to a server. {{{model\|FM36YX}}} tries to handle the session as much as possible; it never closes session by itself. Session can last for hours, days, weeks or session can be closed after every connection in certain GSM networks – this depends on GSM network provider. GPRS Context Week Time defines session re-establish schedule if session was closed by network. New GPRS context is opened if time is 10 minutes till time checked in table. Therefore if all boxes are checked, {{{model\|FM36YX}}} is able to open new connection anytime. At scheduled time match {{{model\|FM36YX}}} checks for GPRS session activity. If GPRS session is alive, {{{model\|FM36YX}}} sends data to server according to Send period parameter. If it is not, {{{model\|FM36YX}}} checks if it is able to re-establish the session.		<span style=color:#0a0372>'''GPRS Week Time tab'''</span> – most GSM billing systems charge number of bytes (kilobytes) transmitted per session. During the session, {{{model\|FM36YX}}} makes connection and transmits data to a server. {{{model\|FM36YX}}} tries to handle the session as much as possible; it never closes session by itself. Session can last for hours, days, weeks or session can be closed after every connection in certain GSM networks – this depends on GSM network provider. GPRS Context Week Time defines session re-establish schedule if session was closed by network. New GPRS context is opened if time is 10 minutes till time checked in table. Therefore if all boxes are checked, {{{model\|FM36YX}}} is able to open new connection anytime. At scheduled time match {{{model\|FM36YX}}} checks for GPRS session activity. If GPRS session is alive, {{{model\|FM36YX}}} sends data to server according to Send period parameter. If it is not, {{{model\|FM36YX}}} checks if it is able to re-establish the session.

Simkunas.ma at 12:29, 31 May 2018

2018-05-31T12:29:04Z

← Older revision		Revision as of 15:29, 31 May 2018
Line 24:		Line 24:
	[[Image:FM36_acquisition_conf.jpg\|800px\|none]]		[[Image:FM36_acquisition_conf.jpg\|800px\|none]]


			<span style=color:#F6A83E>Min Period</span> This parameter indicates time interval in seconds in order to acquire new record. If value is 0 it means no records by min period will be saved.

	<span style=color:#F6A83E>Min Saved Records</span> defines minimum number of coordinates and I/O data that should be transferred with one connection to server. If {{{model\|FM36YX}}} does not have enough coordinates to send to server, it will check again after time interval defined in <span style=color:#F6A83E>Sending Period</span>		<span style=color:#F6A83E>Min Saved Records</span> defines minimum number of coordinates and I/O data that should be transferred with one connection to server. If {{{model\|FM36YX}}} does not have enough coordinates to send to server, it will check again after time interval defined in <span style=color:#F6A83E>Sending Period</span>

Simkunas.ma at 12:05, 31 May 2018

2018-05-31T12:05:56Z

Simkunas.ma at 12:05, 31 May 2018

2018-05-31T12:05:05Z

← Older revision		Revision as of 15:05, 31 May 2018
Line 10:		Line 10:
	\|-		\|-
	\| 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;" \| Note: If there are no operator codes entered into operator list, ~~FM3612~~ will work in Unknown network mode ONLY.		\| style="text-align: left; background: #F6F6FB;" \| Note: If there are no operator codes entered into operator list, {{{model\|FM36YX}}} will work in Unknown network mode ONLY.
	\|}		\|}
	</font>		</font>
Line 39:		Line 39:
	\|-		\|-
	\| 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;" \| Note: Keep in mind that ~~FM3612~~ operates in GMT:0 time zone, without daylight saving.		\| style="text-align: left; background: #F6F6FB;" \| Note: Keep in mind that {{{model\|FM36YX}}} operates in GMT:0 time zone, without daylight saving.
	\|}		\|}
	</font>		</font>

	~~FM3612~~ is able to collect records using four methods at the same time: time, distance, angle and speed based data acquisition:		{{{model\|FM36YX}}} is able to collect records using four methods at the same time: time, distance, angle and speed based data acquisition:
	Time based data acquiring (Min. period) – records are being acquired every time when defined interval of time passes. Entering zero disables data acquisition depending on time.		Time based data acquiring (Min. period) – records are being acquired every time when defined interval of time passes. Entering zero disables data acquisition depending on time.

Simkunas.ma at 12:02, 31 May 2018

2018-05-31T12:02:45Z

← Older revision		Revision as of 15:02, 31 May 2018
Line 23:		Line 23:

	<span style=color:#F6A83E>Min Saved Records</span> defines minimum number of coordinates and I/O data that should be transferred with one connection to server. If {{{model\|FM36YX}}} does not have enough coordinates to send to server, it will check again after time interval defined in <span style=color:#F6A83E>Sending Period</span>		<span style=color:#F6A83E>Min Saved Records</span> defines minimum number of coordinates and I/O data that should be transferred with one connection to server. If {{{model\|FM36YX}}} does not have enough coordinates to send to server, it will check again after time interval defined in <span style=color:#F6A83E>Sending Period</span>

			<span style=color:#F6A83E>Send period</span> – GPRS data sending to server period. Module makes attempts to send collected data to server every defined period. If it does not have enough records (depends on parameter Min. Saved Records described above), it tries again after defined time interval.

			==GPRS Week Time configuration==

			<span style=color:#F6A83E>GPRS Week Time tab</span> – most GSM billing systems charge number of bytes (kilobytes) transmitted per session. During the session, {{{model\|FM36YX}}} makes connection and transmits data to a server. {{{model\|FM36YX}}} tries to handle the session as much as possible; it never closes session by itself. Session can last for hours, days, weeks or session can be closed after every connection in certain GSM networks – this depends on GSM network provider. GPRS Context Week Time defines session re-establish schedule if session was closed by network. New GPRS context is opened if time is 10 minutes till time checked in table. Therefore if all boxes are checked, {{{model\|FM36YX}}} is able to open new connection anytime. At scheduled time match {{{model\|FM36YX}}} checks for GPRS session activity. If GPRS session is alive, {{{model\|FM36YX}}} sends data to server according to Send period parameter. If it is not, {{{model\|FM36YX}}} checks if it is able to re-establish the session.

			[[Image:FM36_GPRS_Week_Time.jpg\|800px\|none]]

			Device checks if the time between last saved record and current time is equal or higher than Time based acquire interval. If so, {{{model\|FM36YX}}} saves record to memory. If not, {{{model\|FM36YX}}} checks if the distance from last record to current record is equal or higher than Distance based acquire interval. If so, saves the record to memory. If not and speed is higher than 10km/h, then {{{model\|FM36YX}}} checks if angle difference between last record and current record is equal or higher than Angle based acquire value. If so, saves the record to memory. These checks are performed every second.

			<font size="+1">
			{\| 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: Keep in mind that FM3612 operates in GMT:0 time zone, without daylight saving.
			\|}
			</font>

			FM3612 is able to collect records using four methods at the same time: time, distance, angle and speed based data acquisition:
			Time based data acquiring (Min. period) – records are being acquired every time when defined interval of time passes. Entering zero disables data acquisition depending on time.

			[[Image:FM36_interval_1.jpg\|800px\|none]]

			Distance based data acquiring (Min. distance) – records are being acquired when the distance between previous coordinate and current position is greater than defined parameter value. Entering zero disables data acquisition depending on distance.

			[[Image:FM36_interval_2.jpg\|800px\|none]]

			Angle based data acquiring (Min. angle) – records are being acquired when angle difference between last recorded coordinate and current position is greater than defined value. Entering zero disables data acquisition depending on angle.

			[[Image:FM36_interval_3.jpg\|800px\|none]]

			Speed based data acquiring (Min. speed delta) – records are being acquired when speed difference between last recorded coordinate and current position is greater than defined value. Entering zero disables data acquisition depending on speed.

			[[Image:FM36_interval_4.jpg\|800px\|none]]

Simkunas.ma at 11:46, 31 May 2018

2018-05-31T11:46:47Z

← Older revision		Revision as of 14:46, 31 May 2018
Line 4:		Line 4:
	operator code is not written in Operator list (but there is at least one operator code in the operator list), device will work in Unknown Acquisition mode. <br />		operator code is not written in Operator list (but there is at least one operator code in the operator list), device will work in Unknown Acquisition mode. <br />
	This functionality allows having different AVL records acquire and send parameters values when object is moving or stands still. Vehicle moving or stop state is defined by Stop Detection Source parameter. There are 3 ways for {{{model\|FM36YX}}} to switch between Vehicle on Stop and Vehicle Moving modes. {{{model\|FM36YX}}} allows having 6 different modes.		This functionality allows having different AVL records acquire and send parameters values when object is moving or stands still. Vehicle moving or stop state is defined by Stop Detection Source parameter. There are 3 ways for {{{model\|FM36YX}}} to switch between Vehicle on Stop and Vehicle Moving modes. {{{model\|FM36YX}}} allows having 6 different modes.

			<font size="+1">
			{\| 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: If there are no operator codes entered into operator list, FM3612 will work in Unknown network mode ONLY.
			\|}
			</font>

	[[Image:FM36_Operator.jpg\|800px\|none]]		[[Image:FM36_Operator.jpg\|800px\|none]]

← Older revision		Revision as of 15:05, 31 May 2018
Line 17:		Line 17:

	==Data Acquisition Mode configuration==		==Data Acquisition Mode configuration==


	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.


	[[Image:FM36_acquisition_conf.jpg\|800px\|none]]		[[Image:FM36_acquisition_conf.jpg\|800px\|none]]


	<span style=color:#F6A83E>Min Saved Records</span> defines minimum number of coordinates and I/O data that should be transferred with one connection to server. If {{{model\|FM36YX}}} does not have enough coordinates to send to server, it will check again after time interval defined in <span style=color:#F6A83E>Sending Period</span>		<span style=color:#F6A83E>Min Saved Records</span> defines minimum number of coordinates and I/O data that should be transferred with one connection to server. If {{{model\|FM36YX}}} does not have enough coordinates to send to server, it will check again after time interval defined in <span style=color:#F6A83E>Sending Period</span>
Line 29:		Line 32:

	<span style=color:#F6A83E>GPRS Week Time tab</span> – most GSM billing systems charge number of bytes (kilobytes) transmitted per session. During the session, {{{model\|FM36YX}}} makes connection and transmits data to a server. {{{model\|FM36YX}}} tries to handle the session as much as possible; it never closes session by itself. Session can last for hours, days, weeks or session can be closed after every connection in certain GSM networks – this depends on GSM network provider. GPRS Context Week Time defines session re-establish schedule if session was closed by network. New GPRS context is opened if time is 10 minutes till time checked in table. Therefore if all boxes are checked, {{{model\|FM36YX}}} is able to open new connection anytime. At scheduled time match {{{model\|FM36YX}}} checks for GPRS session activity. If GPRS session is alive, {{{model\|FM36YX}}} sends data to server according to Send period parameter. If it is not, {{{model\|FM36YX}}} checks if it is able to re-establish the session.		<span style=color:#F6A83E>GPRS Week Time tab</span> – most GSM billing systems charge number of bytes (kilobytes) transmitted per session. During the session, {{{model\|FM36YX}}} makes connection and transmits data to a server. {{{model\|FM36YX}}} tries to handle the session as much as possible; it never closes session by itself. Session can last for hours, days, weeks or session can be closed after every connection in certain GSM networks – this depends on GSM network provider. GPRS Context Week Time defines session re-establish schedule if session was closed by network. New GPRS context is opened if time is 10 minutes till time checked in table. Therefore if all boxes are checked, {{{model\|FM36YX}}} is able to open new connection anytime. At scheduled time match {{{model\|FM36YX}}} checks for GPRS session activity. If GPRS session is alive, {{{model\|FM36YX}}} sends data to server according to Send period parameter. If it is not, {{{model\|FM36YX}}} checks if it is able to re-establish the session.


	[[Image:FM36_GPRS_Week_Time.jpg\|800px\|none]]		[[Image:FM36_GPRS_Week_Time.jpg\|800px\|none]]


	Device checks if the time between last saved record and current time is equal or higher than Time based acquire interval. If so, {{{model\|FM36YX}}} saves record to memory. If not, {{{model\|FM36YX}}} checks if the distance from last record to current record is equal or higher than Distance based acquire interval. If so, saves the record to memory. If not and speed is higher than 10km/h, then {{{model\|FM36YX}}} checks if angle difference between last record and current record is equal or higher than Angle based acquire value. If so, saves the record to memory. These checks are performed every second.		Device checks if the time between last saved record and current time is equal or higher than Time based acquire interval. If so, {{{model\|FM36YX}}} saves record to memory. If not, {{{model\|FM36YX}}} checks if the distance from last record to current record is equal or higher than Distance based acquire interval. If so, saves the record to memory. If not and speed is higher than 10km/h, then {{{model\|FM36YX}}} checks if angle difference between last record and current record is equal or higher than Angle based acquire value. If so, saves the record to memory. These checks are performed every second.
Line 45:		Line 50:
	{{{model\|FM36YX}}} is able to collect records using four methods at the same time: time, distance, angle and speed based data acquisition:		{{{model\|FM36YX}}} is able to collect records using four methods at the same time: time, distance, angle and speed based data acquisition:
	Time based data acquiring (Min. period) – records are being acquired every time when defined interval of time passes. Entering zero disables data acquisition depending on time.		Time based data acquiring (Min. period) – records are being acquired every time when defined interval of time passes. Entering zero disables data acquisition depending on time.


	[[Image:FM36_interval_1.jpg\|800px\|none]]		[[Image:FM36_interval_1.jpg\|800px\|none]]


	Distance based data acquiring (Min. distance) – records are being acquired when the distance between previous coordinate and current position is greater than defined parameter value. Entering zero disables data acquisition depending on distance.		Distance based data acquiring (Min. distance) – records are being acquired when the distance between previous coordinate and current position is greater than defined parameter value. Entering zero disables data acquisition depending on distance.


	[[Image:FM36_interval_2.jpg\|800px\|none]]		[[Image:FM36_interval_2.jpg\|800px\|none]]


	Angle based data acquiring (Min. angle) – records are being acquired when angle difference between last recorded coordinate and current position is greater than defined value. Entering zero disables data acquisition depending on angle.		Angle based data acquiring (Min. angle) – records are being acquired when angle difference between last recorded coordinate and current position is greater than defined value. Entering zero disables data acquisition depending on angle.


	[[Image:FM36_interval_3.jpg\|800px\|none]]		[[Image:FM36_interval_3.jpg\|800px\|none]]


	Speed based data acquiring (Min. speed delta) – records are being acquired when speed difference between last recorded coordinate and current position is greater than defined value. Entering zero disables data acquisition depending on speed.		Speed based data acquiring (Min. speed delta) – records are being acquired when speed difference between last recorded coordinate and current position is greater than defined value. Entering zero disables data acquisition depending on speed.


	[[Image:FM36_interval_4.jpg\|800px\|none]]		[[Image:FM36_interval_4.jpg\|800px\|none]]