UART vs. CAN Bus Displays for Electric Motorcycles and E-Bikes: Which Protocol to Choose

Home›News›UART vs. CAN Bus Displays for Electric Motorcycles and E-Bikes
EV Application Guide
UART vs. CAN Bus Displays for Electric Motorcycles and E-Bikes: Which Protocol to Choose

For an electric motorcycle display, UART is the right choice when one motor controller is the only data source and cost and simplicity matter; CAN bus is the right choice when a battery management system, charger and controller all need to talk, or when the platform will grow. The decision is about vehicle architecture, not about which protocol is "better."

In this guide:

  • What UART and CAN each are, in one paragraph each
  • What an EV dashboard actually needs to show — SOC, voltage, assist level, faults — and where that data lives
  • A decision table for e-bikes, e-scooters and electric motorcycles
  • How ACEWELL has handled both since 2008 and 2015 respectively
In this article
  1. What an EV dashboard has to show, and where the data comes from
  2. UART: one controller, one display
  3. CAN bus: when the vehicle has more than one brain
  4. Decision table
  5. Voltage, wake-up and other things that are not about protocol
  6. How ACEWELL approaches EV displays
  7. FAQ

What an electric motorcycle display has to show, and where the data comes from

A petrol motorcycle dashboard mostly shows what the engine is doing. An electric one has to show what the battery is doing — and the battery has opinions. State of charge (SOC), pack voltage, current draw, temperature, charge status, cell warnings. Add motor controller data (speed, power, assist level, fault codes) and the rider-facing items (trip, odometer, clock, range estimate) and you have a display with three or four data sources instead of one.

That is the whole reason the protocol question exists. On a small e-bike, the motor controller is often the only intelligent device, and it already knows the battery voltage because the battery is plugged into it. One serial link from controller to display covers everything. On an electric motorcycle with a separate battery management system (BMS), a separate charger and sometimes a separate vehicle control unit, the display has to listen to several devices — or one device has to gather everything and forward it.

Definition — the two protocols: UART (Universal Asynchronous Receiver/Transmitter) is a point-to-point serial link — one transmitter, one receiver, a transmit line and a receive line, with a baud rate both sides agree on and a frame format the controller's firmware defines. CAN bus (Controller Area Network) is a multi-node, message-based vehicle bus standardized in ISO 11898: every device on the two-wire bus can send, and messages are identified by priority rather than addressed to a recipient.

ACEWELL's own history mirrors the market's. It delivered its first UART-based electric motorcycle display in 2008, added e-bike applications in 2011, brought CAN 2.0A/2.0B support to its digital meters in 2015, and added LiFePO₄ battery storage monitoring in 2017 — in other words, it has shipped both approaches for over a decade and has no reason to steer a customer toward either.

Building an EV platform and not sure whether the display should be UART or CAN? Send ACEWELL the controller and BMS documentation. The engineering team will tell you which fits.

Contact Our Engineering Team

UART: one controller, one display

If your vehicle has one motor controller and it outputs a serial stream, a UART electric motorcycle display is the straightforward answer. The wiring is minimal, the transceiver hardware is cheap, and — importantly — a huge share of e-bike and e-scooter controllers on the market speak UART natively. The display reads the stream, decodes speed, battery level, assist level and error codes, and shows them.

The catch: there is no "UART standard"

UART defines how bits move, not what they mean. Every controller vendor defines its own frame: which byte is speed, how battery voltage is scaled, what the fault codes are, how often frames are sent, whether the display must send anything back (assist-level selection, headlight on/off, a keep-alive). Two controllers from two vendors are two different integration jobs. If your platform may change controller suppliers over its life, that is a real cost to budget for — the display firmware will need a new decoder each time.

Distance and noise are the other limits. UART is single-ended; it does not have CAN's differential-pair noise immunity. On a compact e-bike or scooter with a short harness, that is rarely a problem. On a larger electric motorcycle with a longer run past a high-current motor cable, it can be.

Where UART fits

Single-controller e-bikes, e-scooters, light electric motorcycles with an integrated controller/BMS, and any product where the display is a cost-sensitive line item and the data set is modest. ACEWELL has supplied UART electric motorcycle display units since 2008 and can adapt to a controller's frame format as part of a semi-customized project.

CAN bus: when the vehicle has more than one brain

A CAN bus electric motorcycle display earns its place the moment a vehicle has a BMS that reports independently of the motor controller — that is where UART starts to strain. Either the controller has to gather BMS data and forward it (adding latency and firmware work on the controller side) or the display needs a second serial port. Add a charger that reports charge state, a vehicle control unit, an ABS module, and the point-to-point model falls apart.

CAN solves this structurally. Every device puts its messages on the one shared bus; the display filters for the ones it needs. The BMS sends state of charge and cell temperatures; the controller sends speed and power; the charger sends charging status. Nobody has to forward anything. Adding a device later means adding a node, not re-wiring the dashboard.

What it costs

A CAN transceiver and controller in the display, termination to manage, a bit rate to match, and — the real cost — a complete, agreed message list (a DBC file, the CAN database format) across every device on the bus. An electric motorcycle display on CAN is only as good as the message definitions behind it. The up-front specification work is heavier than for UART; the ongoing flexibility is far greater.

One bus, two frame formats

Many EV buses mix 11-bit standard frames (CAN 2.0A) from the motor controller with 29-bit extended frames (CAN 2.0B) from a BMS that borrowed its protocol from the commercial-vehicle world. ACEWELL's CAN-capable meters support both formats, so a mixed bus is a configuration task rather than a hardware problem — but it must be documented. The companion article on CAN bus instrument clusters covers the specification checklist in detail.

Decision table

Where each protocol usually lands across the light-EV spectrum. These are patterns, not rules — a premium e-bike can justify CAN, and a cost-engineered motorcycle can run UART.

UART vs. CAN bus for an electric motorcycle display, e-bike display or e-scooter display. General engineering characteristics; verify against your controller and BMS documentation.
CriterionUART displayCAN bus display
Number of data sourcesOne (controller forwards everything)Many (BMS, controller, charger, VCU each speak directly)
WiringTX, RX, power, ground — point to pointTwo-wire shared bus, terminated at both ends
Noise immunityModerate (single-ended); keep runs shortHigh (differential pair)
StandardizationNone — frame format is vendor-specificISO 11898 physical and data-link layer; message content still project-specific
Changing controller supplierDisplay firmware needs a new decoderDisplay needs updated message mapping; bus stays the same
Adding devices laterDifficult — needs forwarding or extra portsAdd a node
Display-side hardware costLowestHigher (transceiver, controller)
Spec effort before quotingFrame format documentFull DBC / message matrix for all nodes
Typical fitE-bikes, e-scooters, light EVs with integrated controllerElectric motorcycles with separate BMS, multi-ECU platforms, fleets
ACEWELL supportSince 2008 (first electric motorcycle UART meter)Since 2015 (CAN 2.0A / 2.0B on digital meters)

If you read only one row: "adding devices later." Platforms live longer than their first spec sheet. If the roadmap includes a smarter BMS, a connected charger or a second model with more electronics, CAN is cheaper over the platform life even when UART is cheaper on day one.

Have the controller's frame document or a draft DBC? ACEWELL's engineers will review it and tell you what maps cleanly, what is missing, and what it would recommend for the display.

Contact Our Engineering Team

Voltage, wake-up and other things that are not about protocol

A few electric motorcycle display requirements get mistaken for protocol questions. They are not, but they belong in the same spec.

  • System voltage. Light EVs run on packs from 36 V to 96 V DC, and the display's power input has to cover the pack's full range including charge and regenerative peaks. ACEWELL's EV meters are built for this 36–96 V DC range; confirm the exact rating per model.
  • State of charge (SOC) display. SOC is a calculated value, not a measurement. Whether it comes from the BMS over CAN or is estimated from voltage over UART changes how accurate the gauge can be. A voltage-estimated SOC on a flat lithium discharge curve is notoriously vague in the middle of the range; a BMS-calculated SOC is far better — one more reason CAN tends to win on bigger packs.
  • Assist level and mode selection. On e-bikes the display often sends as well as receives — the rider's assist level goes back to the controller. That makes the display an active node, which affects both UART (bidirectional frames) and CAN (the display transmits) design.
  • Wake-up and sleep. Does the display wake with the key, with bus activity, or with a dedicated line? Does it need to stay powered to show charging status while the vehicle is off? These decide the power design, not the protocol.
  • Battery storage monitoring. ACEWELL added LiFePO₄ battery energy storage monitoring in 2017; the same data-display discipline applies — voltage, current, SOC, temperature — across a different use case.

How ACEWELL approaches EV displays

ACEWELL's electric vehicle work spans e-bikes and electric motorcycles, and its process does not start with a protocol. It starts with the vehicle architecture. In the semi-customized path, "Customer Product Requirement Definition" is the first step and "Recommendation of Suitable Existing Product" is the second; which communication layer the recommended meter uses — UART, CAN, or the MODBUS, RS485 or non-protocol variants the company also offers — follows from what the vehicle already speaks.

For a fully customized electric motorcycle display, the 14-step process adds industrial design, function definition and user-operation-flow work up front, which is where decisions like "does the SOC show as a percentage, a bar, or a range estimate" get made before any firmware is written. Either way, the display is built on the same SMT, assembly, functional test and waterproof/vibration/reliability test flow as the rest of the range, under IATF 16949.

The Electric Vehicles (EV) applications page lists the current EV-oriented meters, and the OEM/ODM page describes both development paths.

Frequently asked questions

Should an electric motorcycle display use UART or CAN bus?

Use UART when a single motor controller is the only data source and the harness is short — typical of e-bikes and e-scooters. Use CAN bus when a separate BMS, charger or vehicle control unit also needs to report to the display, or when the platform will add electronics over time. The choice follows the vehicle architecture.

Can a UART display show battery state of charge?

Yes, if the motor controller sends it in its serial frame. On many small EVs the controller estimates SOC from pack voltage, which is less accurate in the middle of a lithium discharge curve than a BMS-calculated value. A CAN-connected BMS usually gives a better SOC reading.

Is there a standard UART protocol for e-bike displays?

No. UART defines signaling, not message content; each controller vendor defines its own frame format, baud rate and fault codes. A display must be adapted to each controller's protocol. ACEWELL does this as part of semi-customized projects and has supplied UART electric motorcycle meters since 2008.

What voltage range does an EV display need to support?

Enough to cover the pack's full working range, including charging and regenerative peaks. Light EVs commonly run packs between 36 V and 96 V DC; confirm the specific model's rated input range against your pack before specifying.

Can an electric motorcycle display be switched from UART to CAN later?

Not by firmware alone — CAN needs a transceiver and controller in the hardware. If a later CAN migration is plausible, say so at the feasibility stage; a meter specified with CAN hardware from the start can run UART now and CAN later far more cheaply than a redesign.

Sources

Match the display to the vehicle, not the other way round

Send ACEWELL your controller and BMS documentation and a one-line description of the platform roadmap. The engineering team will recommend UART or CAN for your electric motorcycle display and the meter family to build it on.

 

 2026-10-11