Teltonika Telematics Wiki - User contributions [en]

Universal Device Test Guide

2024-06-21T05:46:08Z

Andrius.abraskevicius: /* STEP 2: Connect the device to PC */

__TOC__
=='''<big>Introduction</big>'''==
[[File:Welcome to the telematics banner 1.1.png]]

Universal Device Testing Guide can be applied to any Teltonika Telematics device. The purpose of this guide is to help new users get acquainted with Teltonika Fleet Management devices and test basic functions in 5 easy steps.

Once you are finished with basic testing, you will find additional instructions on how to test specific use cases and advanced features of our devices as well as remote tracker management platform and other solutions.

In case you have any questions regarding Teltonika devices or their features, do not worry - we have a well of knowledge called '''[[Main Page|Teltonika WIKI]]''', '''[https://community.teltonika.lt/c/teltonika-telematics/6 Teltonika Telematics Community page]''' and our '''[https://www.youtube.com/channel/UCjWIn5amqvtWc7X7tI_04LQ Official Youtube Channel]''', where you can find answers regarding our devices functionalities and specifications.

If you do not find answers to your questions online - do not despair, we have a highly professional team of support engineers who are willing to help and can be reached via Helpdesk.

=='''<big>Basic Testing</big>'''==
[[File:5 easy steps to prepare any Teltonika Telematics device banner.png]]

In this chapter, we will go through 5 easy testing steps which will help you get acquainted with Teltonika Telematics devices. We will cover everything you need to start using the device - from inserting a SIM card, powering the device, and ending with GPS track information directly from your vehicle to the server.

The video below shows the preparation of FMC880 device - please note that the initial steps are universal and can be applied to majority of our devices.

<youtube width="850" height="480">GDGFG6Lh1B0</youtube> ''*Please note that the '''iot.truphone.com''' APN shown in the video should only be used with Truphone SIM cards - please contact Your network operator for the exact APN details, if You are using different SIM cards.''

==='''STEP 1: Prepare the Device'''===
'''''Result: Device has a SIM card installed and internal battery connected'''''

All our devices use SIM cards for telecommunication, thus you will not be able to get any data and/or communicate with the device remotely without the SIM card. In this chapter, you will find a guide on how to insert a SIM card and connect the internal battery.

''Note:'' Different Teltonika devices use different SIM card types: mini-SIM, micro-SIM, nano-SIM, and [[Requirements for eSIM|'''eSIM''']] (which is soldered during device manufacturing process).

'''How to insert SIM card and connect the battery?'''
#Gently remove '''device cover''' using '''plastic pry tool''' from both sides as it is showed in a 1st picture.
#After opening device cover, you will see '''SIM card''' and '''battery''' connection '''slots'''.
#Insert '''SIM''' card as shown with '''PIN request disabled''' or read '''[[FMB120 Security info|Security info]]''' (Universal Guide) how to enter it later in Configurator. Make sure that SIM card '''cut-off corner''' is pointing forward to slot.
#Connect the battery as shown on device. Position the battery in place where it does not obstruct other components.
#Attach device '''cover''' back. Device is ready to be connected.

You can find how exactly the SIM card has to be inserted (and battery connected, if the device comes with one) by seeing the pictures below:

<div class="toccolours mw-collapsible mw-collapsed">
Basic trackers
<div class="mw-collapsible-content">
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMB900
|-
|[[Image:Fmb900_cover_1.png|500px]]
|[[Image:Fmb900_cover_2.png|500px]]
|[[Image:Fmb900_cover_3.png|500px]]
|[[Image:Fmb900_cover_4.png|500px]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMB910, FMB920, FMB930 
|-
|{{{SIM1|[[Image:FMB9_sim_ir_battery_insert-1.png|500px]]}}}
|{{{SIM2|[[Image:FMB9_sim_ir_battery_insert-2.png|500px]]}}}
|{{{SIM3|[[Image:FMB9_sim_ir_battery_insert-3.png|500px]]}}}
|{{{SIM4|[[Image:FMB9_sim_ir_battery_insert-4.png|500px]]}}}
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMC920, FMM920 
|-
|{{{SIM1|[[File:FMC920 1.png|500px]]}}}
|{{{SIM2|[[File:FMC920 2.png|500px]]}}}
|{{{SIM3|[[File:FMC920 3.png|500px]]}}}
|{{{SIM4|[[File:FMC920 4.png|500px]]}}}
|{{{SIM5|[[File:FMC920_5.png|500px]]}}}
|{{{SIM5|[[File:FMC920_6.png|500px]]}}}
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMB965
|-
|{{{SIM1|[[Image:FMB965_sim_ir_battery_insert-1.png|260px]]}}}
|{{{SIM2|[[Image:FMB965_sim_ir_battery_insert-2.png|260px]]}}}
|{{{SIM3|[[Image:FMB965_sim_ir_battery_insert-3.png|260px]]}}}
|{{{SIM4|[[Image:FMB965_sim_ir_battery_insert-4.png|260px]]}}}
|{{{SIM4|[[Image:FMB965_sim_ir_battery_insert-5.png|260px]]}}}
|{{{SIM4|[[Image:FMB965_sim_ir_battery_insert-6.png|260px]]}}}
|}
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed">
Fast & Easy trackers
<div class="mw-collapsible-content">
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMP100
|-
|[[Image:FMP100 1.png|300px]]
|[[Image:FMP100 2.png|300px]]
|[[Image:FMP100 3.png|300px]]
|[[Image:FMP100 4.png|300px]]
|[[Image:FMP100 5.png|300px]]
|[[Image:FMP1000 6.png|300px]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMB010
|-
|{{{insert1|[[Image:Fmb010_cover_1.png|280px]]}}}
|{{{insert2|[[Image:Fmb010_cover_2.png|280px]]}}}
|{{{insert3|[[Image:Fmb010_battery_1.png|280px]]}}}
|{{{insert4|[[Image:Fmb010_cover_3.png|280px]]}}}
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMB020
|-
|{{{insert1|[[Image:Fmb020 card 1.png|280px]]}}}
|{{{insert2|[[Image:Fmb020 card 2.png|280px]]}}}
|{{{insert3|[[Image:Fmb020 card 3.png|280px]]}}}
|{{{insert4|[[Image:Fmb020 card 4.png|280px]]}}}
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMC800, FMM800, FMM80A
|-
|{{{insert1|[[Image:Fmm001_cover_1.png|280px]]}}}
|{{{insert2|[[Image:Fmm0001_cover_2.png|280px]]}}}
|{{{insert3|[[Image:Fmm001_battery_1.png|280px]]}}}
|{{{insert4|[[Image:Fmm001_cover_3.png|280px]]}}}
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMT100, FMC880, FMM880
|-
||[[Image:FMT100_sim_insert-1.png|170px]]     [[Image:FMT100_sim_insert-2.png|170px]]
|[[Image:FMT100_sim_insert-3.png|170px]]     [[Image:FMT100_sim_insert-4.png|170px]]
|[[Image:FMT100_sim_insert-5.png|170px]]     [[Image:FMT100_sim_insert-6.png|170px]]
|}
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed">
Advanced trackers
<div class="mw-collapsible-content">
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMB110
|-
|[[Image:{{{sim_insert_pic1|FMB110-Battery-1.png}}}|260px]]
|[[Image:{{{sim_insert_pic2|FMB110-Battery-2.png}}}|260px]]
|[[Image:{{{sim_insert_pic3|FMB110-Battery-3.png}}}|260px]]
|[[Image:{{{sim_insert_pic4|FMB110-Battery-4.png}}}|260px]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMB120, FMB122, FMB130, FMC130, FMM130
|-
|[[Image:{{{sim_insert_pic1|FMB1_cover1_correct.png}}}|260px]]
|[[Image:{{{sim_insert_pic2|FMB1_cover2_correct.png}}}|260px]]
|[[Image:{{{sim_insert_pic3|FMB1_cover3_correct.png}}}|260px]]
|[[Image:{{{sim_insert_pic4|FMB1_cover4_correct.png}}}|260px]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMC13A, FMM13A
|-
|[[Image:FMC13A_cover1_correct.png|280px]]
|[[Image:FMC13A_cover2_correct.png|280px]]
|[[Image:FMC13A_cover3_correct.png|280px]]
|[[Image:FMC13A_cover4_correct.png|280px]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMB202, FMB204, FMB209
|-
|[[Image:case7.png|250px]]
|[[Image:case4.png|250px]]
|[[Image:case2.png|250px]]
|[[Image:case5.png|250px]]
|[[Image:case3.png|250px]]
|[[Image:case6.png|250px]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMB230
|-
|[[Image:FMX2YX_cover_open1_correct.png|280px]]
|[[Image:FMX2YX_cover2_correct.png|280px]]
|[[Image:FMX2YX cover3 correct.png|280px]]
|[[Image:FMX2YX_cover4_correct.png|280px]]
|[[Image:FMX2YX_cover5_correct.png|middle|280px]]
|[[Image:FMX2YX_cover6_correct.png|middle|280px]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMC230, FMM230, FMC234
|-
|[[Image:FMX2YX_cover_open1_correct.png|280px]]
|[[Image:FMX2YX_cover2_correct.png|280px]]
|[[Image:FMX2YX SIM insert FMC230.png|280px]]
|[[Image:FMX2YX_cover4_correct.png|280px]]
|[[Image:FMX2YX_cover5_correct.png|middle|280px]]
|[[Image:FMX2YX_cover6_correct.png|middle|280px]]
|}
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed">
OBD trackers
<div class="mw-collapsible-content">
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMB001
|-
|{{{insert1|[[Image:Fmb010_cover_1.png|280px]]}}}
|{{{insert2|[[Image:Fmb010_cover_2.png|280px]]}}}
|{{{insert3|[[Image:Fmb010_battery_1.png|280px]]}}}
|{{{insert4|[[Image:Fmb010_cover_3.png|280px]]}}}
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMB002, FMB003
|-
|{{{insert1|[[Image:Fmb020 card 1.png|280px]]}}}
|{{{insert2|[[Image:Fmb020 card 2.png|280px]]}}}
|{{{insert3|[[Image:Fmb020 card 3.png|280px]]}}}
|{{{insert4|[[Image:Fmb020 card 4.png|280px]]}}}
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMC001, FMC003, FMC00A, FMM001, FMM003, FMM00A
|-
|{{{insert1|[[Image:Fmm001_cover_1.png|280px]]}}}
|{{{insert2|[[Image:Fmm0001_cover_2.png|280px]]}}}
|{{{insert3|[[Image:Fmm001_battery_1.png|280px]]}}}
|{{{insert4|[[Image:Fmm001_cover_3.png|280px]]}}}
|}
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed">
CAN trackers
<div class="mw-collapsible-content">
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMB140, FMC150, FMM150
|-
|[[Image:{{{sim_insert_pic1|FMB1_cover1_correct.png}}}|260px]]
|[[Image:{{{sim_insert_pic2|FMB1_cover2_correct.png}}}|260px]]
|[[Image:{{{sim_insert_pic3|FMB1_cover3_correct.png}}}|260px]]
|[[Image:{{{sim_insert_pic4|FMB1_cover4_correct.png}}}|260px]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMB240
|-
|[[Image:FMX2YX_cover_open1_correct.png|280px]]
|[[Image:FMX2YX_cover2_correct.png|280px]]
|[[Image:FMX2YX SIM insert FMC230.png|280px]]
|[[Image:FMX2YX_cover4_correct.png|280px]]
|[[Image:FMX2YX_cover5_correct.png|middle|280px]]
|[[Image:FMX2YX_cover6_correct.png|middle|280px]]
|}
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed">
Professional trackers
<div class="mw-collapsible-content">
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMB641
|-
|[[Image:Fmb640FMB640111.png|260px]]
|[[Image:Fmb640-FMB640222.png|260px]]
|[[Image:Fmb640FMB640333.png|260px]]
|[[Image:Fmb640FMB640444.png|260px]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMC650, FMM650
|-
|[[Image:{{{sim_insert_pic1|{{{model|Fmb640}}}-cover-1.png}}}|260px]]
|[[Image:{{{sim_insert_pic2|{{{model|Fmb640}}}-cover-2.png}}}|260px]]
|[[Image:{{{sim_insert_pic3|{{{model|Fmb640}}}-cover-3.png}}}|260px]]
|[[Image:{{{sim_insert_pic4|{{{model|Fmb640}}}-cover-4.png}}}|260px]]
|[[Image:{{{sim_insert_pic4|{{{model|Fmb640}}}-cover-5.png}}}|260px]]
|[[Image:{{{sim_insert_pic4|{{{model|Fmb640}}}-cover-6.png}}}|260px]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMB125, FMC125, FMM125
|-
|[[Image:{{{sim_insert_pic1|FMB1_cover1_correct.png}}}|260px]]
|[[Image:{{{sim_insert_pic2|FMB122-Battery-Sim-2.png}}}|260px]]
|[[Image:{{{sim_insert_pic3|FMB1_cover3_correct.png}}}|260px]]
|[[Image:{{{sim_insert_pic4|FMB1_cover4_correct.png}}}|260px]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|FMC225
|-
|[[Image:FMX2YX_cover_open1_correct.png|280px]]
|[[Image:FMX2YX_cover2_correct.png|280px]]
|[[Image:FMX2YX SIM insert FMC230.png|280px]]
|[[Image:FMX2YX_cover4_correct.png|280px]]
|[[Image:FMX2YX_cover5_correct.png|middle|280px]]
|[[Image:FMX2YX_cover6_correct.png|middle|280px]]
|}
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed">
Autonomous trackers
<div class="mw-collapsible-content">
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|TAT100, TAT140, TAT240
|-
|[[Image:TAT100 Cover off.png|275px]]
|[[Image:TAT100 SIM in.png|275px]]
|[[Image:TAT100 Device on V3.png|275px]]
|[[Image:TAT100 Cover on.png|275px]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|TMT250
|-
|[[Image:Tmt250battery1.png|185px]]
|[[Image:Tmt250battery2.png|185px]]
|[[Image:Tmt250battery3.png|185px]]
|[[Image:Tmt250battery4.png|185px]]
|[[Image:Tmt250battery5.png|185px]]
|[[Image:Tmt250battery6.png|185px]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|GH5200
|-
|[[Image:GH5200 battery sim insert-1.jpg|250px]]
|[[Image:GH5200 battery sim insert-2.jpg|250px]]
|[[Image:GH5200 battery sim insert-3.jpg|250px]]
|[[Image:GH5200 battery sim insert-4.jpg|250px]]
|}
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed">
E-Mobility trackers
<div class="mw-collapsible-content">
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|TST100
|-
|[[Image:TST100_setup_1.jpg|250px]]
|[[Image:TST100_setup_2.jpg|250px]]
|[[Image:TST100_setup_3.jpg|250px]]
|[[Image:TST100_setup_4.jpg|250px]]
|[[Image:TST100_setup_5.png|250px]]
|[[Image:TST100_setup_6.jpg|250px]]
|[[Image:TST100_setup_7.jpg|250px]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|TFT100
|-
|[[Image:Cover1.png|250px]]
|[[Image:Cover2.png|250px]]
|[[Image:Cover3.png|250px]]
|[[Image:Cover4.png|250px]]
|[[Image:Cover5.png|250px]]
|}
</div>
</div>

{|
|-
|[[File:Alert.png|left|link=]]||SIM card insertion/removal must be performed when device is powered off – external voltage {{{battery|and internal battery}}} disconnected. Otherwise SIM card might be damaged or device will not detect it.
|}

==='''STEP 2: Connect the device to PC'''===
'''''Result: Device is connected to the PC and powered with a power supply, allowing the user to configure it.'''''

One way to control your device is by connecting it to a PC. During this step, we will introduce you to how to establish the connection.

'''How to install USB drivers (Windows)?'''

Download COM port drivers from Teltonika '''[[Media:TeltonikaCOMDriver.zip|here]]''' and install them.

'''PC Connection (Windows)'''

Power-up device with '''DC voltage (10 – 30 V)*''' power supply using '''supplied power cable**'''. LED’s should start blinking, see “'''[[LED Status|LED behaviour description]]'''”.
 

Connect device to computer*** using '''USB cable''' or '''Bluetooth®''' connection.

''* FMB900, FMB910, FMB920, MTB100, FMB202, FMB204 devices support '''(6 - 30 V)''' DC power supply. FMB930 and TFT100 devices support '''(10-90V)''' DC power supply.''

<nowiki>**</nowiki> FMP100, FMB002, FMB020, FMB003 can be powered up and configured via USB without any need for an external power supply.

<nowiki>***</nowiki> If you would like to check how to connect your particular device to PC, please see device [[Main Page|'''Teltonika WIKI documentation.''']] Click on ''your device'' -> First Start -> PC Connection (Windows)

==='''STEP 3: Configure the Device'''===
'''''Result: Device is configured to generate and send records to the specified server.'''''

After powering up your device, it should be configured to meet your needs. Here you will find steps on how to prepare your device for a first start.

'''Configuration'''

At first, the device will have default factory settings set. These settings should be changed according to the user's needs. 
Main configuration can be performed via '''[[Teltonika Configurator]]''' software. Get the latest '''Configurator''' version from '''[[{{{SAS_Configurator_Versions|Teltonika Configurator versions}}}|here.]]''' Configurator operates on Microsoft Windows OS and uses prerequisite latest MS .NET Framework.

The configuration process begins by pressing on the connected device:

[[File:Faceless_configurator_select.png|370x370px]]

After connection to Configurator '''Status window''' will be displayed.

In the status window, you will be able to see crucial information that influences device operation such as GNSS and GSM statuses.

GNSS Info tab contains GNSS Status, Satellites, and Location information.

*GNSS Status describes whether the module is ON, received/sent GNSS packets count, FIX status and FIX time
*Satellites provide you information about visible and currently in-use satellites
*Location provides you the coordinates, speed, altitude, and angle of your current location.

GSM Info tab contains GSM Status, Records, GPRS Traffic, SMS Count, and Sockets information

*GSM Status describes modem status, SIM state, GPRS status, signal level, and operator code
*Records provide you information about sent records count and the date of the last record sent/server response
*GPRS Traffic contains information about data usage
*SMS Count shows you sent/received SMS count
*Sockets provide status about AVL Data server communication

{| class="wikitable"
|+
GNSS/GSM Status
!Illustration
!Description of most important parameters
|-
! rowspan="2" |[[File:GNSS Info.png|frameless|800x800px]]
|Module status - here you will be able to see whether the module is ON or in Sleep mode.
|-
|Fix Status - Fix/No Fix. For a GNSS fix, at least 4 visible satellites are needed, thus for best performance, the device should be facing an open sky.
|-
| rowspan="3" |[[File:GSM Info.png|frameless|801x801px]]
|Signal Level - make sure that the signal is available in order to send the data to the server.
|-
|Type - AVL Data sending status.
|-
|Socket - Closed or Server domain and port which is used when sending AVL Data via TCP/UDP.
|}
Various '''Status window''' tabs display information about '''GNSS, GSM, I/O, Maintenance''' and etc. configuration can be loaded and saved to the device. '''After changing the configuration, make sure that modifications are saved by clicking "Save to device" button.''' To restore default configuration, click '''"Reset configuration"''' button.

{| class="wikitable"
|+
|[[File:Testing_always_sending.png|alt=|frameless]]
|'''Note:''' make sure that "Records Saving/Sending Without TS" in System Tab is configured as "Always" ''for testing purposes.''
This will allow the device to send the data even if there is no GNSS fix (which is hardly obtained inside the buildings) and/or time synchronization.
|}

The most important configurator section is GPRS – where all your server and '''GPRS settings''' can be configured and '''Data Acquisition''' – where data acquiring parameters can be configured.

{| class="wikitable"
|+
GPRS Settings
!Illustration
!Parameter ID
!Description
|-
! rowspan="3" |[[File:GPRS_settings.png|alt=|frameless|400x400px]]
|2001
|'''A'''ccess '''P'''oint '''N'''ame is a gateway between mobile operator and public internet.
It can be obtained from your SIM card provider.

When correct APN settings will be entered device will connect to the internet.

Note: we do have an auto APN functionality, which is described [[Auto APN feature for FM trackers|'''here''']]
|-
|2003
|APN password (if there are no APN password, empty field should be left)
|-
|2002
|APN username (if there are no APN username, empty field should be left)
|-
| rowspan="3" |[[File:SERVER_settings.png|alt=|frameless|400x400px]]
|2004
|Domain/IP of destination server
|-
|2005
|Port of destination server
|-
|2006
|Data sending to destination server protocol (0 – TCP, 1 – UDP)
|}
[[File:SMS_testing.png|alt=|347x347px|thumb|Picture 4: SMS communication between user and device]]

'''Note:''' If you do not have GPS tracking service yet, you can use Teltonika TCP/UDP listener to receive data from the device and Teltonika parser to parse received information. Software can be downloaded from [[Special:Redirect/file/Protocols_and_AVL_parser_pack.zip|'''here.''']] Archive password: 1234

 
If you do not want to configure your device via configurator, you can quickly set up your device GPRS settings by sending this SMS command to it:
" setparam 2001:APN;2002:APN_username;2003:APN_password;2004:Domain;2005:Port;2006:0"
'''Note''': Before SMS text, two space symbols should be inserted.

After successful GPRS/SERVER settings configuration, device will '''synchronize time''' and '''update records''' to '''the configured server''' according to the Data Acquisition time intervals. The default configuration has optimal parameters present to ensure the best performance of track quality and data usage. However, '''''for testing''''', we do recommend these Data Acquisition settings:
{| class="wikitable"
|+
Testing Data Acquisition settings
!Illustration
!Parameter ID
!Description
|-
! rowspan="3" |[[File:Testing_Data_Acquisition_V2.png|alt=|frame|Picture 5: Recommended Data Acquisition values for testing purposes]]
|'''10000'''
|'''Min period''' indicates time interval in seconds in order to acquire new record.
|-
|'''10004'''
|'''Min Saved Records''' defines the minimum number of records in one data packet that can be sent to the server.
|-
|'''10005'''
|'''Send Period''' indicates time interval in seconds after which the device checks whether it has generated enough records based on the'''Min Saved Records''' parameter. If enough records are generated, the device will send them to the server. If the interval is set to 0 seconds, the device will not send any records to the server.

''Note:'' If the link with the server is already open, records are sent to the server immediately after they are generated.
|}

The device will generate periodic records and send them to the server based on Data Acquisition settings.

Using these settings, the device will make a periodic record every 30 seconds and will send it every 30 seconds

After testing, Data Acquisition settings should be configured according to your needs.

The device will switch operating mode between On Stop and Moving based on configured corresponding movement source status.

More details about devices configuration using Configurator and more information about your particular device can be found [[Main Page|'''Teltonika WIKI documentation.''']] Click on ''your device'' -> Configuration.

==='''STEP 4: Mount the Device'''===
'''''Result: Device is mounted in an optimal location, allowing it to have good GNSS and GSM connectivity.'''''

Different types of devices have specific mounting instructions: some of them are simple plug-and-play, while other hard-wired devices require professional installation. Please find your specific device mounting instructions [[Main Page|'''Teltonika WIKI documentation.''']] Click on ''your device'' -> First Start -> Mounting recommendations and precautions.

'''Installation instructions'''

[[File:Mounting picture 02-01.png|frameless|806x806px]]

==='''STEP 5: Track the Device'''===
'''''Result: User is able to track his device on the tracking platform.'''''

Last but not least step for Basic Testing would be to get data/track from your device.

This can be done by using either simple TCP/UDP listeners or pre-made tracking platform like listed [[Fleet Management platforms|'''here.''']]

Below you can find steps on how to set up a simple TCP/UDP listener on your personal computer.

#Open [[Opening TCP/UDP port|'''TCP/UDP port''']]
#Go to [[Java Parser First Start Guide|'''Java Parser First Start Guide''']]

Below you can find pictures of how the track looks on different pre-made tracking platforms:

[[File:TAVL jamming.png]]

[[File:Wialonturbo.jpg]]

=='''<big>Advanced Testing</big>'''==

[[File:Discover more device possibilities in-depth banner.png]]

In this chapter, we will review advanced device functionalities to get the most out of your Teltonika Telematics device. We will go through some of the specific, widespread use cases, however, keep in mind that device scenarios are not limited to just that. Available device functions can accomplish a much wider range of application scenarios, which will be limited only by your imagination!

==='''Advanced SMS capabilities'''===

Teltonika devices have a broad SMS usage spectrum including advanced device configuration and debugging. A full list of SMS commands can be found [[FMB SMS/GPRS Commands|'''here.''']]

For example, one of the most widely used SMS command for configuring the device is "setparam". Below you can see a description of this command:

Setparam changes parameter value. Command structure is: ''"<SMS_Login><Space><SMS_Password><Space>setparam<Space>[Parameter ID]'' ''':''' ''[New Parameter Value]'' ''';''' ''[Parameter ID]'' ''':''' ''[New Parameter Value]''..." Parameter ID consists of 3 or 5 digits. A detailed list of parameters and identifiers can be found [[FMB Device Family Parameter list|'''here.''']]
{| class="wikitable"
|+
|[[File:WIKI_hover.gif]]
|You can also find parameter ID by hovering the mouse pointer over specific parameter in the configurator.
|}
SMS command is limited to 160 characters.

Example:

"setparam 101:1" will change ignition setting to "DIN1".

Answer:

"Param ID:101 Value:1"

Example:

"setparam 101:2;138:1" will change ignition setting to "Accelerometer" and movement source to "Ignition"

==='''Advanced Use Case configuration'''===

Our devices can be as simple or as complicated as you want them to be. Having one firmware and one configurator for all the devices allows different devices to be used in a broad spectrum of use cases. Other use cases have specific devices assigned.

To show how easy it is to use our devices in different use cases we prepared a technical description of what steps are needed to integrate our device into your use case.

Each category explains what parameters have to be configured and why as well as showing examples of what information you should expect on your server and how to read it.

'''General''' use case descriptions, an overview of the most commonly used solutions, their topologies, and possibilities, provided on the Teltonika website '''[https://teltonika-gps.com/industries/use-cases/ USE CASES]'''.

'''Specific technical''' use case instructions can be found [[Usage scenarios|'''here.''']]

=='''<big>Solutions</big>'''==

[[File:Extend device's capabilities with our solutions banner.png]]

In this section, we will get acquainted with our most useful and simple to utilize solutions which will provide remote access, management, and control of your device as well as external devices like tachograph.

==='''FOTA WEB'''===

FOTA WEB – a brand new and exciting solution for remote access to your Teltonika Fleet management devices! FOTA WEB enables firmware upgrades, configuration changes, remote device debugging of FMx devices, as well as CAN adapter updates without a need of a dedicated application – everything is achieved through your regular Web browser, from any device. By default, the device connects to FOTA WEB every 720 minutes (parameter is configurable). For more information click '''[[FOTA WEB|here.]]''' If you would like to have your own FOTA WEB account, please contact your Sales Manager. [https://www.youtube.com/watch?v=SiMwnkEEes4 '''Short video about FOTA WEB.''']

Moreover, we also have a desktop FOTA solution: desktop ''FOTA is the predecessor of FOTA WEB, which is mainly used for updating EOL (End-Of-Life, - FM5300, FMA120, etc.) devices. We strongly advise to use our newest [[FOTA WEB|'''FOTA WEB''']] platform for OTA changes.''

'''''Note:''''' FOTA WEB meets all '''GDPR''' requirements thus '''we do not store, track or analyze your personal data.'''

==='''WEB Tacho'''===

Teltonika WEB Tacho is an online service that allows to remotely download Tachograph files from supported tachographs, using Teltonika professional trackers. Files are stored on server, in defined format (.DDD, .V1B, .C1B, .TGD). Files can be downloaded – directly from the website, receive in Email, receive to a defined FTP server. For more information click '''[[WEB Tacho|here.]]''' If you would like to have your own WEB Tacho account, please contact your Sales Manager.

=='''<big>Protocols</big>'''==

[[File:Understand communication language banner.png]]

Our devices communicate using unique Teltonika's protocols. Protocols are applied for different usage scenarios using Codecs. Each Codec has its own structure and application scenario. A codec is a device or computer program for encoding or decoding a digital data stream or signal.

==='''Data sending protocols'''===

Each Codec used by Teltonika devices has a different purpose. For example, [[Codec#Codec 8 Extended|'''Codec 8 Extended''']] is main FM device protocol used to send data to server, while [[Codec#Codec for communication over GPRS messages|'''Codec 12''']] is used for device-server communication using GPRS messages. All information about Teltonika's communication protocols used by FM devices can be found [[Codec|'''here.''']]

==='''Protocols implementation'''===

TCP/UDP listener and AVL Records parser, which source code could be used as a template for developing your own server, can be helpful for implementing protocols. A full software pack can be downloaded from [[Special:Redirect/file/Protocols_and_AVL_parser_pack.zip|'''here.''']] Archive password: 1234.

Each device I/O parameter has its own unique ID, which is called AVL ID. Once the TCP/UDP listener and AVL Records parser are implemented, received AVL IDs descriptions can be checked in the AVL ID list page for your specific device (for example: [[FMB120_Teltonika_Data_Sending_Parameters_ID|'''FMB120''']] ).

[[Category:General Information]]

General Information

2024-06-14T11:29:54Z

Andrius.abraskevicius:

[[Universal Device Test Guide|First time with a device]] 
[[General PCN]] 
[[Certificates overview]] 
[[Promotional Material]] 
[[Teltonika Data Sending Protocols]] 
 
[[Usage scenarios]] 
[[Fleet Management platforms]] 
[[Firmware versions]] 
[[Setting up Two-Factor Authentication (2FA) in HelpDesk]]

[[Category: Main Page]]

Setting up Two-Factor Authentication (2FA) in Partner Portal/HelpDesk

2024-06-14T11:28:48Z

Andrius.abraskevicius:

==Introduction==

Two-factor authentication (2FA) is a security process that requires users to provide two different authentication factors to verify their identity. These factors typically fall into three categories: something you know (like a password), something you have (like a smartphone or token), and something you are (like a fingerprint or iris scan). By requiring two different types of authentications, 2FA significantly enhances security compared to using only a password.

The reason why 2FA was introduced in Helpdesk, is to enhance security by adding an extra layer of protection against unauthorized access to sensitive data that may be shared, thereby mitigating the risk of data breaches and ensuring compliance with industry regulations.

==Setting the 2FA==

'''Things you'll need:'''

1.Your smartphone

2.Authenticator app (available on '''Google Play Store''' or '''Apple App Store''')

'''Download APP For Android OS:'''

[[File:GOOGLE_apps.jpg|500x700px]]

'''Download APP For Apple iOS:'''

[[File:APPLE_apps.jpg|500x700px]]

'''Steps:'''

'''1. Download and Install the Authenticator App (Microsoft Authenticator, Google Authenticator or similar)'''

'''1.1.''' Open the app store on your smartphone (Google Play Store for Android or Apple App Store for iPhone).

'''1.2.''' Search for e.g. "Google Authenticator" and install the app.

'''1.3.''' Depending on the app chosen, you may need to create or sign in with your Google or Microsoft account.

'''2. Sign in to Helpdesk account'''

'''2.1.''' Open the web browser and go to Helpdesk URL:
https://helpdesk.teltonika-iot-group.com

'''2.2.''' Log in to your account using your username and password.

'''3. Enable 2FA and proceed with the setup'''

'''3.1.''' After a successful login attempt, you will be presented with a pop-up window in the middle of the screen. This window will contain a large QR code and instructions to set up 2FA using an authentication app. Leave this window open.

[[File:2FA.png|alt=|left|453x453px|thumb]]

'''4. Sync Helpdesk with Authenticator app'''

'''4.1.''' Launch the Authenticator app on your smartphone.

'''4.2.''' Press “Add” and choose “Scan QR Code”: Use your phone's camera to scan the QR code displayed in the 2FA setup window on your computer screen. If desired, secret key can be entered manually by hand, we recommend to scan it with camera.

'''5. Verify and Complete Setup'''

'''5.1.''' After scanning the QR code or entering the secret key, a new account will be added to your Authenticator app.

'''5.2.''' The app will generate a unique 6-digit code that changes every minute.

'''5.3.''' Enter code displayed in your Authenticator app to Helpdesk window.

Once you enter the correct code, the 2FA setup will be complete.
From now on, with every new log in to Helpdesk, you will be asked to enter code displayed in your Authenticator app.

[[Category:General Information]]

Setting up Two-Factor Authentication (2FA) in Partner Portal/HelpDesk

2024-06-14T11:24:21Z

Andrius.abraskevicius: /* Setting the 2FA */

Setting up Two-Factor Authentication (2FA) in Partner Portal/HelpDesk

2024-06-14T11:22:42Z

Andrius.abraskevicius:

==Introduction==

Two-factor authentication (2FA) is a security process that requires users to provide two different authentication factors to verify their identity. These factors typically fall into three categories: something you know (like a password), something you have (like a smartphone or token), and something you are (like a fingerprint or iris scan). By requiring two different types of authentications, 2FA significantly enhances security compared to using only a password.

The reason why 2FA was introduced in Helpdesk, is to enhance security by adding an extra layer of protection against unauthorized access to sensitive data that may be shared, thereby mitigating the risk of data breaches and ensuring compliance with industry regulations.

==Setting the 2FA==

'''Things you'll need:'''

1.Your smartphone

2.Authenticator app (available on '''Google Play Store''' or '''Apple App Store''')

'''Android:'''

[[File:GOOGLE_apps.jpg|500x700px]]

'''Apple:'''

[[File:APPLE_apps.jpg|500x700px]]

'''Steps:'''

'''1. Download and Install the Authenticator App (Microsoft Authenticator, Google Authenticator or similar)'''

'''1.1.''' Open the app store on your smartphone (Google Play Store for Android or Apple App Store for iPhone).

'''1.2.''' Search for e.g. "Google Authenticator" and install the app.

'''1.3.''' Depending on the app chosen, you may need to create or sign in with your Google or Microsoft account.

'''2. Sign in to Helpdesk account'''

'''2.1.''' Open the web browser and go to Helpdesk URL:
https://helpdesk.teltonika-iot-group.com

'''2.2.''' Log in to your account using your username and password.

'''3. Enable 2FA and proceed with the setup'''

'''3.1.''' After a successful login attempt, you will be presented with a pop-up window in the middle of the screen. This window will contain a large QR code and instructions to set up 2FA using an authentication app. Leave this window open.

[[File:2FA.png|alt=|left|453x453px|thumb]]

'''4. Sync Helpdesk with Authenticator app'''

'''4.1.''' Launch the Authenticator app on your smartphone.

'''4.2.''' Press “Add” and choose “Scan QR Code”: Use your phone's camera to scan the QR code displayed in the 2FA setup window on your computer screen. If desired, secret key can be entered manually by hand, we recommend to scan it with camera.

'''5. Verify and Complete Setup'''

'''5.1.''' After scanning the QR code or entering the secret key, a new account will be added to your Authenticator app.

'''5.2.''' The app will generate a unique 6-digit code that changes every minute.

'''5.3.''' Enter code displayed in your Authenticator app to Helpdesk window.

Once you enter the correct code, the 2FA setup will be complete.
From now on, with every new log in to Helpdesk, you will be asked to enter code displayed in your Authenticator app.

2024-06-14T11:16:17Z

Andrius.abraskevicius:

Setting up Two-Factor Authentication (2FA) in Partner Portal/HelpDesk

2024-06-14T10:01:50Z

Andrius.abraskevicius:

==Introduction==

Two-factor authentication (2FA) is a security process that requires users to provide two different authentication factors to verify their identity. These factors typically fall into three categories: something you know (like a password), something you have (like a smartphone or token), and something you are (like a fingerprint or iris scan). By requiring two different types of authentications, 2FA significantly enhances security compared to using only a password.

The reason why 2FA was introduced in Helpdesk, is to enhance security by adding an extra layer of protection against unauthorized access to sensitive data that may be shared, thereby mitigating the risk of data breaches and ensuring compliance with industry regulations.

==Setting the 2FA==

'''Things you'll need:'''

1.Your smartphone

2.Authenticator app (available on '''Google Play Store''' or '''Apple App Store''')

'''Android:'''

Google Authenticator Microsoft Authenticator

[[File:Google aut in google store.png|200x200px]]
[[File:google MS aut.png|220x220px]]

'''Apple:'''

Google Authenticator Microsoft Authenticator

[[File:apple google aut.png|200x200px]]
[[File:apple MS aut.png|200x200px]]

'''Steps:'''

'''1. Download and Install the Authenticator App (Microsoft Authenticator, Google Authenticator or similar)'''

'''1.1.''' Open the app store on your smartphone (Google Play Store for Android or Apple App Store for iPhone).

'''1.2.''' Search for e.g. "Google Authenticator" and install the app.

'''1.3.''' Depending on the app chosen, you may need to create or sign in with your Google or Microsoft account.

'''2. Sign in to Helpdesk account'''

'''2.1.''' Open the web browser and go to Helpdesk URL:
https://helpdesk.teltonika-iot-group.com

'''2.2.''' Log in to your account using your username and password.

'''3. Enable 2FA and proceed with the setup'''

'''3.1.''' After a successful login attempt, you will be presented with a pop-up window in the middle of the screen. This window will contain a large QR code and instructions to set up 2FA using an authentication app. Leave this window open.

[[File:2FA.png|alt=|left|453x453px|thumb]]

'''4. Sync Helpdesk with Authenticator app'''

'''4.1.''' Launch the Authenticator app on your smartphone.

'''4.2.''' Press “Add” and choose “Scan QR Code”: Use your phone's camera to scan the QR code displayed in the 2FA setup window on your computer screen. If desired, secret key can be entered manually by hand, we recommend to scan it with camera.

'''5. Verify and Complete Setup'''

'''5.1.''' After scanning the QR code or entering the secret key, a new account will be added to your Authenticator app.

'''5.2.''' The app will generate a unique 6-digit code that changes every minute.

'''5.3.''' Enter code displayed in your Authenticator app to Helpdesk window.

Once you enter the correct code, the 2FA setup will be complete.
From now on, with every new log in to Helpdesk, you will be asked to enter code displayed in your Authenticator app.

Setting up Two-Factor Authentication (2FA) in Partner Portal/HelpDesk

2024-06-14T09:02:31Z

2024-01-19T10:01:54Z

2024-01-16T12:13:12Z

Andrius.abraskevicius:

=='''Firmware'''==
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How do I send SMS command to Teltonika Telematics device? 
|-
|There is a certain structure that the command has to follow:

For example, if we would want to send SMS command getinfo:

If you have set SMS login and password: login pass getinfo

If SMS login and password are not set leave two spaces before command: getinfo
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can we delete records from the device memory? 
|-
|You can clear device's memory by clicking the "format" button in the [Status] window. This will delete all stored records from the device's memory. You can also send the SMS command "sdformat" to the device and it will do the same thing but remotely without the need to connect the device to a computer.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Is it possible to show battery % of EYE sensors/beacons? 
|-
|No, but it is possible to retrieve the battery voltage and estimate the remaining battery life.
More information about it can be found here: [https://wiki.teltonika-gps.com/view/EYE_FAQ#How_does_the_battery_voltage_translate_into_the_percentage_of_the_battery.3F How does the battery voltage translate into the percentage of the battery?]

Both EYE sensors and EYE Beacons can advertise their battery voltage
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is Autoscan and with how many Teltonika device models is this possible? 
|-
|Autoscan is the process of scanning for CANBUS program numbers in the vehicle CANBUS system. Currently, FMB140 and newest external CAN adapters have the Autoscan feature.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to access the latest firmware and how to know when the latest firmware has been released? 
|-
| The latest firmware release information is passed through the Teltonika newsletter. It is encouraged that you subscribe to this service to get real-time notifications about the releases.
Base firmware for all devices can also be found here: [[Firmware versions]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to activate digital output with SMS command? What commands are available? 
|-
| To set digital output use the setdigout command. A description of this command can be found here: [https://wiki.teltonika-gps.com/view/FMB_setdigout FMB_setdigout]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is the difference between Fuel consumed and Fuel consumed (Counted) or Total mileage and Total Mileage (Counted)? 
|-
| Fuel consumed is the total fuel consumed by the vehicle since it was manufactured, while fuel consumed (counted) is the fuel consumed by the vehicle since the CAN device was installed.
Total mileage is the total mileage of the vehicle as displayed on the dashboard of the vehicle since it was manufactured, while total mileage (counted) is the mileage of the vehicle from when the CAN device was installed.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Does FMC125 work with the Iridium Edge use case? 
|-
| Yes, Iridium Edge does work with the FMC125 devices - the 03.28.06.Rev.323 firmware has to be used for this solution to work.
More information about the Iridium Edge solution can be found here: [[Iridium Edge]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Is there a way to encrypt the data that is sent to the server? 
|-
| Yes, our devices have TLS encryption capability, which allows us to secure the data using TLS certificates that are uploaded to the device and the server.
More information about TLS encryption can be found here: [https://wiki.teltonika-gps.com/view/FMB130_GPRS_settings#TLS.2FDTLS TLS settings]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can we check how much data has been used with the current data plan? 
|-
| In the configurator Status tab, we have the GPRS traffic section, where data usage can be seen.
Other than this, there is no way to get the data consumption from the device - this information will be available from the network provider.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Is there a way to implement seat belt detection with a device with only one digital input? 
|-
| There are 2 methods we can follow:

1. Digital Input: if the device only has 1 Digital input which is mostly used to connect the ignition cable, In this use case - the ignition source can be set to power voltage and the seatbelt sensor can be connected to Digital input with priority - High and Operand "On change".

2. Analog Input: The seat belt sensor can be connected to Analog Input 1 with priority - high and low-level values (depending on the voltage from the seatbelt, let's say 12 VDC) - 10 VDC and High level - 13 VDC. The idea is to make the voltage fall between low-level and high-level values and generate an event when the voltage enters that range.

IO settings guide: [[FMC920 I/O settings]]

It is recommended to use FMX130 as the device has a Ground sense option which will be easier to connect and DIN1 can be used for accurate Ignition detection.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How do I get a SIM card IMSI number on my server? 
|-
| The IMSI is not available as an IO element, and it will not be sent to the server with records. However, it can be requested by a SMS/GPRS command "getimsi"
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Why does the TAT100 device appear offline on my server? 
|-
| The TAT100 always works in Deep-sleep mode, and the open link Timeout is 30sec maximum, so the device does not stay connected to the server - this is done to preserve the battery life and allow the device to work longer.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can I send an SMS or command to the TAT100? 
|-
| Yes, you can send a command to the TAT100 and it will execute this command once it wakes up.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|When does TAT100 connect to FOTA WEB? 
|-
| TAT100 devices do not connect to FOTA Web periodically. It will automatically connect to FOTA Web only on initial startup (when the switch is flipped from OFF to ON position). Connection to FOTA Web should be initiated via the 'web_connect' SMS/GPRS command. This is to preserve battery power.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can DSM detect 2 or more events at the same time? 
|-
| Yes, it can detect multiple events at the same time. The events are placed in a queue and then reported based on their generation time.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Which SMS encoding is supported by Teltonika Telematics devices? 
|-
| The device received commands encoded in Unicode and any third-party SMS portal should have the support of format SMS Default Alphabet while initiating communication with the Teltonika device. FMC devices support SMS Default Alphabet, also known as GSM-7, encoding only - this encoding standard should be configured at the sending device/application.
|}

=='''Software'''==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|When opening the configurator, a .NET error is shown. I tried installing .NET 7.0, but the error remained. How can this be solved? 
|-
| New Configurators use the newer .NET version - please make sure the correct version is installed and remove other (unused) .NET versions – more information can be found here: [[.NET Runtime for Desktop installation]]
Note #1: The Ways to determine the required version section is especially important here. It will help you decide which version you should choose.

Note #2: x86 is recommended even with Microsoft Windows 64-bit Operating System.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is FOTA Web and how is it useful? Can you see the device's real-time location using this system? 
|-
| FOTA Web is simply a device management platform that is used to assign files to the device remotely, such as firmware, configuration files, etc.
FOTA Web is '''not''' a tracking platform and does not report the device's real-time location.

You can find more information about the FOTA Web tool here: [[FOTA WEB]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to use the device transfer feature in FOTA Web? 
|-
| Device transfer is a feature in FOTA Web that allows clients to directly move devices amongst their accounts without the need to involve Teltonika.
More information about this feature can be found here: [https://wiki.teltonika-gps.com/view/FOTA_WEB_Devices#Device_transfer Device transfer]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How do I update configurations remotely via Teltonika FOTA Web? 
|-
| Kindly use the FOTA Web to remotely update configurations to units as explained here: [[FOTA WEB|FOTA Web]]

Steps are:

1. Upload the configuration file in FOTA Web under the files tab.

2. Head over to the devices tab then select the devices to receive the configuration.

3. Click on Create Task and choose Update Configuration on the drop-down then below it, choose the uploaded file, then click on Create Task.

The task will be executed the next time the device connects to FOTA Web or you can force it to connect immediately by sending a command '''''web_connect''''', or by forcing a hard restart of the unit by unplugging the power and the internal battery then plugging it back on - then the task will be executed immediately.
|}

== '''Hardware''' ==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What are the SIM card requirements for use with Teltonika Telematics devices? 
|-
| Different Teltonika Telematics devices support Mini SIM, Micro SIM, and Nano SIM sized SIM cards. To know the exact SIM card supported by Your device, please check the General Description Wiki page for Your device.

As for eSIMs, there are a couple of requirements for it to work with our devices - they can be found here: [[Requirements for eSIM]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to connect the fuel gauge sensor to the Analog input of the FMx and calibrate for accurate results? 
|-
| We can measure the fuel level using analog input by matching the voltage coming from the fuel level sensor already mounted in the car, with the fuel level in the tank.
More information on how the AIN has to be connected and calibrated can be found here: [[Analog Fuel Sensor]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Where can we find the connection schemes for CAN-CONTROL adapter? 
|-
| Please create a Helpdesk ticket for our support team and specify the vehicle that the connection scheme is needed for.
The whole supported vehicle list for CAN-CONTROL adapter can be found here: [[CAN adapter supported vehicles]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Does all RFID cards with 125 or 128kHz frequency work with FMC150 ? What about a 13.56 MHz NFC or RFID device? 
|-
|Like other devices with a 1-Wire interface, FMC150 also supports a 1-wire protocol (DS1990A) RFID reader.
If the reader reads cards with 125 or 128 kHz and transmits this data through 1 wire protocol (DS1990A), we can integrate it into FMC150.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How many batteries does TAT1XY use? 
|-
| TAT1XY uses 1 battery, which consists of 2 (7.2V variant) or 3 (10.8V variant) cells. Currently, manufactured TAT devices use 3-cell batteries.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is the battery life of TAT1XY? 
|-
| TAT1XX can send approximately 1000 records, this may differ depending on the environment, coverage, Temperature, and device mounting,
|}

== '''Protocols''' ==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Where can I find how to parse the message from the device in the backend? 
|-
| Teltonika data sending protocol Codec 8 and Codec 8Extended description with examples:

[[Codec|AVL data sending codecs]]

TCP/UDP listener and AVL parser with source code that could be used as a template for implementation of Teltonika protocols. The whole pack can be downloaded from here:

[https://wiki.teltonika-gps.com/view/Universal_Device_Test_Guide#Protocols_implementation Listener and AVL parser]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|In documentation it states that the Beacon data will be sent via AVL ID 385, but data from FMB140 is being sent with AVL ID:548. 
|-
| When the simple mode is selected beacon parsing is done automatically so AVL ID:385 is used

When advanced beacon mode is selected, beacon data capturing can be configured manually and to distinguish simple and advanced functionalities a different ID is used - AVL ID 548.

For advanced beacon configuration documentation, you can find it here: [[Advanced Beacon Capturing Configuration]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|I have implemented Codec8 Extended protocol. Communication is working correctly, IMEI and AVL packets are working fine, but the unit sends 0xFF instead of AVL packets sometimes. Is there any use of this packet and is it necessary to send some data as a response back? 
|-
| It seems that You have enabled the Network Ping Timeout feature.

What Network Ping Timeout does is it sends an empty packet (0xFF) to the server to make sure that the operator does not close a link between the device and the server.

If you don't want to receive 0xFF packets anymore you can set Network Ping Timeout to 0 seconds.
|}

== '''Configuration''' ==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|I have successfully paired the Teltonika Eye sensor to the fleet management device and I can see the data on the I/O tab but the data is not sent to my platform, what could be the issue? 
|-
| For the data to be sent to the platform, the I/O needs to have a priority of ‘Low’, ‘High’, or ‘Panic’ so that the data can be sent with periodical data to the platform.

I/O Settings wiki page - [[FMB125 I/O settings]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Why device doesn't detect the ignition? 
|-
|Please check which ignition source have you chosen and configure the device according to Your use case.

More information about the Ignition sources can be found here: [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Ignition_Source Ignition source]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|When testing the OBD device alarm of the vehicle is triggered when it is parked. What could cause this? 
|-
| This usually occurs when the device tries making OBD requests while the vehicle has no ignition and is locked. This can happen due to improper configuration, so make sure that the OBD device properly detects the ignition of the vehicle, when the ignition is actually ON.
More information about the Ignition sources can be found here: [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Ignition_Source Ignition source]
|}

Starting with Teltonika Telematics

2024-01-16T07:38:39Z

Andrius.abraskevicius:

=='''Firmware'''==
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How do I send SMS command to Teltonika Telematics device? 
|-
|There is a certain structure that the command has to follow:

For example, if we would want to send SMS command getinfo:

If you have set SMS login and password: login pass getinfo

If SMS login and password are not set leave two spaces before command: getinfo
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can we delete records from the device memory? 
|-
|You can clear device's memory by clicking the "format" button in the [Status] window. This will delete all stored records from the device's memory. You can also send the SMS command "sdformat" to the device and it will do the same thing but remotely without the need to connect the device to a computer.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Is it possible to show battery % of EYE sensors/beacons? 
|-
|No, but it is possible to retrieve the battery voltage and estimate the remaining battery life.
More information about it can be found here: [https://wiki.teltonika-gps.com/view/EYE_FAQ#How_does_the_battery_voltage_translate_into_the_percentage_of_the_battery.3F How does the battery voltage translate into the percentage of the battery?]

Both EYE sensors and EYE Beacons can advertise their battery voltage
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is Autoscan and with how many Teltonika device models is this possible? 
|-
|Autoscan is the process of scanning for CANBUS program numbers in the vehicle CANBUS system. Currently, FMB140 and newest external CAN adapters have the Autoscan feature.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to access the latest firmware and how to know when the latest firmware has been released? 
|-
| The latest firmware release information is passed through the Teltonika newsletter. It is encouraged that you subscribe to this service to get real-time notifications about the releases.
Base firmware for all devices can also be found here: [[Firmware versions]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to activate digital output with SMS command? What commands are available for FMB920? 
|-
| Supported commands can be found here: [[FMB920_SMS/GPRS_Commands]]
To set digital output use the setdigout command. A description of this command can be found here: [https://wiki.teltonika-gps.com/view/FMB_setdigout FMB_setdigout]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is the difference between Fuel consumed and Fuel consumed (Counted) or Total mileage and Total Mileage (Counted)? 
|-
| Fuel consumed is the total fuel consumed by the vehicle since it was manufactured, while fuel consumed (counted) is the fuel consumed by the vehicle since the CAN device was installed.
Total mileage is the total mileage of the vehicle as displayed on the dashboard of the vehicle since it was manufactured, while total mileage (counted) is the mileage of the vehicle from when the CAN device was installed.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Does FMC125 work with the Iridium Edge use case? 
|-
| Yes, Iridium Edge does work with the FMC125 devices - the 03.28.06.Rev.323 firmware has to be used for this solution to work.
More information about the Iridium Edge solution can be found here: [[Iridium Edge]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Is there a way to encrypt the data that is sent to the server? 
|-
| Yes, our devices have TLS encryption capability, which allows us to secure the data using TLS certificates that are uploaded to the device and the server.
More information about TLS encryption can be found here: [https://wiki.teltonika-gps.com/view/FMB130_GPRS_settings#TLS.2FDTLS TLS settings]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can we check how much data has been used with the current data plan? 
|-
| In the configurator Status tab, we have the GPRS traffic section, where data usage can be seen.
Other than this, there is no way to get the data consumption from the device - this information will be available from the network provider.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Is there a way to implement seat belt detection with FMC920 device? 
|-
| There are 2 methods we can follow:

1. Digital Input: The FMC920 device only has 1 Digital input which is mostly used to connect the ignition cable, In this use case - the ignition source can be set to power voltage and the seatbelt sensor can be connected to Digital input with priority - High and Operand "On change".

2. Analog Input: The seat belt sensor can be connected to Analog input 1 with priority - high and low level values (depending on the voltage from the seatbelt, let's say 12 VDC) - 10 VDC and High level - 13 VDC. The idea is to make the voltage fall between low-level and high-level values and generate an event when the voltage enters that range.

IO settings guide: [[FMC920 I/O settings]]

It is recommended to use FMX130 as the device has a Ground sense option which will be easier to connect and DIN1 can be used for accurate Ignition detection.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How do I get a SIM card IMSI number on my server? 
|-
| The IMSI is not available as an IO element, and it will not be sent to the server with records. However, it can be requested by a SMS/GPRS command "getimsi"
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Why does the TAT100 device appear offline on my server? 
|-
| The TAT100 always works in Deep-sleep mode, and the open link Timeout is 30sec maximum, so the device does not stay connected to the server - this is done to preserve the battery life and allow the device to work longer.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can I send an SMS or command to the TAT100? 
|-
| Yes, you can send a command to the TAT100 and it will execute this command once it wakes up.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|When does TAT100 connect to FOTA WEB? 
|-
| TAT100 devices do not connect to FOTA Web periodically. It will automatically connect to FOTA Web only on initial startup (when the switch is flipped from OFF to ON position). Connection to FOTA Web should be initiated via the 'web_connect' SMS/GPRS command. This is to preserve battery power.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can DSM detect 2 or more events at the same time? 
|-
| Yes, it can detect multiple events at the same time. The events are placed in a queue and then reported based on their generation time.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Which SMS encoding is supported by Teltonika Telematics devices? 
|-
| The device received commands encoded in Unicode and any third-party SMS portal should have the support of format SMS Default Alphabet while initiating communication with the Teltonika device. FMC devices support SMS Default Alphabet, also known as GSM-7, encoding only - this encoding standard should be configured at the sending device/application.
|}

=='''Software'''==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|When opening the configurator, a .NET error is shown. I tried installing .NET 7.0, but the error remained. How can this be solved? 
|-
| New Configurators use the newer .NET version - please make sure the correct version is installed and remove other (unused) .NET versions – more information can be found here: [[.NET Runtime for Desktop installation]]
Note #1: The Ways to determine the required version section is especially important here. It will help you decide which version you should choose.

Note #2: x86 is recommended even with Microsoft Windows 64-bit Operating System.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is FOTA Web and how is it useful? Can you see the device's real-time location using this system? 
|-
| FOTA Web is simply a device management platform that is used to assign files to the device remotely, such as firmware, configuration files, etc.
FOTA Web is '''not''' a tracking platform and does not report the device's real-time location.

You can find more information about the FOTA Web tool here: [[FOTA WEB]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to use the device transfer feature in FOTAWEB? 
|-
| Device transfer is a feature in FOTAWEB that allows clients to directly move devices amongst their accounts without the need to involve Teltonika.
More information about this feature can be found here: [https://wiki.teltonika-gps.com/view/FOTA_WEB_Devices#Device_transfer Device transfer]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How do I update configurations remotely via Teltonika FOTA Web? 
|-
| Kindly use the FOTA Web to remotely update configurations to units as explained here: [[FOTA WEB]]

Steps are:

1. Upload the configuration file in FOTA WEB under the files tab.

2. Head over to the devices tab then select the devices to receive the configuration.

3. Click on Create Task and choose Update Configuration on the drop-down then below it, choose the uploaded file, then click on Create Task.

The task will be executed the next time the device connects to FOTA WEB or you can force it to connect immediately by sending a command " web_connect" with two spaces before the command and no quotes, or hard restart the unit by unplugging the power and the internal battery then plugging it back on then the task will be executed immediately.
|}

== '''Hardware''' ==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What are the SIM card requirements for use with Teltonika Telematics devices? 
|-
| Different Teltonika Telematics devices support Mini SIM, Micro SIM, and Nano SIM sized SIM cards. To know the exact SIM card supported by Your device, please check the General Description Wiki page for Your device.

As for eSIMs, there are a couple of requirements for it to work with our devices - they can be found here: [[Requirements for eSIM]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to connect the fuel gauge sensor to the Analog input of the FMx and calibrate for accurate results? 
|-
| We can measure the fuel level using analog input by matching the voltage coming from the fuel level sensor already mounted in the car, with the fuel level in the tank.
More information on how the AIN has to be connected and calibrated can be found here: [[Analog Fuel Sensor]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Where can we find the connection schemes for CAN-CONTROL adapter? 
|-
| Please use the link below to find and download the necessary connection scheme.

Link: https://drive.teltonika.lt/d/31c32f08610044b699b3/

Password: wzh1XNp0
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Does all RFID cards with 125 or 128kHz frequency work with FMC150 ? What about a 13.56 MHz NFC or RFID device? 
|-
|Like other devices with a 1-Wire interface, FMC 150 also supports a 1-wire protocol (DS1990A) RFID reader.
If the reader reads cards with 125 or 128 kHz and transmits this data through 1 wire protocol (DS1990A), we can integrate it into FMC150.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How many batteries does TAT use? 
|-
| TAT uses 1 battery, which consists of 2 (7.2V variant) or 3 (10.8V variant) cells. Currently, manufactured TAT devices use 3-cell batteries.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is the battery life of TAT1XY? 
|-
| TAT1XX can send approximately 1000 records, this may differ depending on the environment, coverage, Temperature, and device mounting,
|}

== '''Protocols''' ==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Where can I find how to parse the message from the device in the backend? 
|-
| Teltonika data sending protocol Codec 8 and Codec 8Extended description with examples:

[[Codec|AVL data sending codecs]]

TCP/UDP listener and AVL parser with source code that could be used as a template for implementation of Teltonika protocols. The whole pack can be downloaded from here:

[https://wiki.teltonika-gps.com/view/Universal_Device_Test_Guide#Protocols_implementation Listener and AVL parser]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|In documentation it states that the Beacon data will be sent via AVL ID 385, but data from FMB140 is being sent with AVL ID:548. 
|-
| When the simple mode is selected beacon parsing is done automatically so AVL ID:385 is used

When advanced beacon mode is selected, beacon data capturing can be configured manually and to distinguish simple and advanced functionalities a different ID is used - AVL ID 548.

For advanced beacon configuration documentation, you can find it here: [[Advanced Beacon Capturing Configuration]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|I have implemented Codec8 Extended protocol. Communication is working correctly, IMEI and AVL packets are working fine, but the unit sends 0xFF instead of AVL packets sometimes. Is there any use of this packet and is it necessary to send some data as a response back? 
|-
| It seems that You have enabled the Network Ping Timeout feature.

What Network Ping Timeout does is it sends an empty packet (0xFF) to the server to make sure that the operator does not close a link between the device and the server.

If you don't want to receive 0xFF packets anymore you can set Network Ping Timeout to 0 seconds.
|}

== '''Configuration''' ==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|I have successfully paired the Teltonika Eye sensor to the FMB130 and I can see the data on the I/O tab but the data is not sent to my platform, what could be the issue? 
|-
| For the data to be sent to the platform, the I/O needs to have a priority of ‘Low’, ‘High’, or ‘Panic’ so that the data can be sent with periodical data to the platform.

I/O Settings wiki page - [[FMB125 I/O settings]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Why device doesn't detect the ignition? 
|-
|Please check which ignition source have you chosen and configure the device according to Your use case.

More information about the Ignition sources can be found here: [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Ignition_Source Ignition source]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|When testing the OBD device alarm of the vehicle is triggered when it is parked. What could cause this? 
|-
| This usually occurs when the device tries making OBD requests while the vehicle has no ignition and is locked. This can happen due to improper configuration, so make sure that the OBD device properly detects the ignition of the vehicle, when the ignition is actually ON.
More information about the Ignition sources can be found here: [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Ignition_Source Ignition source]
|}

Starting with Teltonika Telematics

2024-01-16T07:37:22Z

Andrius.abraskevicius:

=='''Firmware'''==
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How do I send SMS command to Teltonika Telematics device? 
|-
|There is a certain structure that the command has to follow:

For example, if we want to send the SMS command getinfo:

If you have set SMS login and password: login pass getinfo

If SMS login and password are not set leave two spaces before the command:<space><space>getinfo
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can we delete records from the device memory? 
|-
|You can clear device's memory by clicking the "format" button in the [Status] window. This will delete all stored records from the device's memory. You can also send the SMS command "sdformat" to the device and it will do the same thing but remotely without the need to connect the device to a computer.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Is it possible to show battery % of EYE sensors/beacons? 
|-
|No, but it is possible to retrieve the battery voltage and estimate the remaining battery life.
More information about it can be found here: [https://wiki.teltonika-gps.com/view/EYE_FAQ#How_does_the_battery_voltage_translate_into_the_percentage_of_the_battery.3F How does the battery voltage translate into the percentage of the battery?]

Both EYE sensors and EYE Beacons can advertise their battery voltage
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is Autoscan and with how many Teltonika device models is this possible? 
|-
|Autoscan is the process of scanning for CANBUS program numbers in the vehicle CANBUS system. Currently, FMB140 and newest external CAN adapters have the Autoscan feature.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to access the latest firmware and how to know when the latest firmware has been released? 
|-
| The latest firmware release information is passed through the Teltonika newsletter. It is encouraged that you subscribe to this service to get real-time notifications about the releases.
Base firmware for all devices can also be found here: [[Firmware versions]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to activate digital output with SMS command? What commands are available for FMB920? 
|-
| Supported commands can be found here: [[FMB920_SMS/GPRS_Commands]]
To set digital output use the setdigout command. A description of this command can be found here: [https://wiki.teltonika-gps.com/view/FMB_setdigout FMB_setdigout]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is the difference between Fuel consumed and Fuel consumed (Counted) or Total mileage and Total Mileage (Counted)? 
|-
| Fuel consumed is the total fuel consumed by the vehicle since it was manufactured, while fuel consumed (counted) is the fuel consumed by the vehicle since the CAN device was installed.
Total mileage is the total mileage of the vehicle as displayed on the dashboard of the vehicle since it was manufactured, while total mileage (counted) is the mileage of the vehicle from when the CAN device was installed.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Does FMC125 work with the Iridium Edge use case? 
|-
| Yes, Iridium Edge does work with the FMC125 devices - the 03.28.06.Rev.323 firmware has to be used for this solution to work.
More information about the Iridium Edge solution can be found here: [[Iridium Edge]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Is there a way to encrypt the data that is sent to the server? 
|-
| Yes, our devices have TLS encryption capability, which allows us to secure the data using TLS certificates that are uploaded to the device and the server.
More information about TLS encryption can be found here: [https://wiki.teltonika-gps.com/view/FMB130_GPRS_settings#TLS.2FDTLS TLS settings]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can we check how much data has been used with the current data plan? 
|-
| In the configurator Status tab we have the GPRS traffic section, where data usage can be seen. Other than this, there is no way to get the data consumption from the device - this information will be available from the network provider.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Is there a way to implement seat belt detection with FMC920 device? 
|-
| There are 2 methods we can follow:

1. Digital Input: The FMC920 device only has 1 Digital input which is mostly used to connect the ignition cable, In this use case - the ignition source can be set to power voltage and the seatbelt sensor can be connected to Digital input with priority - High and Operand "On change".

2. Analog Input: The seat belt sensor can be connected to Analog input 1 with priority - high and low level values (depending on the voltage from the seatbelt, let's say 12 VDC) - 10 VDC and High level - 13 VDC. The idea is to make the voltage fall between low-level and high-level values and generate an event when the voltage enters that range.

IO settings guide: [[FMC920 I/O settings]]

It is recommended to use FMX130 as the device has a Ground sense option which will be easier to connect and DIN1 can be used for accurate Ignition detection.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How do I get a SIM card IMSI number on my server? 
|-
| The IMSI is not available as an IO element, and it will not be sent to the server with records. However, it can be requested by a SMS/GPRS command "getimsi"
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Why does the TAT100 device appear offline on my server? 
|-
| The TAT100 always works in Deep-sleep mode, and the open link Timeout is 30sec maximum, so the device does not stay connected to the server - this is done to preserve the battery life and allow the device to work longer.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can I send an SMS or command to the TAT100? 
|-
| Yes, you can send a command to the TAT100 and it will execute this command once it wakes up.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|When does TAT100 connect to FOTA WEB? 
|-
| TAT100 devices do not connect to FOTA Web periodically. It will automatically connect to FOTA Web only on initial startup (when the switch is flipped from OFF to ON position). Connection to FOTA Web should be initiated via the 'web_connect' SMS/GPRS command. This is to preserve battery power.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can DSM detect 2 or more events at the same time? 
|-
| Yes, it can detect multiple events at the same time. The events are placed in a queue and then reported based on their generation time.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Which SMS encoding is supported by Teltonika Telematics devices? 
|-
| The device received commands encoded in Unicode and any third-party SMS portal should have the support of format SMS Default Alphabet while initiating communication with the Teltonika device. FMC devices support SMS Default Alphabet, also known as GSM-7, encoding only - this encoding standard should be configured at the sending device/application.
|}

=='''Software'''==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|When opening the configurator, a .NET error is shown. I tried installing .NET 7.0, but the error remained. How can this be solved? 
|-
| New Configurators use the newer .NET version - please make sure the correct version is installed and remove other (unused) .NET versions – more information can be found here: [[.NET Runtime for Desktop installation]]
Note #1: The Ways to determine the required version section is especially important here. It will help you decide which version you should choose.

Note #2: x86 is recommended even with Microsoft Windows 64-bit Operating System.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is FOTA Web and how is it useful? Can you see the device's real-time location using this system? 
|-
| FOTA Web is simply a device management platform that is used to assign files to the device remotely, such as firmware, configuration files, etc.
FOTA Web is '''not''' a tracking platform and does not report the device's real-time location.

You can find more information about the FOTA Web tool here: [[FOTA WEB]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to use the device transfer feature in FOTAWEB? 
|-
| Device transfer is a feature in FOTAWEB that allows clients to directly move devices amongst their accounts without the need to involve Teltonika.
More information about this feature can be found here: [https://wiki.teltonika-gps.com/view/FOTA_WEB_Devices#Device_transfer Device transfer]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How do I update configurations remotely via Teltonika FOTA Web? 
|-
| Kindly use the FOTA Web to remotely update configurations to units as explained here: [[FOTA WEB]]

Steps are:

1. Upload the configuration file in FOTA WEB under the files tab.

2. Head over to the devices tab then select the devices to receive the configuration.

3. Click on Create Task and choose Update Configuration on the drop-down then below it, choose the uploaded file, then click on Create Task.

The task will be executed the next time the device connects to FOTA WEB or you can force it to connect immediately by sending a command " web_connect" with two spaces before the command and no quotes, or hard restart the unit by unplugging the power and the internal battery then plugging it back on then the task will be executed immediately.
|}

== '''Hardware''' ==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What are the SIM card requirements for use with Teltonika Telematics devices? 
|-
| Different Teltonika Telematics devices support Mini SIM, Micro SIM, and Nano SIM sized SIM cards. To know the exact SIM card supported by Your device, please check the General Description Wiki page for Your device.

As for eSIMs, there are a couple of requirements for it to work with our devices - they can be found here: [[Requirements for eSIM]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to connect the fuel gauge sensor to the Analog input of the FMx and calibrate for accurate results? 
|-
| We can measure the fuel level using analog input by matching the voltage coming from the fuel level sensor already mounted in the car, with the fuel level in the tank.
More information on how the AIN has to be connected and calibrated can be found here: [[Analog Fuel Sensor]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Where can we find the connection schemes for CAN-CONTROL adapter? 
|-
| Please use the link below to find and download the necessary connection scheme.

Link: https://drive.teltonika.lt/d/31c32f08610044b699b3/

Password: wzh1XNp0
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Does all RFID cards with 125 or 128kHz frequency work with FMC150 ? What about a 13.56 MHz NFC or RFID device? 
|-
|Like other devices with a 1-Wire interface, FMC 150 also supports a 1-wire protocol (DS1990A) RFID reader.
If the reader reads cards with 125 or 128 kHz and transmits this data through 1 wire protocol (DS1990A), we can integrate it into FMC150.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How many batteries does TAT use? 
|-
| TAT uses 1 battery, which consists of 2 (7.2V variant) or 3 (10.8V variant) cells. Currently, manufactured TAT devices use 3-cell batteries.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is the battery life of TAT1XY? 
|-
| TAT1XX can send approximately 1000 records, this may differ depending on the environment, coverage, Temperature, and device mounting,
|}

== '''Protocols''' ==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Where can I find how to parse the message from the device in the backend? 
|-
| Teltonika data sending protocol Codec 8 and Codec 8Extended description with examples:

[[Codec|AVL data sending codecs]]

TCP/UDP listener and AVL parser with source code that could be used as a template for implementation of Teltonika protocols. The whole pack can be downloaded from here:

[https://wiki.teltonika-gps.com/view/Universal_Device_Test_Guide#Protocols_implementation Listener and AVL parser]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|In documentation it states that the Beacon data will be sent via AVL ID 385, but data from FMB140 is being sent with AVL ID:548. 
|-
| When the simple mode is selected beacon parsing is done automatically so AVL ID:385 is used

When advanced beacon mode is selected, beacon data capturing can be configured manually and to distinguish simple and advanced functionalities a different ID is used - AVL ID 548.

For advanced beacon configuration documentation, you can find it here: [[Advanced Beacon Capturing Configuration]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|I have implemented Codec8 Extended protocol. Communication is working correctly, IMEI and AVL packets are working fine, but the unit sends 0xFF instead of AVL packets sometimes. Is there any use of this packet and is it necessary to send some data as a response back? 
|-
| It seems that You have enabled the Network Ping Timeout feature.

What Network Ping Timeout does is it sends an empty packet (0xFF) to the server to make sure that the operator does not close a link between the device and the server.

If you don't want to receive 0xFF packets anymore you can set Network Ping Timeout to 0 seconds.
|}

== '''Configuration''' ==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|I have successfully paired the Teltonika Eye sensor to the FMB130 and I can see the data on the I/O tab but the data is not sent to my platform, what could be the issue? 
|-
| For the data to be sent to the platform, the I/O needs to have a priority of ‘Low’, ‘High’, or ‘Panic’ so that the data can be sent with periodical data to the platform.

I/O Settings wiki page - [[FMB125 I/O settings]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Why device doesn't detect the ignition? 
|-
|Please check which ignition source have you chosen and configure the device according to Your use case.

More information about the Ignition sources can be found here: [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Ignition_Source Ignition source]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|When testing the OBD device alarm of the vehicle is triggered when it is parked. What could cause this? 
|-
| This usually occurs when the device tries making OBD requests while the vehicle has no ignition and is locked. This can happen due to improper configuration, so make sure that the OBD device properly detects the ignition of the vehicle, when the ignition is actually ON.
More information about the Ignition sources can be found here: [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Ignition_Source Ignition source]
|}

Starting with Teltonika Telematics

2024-01-16T07:36:17Z

Andrius.abraskevicius: /* Firmware */

=='''Firmware'''==
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How do I send SMS command to Teltonika Telematics device? 
|-
|There is a certain structure that the command has to follow:

For example, if we would want to send SMS command getinfo:

If you have set SMS login and password: login pass getinfo

If SMS login and password are not set leave two spaces before command: getinfo
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can we delete records from the device memory? 
|-
|You can clear device's memory by clicking the "format" button in the [Status] window. This will delete all stored records from the device's memory. You can also send the SMS command "sdformat" to the device and it will do the same thing but remotely without the need to connect the device to a computer.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Is it possible to show battery % of EYE sensors/beacons? 
|-
|No, but it is possible to retrieve the battery voltage and estimate the remaining battery life.
More information about it can be found here: [https://wiki.teltonika-gps.com/view/EYE_FAQ#How_does_the_battery_voltage_translate_into_the_percentage_of_the_battery.3F How does the battery voltage translate into the percentage of the battery?]

Both EYE sensors and EYE Beacons can advertise their battery voltage
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is Autoscan and with how many Teltonika device models is this possible? 
|-
|Autoscan is the process of scanning for CANBUS program numbers in the vehicle CANBUS system. Currently, FMB140 and newest external CAN adapters have the Autoscan feature.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to access the latest firmware and how to know when the latest firmware has been released? 
|-
| The latest firmware release information is passed through the Teltonika newsletter. It is encouraged that you subscribe to this service to get real-time notifications about the releases.
Base firmware for all devices can also be found here: [[Firmware versions]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to activate digital output with SMS command? What commands are available for FMB920? 
|-
| Supported commands can be found here: [[FMB920_SMS/GPRS_Commands]]
To set digital output use the setdigout command. A description of this command can be found here: [https://wiki.teltonika-gps.com/view/FMB_setdigout FMB_setdigout]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is the difference between Fuel consumed and Fuel consumed (Counted) or Total mileage and Total Mileage (Counted)? 
|-
| Fuel consumed is the total fuel consumed by the vehicle since it was manufactured, while fuel consumed (counted) is the fuel consumed by the vehicle since the CAN device was installed.
Total mileage is the total mileage of the vehicle as displayed on the dashboard of the vehicle since it was manufactured, while total mileage (counted) is the mileage of the vehicle from when the CAN device was installed.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Does FMC125 work with the Iridium Edge use case? 
|-
| Yes, Iridium Edge does work with the FMC125 devices - the 03.28.06.Rev.323 firmware has to be used for this solution to work.
More information about the Iridium Edge solution can be found here: [[Iridium Edge]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Is there a way to encrypt the data that is sent to the server? 
|-
| Yes, our devices have TLS encryption capability, which allows us to secure the data using TLS certificates that are uploaded to the device and the server.
More information about TLS encryption can be found here: [https://wiki.teltonika-gps.com/view/FMB130_GPRS_settings#TLS.2FDTLS TLS settings]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can we check how much data has been used with the current data plan? 
|-
| In the configurator Status tab we have the GPRS traffic section, where data usage can be seen. Other than this, there is no way to get the data consumption from the device - this information will be available from the network provider.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Is there a way to implement seat belt detection with FMC920 device? 
|-
| There are 2 methods we can follow:

1. Digital Input: The FMC920 device only has 1 Digital input which is mostly used to connect the ignition cable, In this use case - the ignition source can be set to power voltage and the seatbelt sensor can be connected to Digital input with priority - High and Operand "On change".

2. Analog Input: The seat belt sensor can be connected to Analog input 1 with priority - high and low level values (depending on the voltage from the seatbelt, let's say 12 VDC) - 10 VDC and High level - 13 VDC. The idea is to make the voltage fall between low-level and high-level values and generate an event when the voltage enters that range.

IO settings guide: [[FMC920 I/O settings]]

It is recommended to use FMX130 as the device has a Ground sense option which will be easier to connect and DIN1 can be used for accurate Ignition detection.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How do I get a SIM card IMSI number on my server? 
|-
| The IMSI is not available as an IO element, and it will not be sent to the server with records. However, it can be requested by a SMS/GPRS command "getimsi"
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Why does the TAT100 device appear offline on my server? 
|-
| The TAT100 always works in Deep-sleep mode, and the open link Timeout is 30sec maximum, so the device does not stay connected to the server - this is done to preserve the battery life and allow the device to work longer.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can I send an SMS or command to the TAT100? 
|-
| Yes, you can send a command to the TAT100 and it will execute this command once it wakes up.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|When does TAT100 connect to FOTA WEB? 
|-
| TAT100 devices do not connect to FOTA Web periodically. It will automatically connect to FOTA Web only on initial startup (when the switch is flipped from OFF to ON position). Connection to FOTA Web should be initiated via the 'web_connect' SMS/GPRS command. This is to preserve battery power.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can DSM detect 2 or more events at the same time? 
|-
| Yes, it can detect multiple events at the same time. The events are placed in a queue and then reported based on their generation time.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Which SMS encoding is supported by Teltonika Telematics devices? 
|-
| The device received commands encoded in Unicode and any third-party SMS portal should have the support of format SMS Default Alphabet while initiating communication with the Teltonika device. FMC devices support SMS Default Alphabet, also known as GSM-7, encoding only - this encoding standard should be configured at the sending device/application.
|}

=='''Software'''==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|When opening the configurator, a .NET error is shown. I tried installing .NET 7.0, but the error remained. How can this be solved? 
|-
| New Configurators use the newer .NET version - please make sure the correct version is installed and remove other (unused) .NET versions – more information can be found here: [[.NET Runtime for Desktop installation]]
Note #1: The Ways to determine the required version section is especially important here. It will help you decide which version you should choose.

Note #2: x86 is recommended even with Microsoft Windows 64-bit Operating System.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is FOTA Web and how is it useful? Can you see the device's real-time location using this system? 
|-
| FOTA Web is simply a device management platform that is used to assign files to the device remotely, such as firmware, configuration files, etc.
FOTA Web is '''not''' a tracking platform and does not report the device's real-time location.

You can find more information about the FOTA Web tool here: [[FOTA WEB]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to use the device transfer feature in FOTAWEB? 
|-
| Device transfer is a feature in FOTAWEB that allows clients to directly move devices amongst their accounts without the need to involve Teltonika.
More information about this feature can be found here: [https://wiki.teltonika-gps.com/view/FOTA_WEB_Devices#Device_transfer Device transfer]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How do I update configurations remotely via Teltonika FOTA Web? 
|-
| Kindly use the FOTA Web to remotely update configurations to units as explained here: [[FOTA WEB]]

Steps are:

1. Upload the configuration file in FOTA WEB under the files tab.

2. Head over to the devices tab then select the devices to receive the configuration.

3. Click on Create Task and choose Update Configuration on the drop-down then below it, choose the uploaded file, then click on Create Task.

The task will be executed the next time the device connects to FOTA WEB or you can force it to connect immediately by sending a command " web_connect" with two spaces before the command and no quotes, or hard restart the unit by unplugging the power and the internal battery then plugging it back on then the task will be executed immediately.
|}

== '''Hardware''' ==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What are the SIM card requirements for use with Teltonika Telematics devices? 
|-
| Different Teltonika Telematics devices support Mini SIM, Micro SIM, and Nano SIM sized SIM cards. To know the exact SIM card supported by Your device, please check the General Description Wiki page for Your device.

As for eSIMs, there are a couple of requirements for it to work with our devices - they can be found here: [[Requirements for eSIM]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to connect the fuel gauge sensor to the Analog input of the FMx and calibrate for accurate results? 
|-
| We can measure the fuel level using analog input by matching the voltage coming from the fuel level sensor already mounted in the car, with the fuel level in the tank.
More information on how the AIN has to be connected and calibrated can be found here: [[Analog Fuel Sensor]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Where can we find the connection schemes for CAN-CONTROL adapter? 
|-
| Please use the link below to find and download the necessary connection scheme.

Link: https://drive.teltonika.lt/d/31c32f08610044b699b3/

Password: wzh1XNp0
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Does all RFID cards with 125 or 128kHz frequency work with FMC150 ? What about a 13.56 MHz NFC or RFID device? 
|-
|Like other devices with a 1-Wire interface, FMC 150 also supports a 1-wire protocol (DS1990A) RFID reader.
If the reader reads cards with 125 or 128 kHz and transmits this data through 1 wire protocol (DS1990A), we can integrate it into FMC150.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How many batteries does TAT use? 
|-
| TAT uses 1 battery, which consists of 2 (7.2V variant) or 3 (10.8V variant) cells. Currently, manufactured TAT devices use 3-cell batteries.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is the battery life of TAT1XY? 
|-
| TAT1XX can send approximately 1000 records, this may differ depending on the environment, coverage, Temperature, and device mounting,
|}

== '''Protocols''' ==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Where can I find how to parse the message from the device in the backend? 
|-
| Teltonika data sending protocol Codec 8 and Codec 8Extended description with examples:

[[Codec|AVL data sending codecs]]

TCP/UDP listener and AVL parser with source code that could be used as a template for implementation of Teltonika protocols. The whole pack can be downloaded from here:

[https://wiki.teltonika-gps.com/view/Universal_Device_Test_Guide#Protocols_implementation Listener and AVL parser]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|In documentation it states that the Beacon data will be sent via AVL ID 385, but data from FMB140 is being sent with AVL ID:548. 
|-
| When the simple mode is selected beacon parsing is done automatically so AVL ID:385 is used

When advanced beacon mode is selected, beacon data capturing can be configured manually and to distinguish simple and advanced functionalities a different ID is used - AVL ID 548.

For advanced beacon configuration documentation, you can find it here: [[Advanced Beacon Capturing Configuration]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|I have implemented Codec8 Extended protocol. Communication is working correctly, IMEI and AVL packets are working fine, but the unit sends 0xFF instead of AVL packets sometimes. Is there any use of this packet and is it necessary to send some data as a response back? 
|-
| It seems that You have enabled the Network Ping Timeout feature.

What Network Ping Timeout does is it sends an empty packet (0xFF) to the server to make sure that the operator does not close a link between the device and the server.

If you don't want to receive 0xFF packets anymore you can set Network Ping Timeout to 0 seconds.
|}

== '''Configuration''' ==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|I have successfully paired the Teltonika Eye sensor to the FMB130 and I can see the data on the I/O tab but the data is not sent to my platform, what could be the issue? 
|-
| For the data to be sent to the platform, the I/O needs to have a priority of ‘Low’, ‘High’, or ‘Panic’ so that the data can be sent with periodical data to the platform.

I/O Settings wiki page - [[FMB125 I/O settings]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Why device doesn't detect the ignition? 
|-
|Please check which ignition source have you chosen and configure the device according to Your use case.

More information about the Ignition sources can be found here: [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Ignition_Source Ignition source]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|When testing the OBD device alarm of the vehicle is triggered when it is parked. What could cause this? 
|-
| This usually occurs when the device tries making OBD requests while the vehicle has no ignition and is locked. This can happen due to improper configuration, so make sure that the OBD device properly detects the ignition of the vehicle, when the ignition is actually ON.
More information about the Ignition sources can be found here: [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Ignition_Source Ignition source]
|}

Starting with Teltonika Telematics

2024-01-15T13:42:45Z

Andrius.abraskevicius:

=='''Firmware'''==
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can we delete records from the device memory? 
|-
|You can clear device's memory by clicking the "format" button in the [Status] window. This will delete all stored records from the device's memory. You can also send the SMS command "sdformat" to the device and it will do the same thing but remotely without the need to connect the device to a computer.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Is it possible to show battery % of EYE sensors/beacons? 
|-
|No, but it is possible to retrieve the battery voltage and estimate the remaining battery life.
More information about it can be found here: [https://wiki.teltonika-gps.com/view/EYE_FAQ#How_does_the_battery_voltage_translate_into_the_percentage_of_the_battery.3F How does the battery voltage translate into the percentage of the battery?]

Both EYE sensors and EYE Beacons can advertise their battery voltage
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is Autoscan and with how many Teltonika device models is this possible? 
|-
|Autoscan is the process of scanning for CANBUS program numbers in the vehicle CANBUS system. Currently, FMB140 and newest external CAN adapters have the Autoscan feature.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to access the latest firmware and how to know when the latest firmware has been released? 
|-
| The latest firmware release information is passed through the Teltonika newsletter. It is encouraged that you subscribe to this service to get real-time notifications about the releases.
Base firmware for all devices can also be found here: [[Firmware versions]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to activate digital output with SMS command? What commands are available for FMB920? 
|-
| Supported commands can be found here: [[FMB920_SMS/GPRS_Commands]]
To set digital output use the setdigout command. A description of this command can be found here: [https://wiki.teltonika-gps.com/view/FMB_setdigout FMB_setdigout]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is the difference between Fuel consumed and Fuel consumed (Counted) or Total mileage and Total Mileage (Counted)? 
|-
| Fuel consumed is the total fuel consumed by the vehicle since it was manufactured, while fuel consumed (counted) is the fuel consumed by the vehicle since the CAN device was installed.
Total mileage is the total mileage of the vehicle as displayed on the dashboard of the vehicle since it was manufactured, while total mileage (counted) is the mileage of the vehicle from when the CAN device was installed.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Does FMC125 work with the Iridium Edge use case? 
|-
| Yes, Iridium Edge does work with the FMC125 devices - the 03.28.06.Rev.323 firmware has to be used for this solution to work.
More information about the Iridium Edge solution can be found here: [[Iridium Edge]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Is there a way to encrypt the data that is sent to the server? 
|-
| Yes, our devices have TLS encryption capability, which allows us to secure the data using TLS certificates that are uploaded to the device and the server.
More information about TLS encryption can be found here: [https://wiki.teltonika-gps.com/view/FMB130_GPRS_settings#TLS.2FDTLS TLS settings]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can we check how much data has been used with the current data plan? 
|-
| In the configurator Status tab we have the GPRS traffic section, where data usage can be seen. Other than this, there is no way to get the data consumption from the device - this information will be available from the network provider.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Is there a way to implement seat belt detection with FMC920 device? 
|-
| There are 2 methods we can follow:

1. Digital Input: The FMC920 device only has 1 Digital input which is mostly used to connect the ignition cable, In this use case - the ignition source can be set to power voltage and the seatbelt sensor can be connected to Digital input with priority - High and Operand "On change".

2. Analog Input: The seat belt sensor can be connected to Analog input 1 with priority - high and low level values (depending on the voltage from the seatbelt, let's say 12 VDC) - 10 VDC and High level - 13 VDC. The idea is to make the voltage fall between low-level and high-level values and generate an event when the voltage enters that range.

IO settings guide: [[FMC920 I/O settings]]

It is recommended to use FMX130 as the device has a Ground sense option which will be easier to connect and DIN1 can be used for accurate Ignition detection.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How do I get a SIM card IMSI number on my server? 
|-
| The IMSI is not available as an IO element, and it will not be sent to the server with records. However, it can be requested by a SMS/GPRS command "getimsi"
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Why does the TAT100 device appear offline on my server? 
|-
| The TAT100 always works in Deep-sleep mode, and the open link Timeout is 30sec maximum, so the device does not stay connected to the server - this is done to preserve the battery life and allow the device to work longer.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can I send an SMS or command to the TAT100? 
|-
| Yes, you can send a command to the TAT100 and it will execute this command once it wakes up.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|When does TAT100 connect to FOTA WEB? 
|-
| TAT100 devices do not connect to FOTA Web periodically. It will automatically connect to FOTA Web only on initial startup (when the switch is flipped from OFF to ON position). Connection to FOTA Web should be initiated via the 'web_connect' SMS/GPRS command. This is to preserve battery power.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Can DSM detect 2 or more events at the same time? 
|-
| Yes, it can detect multiple events at the same time. The events are placed in a queue and then reported based on their generation time.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Which SMS encoding is supported by Teltonika Telematics devices? 
|-
| The device received commands encoded in Unicode and any third-party SMS portal should have the support of format SMS Default Alphabet while initiating communication with the Teltonika device. FMC devices support SMS Default Alphabet, also known as GSM-7, encoding only - this encoding standard should be configured at the sending device/application.
|}

=='''Software'''==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|When opening the configurator, a .NET error is shown. I tried installing .NET 7.0, but the error remained. How can this be solved? 
|-
| New Configurators use the newer .NET version - please make sure the correct version is installed and remove other (unused) .NET versions – more information can be found here: [[.NET Runtime for Desktop installation]]
Note #1: The Ways to determine the required version section is especially important here. It will help you decide which version you should choose.

Note #2: x86 is recommended even with Microsoft Windows 64-bit Operating System.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is FOTA Web and how is it useful? Can you see the device's real-time location using this system? 
|-
| FOTA Web is simply a device management platform that is used to assign files to the device remotely, such as firmware, configuration files, etc.
FOTA Web is '''not''' a tracking platform and does not report the device's real-time location.

You can find more information about the FOTA Web tool here: [[FOTA WEB]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to use the device transfer feature in FOTAWEB? 
|-
| Device transfer is a feature in FOTAWEB that allows clients to directly move devices amongst their accounts without the need to involve Teltonika.
More information about this feature can be found here: [https://wiki.teltonika-gps.com/view/FOTA_WEB_Devices#Device_transfer Device transfer]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How do I update configurations remotely via Teltonika FOTA Web? 
|-
| Kindly use the FOTA Web to remotely update configurations to units as explained here: [[FOTA WEB]]

Steps are:

1. Upload the configuration file in FOTA WEB under the files tab.

2. Head over to the devices tab then select the devices to receive the configuration.

3. Click on Create Task and choose Update Configuration on the drop-down then below it, choose the uploaded file, then click on Create Task.

The task will be executed the next time the device connects to FOTA WEB or you can force it to connect immediately by sending a command " web_connect" with two spaces before the command and no quotes, or hard restart the unit by unplugging the power and the internal battery then plugging it back on then the task will be executed immediately.
|}

== '''Hardware''' ==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What are the SIM card requirements for use with Teltonika Telematics devices? 
|-
| Different Teltonika Telematics devices support Mini SIM, Micro SIM, and Nano SIM sized SIM cards. To know the exact SIM card supported by Your device, please check the General Description Wiki page for Your device.

As for eSIMs, there are a couple of requirements for it to work with our devices - they can be found here: [[Requirements for eSIM]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How to connect the fuel gauge sensor to the Analog input of the FMx and calibrate for accurate results? 
|-
| We can measure the fuel level using analog input by matching the voltage coming from the fuel level sensor already mounted in the car, with the fuel level in the tank.
More information on how the AIN has to be connected and calibrated can be found here: [[Analog Fuel Sensor]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Where can we find the connection schemes for CAN-CONTROL adapter? 
|-
| Please use the link below to find and download the necessary connection scheme.

Link: https://drive.teltonika.lt/d/31c32f08610044b699b3/

Password: wzh1XNp0
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Does all RFID cards with 125 or 128kHz frequency work with FMC150 ? What about a 13.56 MHz NFC or RFID device? 
|-
|Like other devices with a 1-Wire interface, FMC 150 also supports a 1-wire protocol (DS1990A) RFID reader.
If the reader reads cards with 125 or 128 kHz and transmits this data through 1 wire protocol (DS1990A), we can integrate it into FMC150.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|How many batteries does TAT use? 
|-
| TAT uses 1 battery, which consists of 2 (7.2V variant) or 3 (10.8V variant) cells. Currently, manufactured TAT devices use 3-cell batteries.
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|What is the battery life of TAT1XY? 
|-
| TAT1XX can send approximately 1000 records, this may differ depending on the environment, coverage, Temperature, and device mounting,
|}

== '''Protocols''' ==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Where can I find how to parse the message from the device in the backend? 
|-
| Teltonika data sending protocol Codec 8 and Codec 8Extended description with examples:

[[Codec|AVL data sending codecs]]

TCP/UDP listener and AVL parser with source code that could be used as a template for implementation of Teltonika protocols. The whole pack can be downloaded from here:

[https://wiki.teltonika-gps.com/view/Universal_Device_Test_Guide#Protocols_implementation Listener and AVL parser]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|In documentation it states that the Beacon data will be sent via AVL ID 385, but data from FMB140 is being sent with AVL ID:548. 
|-
| When the simple mode is selected beacon parsing is done automatically so AVL ID:385 is used

When advanced beacon mode is selected, beacon data capturing can be configured manually and to distinguish simple and advanced functionalities a different ID is used - AVL ID 548.

For advanced beacon configuration documentation, you can find it here: [[Advanced Beacon Capturing Configuration]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|I have implemented Codec8 Extended protocol. Communication is working correctly, IMEI and AVL packets are working fine, but the unit sends 0xFF instead of AVL packets sometimes. Is there any use of this packet and is it necessary to send some data as a response back? 
|-
| It seems that You have enabled the Network Ping Timeout feature.

What Network Ping Timeout does is it sends an empty packet (0xFF) to the server to make sure that the operator does not close a link between the device and the server.

If you don't want to receive 0xFF packets anymore you can set Network Ping Timeout to 0 seconds.
|}

== '''Configuration''' ==

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|I have successfully paired the Teltonika Eye sensor to the FMB130 and I can see the data on the I/O tab but the data is not sent to my platform, what could be the issue? 
|-
| For the data to be sent to the platform, the I/O needs to have a priority of ‘Low’, ‘High’, or ‘Panic’ so that the data can be sent with periodical data to the platform.

I/O Settings wiki page - [[FMB125 I/O settings]]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|Why device doesn't detect the ignition? 
|-
|Please check which ignition source have you chosen and configure the device according to Your use case.

More information about the Ignition sources can be found here: [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Ignition_Source Ignition source]
|}

{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|When testing the OBD device alarm of the vehicle is triggered when it is parked. What could cause this? 
|-
| This usually occurs when the device tries making OBD requests while the vehicle has no ignition and is locked. This can happen due to improper configuration, so make sure that the OBD device properly detects the ignition of the vehicle, when the ignition is actually ON.
More information about the Ignition sources can be found here: [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Ignition_Source Ignition source]
|}