Template:FTX Tracking settings: Difference between revisions
No edit summary |
|||
| Line 52: | Line 52: | ||
| ATC700 = | | ATC700 = | ||
== Asset tracking modes == | == Asset tracking modes == | ||
'''Note:'''This scenario is only available for asset | '''Note:'''This scenario is only available for asset tracking (''ATX'') devices. | ||
Asset tracking modes functionality controls records profiles with conditions on how records are being saved and sent. | Asset tracking modes functionality controls records profiles with conditions on how records are being saved and sent. | ||
| Line 62: | Line 62: | ||
Record generation and sending reuses existing periodic record configuration parameters. Records are generated at a fixed interval, configurable via parameters “By time” - in Home network (ID 10000) and in Roaming network (ID 10100). | Record generation and sending reuses existing periodic record configuration parameters. Records are generated at a fixed interval, configurable via parameters “By time” - in Home network (ID 10000) and in Roaming network (ID 10100). | ||
Records are sent at a separate fixed interval, configurable via parameters “Send period” - in Home network (ID 10005) and in Roaming network (ID 10105). | |||
If the device is configured to send records in Low priority, minimum number of records have to be generated before sending occurs. This value can be configured via parameters “Min Saved Records” - in Home network (ID 10004) and in Roaming network (ID 10104). | If the device is configured to send records in Low priority, minimum number of records have to be generated before sending occurs. This value can be configured via parameters “Min Saved Records” - in Home network (ID 10004) and in Roaming network (ID 10104). | ||
| Line 103: | Line 103: | ||
</table> | </table> | ||
}} | }} | ||
==Network operators settings== | ==Network operators settings== | ||
[[File:FTX network operators settings.png|right|500 px]] | [[File:FTX network operators settings.png|right|500 px]] | ||
Revision as of 14:29, 3 December 2025
Records settings

Saving/sending mode
This feature will be used to save and send records to the server without time synchronization.
Possible options:
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.
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.
Sort by
Can be set as either Newest or Oldest. For example, if the Oldest is marked, the device first will send the Oldest information, and if the Newest is marked, the device will send the newest information. Suppose the device had no connection (GSM or GPRS) due to bad coverage or being in an area with no signal, the device continues to save records into internal memory, and once GSM and GPRS are recovered, the device will start sending saved data to the server. In this example, if Oldest is configured - until the newest data is seen on the server, all of the oldest records have to be sent first. If Newest is configured - previous data and track won't be seen until the newest data is sent first. If high priority on I/O parameters or Features is configured device will send the generated records with High Priority first.
Server Confirmation Method
Defines the device's ability to establish GPRS connection through specific acknowledgement (ACK) type. Can be set as either TCP/IP or AVL.
If TCP/IP is selected, then server acknowledgement is not needed and the device will accept TCP/IP layer ACK.
If AVL is selected, then the server must respond with an acknowledgement.
Data protocol
In Data Protocol only protocol version (Codec 8 Extended) is available for data sending to the server.
Network operators settings

Operator selection logic utilizes three user-defined operator lists to control network connectivity:
Roaming network operators
- List of operators that have the highest priority when the home network is unavailable.
Blacklisted network operators
- List of operators that are only connected to when no other higher priority operators are available. If the device is connected to a blacklisted operator, GPRS data sending is disabled. Device should continue checking if any higher priority operators are available. To avoid device looping between blacklisted operator and higher priority operator which is not registrable, ban list should be enabled. Otherwise it’s an expected behaviour.
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

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.
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.
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.
Parameter Description
Data Acquisition Profiles
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.
- Send Period
- 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.
| |
Device operates in GMT:0 time zone, without daylight saving. |
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.

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.
Records schedule

This feature, also known as the Scheduler, allows the device to wake up from a low-power sleep mode at pre-configured times to acquire a GNSS position and send a data record to a server. However, this feature can operate in any power Mode.
This functionality is essential for asset tracking scenarios where power conservation is critical, such as monitoring trailers, containers, or any equipment without a constant power source. By waking up only at specified intervals to report its location, the device can operate on its internal battery for extended periods.
The user can define up to six unique scheduled times for each weekday. At each configured time, the device exits its sleep state, activates its GNSS module to determine its current location, establishes a connection to send the data, and then returns to the same Mode until the next scheduled event. This ensures periodic updates while maximizing battery life.
Prerequisites and Important Settings
- The device must be configured to operate in a sleep mode that supports scheduled wake-ups, such as "Deep Sleep" or "Online Deep Sleep" mode. This is typically configured in System > Power saving settings > Mode.
- Accurate time synchronization is required for the scheduler to function correctly. The device must be able to acquire the current time, either from a GNSS satellite fix or through an NTP server, before the schedules can be reliably executed.
- The device must have a server configured for data sending in Mobile Network > Primary server settings.
Basic Operation
- Entering Sleep Mode:
○ After its initial configuration and data sending, the device enters the selected low-power sleep mode. In this state, most modules, including GNSS and the modem, are powered down to conserve energy.
- Scheduled Wake-up:
- The device's internal clock continuously runs. When the current time matches one of the configured schedules, the device initiates the wake-up sequence.
- The main controller powers on the GNSS module to acquire a satellite fix and determine the current coordinates.
- Data Record and Transmission:
- Once a position fix is obtained, the device powers on the modem.
- It creates a new data record containing the latest location information and other configured I/O parameters.
- The device establishes a connection to the server and sends the record.
- Returning to Sleep:
- After successfully sending the record, the device powers down the GNSS and modem modules.
- It then returns to the low-power sleep mode, awaiting the next scheduled wake-up time.
- If the device fails to get a GNSS fix or send the data within a predefined timeout, it will abort the process and return to sleep to prevent battery drain.
Parameters list
| PARAMETER NAME | PARAMETER ID (RELATED AVL ID) | DESCRIPTION | VALUES |
|---|---|---|---|
| Sunday Time 1-6 | 35100-35105 | Sets the times for scheduled records on Sunday | 0-2359 or 2500 |
| Monday Time 1-6 | 35200-35205 | Sets the time for a scheduled record on Monday | 0-2359 or 2500 |
| Tuesday Time 1-6 | 35300-35305 | Sets the time for a scheduled record on Tuesday | 0-2359 or 2500 |
| Wednesday Time 1-6 | 35400-35405 | Sets the time for a scheduled record on Wednesday | 0-2359 or 2500 |
| Friday Time 1-6 | 35600-35605 | Sets the time for a scheduled record on Friday | 0-2359 or 2500 |
| Saturday Time 1-6 | 35700-35705 | Sets the time for a scheduled record on Saturday | 0-2359 or 2500 |
Note: Wakeup times in configuration are stored as a list of uint16 variables in format HHmm (range from 0 to 2359), for example: 12:00 -> 1200, 01:45 -> 145, 23:59 -> 2359. Default value for unconfigured timestamps is 2500.
Limitations, Edge Cases & Additional Notes
- A maximum of six unique schedules can be configured per weekday.
- The reliability of this feature is dependent on the device's ability to acquire a GNSS signal at the scheduled time. If the device is in a location with poor signal (e.g., indoors, underground garage), it may fail to get a fix and will not send a record.
- If the device's internal battery is completely drained, it will lose time synchronization and will not be able to execute scheduled wake-ups until it is powered on and can sync its clock again.
[[Category:{{{model}}} Configuration]]
