ATM700 Tracking settings

Main Page > Autonomous Trackers > ATM700 > ATM700 Configuration > ATM700 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. Coordinate acquisition time is configured via the "GNSS position fix search timeout" parameter.

After Time Sync - records will be saved and sent only after time synchronization. “GNSS position fix search timeout” is not used here; therefore, records may lack GNSS location data.

Always - records will always be saved and sent even if there is no time synchronization. “GNSS position fix search timeout” is not used here; therefore, records may lack GNSS location data.

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.

GNSS position fix search timeout (s)

GNSS position fix search timeout in seconds, after timeout periodic and scheduled records are generated without position fix and sleep is allowed.

This parameter is measured in seconds. Default value is 120 seconds.
Minimal value = 0 seconds, maximum value = 86400 seconds.

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.

Asset tracking modes

Note:This scenario is only available for asset tracking (ATX) devices. Asset tracking modes functionality controls records profiles with conditions on when records are being saved and sent.

Basic mode

In Basic tracking mode, the accelerometer is disabled. The device relies only on periodic wake-ups. Records are generated and sent at a fixed interval. Depending on configured periodic record priority, records can be:

Sent immediately when generated in High priority case.
Stored until they are sent in batches in Low priority case.

Record generation and sending uses 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).

Movement mode

In Movement tracking mode, the accelerometer is enabled. The device generates and sends records based on detected movement state rather than fixed periodic wake ups only. This mode supports two independent periodic configurations: one for when the device is stationary (On Stop) and another for when it is moving (On Move).

Movement detection
Movement detection relies on the accelerometer. A movement event is detected when the measured acceleration magnitude exceeds a configured threshold (parameter ID 19000). When this threshold is exceeded:

Instant Movement status is set.
A second movement event must be detected within the next 5 seconds.

If the second event is detected within this window, the device switches to On Move mode and starts using parameters configured for the Moving state.
If the second event is not detected, the device remains in On Stop mode.

Movement and stop behavior

Once in On Move mode, the device remains in this state until it generates a periodic record.
After that record is generated, the device switches back to On Stop mode unless another movement event is detected before the record generation interval elapses.
If another movement event is detected while in On Move mode, the On Move state is extended.

Movement extension uses a single accelerometer interrupt:

The two event / 5 second sequence is not required during extension.
When an extension occurs, the upcoming periodic record is generated with movement state set to On Move.
After extension, the accelerometer is disabled until the next periodic record is generated to reduce power consumption and avoid repeated wake ups.

Record generation and sending
Record generation and sending are handled internally by the movement scenario logic and are based on the current movement state:

On Stop state

Periodic records are generated using parameters configured for the Stationary state.

On Move state

Periodic records are generated using parameters configured for the Moving state. Each state has its own:

Periodic record generation interval
Record sending configuration (including priority and batching behavior)

Movement IO element Periodic records with Movement = 0 (On Stop) are generated when:

The device is in On Stop mode and the periodic record generation interval for the stationary state elapses.
The device is in On Move mode, generates a periodic record, and then switches to On Stop mode.

Periodic records with Movement = 1 (On Move) are generated when:

The device switches from On Stop to On Move mode due to detected movement.
The device is already in On Move mode and the periodic record generation interval for the moving state elapses after movement extension.

Limitations, Edge Cases & Additional Notes

Switching to On Move mode is similar in Online and Power Off modes. In Online mode, movement is detected immediately. In Power Off mode, the device wakes on a movement interrupt and waits up to 5 seconds for a second event; wake up latency may delay detection and entry into On Move mode.

Parameters list

PARAMETER NAME	PARAMETER ID (RELATED AVL ID)	DESCRIPTION	VALUES
Asset tracking modes	12150	In Basic tracking mode, the accelerometer is disabled. The device relies only on periodic wakeups whereas records are generated and sent at a fixed interval(s). 0 value in "Send period" field turns off periodic Low priority record sending.	0 = Basic mode 1 = Movement mode
By time (s)	10000 (Home) 10100 (Roaming)	This parameter indicates a time interval in seconds in order to acquire a new record. If the value is 0 it means no records by min period will be saved.	Minimum value = 0 Maximum value = 2592000
Send period (s)	10005 (Home) 10105 (Roaming)	This parameter indicates the frequency (time interval in seconds) of sending data to the server.	Minimum value = 0 Maximum value = 2592000
Min saved records	10004 (Home) 10104 (Roaming)	This parameter defines a minimum number of records in one data packet that can be sent to the server. It has a higher priority than data send period (s).	Minimum value = 1 Maximum value = 225

Race mode

Race Mode is an accuracy focused operating mode that controls periodic record timestamps strictly by GPS time (NMEA). It is designed to improve timestamp precision and prevent unexpected coordinate jumps during movement.

Prerequisites and Important settings

Race Mode should be enabled only when short sending periods are used and high timestamp accuracy is required during movement.

Basic operation

When Race Mode is enabled, periodic record generation is synchronized directly to GNSS time while the device is moving. Records are created only after the configured Min Saving Period elapses, using the timestamp provided by the GPS module together with all required GNSS data.

Compatibility conditions Race Mode is available only when all of the following conditions are met:

Location source is set to GNSS
Tracking mode is not Basic (for ATx mini devices)
Device is in a movement capable tracking mode (e.g. Movement mode)

Limitations, Edge Cases & Additional Notes

Race Mode operates only while device movement is detected.
If the device enters On Stop state, or if GNSS fix is lost, periodic records are generated using the standard flow:

Without GPS data
Without GPS based time synchronization

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.

When GNSS data is saved and transmitted according to the configured Scheduler, GNSS FIX acquisition for the next record is started earlier than the scheduled time. The advance start time is dynamically calculated based on the GNSS FIX acquisition duration of the previous record.

Key points:

The advance time cannot exceed the configured GNSS FIX search timeout.
The maximum allowed advance offset is up to 10 minutes.

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.