TAT140 System settings

From Wiki Knowledge Base | Teltonika Mobility

System Settings

System settings TAT100.png

GNSS Source settings

User can configure which GNSS system(s) to use.
User has a choice to use only one system between GPS, GLONASS, Galileo or Beidou and it is possible to choose two or three systems together. One exception is that you cannot combine BeiDou and GLONASS systems together.

Examples of non-configurable GNSS source combinations are:

  • GLONASS + BeiDou;
  • Galileo + GLONASS + BeiDou;
  • GPS + GLONASS + BeiDou;
  • GPS + Galileo + GLONASS + BeiDou.

List of configurable GNSS sources:

  • GPS only;
  • GPS + BeiDou;
  • GPS + GLONASS;
  • GPS + GLONASS + Galileo.

Data Protocol

User can choose which protocol version to use for data sending to server.

  • Codec 8 supports up to 255 AVL ID;
  • Codec 8 Extended supports up and above 255 AVL ID.

Tracking with LBS

LBS1.jpg

LBS - location based services. It helps us to find the approximate location without using a GNSS, but using cell towers information instead. Device cannot find the location using LBS by itself, approximate location is calculated on the server side according to the information provided by the device. Therefore, to locate a unit by LBS the device should send at least 4 parameters: mcc, mnc, lac, cell ID.


  • If LBS is selected as a location source, the device will send information about the cell towers to the server and will not use GNSS.
  • If GNSS or LBS is selected, device will use GNSS if the satellites are visible, if not - it will start sending cell towers information to the server, which will be able to calculate the approximate location using LBS.

Also, GSM Cell ID and Active GSM Operator should have at least Low priority in I/O settings.

LBS IO.jpg





Coordinate acquisition timeout

The configured time adds a delay when the coordinates of the device are taken to stabilize and ensure accuracy. Important thing to note that TAT100 can take up to 180 seconds to get the GPS fix and the configured timeout would only go after the GPS fix timeout has finished or the coordinates were received.

Static Navigation Settings

Static navigation PT.png

Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.

When enabled the device monitors the accelerometer and registers movement events by configured movement sensitivity. When the device wakes up to save and send a periodic record, and movement was not registered, the device will use the last known coordinates and will generate a record without turning ON the GPS module. However, if there are no last known coordinates, then the device will enable the GPS module and will try to get a new GPS fix.


The functionality is illustrated in the flowchart below:

Staticnavflowchart.png


Movement sensitivity

This feature sets the sensitivity threshold levels for movement event registration. Higher configured level makes the device “less sensitive” and vice versa. Currently, there are 10 configurable Movement Sensitivity levels. Levels are measured in mG - thousandth parts of the gravitational force equivalent or gravitational acceleration of Earth (9.8 m/s). It means that if Movement Sensitivity is set to 1000 mG, the device has to be free falling, experience fierce stops/accelerations or vibrations to detect movement.

Time Synchronization

Time synchronization.PNG

User can select which NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.