Speed Pulse vs CAN Speed vs OBD Speed: Which Signal to Use
By Alec J. Reviewed byJames M.
Use CAN speed, read passively from the vehicle network, for anything that needs a continuous feed. Use a speed pulse when the device only accepts a pulse input. Keep OBD speed for occasional polled checks. A speed pulse is CAN speed re-expressed as a frequency, so the real choice is between listening to the network and asking the vehicle a question.
Key facts:
- Speed pulse: a square wave whose frequency rises with speed, scaled in pulses per kilometre.
- CAN speed: a message the vehicle broadcasts on its own schedule, with no request needed.
- OBD speed: a value returned only when a tool asks for it, as one whole number in km/h.
- Weak spot of OBD: sleep, secure gateways and anything that must never go blind.
- One source: all three normally trace back to the same wheel-speed measurement.
What are the three speed signals?
Each one carries the same fact in a different form.
- Speed pulse. A frequency that follows speed. Receiving equipment is set to a number of pulses per kilometre, so a tracker, limiter or tachograph input turns frequency back into speed. It is the oldest form, from the days of a gearbox sender and a speedometer wire.
- CAN speed. A message on the vehicle’s CAN network. On trucks and buses, SAE J1939 names the signal wheel-based vehicle speed (SAE). On cars and vans each manufacturer defines its own message and scaling, which is why a reader has to be set up per vehicle.
- OBD speed. The diagnostic route. A tool sends a service 01 request for the vehicle speed parameter defined in SAE J1979 and the engine control unit answers with a single byte, 0 to 255 km/h (SAE). The tool plugs into the 16-pin OBD-II port.
GNSS speed, worked out from satellite signals, is a fourth source. It needs no connection to the vehicle, but it drops out in tunnels and under cover, so it’s a cross-check more than a replacement.
Which one is most accurate?
None of them adds accuracy. They all start from wheel-speed sensing, so the question is which one loses the least on the way and which module’s version of speed it carries.
The UN speedometer regulation says the dashboard must never read below true speed, and may read above it by up to 10 per cent plus 4 km/h (UN Regulation No 39). A message that feeds the display can therefore carry that built-in allowance. A raw wheel-speed message may not. Which one the vehicle broadcasts is the manufacturer’s choice.
- CAN speed keeps the full resolution the vehicle uses internally.
- OBD speed is rounded to whole km/h, which is fine for a log and coarse for control.
- A speed pulse is only as good as its scaling. Set 10 per cent too many pulses per kilometre and the receiving device reads 10 per cent fast, at every speed.
A practical check is to compare the reading against GNSS speed at a steady 50 mph on a clear road, then confirm the scaling the receiving device expects.
How do they compare on delay?
CAN speed arrives as a periodic broadcast, so the value is as fresh as the last frame. Repetition rates are set by the manufacturer on car and van buses; on heavy vehicles, SAE J1939-71 defines a default rate for the cruise control and vehicle speed message, so a J1939 speed value is refreshed many times a second.
A pulse adds two delays. The interface has to decode the message, and the receiver has to count pulses over a window to turn them into speed. The slower the vehicle, the longer a pulse takes. With an example scaling of 8000 pulses per kilometre, the frequency is speed in km/h times 8000 divided by 3600:
| Speed | Frequency | Gap between pulses |
|---|---|---|
| 10 km/h | about 22 Hz | about 45 ms |
| 2 km/h | about 4.4 Hz | about 225 ms |
The figure of 8000 is an illustration, not a product setting. Always use the value in the receiving device’s documentation.
OBD adds a full request and reply for every reading. How often that happens depends on the polling tool and on the other diagnostic traffic sharing the port, which in practice is often a handful of readings a second.
When is OBD polling unsuitable?
Whenever the feed has to be continuous, or the vehicle won’t answer.
- Continuous feeds. A limiter, a tachograph input or a safety interlock can’t stop knowing the speed between polls. A missed reply becomes a gap.
- Sleep. When the network sleeps, control units stop answering. Polling to find out can wake the bus again and keep it awake, which runs the battery down on a parked vehicle.
- Secure gateways. A secure gateway sits between the diagnostic port and the internal networks and can filter or authenticate requests. A plug-in device that relies on polling may get no answer, or only a limited one. The glossary entry on secure gateways explains the term.
- Shared port. A workshop tool, a tracker and a dongle can’t all poll comfortably at once.
- Heavy vehicles. Many trucks and buses use a 9-pin J1939 diagnostic connector rather than the 16-pin OBD-II one, and their speed is already on the J1939 network.
Reading CAN passively avoids most of this. A controller in listen-only mode receives frames without acknowledging or sending anything, so the vehicle’s own traffic is left alone. The catch is that someone has to know the right message for each vehicle.
Which signal suits which job?
| Job | Usual choice | Why |
|---|---|---|
| Tracker or telematics unit | CAN speed, or a pulse if the unit takes a pulse input | Continuous, and works while the vehicle is moving |
| Tachograph | Whatever its installation instructions specify | A regulated instrument with its own approved input |
| Speed limiter | CAN speed or pulse, as the limiter requires | Needs an unbroken, current value |
| Speed-aware camera or display | CAN speed or pulse | Threshold changes need a prompt reading |
| Occasional logging or diagnostics | OBD speed | A single value on request is enough |
Trackers and telematics. Journey, distance and driver-behaviour data all depend on speed, so a continuous source matters. See the telematics speed interface.
Tachographs. A tachograph is type-approved and calibrated by an approved workshop. What may feed it is decided by the tachograph maker’s instructions and the regulations, so confirm the input first, then choose the source to match.
Limiters. A limiter acts on the real road speed, so a stale or missing value is the worst outcome. Our speed limiter interface page covers how the signal and the limiter fit together.
How does a CAN interface produce a speed pulse?
It turns the network message back into the frequency older equipment expects.
- Listen. The interface joins the CAN network and receives frames without transmitting.
- Pick the message. It filters for the identifier that carries speed on that vehicle.
- Decode. It applies the scaling and offset for that message to get speed.
- Convert. It calculates the output frequency from speed and the pulses per kilometre the receiving device wants.
- Drive the output. It generates the pulse at that frequency, and should fall silent if the messages stop arriving.
That is the job of a speed pulse interface. CAN KONTROL SPEED, built by our group company Intellitec MV, does it for meters, tachographs, limiters and trackers, set up for the vehicle and the device it feeds. Output type and scaling have to match the input of the equipment it connects to, so check that device’s specification.
Frequently Asked Questions
Is a speed pulse the same as CAN speed?
No, though they carry the same information. CAN speed is a digital message on the network, while a speed pulse is an electrical signal whose frequency follows the speed. A CAN interface converts one into the other.
Can I use the OBD port to get speed for a tracker?
Sometimes, but it is the least dependable route. The tracker has to poll for each reading, the vehicle may not answer while asleep, and a secure gateway can block or limit the request. A passive CAN read avoids all three.
Why does my device read a different speed from the dashboard?
The dashboard is allowed to read above true speed, by up to 10 per cent plus 4 km/h under UN Regulation No 39. A device taking raw wheel speed will usually show a lower figure, and a wrong pulses-per-kilometre setting adds its own error.
Does OBD polling drain the battery?
It can. Repeated requests may keep the control units awake after the vehicle is parked, so a device that polls through the night draws current a sleeping vehicle wouldn’t.
Which signal does a speed limiter need?
One that is continuous and current, which in practice means CAN speed or a pulse made from it. A value that appears only when polled isn’t suitable for a device that has to act on every change.
What pulses per kilometre should I set?
Use the figure in the documentation of the device receiving the pulse, and match the interface to it. The number isn’t universal, so there is no safe default.
Sources
- ISO 11898-1: Controller area network (CAN), data link layer and physical signalling, ISO
- SAE J1939 standards collection, SAE International
- SAE J1979: E/E diagnostic test modes, SAE International
- UN Regulation No 39, speedometer and odometer equipment, EUR-Lex
Talk to us about your speed signal
Tell us the vehicle and what the speed feed drives, and our engineers will confirm the right interface. Browse the CAN bus glossary for any term here, or see CAN bus integration for the full range.
- Speak to us about the vehicle and the device
Speak to our team
Questions about vehicle security, tracking or fleet telematics? Our UK team will point you to the right product for your vehicle or fleet.
Related Products
View all products →- CAN bus
- speed signal
- telematics
- tachograph
- speed limiter
Alec J.
Software Engineer at Scorpion Automotive
Alec J., a Software Engineer at Scorpion Automotive in Chorley, covers CAN bus, vehicle electronics and electric vehicles.
Reviewed by James M., Technical Director at Scorpion Automotive