Telematics without a CAN bus: what you can still read, and what you can't.

"There's no CAN bus" usually gets treated as the end of the conversation - as if the machine has nothing left to say. It doesn't, quite. Some data genuinely disappears without an ECU connection. A surprising amount doesn't. The honest answer is always machine-specific, and it's worth knowing which is which before anyone promises you a dashboard.

This is the breakdown we actually use in the field: what a retrofit sensor on an edge device can capture without CAN bus access, and what it flatly can't - no matter how the sales deck phrases it.

Why some machines have no CAN bus at all.

Most modern diesel machines broadcast J1939 data whether you read it or not. The machines that genuinely don't fall into a few categories: older mechanical-injection engines from before electronic control was standard, certain compact and specialised engine families used in telehandlers, generators and smaller equipment, and largely mechanical equipment where there is often no meaningful engine electronics to read in the first place.

In practice, the only way to know is unit by unit. On a typical mixed fleet audit we go through the engine make, model and emissions stage of every machine to work out which ones give CAN data and which don't. It is not unusual for a meaningful share of an older fleet to have no usable CAN bus at all.

What you can still measure without CAN bus.

With the right external sensors on a standard edge device, most of the operational picture is still recoverable:

• Engine hours - via vibration or voltage detection (engine on/off), or a dedicated hour meter
• Real-time engine RPM - an inductive sensor on the flywheel or pulley
• Idle / normal / full-load state - derived from the RPM reading
• Engine oil level - an analogue float sensor, where the tank is physically accessible
• Engine oil temperature - a 1-Wire clamp-on or inline sensor
• Coolant temperature - a 1-Wire sensor
• AdBlue level - where a tank is fitted
• Fuel level - an analogue float or ultrasonic sensor, where the tank is accessible
• Hydraulic oil level - an analogue level sensor, where the tank is accessible

Fuel consumption and hydraulic flow sit in a grey zone: a level sensor plus running-time gives an indicative burn rate, not an exact figure, and real flow measurement needs an inline flow meter - more invasive than a standard retrofit.

What genuinely isn't possible.

Three things stay off the table regardless of sensor choice:

• Fault codes and diagnostic data - these live inside the ECU's own logic and can't be reconstructed from external sensors
• Emissions and exhaust parameters - same reason, ECU-only data
• Oil and hydraulic pressure - technically measurable, but only by tapping into a pressure line, which is invasive and usually outside the scope of a standard retrofit

Anyone offering fault codes or pressure readings off a machine with no CAN bus is either tapping the ECU some other way, or promising something the hardware can't deliver.

Why some machines need a site visit before you get an answer.

A parts list and an engine model tell you most of what you need to know - but not always where the tank sits, whether the connector is accessible, or whether a sensor can physically be fitted without disassembly. Largely mechanical equipment is the clearest example: there is no ECU to check on paper, so the only way to know what is measurable is to look at the machine itself.

The short version.

1. Not every machine without CAN bus is a dead end - most of the operational picture is still recoverable
2. Hours, RPM, oil and coolant temperature, and fluid levels are realistic with the right external sensors
3. Fault codes, emissions data and pressure readings stay off the table without an ECU connection
4. Largely mechanical equipment needs a physical look before anyone can promise a number