GPS for transport fleets: what to look at (and what to ignore)

If you manage rigid trucks, tractor units or heavy delivery, this page is for you. We explain what to read from the J1939 bus, how to comply with the digital tachograph without doubling your admin work, and where the real ROI is.

On this page

The problem with "just tracking location"

A GPS unit with no bus reading tells you where the truck is and little else. For a transport fleet, that's 20% of the value. The remaining 80% is in real consumption per route, driving hours versus paid hours, driver identification and auditable eco-driving events. Without J1939 and without the tachograph, you're paying for a tracker.

The right approach: a hardwired unit with native CAN + tachograph reading + independent LLS fuel sensors to cross-check the data. Three sources, one single truth.

Reading the J1939 bus

J1939 is the standardised CAN protocol for heavy vehicles (SAE J1939). The PGNs you care about travel over it:

  • Instant and cumulative consumption (litres, l/100 km).
  • Engine RPM and load rate.
  • Speed and real odometer (no odometer tampering).
  • Coolant temperature, oil pressure, AdBlue.
  • Engine brake, retarder and PTO status.

The FMC650 reads it out of the box: you plug the J1939 connector into the truck's corresponding port (no external CAN-CONTROL needed) and the PGNs arrive parsed at the server via Codec 8 Extended.

Digital tachograph: reading and remote download

For tractor units and trucks >3.5 t, the digital tachograph is a legal requirement. The FMC650 covers two things:

  1. Real-time reading of driver activity (driving, rest, other work, availability). The fleet manager sees what each driver is doing without waiting for the weekly download.
  2. Remote DDD download of the C files (driver card) and M files (mass memory). No manual plugging in, no need to send the driver to the office.

This removes the admin friction of "the driver forgot to bring the card on Friday". And it leaves a complete legal audit trail, with a server timestamp.

Complementary sensors

J1939 covers almost everything, but there is data where the bus lies or doesn't expose it:

  • Capacitive LLS probe in the tank, connected via RS485. It detects fuel theft (a sharp drop in level with the vehicle parked and the engine off). J1939 itself gives you consumption, but it doesn't detect theft in the parking lot.
  • BLE temperature probes for refrigerated transport: up to 4 per unit, with no additional wiring.
  • Driver identification via iButton or RFID, complementary to the tachograph card (for short movements with no tachograph requirement, e.g. yard manoeuvres).
  • ADAS camera if your insurer requires a DVR or if you've had recent claims.

ROI calculation: three real levers

The ROI of GPS in a heavy fleet is quantified, not guessed. Three common levers:

1. Lower consumption through eco-driving

Harsh acceleration, prolonged idling and excessive revving events drop by between 5% and 12% in the first 6 months when there is a weekly report to the driver. Across a fleet of 20 trucks each consuming 30,000 l/year, a 6% reduction is 36,000 l/year.

2. Optimising driving hours

Cross-referencing tachograph activity against the route sheet: you identify dead time, billable waits at the client and real overtime. Typical recovery: 3–5% of non-productive hours turned into billable or avoided.

3. Preventive maintenance

J1939 DTCs + real odometer + engine hours let you schedule services at real mileage, not by estimate. It reduces roadside breakdowns and stops at non-contracted workshops.

In practice, an FMC650 + LLS probe + fleet server installation pays for itself in 6–10 months for fleets of 10 trucks or more. Below that, the cut-off comes down to whether the end client requires the tachograph on the platform or not.

Recommended hardware

  • Tractor units and heavy rigids: FMC650 with J1939 + tachograph reading + RS485 for LLS.
  • Large vans and heavy delivery vehicles without a tachograph: FMC150 with native CAN.
  • Construction machinery moving in and out of the depot: see GPS for construction.
  • Trailers without a constant power supply: TAT240 with an internal battery.

For all of the above, management via FOTA Web is included.

Frequently asked questions

Does the FMC650 work for both new and old trucks?

Yes, as long as the truck has a digital tachograph (mandatory since 2006) and a J1939 bus (standard since the late 90s in heavy vehicles). For pre-2000 vehicles without J1939, you have to use external sensors.

Is remote DDD download legal in Spain?

Yes, as long as the download is made to a system that complies with the legal retention of the C and M files, with their original digital signatures. Remote download has been recognised since Regulation (EU) 165/2014.

How many trucks justify an LLS probe?

From 5 trucks with their own tank, usually yes. The capacitive probe detects fuel theft that J1939 can't see because the engine is off.

What if my fleet is mixed (truck + van + car)?

Mix the references: FMC650 in the truck, FMC150 in large vans, FMC920 in cars. They all report to the same server with a compatible codec.

Do I need my own platform or is the manufacturer's enough?

Teltonika has no commercial platform of its own. The unit reports to any compatible server (Wialon, Navixy, flespi, mapon, custom integrations). If you need a platform recommendation for your case, get in touch.

Moving to a quote

If you're clear that you need the FMC650 or you want a proposal for your fleet, go through the advisor or write to info@trackiber.com with the number of units and truck models. We are an official Teltonika distributor.

Request a proposal