Teltonika GPS technical glossary
22 terms you'll read in any spec sheet, integration or conversation with your installer. Short definitions, no generic redefinitions: if you already know what a GPS is, this is what sits underneath.
Jump to a letterA
AVL (Automatic Vehicle Location)
Automatic vehicle location system. In the Teltonika world, AVL describes the full logic: GNSS + modem + event logic + protocol for sending data to the server. When you see "AVL ID" in the documentation, it refers to the numeric identifier of each reportable parameter (e.g. AVL ID 239 = ignition).
ADAS
Advanced Driver Assistance Systems. A set of vision-based driving aids: forward collision warning, unintended lane departure, safe following distance. In the catalogue you'll find it as the Teltonika ADAS camera, integrated with the tracker over RS232 or Bluetooth.
Accelerometer / gyroscope
Internal inertial sensors in the tracker. They detect harsh acceleration, hard braking, cornering and impacts. They're the basis of eco-driving and of crash detection events. Every modern FMC/FMB includes them as standard.
B
CAN bus
Controller Area Network. The vehicle's internal serial communication bus (engine, ABS, BCM). Reading it lets you access RPM, fuel consumption, real odometer, fuel level and door states without extra sensors. It's read with modules like the CAN-CONTROL or devices with native CAN such as the FMC150.
BLE (Bluetooth Low Energy)
Low-power Bluetooth 4.0+. On Teltonika it's used to pair external sensors: temperature probes, asset identification beacons, fuel pulse readers.
C
Codec 8 / 8 Extended / 16
Binary formats the tracker uses to pack data before sending it to the server. Codec 8 is the basic one; 8 Extended adds 2-byte IDs (more AVL IDs available); 16 adds a record-generation timestamp on top of the send timestamp. Details in Codec 8/8E/16 protocols.
CAT-M1 / NB-IoT
Low-power 4G LTE variants. Cat M1 keeps voice and handover; NB-IoT does not. Most Teltonika FMC devices are LTE Cat 1, not Cat M1: be careful when comparing with pure IoT trackers.
D
DIN / DOUT
Digital Input / Digital Output. The inputs read binary states (ignition, door, panic button). The outputs drive external relays: engine cut-off, siren, hazard lights. A Teltonika DOUT is open collector: it needs a relay to switch real power.
DTC
Diagnostic Trouble Codes. Vehicle fault codes read via OBD II or J1939. Devices like the FMC003 report them automatically.
E
Eco-driving
Analysis of driving behaviour from accelerometer events: harsh acceleration, hard braking, aggressive cornering. It doesn't measure "style" in the abstract; it measures specific events above configurable thresholds (mg / m/s²).
F
FOTA (Firmware Over The Air)
Remote update of the tracker's firmware and configuration without touching it physically. Essential once you're managing more than 50 units. It's done from Teltonika's FOTA Web platform.
2G fallback
The ability of a 4G device to drop to 2G when it loses LTE coverage. Useful until 2G is switched off for good in Spain (planned for 2027–2030 depending on the operator). After the switch-off, fallback no longer makes sense.
G
Geofence
A virtual polygon or circle on the map. The tracker fires an event on entry or exit. Up to 50 geofences per device can be configured on the usual FMC models.
GNSS
Global Navigation Satellite System. The correct term: "GPS" is a specific constellation (the American one). GNSS covers GPS + GLONASS + Galileo + BeiDou. Modern Teltonika devices read all four simultaneously.
I
iButton (Dallas 1-Wire)
A contact key with a unique number, used for driver identification. It connects to the tracker over 1-Wire (a single wire + ground). The de facto standard in delivery fleets.
IP67 / IP68 / IP69K
IEC 60529 protection ratings. IP67: immersion at 1 m for 30 min. IP68: continuous immersion at a specified depth. IP69K: high-pressure, high-temperature water jets (industrial washing). For heavy machinery, don't go below IP67 (FMC234); for wash-downs, IP69K (FTC880).
J
J1939
CAN protocol for trucks, buses and heavy machinery (SAE). It's read by devices like the FMC650: real fuel consumption, RPM, mileage, engine temperature, AdBlue levels.
R
RS232 / RS485
Industrial serial ports. RS232 is point-to-point (a single peripheral). RS485 is a differential bus: you chain several sensors. RS485 is used for LLS fuel probes or professional RFID readers. Available on the FMC125.
RFID
Radio Frequency Identification. Used for driver identification (an alternative to the iButton) and asset control in warehouses and on site.
T
Digital tachograph
Legal recorder of driving times for vehicles over 3.5 t. Teltonika devices read it over the K-Line port or via remote DDD (Digital Data Download). The FMC650 is built for this.
TCP / UDP
Protocols for sending the codec to the server. TCP confirms delivery (more reliable, more traffic); UDP does not (less traffic, ideal for large fleets with a solid server). Configurable per device.
Frequently asked questions
Is there an official manual with all the AVL IDs?
Yes, Teltonika publishes the list on its wiki per model. If you need the document to integrate your own server, request it at info@trackiber.com stating the exact model.
What's the difference between Codec 8 and 8 Extended?
8 Extended uses 2-byte IDs, which lets you handle more than 256 different parameters. For any new integration, use 8E or 16 straight away.
Does IP67 withstand pressure washing?
Not reliably. IP67 guarantees immersion, not high-pressure, high-temperature jets. For industrial washing you need IP69K.
Do I need a separate SIM card or does Teltonika include one?
Teltonika never includes a SIM. You choose it: local operator M2M, industrial eSIM or a normal SIM with an open APN.
Missing a term?
If you'd like us to add a concept to this glossary, email it to info@trackiber.com. If you need to pick a device based on your use case, go straight to the advisor.