Difference between revisions of "Template:FM3612 Data acquisition mode settings"
Simkunas.ma (talk | contribs) (Created page with "Data Acquisition Modes are an essential part of {{{model|FM36YX}}} device, it is also highly configurable. By configuration user defines how records will be saved and sent. Th...") |
|||
(15 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | Data Acquisition Modes are an essential part of {{{model|FM36YX}}} device, it is also highly configurable. By configuration user defines how records will be saved and sent. There are three different modes: Home, Roaming and Unknown. | + | Data Acquisition Modes are an essential part of {{{model|FM36YX}}} device, it is also highly configurable. <br /> |
− | All these modes with configured data acquisition and send frequencies depend on current GSM Operator defined in Operator list and are switched when GSM operator changes (e.g. vehicle passes through country boarder). | + | By 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 send frequencies depend on current GSM Operator defined in Operator list and are switched when GSM operator changes (e.g. vehicle passes through country boarder). <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 | 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 Operator list (but there is at least one operator code in the operator list), device will work in Unknown Acquisition mode. This functionality allows having different AVL records acquire | + | 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 /> |
− | 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 | + | 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. |
− | Moving modes 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, {{{model|FM36YX}}} will work in Unknown network mode ONLY. | ||
+ | |} | ||
+ | </font> | ||
+ | |||
+ | [[Image:FM36_Operator.jpg|700px|center]] | ||
+ | |||
+ | ==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. | ||
+ | |||
+ | |||
+ | {{{dataAcquisitionFoto|[[Image:FM36_acquisition_conf.jpg|700px|none]]}}} | ||
+ | |||
+ | |||
+ | <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:#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:#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== | ||
+ | |||
+ | <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. | ||
+ | |||
+ | |||
+ | [[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 {{{model|FM36YX}}} operates in GMT:0 time zone, without daylight saving. | ||
+ | |} | ||
+ | </font> | ||
+ | |||
+ | {{{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. | ||
+ | |||
+ | |||
+ | [[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]] |
Latest revision as of 09:34, 23 August 2018
Data Acquisition Modes are an essential part of FM36YX device, it is also highly configurable.
By 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 send frequencies depend on current GSM Operator defined in Operator list and are switched when GSM operator changes (e.g. vehicle passes through country boarder).
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 Operator list (but there is at least one operator code in the operator list), device will work in Unknown Acquisition mode.
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 FM36YX to switch between Vehicle on Stop and Vehicle Moving modes. FM36YX allows having 6 different modes.
Note: If there are no operator codes entered into operator list, FM36YX will work in Unknown network mode ONLY. |
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.
Min Period 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.
Min Saved Records defines minimum number of coordinates and I/O data that should be transferred with one connection to server. If FM36YX does not have enough coordinates to send to server, it will check again after time interval defined in Sending Period
Send period – 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 tab – most GSM billing systems charge number of bytes (kilobytes) transmitted per session. During the session, FM36YX makes connection and transmits data to a server. 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, FM36YX is able to open new connection anytime. At scheduled time match FM36YX checks for GPRS session activity. If GPRS session is alive, FM36YX sends data to server according to Send period parameter. If it is not, FM36YX checks if it is able to re-establish the session.
Device checks if the time between last saved record and current time is equal or higher than Time based acquire interval. If so, FM36YX saves record to memory. If not, 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 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.
Note: Keep in mind that FM36YX operates in GMT:0 time zone, without daylight saving. |
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.
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.
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.
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.