Jump to content
  • EN

FTC921 Tracking settings: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
No edit summary
Replaced content with "{{Template:FTX Tracking settings|model=FTC921}}"
Tag: Replaced
 
Line 1: Line 1:
==Records settings==
{{Template:FTX Tracking settings|model=FTC921}}
 
[[File:Record Settings latest.png|right|500 px]]
 
'''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#Codec 8 Extended|Codec 8 Extended]]''') is available for data sending to the server.<br></br>
 
==Records profile settings==
[[File:FTC921_Records_profile_settings_1.png|right|400 px]]
[[File:FTC921_Records_profile_settings_2.png|right|380 px]]
 
Data Acquisition modes are an essential part of {{{model|FTC921}}} device, they are also highly configurable.<br/>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).<br/>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.<br/>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 Stop Detection Source parameter. There are {{{txt_num|3}}} ways for {{{model|FTC921}}} to switch between Vehicle on Stop and Vehicle Moving modes, please refer to Movement settings in {{{ctrSystem|[[FTC921 System]]}}}.<br/>
 
 
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.
 
<br/>
 
'''Record Saving settings'''
 
''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|FTC921}}} does not have enough coordinates to send to the server, it will check again after a time interval defined in ''Send Period'' field.<br/>''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.
 
{| 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;"        | Keep in mind that {{{model|FTC921}}} operates in GMT:0 time zone, without daylight saving.
|}
 
{{{model|FTC921}}} 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.
* 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.
* 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.
* 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.
 
[[Image:Fmb120_daq_mode_basis.png|700px|none]]
 
[[Category:FTC921 Configuration]]

Latest revision as of 12:38, 8 May 2025

Main Page > Basic Trackers > FTC921 > FTC921 Configuration > FTC921 Tracking settings

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 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 may 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.
Retrieved from "https://wiki.teltonika-gps.com/index.php?title=FTC921_Tracking_settings&oldid=104742"