Template:Common configuration issues of TAT100

From Wiki Knowledge Base | Teltonika Mobility
Revision as of 09:52, 20 June 2022 by Veronika (talk | contribs)

(diff) ← Older revision | Approved revision (diff) | Latest revision (diff) | Newer revision → (diff)


1. Data is being sent too often

Tata periodic.png

Consequences:
Battery of the device will discharge in a few days.

Reasons:
If default Tracking Period (360 sec.) is set the device will send data about 240 times a day. Sending 240 records a day will cause a full battery discharge in about 3 days.


2. Scheduler is not configured properly

Selecting days.gif

Consequences:
Device will not send any record.

Reasons:
Days of the week are not selected by pressing on them. Active days are marked in blue color. If a day marked in grey color - records will not be sent for that day even if the times are configured.


3. Always try to keep GNSS antenna facing the sky

TAT100 Antenna.png

Consequences:
Device has up to 3 min. hardcoded time to get fixed position while it's awake from a Sleep Mode. If GNSS signal is poor - device will need more time to get fixed position. Battery usage is higher while device is looking for GNSS positions than it stays in Sleep Mode. So, mounting the device with GNSS antenna facing down causes shorter battery life and there is a possibility that device will not obtain position at all.

Reasons:
It's more difficult to get positions for the device if GNSS antenna is looking downwards. So, always try to keep GNSS antenna facing the sky, no matter where the device is mounted.


4. Periodic tracking misconfiguration

TAT100 Tracking misconception.png


If On Move tracking period is configured to be greater than On Stop, when devices detects movement, On Move countdown will start and data package will be sent to the server once On Move countdown completes.