The FMB, FMC, FMM and FMU families speak Codec 8 and Codec 8 Extended. Our platform ingests both, including the AVL IO elements that carry CAN data, fuel level, temperature and driver identification.
The widest IO set in the market and a configurator that makes remote reconfiguration genuinely practical.
Protocol-level facts from the manufacturer’s own documentation. Model-level behaviour varies within a series, so confirm your exact unit with us rather than assuming.
| Item | Supported | Notes |
|---|---|---|
| Protocol family | Codec 8, Codec 8 Extended | Binary AVL packets with typed IO elements |
| Transport | TCP and UDP | TCP is normal for fleet; UDP appears on low-power asset trackers |
| Series commonly deployed | FMB (vehicle), FMC (LTE Cat-1), FMM (Cat-M1/NB-IoT), TAT (asset) | Series determines network, not protocol |
| CAN data | Via LV-CAN200 / ALL-CAN300 adapters | Adapter presents CAN values as standard IO elements |
| Fuel sensing | RS232 / RS485 digital probes, analogue input | Digital LLS probes are considerably more stable than analogue |
| Driver ID | 1-Wire iButton, RFID reader | Arrives as its own IO element, not a text field |
| Remote configuration | SMS commands, FOTA WEB | Server re-pointing without touching the vehicle |
Most platform vendors publish a list of supported model numbers. It looks reassuring and it is usually out of date, because it describes a snapshot of what somebody tested once rather than how the integration actually works. GPS platforms do not implement models; they implement protocols. Teltonika devices report over Codec 8 / Codec 8 Extended across TCP and UDP, and the platform decodes that protocol — which is why a new unit in the FMB, FMC, FMM, FMU, FMT, TAT, TFT families generally works on the day it ships rather than after a development cycle.
What genuinely varies between models is not the protocol but the hardware: which inputs physically exist, whether a CAN interface is present, whether there is a relay output, how many 1-Wire devices can be attached. That is why we ask for your exact model and firmware version rather than publishing a matrix. It takes us a day to confirm against a live server, and it is the difference between a deployment that works and one that discovers a missing input after the units are installed.
Send the model, the firmware version and what you need to report on. You will get back a straight answer on three things: whether the unit reports into the platform at all, which of your required data points it can actually produce, and whether a cheaper unit in the same range would do the same job. That last one costs us margin and saves you money, which is the point — a fleet that buys the wrong hardware blames the platform.
Teltonika units already in the field can be re-pointed to a new server remotely, so a migration does not mean visiting vehicles. We audit what is connected first, import your historical data, re-point a pilot group, and cut the rest across only once the pilot reconciles cleanly against your old system. The old endpoint stays live through the window. Full detail is on the hosting and migration page.
Send your Teltonika model list and we will confirm compatibility against a live server before you commit. Request a compatibility check or message us on WhatsApp — include firmware versions if you have them, and tell us what you need to report on.
Support is implemented at the protocol level rather than model by model. Any device speaking Codec 8 or Codec 8 Extended — which covers the FMB, FMC, FMM, FMU and TAT families — reports into the platform. Send us your exact model and firmware version and we will confirm against a live server before you commit to anything.
For CAN-derived fuel level, yes — an LV-CAN200 or ALL-CAN300 sits between the vehicle bus and the tracker and presents the values as standard IO elements. A direct RS232 or RS485 fuel probe is the alternative and is usually more accurate on tanks that matter, because it measures the tank rather than trusting the vehicle gauge.
Yes. Teltonika trackers accept server IP and port changes by SMS command, and FOTA WEB can push configuration across a fleet. We batch the change fleet by fleet and keep your old endpoint live during the window so nothing is lost mid-switch.
Yes. Driver ID arrives as its own IO element rather than embedded text, so it maps cleanly to a driver record and drives the driver behaviour, attendance and payroll modules rather than sitting as an unparsed string.
Teltonika devices buffer records on-device and send them when the link returns. The platform accepts the backlog and writes it against the original timestamps, so a tunnel or a dead-coverage route leaves no gap in the trip history.
Send us your exact models and firmware versions. We will test them against a live server and tell you what works before you commit to anything.
Check My Device →