TMT250 Features settings

From Wiki Knowledge Base | Teltonika Mobility
Main Page > Personal Trackers > TMT250 > TMT250 Configuration > TMT250 Features settings

Over Speeding

Tmt250 over speeding.png

This feature is used to prevent the driver from exceeding fixed speed and inspects the driver if needed. When vehicle speed exceeds maximum configured speed value the scenario is activated, and a record is generated. Scenario is activated until speed value decreases below the set parameter value.


TMT250 Alarm window.jpg

This function can only be triggered by the configured button. When the alarm is triggered, an event with IO ID 236 is generated. Eventually an SMS will be sent informing user about the event. A call possibility is also available if desired number is selected near Call to parameter. In addition, users are allowed to configure event priority. Two options are available - Call where voice call comes first and Record where data transmission to servers will be prioritized over a voice call.


TMT250 mandown.JPG

This feature gets current accelerometer data and calculates angle between offset positions. Currently there are two positions: horizontal (when device is in horizontal position and alarm button is on top) and vertical (when device is in vertical position and magnetic USB connector is facing up). Scanning is performed each second. If On-Entrance option is selected, event will be generated once calculated angle exceeds configured threshold for configured timeout. If On-Exit option is selected, event will be generated once device exits ManDown scenario. If On-Both is selected, event will be generated both times. SMS event and/or call takes place, if it is configured.

Horizontal position
Vertical position
Horizontal position
Vertical position

Event Notification

GH5200 EventNotification.png

The purpose of this function is to notify any alarm events by sending an SMS message to up to 5 receivers and to call up to 5 pre-defined numbers.
These high priority events can be configured:

  • Alarm;
  • ManDown;
  • Movement Event.

At least one of the following has to be selected for this feature to work - Alarm, ManDown or Movement Event. In addition, at least one SMS Number or one Call Number has to be configured.

Users are allowed to configure SMS sending method. Two options are available - GPRS or SMS option which sends an SMS when GPRS fails and GPRS and SMS option which sends an SMS when GPRS fails or device sends records to the server.

Call Answer Timeout is used for indicating successful call - if voice call was answered but configured time-out has not been reached, the voice call is considered unsuccessful and if only one number is configured, the device repeats the call as many times as the value configured in Call Repeat field. However, if the call is not successful and there are other predefined numbers selected, the device continues to call other configured numbers instead of repeating voice calls to the same number.

NOTE! Some operators provide voice information when the recipient is unreachable or call is not accepted. Such voice information may last longer than the configured time. In that case, the call will be considered as accepted.

Movement Event

Movement Event.png

Movement Event scenario makes an eventual high priority record (and sends an optional SMS) when the device is stationary or in motion (depending on configured "Mode") for set Timeout.
Timeout is a configured amount of time (in seconds) after which an eventual high priority record is generated.
Movement Event mode generates a record after the start of movement whereas No Movement Event generates a record after the stop of movement.

NOTE! In case if No Movement Event is selected as Mode, then Pre Alarm Timeout is counted additionally.

ManDown/No/Movement while charging disables Mandown, No Movement, Movement events while on device is charging.

Additional Features

GH5200 User ID.png

User ID feature allows users to send custom number as AVL ID 854 parameter.


TMT250 with ankle strap.jpg

This functionality is adapted to the TMT250 with a tamper case holder (bracelet). Tamper detection works by checking the voltage level between the USB Data Plus and Data Minus outputs. This functionality must allow the device to charge normally. This functionality can be enabled via a configurator or sms message. After turning on the device, tamper detection is delayed by 60s. When the bracelet is disconnected or damaged, the device turns on the indication, calls to the specified number, generates a record, and sends an SMS.

Bw nb1.png NOTE! When the functionality is enabled, communication via USB will no longer work. However, the functionality can be disabled via TCP / SMS or within 60 s. after restart via configurator.

Tamper feature is available with Firmware Version 55.01.02.Rev.200 and Teltonika Configurator 1.5.15

Tamper feature sends records with AVL ID 520

Tamper cfg.png

How Tamper configuration looks in the configurator is shown on the right. You can enable or disable this functionality by pressing one of the buttons.

  • Call To specifies the phone number from 10 GSM Predefined Numbers list to which alarm call will be made.
  • Send SMS To specifies the phone number from 10 GSM Predefined Numbers list to which SMS text will be sent.
  • SMS Text defines SMS text that will be sent when tamper event is generated.

Amber Alert

NOTE! Amber Alert can be tested on FW 55.00.10.Rev.01 or newer

Important Amber Alert parameters in features section:
Timeout: Defines time until Amber Alert alarm is processed.
Pre-Alarm: Sets the remaining time, when the pre-alarm should be triggered.
Order Priority: Defines call or record priority.
When Call is selected, device will call to defined number and creates Amber Alert record.
When Record is selected, device will create Amber Alert record and calls to defined number.
Initial call number: Select a number from 10 GSM Predefined Numbers list to which alarm call will be made.
Alarm call number: Select a number from 10 GSM Predefined Numbers list to which alarm call will be made.
Send SMS To:Selects number from 10 GSM Predefined Numbers list to which Amber Alert SMS will be send.
SMS Text:Defines SMS text that will be send when Amber Alert event will be generated.

Last Known Position

Last Known Position.png
NOTE! Last Known Position can be tested on FW 55.00.10.Rev.01 or newer

This feature adds low priority record AVL ID 386 to all records.
The record shows how much time in seconds has passed since last GNSS fix.

Alert.png This feature affects Alarm, ManDown, Movement event and Amber Alert features.

If the last good coordinate at the time the record is created is older than 60 seconds, then the new high priority record AVL ID 69 will be sent immediately after GNSS fix appears. No matter how many different records have been created when there was no GNSS fix, only one high priority AVL ID 69 record will be created when GNSS fix appears.

Heart rate Alert

NOTE! Heart rate Alert feature is available on FW 55.00.21.Rev.00 or newer

When this feature is enabled, handheld device searches for configured Xiaomi Mi Band 2 MAC address. When the band is found, handheld device initiates connection. Once connected, it tries to authenticate with the band. If authentication succeeds, handheld queries the time set in Xiaomi Mi Band 2. When time difference between synchronized handheld and the band is more than 30 seconds, Teltonika device sets its time to band, taking into account configured time zone.

When this initial process is done, one-time heart rate measurement request is sent to Xiaomi Mi Band. Usually it takes 7 to 14 seconds for the measurement. Afterwards, at each ‘Scan Period’ (param ID 1802) a new heart rate measurement is made and saved.

If the measured heart rate is outside the configured Min/Max rates, there will be a call to a specified number and High priority record made. Order priority: call, then record sending.

NOTE! Heart rate that is within Min/Max is saved in a low priority periodic record with AVL ID 403.

Otherwise it is saved in eventual high priority record with the same AVL ID: 403. They are sent according to ‘Send Period’ configured in ‘Data Acquisition’.