Template:FTX Tracking settings: Difference between revisions

(3 intermediate revisions by the same user not shown)

Line 1:

==Records settings==

[[File:~~Record Settings latest~~.png|right|500 px]]

[[File:FTX records settings.png|right|500 px]]

'''Saving/sending mode'''

Line 9:

'''Possible options:'''

''After Position Fix'' - records will be saved and sent only after position fix.

'''After Position Fix''' - records will be saved and sent only after position fix.

''After Time Sync'' - records will be saved and sent only after time synchronization.

'''After Time Sync''' - records will be saved and sent only after time synchronization.

''Always'' - records will always be saved and sent even if there is no time synchronization.

'''Always''' - records will always be saved and sent even if there is no time synchronization.

Note: If the record is without valid coordinates – (there were no GPS fix at the moment of data acquisition) – Longitude, Latitude and Altitude values are sent as per the last valid fix, and Angle, Satellites and Speed will be 0. However, if there is a reboot then it will send zero coordinates.

Line 34:

==Network operators settings==

[[File:~~Network~~ operators settings.png|right|500 px]]

[[File:FTX network operators settings.png|right|500 px]]

Operator selection logic utilizes three user-defined operator lists to control network connectivity:

Line 43:

'''Forbidden network operators'''

*List of operators that are not allowed to be connected to. If device connects to forbidden operator, operator is placed into FPLMN list and modem reset.

'''Ban list control'''

*'''Enable''' or '''disable''' the banning of mobile operators following repeated failed connection attempts, PDP activation failures, or APN configuration issues. The ban duration is 30 minutes.

==Records profile settings==

[[File:~~FTC921_Records_profile_settings_1~~.png|right|~~400 px]]~~

[[File:FTX_Records_profile_settings.png|right|500 px]]

~~[[File:FTC921_Records_profile_settings_2.png|right|380~~ px]]

Data Acquisition ~~modes are an essential part of {{{model|FTX}}}~~ device~~, they are also highly configurable. Through configuration user defines how~~ records ~~will be saved and sent. There are two~~ different ~~modes:~~ Home ~~and~~ Roaming~~. All these modes with configured data acquisition~~ and ~~report frequencies depend on the current GSM Operator and are switched when the GSM operator changes~~ (e.~~g. vehicle passes through a country border~~).~~ If the current GSM operator is defined as Home Operator~~, ~~the device will work in Home Data Acquisition mode if the current operator~~ is ~~defined as Roaming Operator, the device will work in Roaming Data Acquisition mode. This functionality allows having different AVL records to acquire~~ and send parameter values when the object is moving or standing still. The vehicle moving or stop state is defined by the Movement Source parameter, please refer to Movement settings in [[{{{model}}} System]].~~ ~~

'''Data Acquisition Modes''' allow you to control how the device '''collects''' and '''sends''' records under different network (Home vs. Roaming) and movement (Moving vs. On Stop) conditions. By tailoring data acquisition profiles, you can optimize data usage and power consumption, ensuring that relevant information is captured and transmitted at appropriate intervals.

For example, you might configure the device to:

*Generate a record every '''1 minute''' when '''Home''' and '''Moving'''.

*Generate a record every '''10 minutes''' when '''Roaming''' and '''Moving'''.

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

===Prerequisites===

'''Connectivity'''

*The device must have available cellular connectivity to send data to a remote server.

~~ ~~

'''Network Mode Awareness'''

*The device should identify whether it is in Home or Roaming mode.

'''~~Record Saving settings~~'''

'''Movement Detection'''

*The device needs a method (e.g., GNSS speed threshold, accelerometer, or ignition source) to determine whether it is currently Moving or On Stop.

'''Configuration Access'''

*A configuration tool or firmware interface is required to set the acquisition intervals and thresholds for each combination of '''GSM''' and '''Movement''' modes.

''~~Min Saved Records~~'' defines the minimum number of coordinates and I/O data that should be transferred within a single connection to the server. If {{{model|FTX}}} 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 saved data being sent to the server over GPRS. The module makes attempts to send collected data to the server every defined period of time. If it does not have enough records (depending on the parameter ''Min. Saved Records'' described above), it tries again after the defined time interval.

===Parameter Description===

'''Data Acquisition Profiles'''

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

Each combination of '''GSM Mode''' (Home, Roaming) and '''Movement Mode''' (Moving, On Stop) can have its own acquisition settings. Typical parameters within each profile include:

|+

*'''Min Saved Records'''

|-

**The minimum number of coordinates (records) that must be accumulated before the device attempts to send data to the server.

~~| style="text-align: left; background: #F6F6FB;" | [[Image:Bw_nb~~.~~png|50px]]~~

*'''Send Period'''

~~| style="text-align: left; background: #F6F6FB~~;~~" | Keep in mind that {{{model|FTX}}} operates in GMT:0 time zone~~, ~~without daylight saving~~.

**Defines how often (in seconds or minutes) the device checks whether it has met the '''Min Saved Records''' threshold. If enough records are available, the device sends them; otherwise, it waits until the next send period.

|}

~~{{{model|FTX}}} 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.

<tr>

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

<td> [[Image:Alert.png|center|50px]] </td>

* Angle-based data acquisition (''Min Angle'') – records are acquired when the angle difference between the last recorded coordinate and current position is greater than a defined value. Entering zero disables data acquisition based on the angle.

<td> Device operates in GMT:0 time zone, without daylight saving. </td>

* Speed-based data acquisition (''Min Speed Delta'') – records are acquired when the speed difference between the last recorded coordinate and current position is greater than a defined value. Entering zero disables data acquisition based on speed.

</tr>

</table>

[[Image:~~Fmb120_daq_mode_basis~~.png|~~700px~~|none]]

'''Data Collection Methods'''

The device can collect records using one or more of the following methods '''simultaneously''':

*'''Time-Based Data Acquisition (Min Period)'''

**Acquires a record each time a specified interval of time passes.

**Setting this to zero '''disables''' time-based acquisition.

*'''Distance-Based Data Acquisition (Min Distance)'''

**Acquires a record when the device’s traveled distance (from the last recorded coordinate) exceeds a specified value (in meters).

**Setting this to zero '''disables''' distance-based acquisition.

*'''Angle-Based Data Acquisition (Min Angle)'''

**Acquires a record when the angle difference between the last recorded coordinate and the current heading exceeds a defined threshold (in degrees).

**Setting this to zero '''disables''' angle-based acquisition.

*'''Speed-Based Data Acquisition (Min Speed Delta)'''

**Acquires a record when the difference in speed (from the last recorded speed) exceeds a defined threshold (in km/h or m/s, depending on configuration).

**Setting this to zero '''disables''' speed-based acquisition.

[[Image:tracking parameters diagram.png|595px|none]]

'''Data Collection Methods'''

*'''Record Collection'''

**The device continuously checks for any of the enabled conditions (time, distance, angle, speed).

**If any threshold is met (e.g., Min Period elapsed, Min Distance exceeded), a new record is stored in internal memory.

*'''Record Storage & Batching'''

**Records are accumulated until '''Min Saved Records''' is reached or the '''Send Period''' timer expires.

**If neither condition is met, the device continues to collect data without initiating a connection.

*'''Data Transmission'''

**Once '''Min Saved Records''' is reached or the '''Send Period''' elapses (whichever comes first), the device attempts to send all stored records to the server.

**If the device is in '''Roaming mode''', it may use less frequent intervals to reduce data costs (based on your configuration).

*'''Profile Switching'''

**The device automatically switches to the corresponding profile when it detects changes in '''GSM Mode''' (Home ↔ Roaming) or '''Movement Mode''' (Moving ↔ On Stop).

**For instance, if the vehicle transitions from moving to a standstill, the device switches from the “Moving” to the “On Stop” settings.

*'''Configuration Overrides'''

**Certain high-priority events (e.g., crashes, alarms) may override the data acquisition intervals and send records immediately, regardless of the configured mode.

[[Category:{{{model}}} Configuration]]