What a CAN bus interface is
Modern vehicles no longer provide most of their information on dedicated wires. Road speed, ignition state, doors, gear, lamps and hundreds of other values travel as messages on the vehicle's CAN networks, shared by dozens of ECUs. Equipment that once read a single wire now needs a device that joins the network correctly and delivers the required values in a form the equipment understands.
That device is the CAN bus interface. Physically, it connects to a vehicle bus through a galvanic tap, a plug-in adapter, a contactless pick-up or an interface provided by the vehicle manufacturer. Electrically, it must respect the bus: a short stub, no extra termination, correct behaviour at every bit rate on the network and no interference with sleep. Functionally, it provides outputs: a speed pulse in pulses per kilometre, digital states such as ignition or doors, or a serial data stream to the host equipment.
- Regulated instruments: taximeters under the Measuring Instruments Directive (MID) and tachographs under the EU tachograph rules, which depend on a correct distance and speed input.
- Fleet and telematics: trips, ignition and usage times, odometer and fuel-related values.
- Special vehicles: emergency, municipal and body-builder equipment that switches on vehicle states.
- Mobility services: shared and rental vehicles that need door, ignition and lock states.
CAN 2.0, OBD-II, J1939 and CAN FD: what actually differs
These four names are often compared as if they were alternatives. They sit on different levels: two are data link protocols, one is a diagnostic standard and one is an application-layer standard for heavy vehicles. A buyer needs to know which of them a product handles, and how well.
Why the diagnostic connector is not a data bus
OBD-II was created to give inspectors and workshops standardised access to emission-related diagnostics. On CAN, ISO 15765-4 defines how diagnostic requests and responses travel, and the standardised content is limited to emission-relevant data; everything else is manufacturer-specific diagnostics, typically UDS to ISO 14229. Since cybersecurity became part of vehicle type approval under UN Regulation No. 155, mandatory for all new vehicles in the EU since July 2024, manufacturers increasingly place the connector behind a gateway that filters, authenticates and limits access.
For a buyer this has three consequences. An OBD-based device works by asking questions, so it adds diagnostic traffic and can keep control units awake. It competes with workshop tools for the same port. And its coverage depends on what each manufacturer chooses to answer through the gateway, today and after the next software release. OBD access remains valuable for diagnostics and short-term use; as the foundation of a permanent or regulated installation it is increasingly fragile. See OBD-II and secure gateways.
Why CAN FD support is not optional in 2026
Approximate figures for an 11-bit identifier, without stuff bits.
CAN FD keeps arbitration at the nominal bit rate, commonly 500 kbit/s in cars, and when the BRS bit is set it transmits the data phase faster, typically at 2 Mbit/s and on some networks at 5 Mbit/s. Payloads grow from 8 to as many as 64 bytes, giving the network room for driver assistance, electrification and security functions.
The critical detail is that compatibility works in one direction only. A classic CAN controller designed before ISO 11898-1:2015 does not understand the FD format. When an FD frame appears, it sees what it takes for errors and transmits error flags, destroying the frame for every node on the bus. Such a device on a CAN FD network is not merely blind; in normal operation it is a source of network faults. ISO 11898-1:2015 introduced a protocol exception behaviour that lets classic controllers tolerate FD frames without disturbing them, but a tolerant device still cannot read them.
How to choose: seven criteria
1. Coverage model
The first question is not ‘is my vehicle supported?’ but ‘how does a vehicle become supported?’ Interfaces differ fundamentally here, and the answer shapes your operations for years.
2. New-model readiness
Fleets renew, taxi operators switch brands and new electric models arrive every quarter. The real cost of a coverage model appears in the gap between a vehicle's launch and the day you can install on it. Ask suppliers for concrete answers: how long their most recent new models took to become supported, whether a request was needed, and who carried the cost. Where the answer is ‘it depends’, plan for waiting.
3. CAN FD support
Insist on full CAN FD capability at the data-phase bit rates used in the vehicles you serve, with transceivers specified for them. A buyer in 2026 who chooses a classic-only interface is choosing to exclude a growing share of new vehicles, and taking a risk with those already in service. Classic CAN vs CAN FD explains the protocol in detail.
4. Outputs that match your equipment
Most instruments take a speed pulse, a digital level or a serial stream. For pulse outputs, check the output stage (open collector or push-pull), the high level (5, 12 or 24 V), the pull-up arrangement and the maximum frequency. The frequency required follows directly from the instrument's k constant:
f = v × k ÷ 3600Worked example. With k = 8,000 pulses/km at 180 km/h, f = 180 × 8,000 ÷ 3,600 = 400 Hz, a period of 2.5 ms. An open-collector output with a 4.7 kΩ pull-up driving 10 nF of cable and input capacitance has a time constant of 47 µs, so each rising edge settles in roughly 100–150 µs, comfortably inside the period. With much higher constants or long, heavily loaded cables, the same pull-up becomes marginal; a lower value speeds the edge at the cost of more current through the output.
5. Companion app and tooling
An interface is installed once and lived with for years. A professional companion app determines how the installation is commissioned, how the installer verifies the result before the vehicle leaves the workshop, and how service partners handle a vehicle that comes back. Look for an app built for authorised installers rather than end users, with clear status information, guided verification and an auditable record of what was done to which device.
6. Installation guidance and electrical behaviour
The best interface becomes a liability when installed badly. Expect documentation covering tap points, stub length, joint methods, power, ground and sleep behaviour, in line with Installation best practices, and ask how the device behaves on the bus:
- A documented quiescent current, and confirmation that the device lets the network sleep.
- No termination on the vehicle side, or termination that is off by default.
- What the device transmits on the vehicle bus, if anything, and how it behaves at bus-off and recovery.
- Operation on 12 V and 24 V systems if you serve both cars and commercial vehicles.
7. Environmental ratings and support model
Vehicle electronics live in a harsh place. Ask for evidence rather than adjectives: test reports against established standards.
Then the support model. Who installs: authorised partners, or anyone with a crimping tool? Who answers when a vehicle behaves unexpectedly, and how fast? Is documentation available in the installer's language, with partners in the countries where your vehicles operate? A support model is only as good as its answer on a Friday afternoon with a vehicle on the lift.
An evaluation procedure in seven steps
- 01List your vehicles
Makes, models, years, bus types, drivetrains, 12 V or 24 V, and the models you expect to add over the next two years.
- 02Define the outputs
Which values each instrument needs, in which electrical form, at which constant or data rate.
- 03Classify the coverage model
For every interface on your shortlist, establish how a vehicle becomes supported and what a new model launch means in days and requests.
- 04Check CAN FD at the right level
Full CAN FD at your vehicles' data-phase bit rates; tolerance alone is not enough.
- 05Review installation and bus behaviour
Documentation, stub, termination, sleep current, bus-off behaviour and supply voltage range.
- 06Demand environmental evidence
Test reports for transients, vibration, temperature, ingress and EMC.
- 07Pilot on real vehicles
Install on a small group including your newest model and an electric vehicle, commission with all four wheels on the ground, and verify sleep behaviour after a full night.
Why Santim SC-1 fits
Measured against these criteria, the decisive questions are coverage and new-model readiness. That is exactly where Santim SC-1 stands apart.
Its companion is SConnect, a professional app for authorised Santim service partners. Discover Santim SC-1.
Is an OBD-II dongle a CAN bus interface?
It connects to a CAN bus, but only to the diagnostic one and only through the services the gateway allows. For permanent installations, especially for regulated instruments, a properly installed interface on the vehicle network is the more robust choice.
Do I need CAN FD if my current vehicles are classic CAN?
Yes, if you will add new vehicles. CAN FD is established on new passenger-car platforms, and an interface bought today will meet them during its service life.
What is the difference between J1939 and the FMS interface?
J1939 is the SAE standard family used by heavy-vehicle networks. The FMS interface is a manufacturer-provided gateway, defined by European truck and bus makers, that exposes a selected set of J1939 data to third-party equipment.
Can one interface serve cars, vans and trucks?
Yes, if it supports classic CAN and CAN FD at the bit rates of all three, runs on 12 V and 24 V and handles both 11-bit and 29-bit identifiers. Check each point explicitly.
Should a CAN bus interface change how the vehicle behaves?
No. Termination, timing, error behaviour and sleep must stay exactly as the manufacturer designed them. That is why installation practice and bus behaviour are selection criteria, not afterthoughts.
