CAN Bus Instrument Clusters for Motorcycles & EVs: How They Work and What to Specify
A motorcycle CAN bus instrument cluster is a display that reads speed, RPM, gear, temperature and warning states as digital messages from the vehicle's ECU over a two-wire Controller Area Network (CAN), instead of from individual sensor wires. To specify one, you need the protocol version, the message list (DBC), the bit rate, and the fallback behavior when a message goes missing.
What this guide covers:
- How CAN 2.0A and CAN 2.0B actually move data to a dashboard
- The seven items an OEM must put in a cluster spec before quoting
- CAN vs. UART vs. analog inputs — a decision table
- How ACEWELL handles protocol mapping inside its OEM/ODM process
In this article
Why dashboards moved to CAN
Picture a mid-size motorcycle from 2005. Behind the speedometer there is a harness with maybe fourteen wires: one from the speed sensor, one from the tachometer pickup, one per indicator lamp, a temperature signal, fuel level, high beam, neutral. Every new feature meant another wire, another connector pin, another thing to corrode. Nobody liked it, but it worked.
Then the engine got an engine control unit (ECU), and the ECU already knew all of those values. Running them a second time as separate analog signals to the dashboard started to look wasteful. CAN fixed that. One twisted pair carries every signal the ECU has, and the cluster simply listens for the messages it needs.
For an OEM, the shift matters in two ways. First, the harness gets simpler and cheaper. Second — and this is the part that trips up newcomers — the dashboard is no longer a "dumb gauge." It is a network node with firmware, and that firmware has to agree with your ECU on exactly what each message means. Get that agreement wrong and you have a beautiful display showing the wrong gear.
ACEWELL started adding CAN 2.0A and 2.0B support to its digital meters in 2015, after years of UART-based displays for electric motorcycles. The reason was the same one every manufacturer eventually hits: customers' ECUs were already talking CAN, and the dashboard needed to join the conversation. Since then the motorcycle CAN bus instrument cluster has gone from option to default on most new platforms.
Already have an ECU message list and need a display that speaks it? ACEWELL reviews communication requirements at the feasibility-evaluation stage, before any tooling is cut.
Contact Our Engineering TeamHow a motorcycle CAN bus instrument cluster works
Here is the sequence, stripped of jargon:
- The ECU broadcasts. Several times a second it puts frames on the bus: engine speed, vehicle speed, coolant temperature, fault codes. Each frame has an identifier and up to 8 bytes of data in classic CAN.
- The cluster filters. Its CAN controller is configured to accept only the identifiers it cares about and ignore the rest — the ABS module and the immobilizer are also talking, and the dashboard does not need to hear them.
- Firmware decodes. A message is just bytes. The firmware knows, for example, that bytes 2–3 of identifier 0x1A0 are engine speed in 0.25 RPM steps. That knowledge comes from your DBC file (the CAN database format) or signal matrix.
- The display renders. The decoded value drives the needle, the liquid-crystal display (LCD) digits, the thin-film-transistor (TFT) graphic or the warning icon. On a needle-plus-LCD hybrid meter, the same decoded value can drive both the needle and a digital readout.
- Timeouts are handled. If an expected message stops arriving, the cluster has to decide: hold the last value, blank the field, or show a warning. This is a spec decision, not a default.
Two physical details every OEM should know. The bus is a differential pair (CAN_H and CAN_L), which is why it tolerates the electrical noise of an ignition system far better than single-ended analog signals. And the bus needs termination resistors — typically 120 Ω at each physical end. If the dashboard sits at one end of your harness, you have to decide whether the termination lives inside the meter or in the harness. Specify it. Unterminated or double-terminated buses are a classic cause of "it worked on the bench but not on the bike."
CAN 2.0A vs. CAN 2.0B — which one do you have?
The difference is the identifier length. CAN 2.0A uses an 11-bit identifier (2,048 possible message IDs). CAN 2.0B adds a 29-bit "extended" identifier, which is what SAE J1939 — common on commercial and agricultural vehicles — is built on. Most motorcycle ECUs use 11-bit standard frames; many EV battery management systems and anything borrowed from the truck world use 29-bit.
Why it matters for the cluster: a controller configured for 2.0A only will not see 29-bit frames at all. Not "see them wrong" — not see them. ACEWELL's CAN-capable meters handle both 2.0A and 2.0B, so the question becomes one of configuration rather than hardware, but your spec still has to say which format each message uses. Mixed buses, where the ECU sends standard frames and the BMS sends extended ones, are common on electric scooters and perfectly workable as long as they are documented.
A quick aside on bit rate: 250 kbit/s and 500 kbit/s are the two values that turn up most often in powersports and light-EV platforms. The display must match the bus exactly; there is no auto-negotiation in classic CAN. Put the number in the spec.
What to put in the spec
When a project arrives at any cluster supplier with "we need a CAN dashboard" and nothing else, the first weeks go into asking questions. Here is the list that lets you skip that. Send these seven items for your motorcycle CAN bus instrument cluster and the feasibility evaluation can start immediately.
1. Protocol version and bit rate
CAN 2.0A, 2.0B, or both. 125 / 250 / 500 kbit/s or 1 Mbit/s. If a CAN FD bus is involved, say so — classic CAN controllers cannot read FD frames.
2. The message list (DBC or signal matrix)
For every signal the display must show: identifier, start bit, length, byte order, scale factor, offset, unit, valid range, and transmit period. A DBC file is the industry format; a spreadsheet works if it is complete. Incomplete signal definitions are the single biggest cause of schedule slips in cluster projects.
3. Signals the cluster must transmit
Many clusters are listen-only. Some must send — odometer value back to the ECU, trip reset events, a "cluster alive" heartbeat, or a user menu selection. If the dashboard transmits, the ECU side has to be ready for it.
4. Timeout and fault behavior
For each signal: what happens when it is late or missing? Blank the field, freeze the value, show a dashed line, light a warning. For safety-relevant items such as speed, regulators and your own legal team will have opinions.
5. Mixed inputs
Real motorcycles are rarely 100 % CAN. Fuel level may still be a resistive sender; turn signals may still be hard-wired lamps. List every non-CAN input the cluster must accept, so the hardware is built with the right input channels from the start.
6. Termination and wake-up
Does the meter terminate the bus? Does it wake on ignition, on bus activity, or on a dedicated line? Does it need to stay awake after key-off to save odometer data?
7. Diagnostics
Do you need Unified Diagnostic Services (UDS) or a proprietary diagnostic channel over CAN for end-of-line programming, VIN writing or odometer initialization? This affects firmware scope more than most OEMs expect.
One more thing, because it comes up on nearly every project: if your platform might ship in regions or variants that use MODBUS or RS485 instead of CAN — fleet vehicles and some industrial platforms do — mention it at the start. ACEWELL offers MODBUS, RS485 and non-protocol variants of its communication layer, but the decision is far cheaper at the concept stage than after sample validation.
CAN vs. UART vs. analog: comparison table
Three ways to get data into a motorcycle CAN bus instrument cluster — or its UART and analog cousins. None is "best"; each fits a different vehicle architecture.
| Criterion | CAN bus (2.0A / 2.0B) | UART (serial) | Analog / direct sensor |
|---|---|---|---|
| Wiring | One twisted pair shared by all nodes | Point-to-point, typically 2–3 wires | One or more wires per signal |
| Noise immunity | High (differential signaling) | Moderate; distance-limited | Low to moderate; depends on shielding |
| Multiple nodes | Yes — ECU, BMS, ABS, dash on one bus | No — one controller to one display | Not applicable |
| Data richness | Any value the ECU has, plus fault codes | Whatever the controller firmware sends | Only what has a dedicated sensor |
| Typical use | Modern ICE motorcycles, EVs with BMS, agricultural and specialty vehicles | E-scooters and e-bikes with a single motor controller | Retrofit, classic bikes, simple ATVs |
| Spec effort | Highest — needs a complete DBC | Medium — needs the frame format | Lowest — needs sensor type and range |
| ACEWELL support | Since 2015 on digital meters; 2.0A and 2.0B | Since 2008 for electric motorcycles | Non-protocol (direct sensor) variants offered |
The honest guidance: if your ECU already speaks CAN, use it. If you are building a small EV around a single motor controller that outputs UART, UART is simpler and cheaper and there is no reason to add a CAN transceiver you will not use. If you are retrofitting or building something minimal, analog still works. The mistake is choosing the interface before you know what the rest of the vehicle speaks.
Not sure whether your platform should be CAN, UART or mixed? Send ACEWELL the ECU documentation you have. The engineering team will tell you what it can map, what is missing, and what it would recommend.
Contact Our Engineering TeamHow ACEWELL maps your protocol
Protocol work does not happen at the end of a project. In ACEWELL's fully customized OEM/ODM process, the second step after "Customer Concept" is "Feasibility Evaluation (Discussion & Technical Suggestions)" — and the CAN message list belongs in that review. The company describes its approach as "aligning with client vehicle architectures and regulations from the earliest stages," with an in-house team covering mechanical design, electronic circuitry and firmware development. Communication protocols are explicitly part of what it customizes, alongside the user interface and styling.
In practice, a CAN cluster project at any capable supplier runs roughly like this (the labels below are generic, not ACEWELL's formal step names):
- Message review. Your DBC or signal matrix is checked for completeness: missing scale factors, undefined timeouts, conflicting identifiers.
- Display mapping. Each signal is assigned to a display element — digits, bar graph, icon, needle — and the behavior on fault is agreed.
- Firmware build and bench test. The cluster is exercised against a CAN simulator that replays your messages, including the ugly cases: bus-off, late frames, out-of-range values.
- Sample verification on the vehicle. This is where termination, wake-up and electrical noise get tested for real, on your harness.
- Production engineering. End-of-line configuration — which protocol variant, which bit rate — is locked into the manufacturing process so every unit ships with the right settings.
For a semi-customized project, where an existing ACEWELL meter is adapted to your ECU, the steps compress: the hardware is proven, and the work is mainly firmware mapping and validation. For a fully customized cluster — a new housing, a new TFT layout, a new connector — the same CAN work sits inside the longer 14-step program described on the OEM/ODM page.
Either way, the dashboards go through the same production flow: SMT lines, assembly and functional test, waterproof, vibration and reliability testing, final inspection, and a production traceability and quality management system. ACEWELL has held IATF 16949 certification since upgrading from ISO/TS 16949 in 2018, and ships to customers in more than 70 countries — which is relevant here because configuration control of this kind is exactly what an automotive quality system exists to govern.
Frequently asked questions
What is a motorcycle CAN bus instrument cluster?
It is a dashboard that receives speed, RPM, temperature, gear position, warnings and other values as digital CAN messages from the vehicle's ECU over a shared two-wire bus, decodes them in firmware, and shows them on an LCD, TFT or hybrid needle-and-digital display — instead of reading each value from its own sensor wire.
Can a CAN bus instrument cluster also read analog sensors?
Yes. Most real vehicles mix the two. A CAN cluster typically still accepts direct inputs such as a resistive fuel sender, indicator lamp signals or a hard-wired speed sensor. List every non-CAN input in your spec so the hardware is built with the right input channels.
What is the difference between CAN 2.0A and CAN 2.0B for a dashboard?
CAN 2.0A uses 11-bit message identifiers; CAN 2.0B adds 29-bit extended identifiers, which SAE J1939 and many EV battery systems rely on. A cluster that supports 2.0B reads both formats. One that supports only 2.0A will not see extended frames at all. ACEWELL's CAN-capable meters support both.
What do I need to send a supplier to get a motorcycle CAN bus instrument cluster quoted?
At minimum: the CAN version and bit rate, a complete message list (DBC or signal matrix with identifier, start bit, length, scale, offset, unit and period), any messages the cluster must transmit, the required behavior when a signal times out, and a list of any non-CAN inputs. With those, a feasibility evaluation can begin immediately.
Can the same instrument cluster be switched to MODBUS or RS485 later?
Often, yes — ACEWELL offers MODBUS, RS485 and non-protocol variants of its communication layer — but the decision should be made at the concept or feasibility stage, because it affects transceiver hardware and firmware scope. Changing protocol after sample validation means repeating validation.
Sources
- ISO 11898-1:2024, Road vehicles — Controller area network (CAN) — Part 1: Data link layer and physical coding sublayer. iso.org/standard/86384.html
- ACEWELL International Co., Ltd., OEM/ODM Development & Manufacturing and About ACEWELL (company milestones, protocol support dates).
Start your motorcycle CAN bus instrument cluster project
Send ACEWELL your ECU message list and vehicle architecture. The engineering team will come back with a feasibility evaluation and technical suggestions — step 2 of the process, at a company founded in 2003 whose instruments now ship to customers in 70+ countries.