CAN bus telematics and speed interface
Feed a tracker, tachograph or fleet device clean speed and status signals off the vehicle network, with no cutting into the factory loom.
What a CAN bus telematics interface does
A CAN bus telematics interface takes the signals a fleet device needs, road speed, ignition and status, off the vehicle network and provides them cleanly to a tracker, tachograph or fleet unit. The device reports accurate journeys and driver data without a single cut into the factory wiring.
It's how telematics goes onto a modern vehicle tidily. Rather than chasing a speed wire or an ignition feed through the loom, the interface reads the network and hands the fleet device exactly what it expects.
Why fleet installs read the network
A tracker is only as good as its data. It needs true road speed for journey and driver reporting, and a reliable ignition state to log trips correctly. On a modern vehicle those signals live on the CAN bus, so reading the network beats splicing wires that may no longer exist.
- Accurate reporting: a true speed feed means correct journeys, distances and driver behaviour.
- Clean trip logging: a reliable ignition state records start and stop without guesswork.
- A tidy install: the interface reads the network rather than cutting the loom.
- One method across the fleet: the same approach fits a mixed fleet of makes and models.
What the telematics feed drives
Clean speed and status signals are the foundation of accurate fleet data.
Vehicle trackers
True speed and ignition for journey logging, driver behaviour and fleet reporting.
Digital tachographs
A speed signal for tachograph systems on commercial vehicles, matched to the input they expect.
Fleet management units
Status feeds for utilisation, timesheets and duty-of-care reporting.
Driver behaviour systems
Accurate speed data for scoring harsh driving and speeding events.
Asset and plant tracking
Engine and ignition status for tracking working plant and equipment.
Insurance and compliance telematics
Reliable data for insurance-linked and compliance-driven schemes.
CAN KONTROL lines for tracker and telematics feeds
CAN KONTROL SPEED(opens in a new tab)
The road speed feed for a tracker input, set up for the vehicle and the tracking unit.
CAN KONTROL SPEED IGN(opens in a new tab)
Pairs speed with an ignition reference for devices that wake on ignition.
CAN KONTROL ODO(opens in a new tab)
Distance-travelled output for journey logging and mileage records.
Telematics feed lines at Intellitec MV(opens in a new tab)Compare with CANM8 product names
Rolling telematics out across a fleet?
Tell us the fleet and the devices, and our engineers will confirm a clean speed and status feed off the CAN bus.
Reference
Fitting a CAN speed and ignition feed for a tracker
A tracker earns its keep on journey data, and journey data depends on trustworthy speed and ignition inputs. Fit the feeds in this order and confirm them on the fleet platform, not just at the vehicle.
Tools for the job
- Digital multimeter
- Wiring information for the vehicle
- Trim removal tools
- Laptop or phone with access to the fleet platform
- The tracker's installation sheet
Supplies to have ready
- Fuse and holder for the module's supply
- Back-probe connectors for the CAN pair
- Leads for the speed and ignition inputs
- Heat-shrink, tape and labels
- 1
Read the tracker's input list
Check which digital or pulse inputs the tracker has for speed and ignition, and whether it wants distance as well. Tell us the tracker model so each module output is matched to a real input.
- 2
Fit the tracker's own power and antennas first
Mount the tracker, power it as its guide says and place its antennas for a clear sky view. Keep the tracker supply separate from the module's supply so a fault in one cannot cut the other.
- 3
Reach the bus
Speed and ignition are commonly found at a body control module connector or behind the dash. On trucks and buses a fleet-management connector may be provided for exactly this purpose.
- 4
Pick out high and low and connect
Tag the twisted pair, confirm it is alive, and connect through back-probes or the no-cut inductive reader. Avoid touching the vehicle's own tracking-related or immobiliser wiring.
- 5
Supply the module
Feed the module from a fused permanent live and earth to bare, sealed metal. A tracker vehicle may stand for weeks, so keep the module's draw in mind and ask us for its standby figure.
- 6
Wire speed, ignition and odometer outputs
Connect the speed output and, where used, the ignition reference to the tracker's inputs. The odometer line offers a distance-travelled output for journey logging and mileage records.
- 7
Mount and label
Fix the module away from heat and water, label each output lead with the tracker input it feeds and note the connections for the next engineer.
- 8
Register the install
Enter the vehicle details on the fleet platform, so the first ignition and speed events land against the right asset.
Confirming the data on the platform
- Switch the ignition on and confirm an ignition-on event appears against the vehicle on the fleet platform.
- Drive a short loop and check that the reported speed tracks the dashboard and a GPS reference.
- Compare the platform's recorded distance with the odometer over a measured trip.
- Switch off and confirm the ignition-off event is logged and the tracker settles into its low-power state.
- Leave the vehicle for the night and check the battery voltage and the tracker's reported state in the morning.
How the telematics interface works
It reads the signals the fleet device needs and provides them without touching the loom.
- 1
Connect to the network
The interface joins the vehicle CAN bus and reads speed, ignition and status messages already present, with no splice into the loom.
- 2
Decode the feeds
It identifies road speed and ignition state for that make and model, and other status where the device needs it.
- 3
Provide clean outputs
It presents a speed signal and an ignition feed in the form the tracker or tachograph expects.
- 4
Report accurately
The fleet device logs journeys, distance and driver data from true vehicle signals.
Which vehicles it covers
Speed, ignition and status are carried on the CAN bus of modern cars, vans, trucks and buses, the full span of a mixed fleet. The interface reads each manufacturer's messages in configuration, so one product covers them without different hardware.
Coverage spans the common UK fleet, kept current with in-house firmware. Scorpion has designed and built vehicle telematics in the UK since 1973, so the tracking and the interface come from the same manufacturer.
As a telematics manufacturer, we build the tracking as well as the interface. ScorpionTrack devices and our fleet platform are designed and supported in-house, so the whole chain, from the signal on the network to the report on the screen, is engineered by one company.
For tachograph work the interface can supply a speed signal on commercial vehicles, matched to the input your tachograph expects. For a wider install it pairs with the multi-output interface, so cameras and lighting run from the same clean takeoff.
Common fitments include:
Common questions
What is a CAN bus telematics interface?
It is an interface that takes speed, ignition and status signals off the vehicle network and provides them to a tracker, tachograph or fleet device, so it reports accurately without cutting the loom.
Why does a tracker need a CAN speed feed?
True road speed gives accurate journeys, distances and driver-behaviour data. On a modern vehicle that speed is a network message, so an interface provides it cleanly.
Does it work with tachographs?
It can supply a road-speed signal to a tachograph system on a commercial vehicle. Confirm the input specification of your tachograph, and leave fitting and calibration of the tachograph itself to the maker or an approved workshop.
Can I fit telematics without cutting the loom?
Yes. Reading the network rather than splicing wires is the whole point of a CAN interface, keeping the install clean and reversible.
Do you make the tracking as well?
Yes. Scorpion designs and manufactures ScorpionTrack telematics and the fleet platform in the UK, so the signal, the device and the reporting come from one company. Speak to us about the fleet.
Why does the tracker never log an ignition event?
Check the tracker's ignition input is wired to the right output, then test that output with a meter while switching the ignition. No change at the output means the module isn't reading the ignition state, so send us the vehicle details.
Why doesn't the speed on the platform match the dashboard?
A small gap is normal, since dashboards often over-read. A proportional gap points at the tracker's input scaling, so check its setup against the signal the module provides, and compare with GPS speed.
Why does the tracker's distance drift from the odometer?
Distance from a speed feed is calculated, so small drift over a long trip can occur. Check the tracker's configured scaling first, and use the distance output where the job needs mileage that follows the vehicle's own odometer.
Why does the tracker keep draining the vehicle battery?
Look at the tracker's power mode and the module's standby draw separately. A tracker held awake by a stuck ignition input will draw more, so check that the ignition output drops when the vehicle sleeps.
Why do ignition events arrive late or out of order?
Check the tracker's reporting settings and its signal quality first. If the module's ignition output switches promptly at the vehicle, the delay is on the reporting side.
Will it feed a tachograph as well as the tracker?
A speed output can feed more than one device only if the outputs and the devices' input specifications allow it. Check each device's input specification and tell us the equipment, so we can say how the outputs should be arranged.
Does the tracker's input reject the signal?
Compare the input type the tracker expects with what the module was configured to give it, and check for noise on the lead. Tell us the tracker model and we'll check the configuration.
Can I use the same module on a 24V fleet?
The module runs from 12V and 24V supplies. Confirm the tracker's supply range, and tell us the vehicles so the speed source is read correctly on each type.