TST100 System settings

From Wiki Knowledge Base | Teltonika GPS
Main Page > E-Mobility Trackers > TST100 > TST100 Configuration > TST100 System settings

System Settings

Movement Source

User can select which source will be used to determine when vehicle is on stop or moving. When multiple are selected, if any of selected are active, Vehicle MOVING mode is used. Available movement source:

Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png
  • Ignition: checks ignition settings which depends on Ignition Source settings;
  • GNSS: movement detected if Fix position available and speed is bigger or equal to 5km/h;
  • Accelerometer: movement detection depends on Accelerometer Delay Settings;
  • CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.

When multiple source are selected, if any of selected are active, Movemenet is detected.

Records settings

Here user can enable or disable records when GPS is not available (no GPS fix).

  • After Position Fix - Device must have GPS fix and time to save/send records.
  • After Time Sync - Device must have correct time to save/send records. Allows record sending with no coordinates.
  • Always - Always save/send records. Allows record sending with no coordinates and no correct time.

LED Indication

User can turn on or off the indication LEDs.


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.

Battery Charge Mode

Here user can change battery charger settings, where charging is allowed. Battery will be charged: On Need (battery will be charged anytime when it needs to be charged) and After Ignition ON (battery will be charged only when ignition is on).

Three charging modes is available:

  • On neeed: charger enabled if external voltage is higher than 5.05 voltage and Battery Voltage is below 3.90V. Charging is disabled if device enters any sleep mode.
  • After Ignition On: charger enabled after ignition is turned on, except if the battery is fully charged or 10-minute timeout has not passed since the device was turned on for faster FIX receiving.
  • Always: charger is always enabled, except if the battery is fully charged or 10-minute timeout has not passed since the device was turned on for faster FIX receiving.

Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png

DOUT Overcurrent protection

DOUTs have overcurrent protection that triggers after the current exceeds 300 mA. This protection works by generating pulses on the hardware. When the firmware detects at least 20 impulses on a DOUT it turns off that DOUT for 5 minutes. During this time all scenarios that try to turn this DOUT on will fail.


Static Navigation Settings

Static navigation PT.png

Static Navigation mode is a filter, which filters out track jumps when the object is stationary. If static navigation filter is disabled, it will apply no changes to GPS data. If static navigation filter is enabled, it will filter changes in GPS position if no movement (as defined by configured movement source) or ignition (as defined by configured ignition source) is detected. It allows filtering GPS jumps when the object is parked (not moving) and GPS position is still traced.
Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation.

Call Duration Limits

Call duration limits.png

These is two places for these settings. First one can be found in the SMS \ Calls Settings section. This setting applies to incoming and outgoing calls, except for the keyboard “Call” action and the Amber Alert feature.

Cal duration limit2.png

Second one can be found in the Keyboard section. These settings are only visible when the button action is Call. There is only one parameter per button, so the same parameter applies to all button presses.

Sleep Mode

User can choose sleep mode. More about sleep modes can be found here.
Sleep mode TST100.png

BT/BLE module OFF during Sleep modes


Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.

From the version, 03.28.XX this new functionality includes new parameters:

  • Periodic Wakeup – if value is greater than zero, device while being in Deep Sleep or Online Deep Sleep, will wake up after defined period for beacon collection. This is mainly should be used when Bluetooth is disabled in sleep.
  • Bluetooth On While In Sleep- by default this parameter value is set to Enable and BT will work as in base functionality. If this value is set to Disable, Bluetooth will be turned off when device goes to Deep Sleep or Online Deep Sleep and will be turned on during Periodic Wakeup or if device enters normal state.
PWU.jpg



Note: In case when during scan after wakeup no BLE devices will be found FMB will be active for configured scan duration time in Bluetooth 4.0 tab. After that timeout FMB will go to sleep state.

Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state and can only wake up if one of the conditions is true:

  • Movement is detected by accelerometer (not by the configured movement source);
  • External power is applied;
  • It is the time to make a new periodic record (new feature);


Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.

Movement Settings

Accelerometer settings.png

Here the user can set the movement start/stop delays.
For example, if the Movement Start Delay is set to 1s and Movement Stop Delay to 60s, the movement will be detected after 1s of moving and defined as stopped after 60s when device stopped moving. Accelerometer Sensitivity in Sleep parameter defines how much movement device needs to experience to exit sleep mode. The lower the sensitivity - the more movement is required.

  • Minimal – approximately 40% higher movement threshold comparing to Normal
  • Reduced – approximately 20% higher movement threshold comparing to Normal
  • Normal – recommended value for most users
  • Increased – approximately 20% lower movement threshold comparing to Normal
  • Maximum – approximately 40% lower movement threshold comparing to Normal

Changing Accelerometer Sensitivity in Sleep parameter might result in fake movement record or skipped movement events! Only change that if you experience problems with movement detection!

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.

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

Parameter ID Name Value/Type Min Max Default
901 NTP Resync (hours) uint8 0 24 0
902 NTP Server 1 char 0 55 avl1.teltonika.lt
903 NTP Server 2 char 0 55 pool.ntp.org

Time synchronization works by waiting a minute on startup to acquire fix and consequently synchronizes the time via GNSS. If the firmware acquires the fix, it starts working in the syncing by GNSS state. This state checks the difference of RTC and GNSS times every second. If the difference of at least 3 seconds persists to be for 5 seconds, the firmware triggers a procedure by GNSS.

After that, the the time difference is still calculated, but the difference is expected to persist for at least 5 minutes to trigger a GNSS time resynchronization. This is done to prevent false GNSS timestamps (such as year 2080 and etc.). If there’s no time difference found, the difference is expected to persist again for a period of 5 seconds later on when calculating. In the case that there is no fix or it is lost during the syncing by GNSS state, the firmware goes to state of syncing by NTP.

Entering the state of NTP syncing, the firmware immediately attempts to synchronize the time by triggering NTP and later on, does this periodically every time the configured NTP resynchronization time is reached. If the NTP resynchronization time is set to 0, no periodical resynchronization is done in this state. Time synchronization by NITZ can occur any time.

Time sync chart.png

Mounting Guidelines

The device should be mounted according to the picture below. Logo/Antenna must be facing up.

Screenshot 2024-03-04 at 09-01-13 tft100-mounting-guidelines.jpg (JPEG Image 900 × 600 pixels).png













Accelerometer delay

Configurable movement start/stop delay settings.

Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png

{