Insights/Telematics

Retrofit telematics: getting live data from machines without factory telematics.

Every fleet has a machine nobody's told can be a data source. Here's what a retrofit gateway actually does, what it costs, and what to check before you buy one.

Thibaut De RidderHead of Product, monytr7 min read

Somewhere in most fleets there's a machine nobody has told you can be a data source. An excavator from 2014, a static generator that's never been near an app, a wheel loader bought used with no telematics subscription attached. The assumption is usually that these machines are just outside the system - too old, too basic, not worth the trouble. That assumption is usually wrong.

Retrofit telematics is the practice of adding a gateway to a machine that has no factory system, and reading the same signals - engine hours, faults, location, fuel - directly off the machine's own network instead of waiting for the OEM to publish them. Here's what it actually involves, and what to check before you commit.

What "no factory telematics" really means.

Machines fall into three rough categories. The first genuinely has nothing: no telemetry hardware, no data bus worth reading, usually pre-2005 or very basic equipment. The second - the largest group by far - has a working CAN bus (usually J1939) broadcasting engine hours, fault codes and fuel data internally, but no gateway ever installed to get it off the machine. The third has factory telematics that's simply not connected to anything, either because the OEM subscription lapsed or because the portal never talked to anyone outside the manufacturer's own app.

Retrofit only solves the second and third categories - but that's most of a typical mixed fleet's older iron.

What a retrofit gateway actually does.

A retrofit gateway is a small unit wired into the machine's diagnostic or CAN connector. It listens passively to the same J1939 traffic the machine's own dashboard reads, and reports it over cellular to a platform - the same shape of data an OEM feed would send, just captured at the source instead of through the manufacturer's cloud.

  • Engine hours, read continuously from the ECU
  • Fault codes (SPN/FMI), as they're broadcast, not on a delay
  • Fuel level, where the machine exposes it on the bus
  • Ignition and engine-run state
  • Location and movement, from the gateway's own GPS
  • On fixed equipment like generators, Modbus signals - load, fuel, runtime - through the same principle over a different protocol

None of this depends on the OEM's cooperation, subscription status, or app. The machine is already saying all of this on its own network; the gateway just listens.

What it costs, roughly.

As a rough industry benchmark, a retrofit gateway plus installation typically runs somewhere in the €300-€600 range per machine, one-off, on top of a monthly per-machine platform fee similar to what you'd pay for a machine with factory telematics. Installation itself is usually under half a day per unit for a straightforward CAN tap; fixed equipment with a Modbus controller is often quicker. The real cost question isn't the hardware - it's how many machines in your fleet are currently invisible because nobody priced this out.

What to ask before you buy a retrofit solution.

  1. Is the gateway reading passively, or does it write anything back onto the bus? (It should only listen.)
  2. Does the installer know your specific make and model's connector pinout, or are they figuring it out on your machine?
  3. What happens to fault codes that aren't in the standard J1939 dictionary - does the platform translate OEM-specific codes too, or only the generic ones?
  4. If the machine has no exposed fuel signal, what's the fallback - no data, or a separate fuel sensor?
  5. Does the retrofit data land in the same dashboard as your factory-telematics machines, or a separate one?

Why this matters more than it looks.

The machines most fleets leave off telematics are usually the ones costing the most in hidden ways - older, more failure-prone, least visible when something goes wrong. Bringing them into the same picture as the rest of the fleet is often where the first real savings show up, precisely because nobody was watching them before.

Talk to us

Book a 30-minute demo.

A walkthrough of the platform - idle time, fault codes, fuel and utilisation in one screen - and a straight answer on how it would fit your fleet.

Book a demo
Keep reading

More from monytr Insights.