Home › Insights › CAN, CAN-FD, RS485 or UART: Choosing the Right Radar Interface

CAN, CAN-FD, RS485 or UART: Choosing the Right Radar Interface

Every additional translation layer is a place where engineering hours and failure modes accumulate. Here is how to avoid that.

Launston Engineering•2026-10-30•8 min read

Ask any integrator integrating a radar module for the first time and the same question surfaces: which interface should I specify? CAN, CAN-FD, RS485, UART, Ethernet, IO — all of them appear in radar datasheets, and choosing the wrong one is one of the most common causes of a project slipping a quarter.

The honest answer

The best interface is the one your vehicle controller already speaks, and nothing else. Every additional translation layer — a gateway, a converter, a custom driver — is a place where engineering hours and failure modes accumulate.

InterfaceTypical useStrengthConstraint
CAN 2.0BAutomotive, micromobility, industrial vehiclesUniversally understood by vehicle ECUs; robust differential signalling; arbitration built in1 Mbit/s ceiling — fine for 10–64 targets, tight for point clouds
CAN-FDNewer platforms, higher target countsUp to 8 Mbit/s data phase, larger payloadsNot every ECU supports it; needs a transceiver choice up front
RS485Traffic & industrial, pole-mounted, long cable runsLong reach (up to 1200 m), strong noise immunity, simplePoint-to-point only, no multi-drop arbitration
UART / TTLLow-cost embedded, UAV flight controllersCheapest, lowest latency, trivial to read on an MCUSingle-ended — noise sensitive over long cables; no standardisation
EthernetTraffic & ITS, infrastructure, 4D imagingVery high bandwidth for point clouds; PoE possible; standard toolingHigher power, more expensive; needs network commissioning
IO / Relay / LEDWarning-only modules, ag machinery, low-speed vehiclesZero software; works on any controller with one GPIONo distance or speed information — only a trigger
Rule of thumb: if the target list fits in a classic CAN frame, specify CAN. If it does not, specify CAN-FD or Ethernet — but confirm the host controller supports it before you design the harness.

What Launston ships today

Because we develop the protocol stack in-house, most platforms can be delivered with more than one output. The RBT-7706 forward/rear anti-collision radar is a good example: it is available with TTL, CAN, and high-level output in the same housing, so the same hardware can be evaluated on a bench and then integrated into a vehicle. The T8000 traffic flow radar ships with Ethernet and RS485 side by side because traffic integrators genuinely need both.

Three integration mistakes we see repeatedly

1. Specifying a protocol, then discovering the message cycle is wrong

A radar that outputs 64 targets at 20 Hz over CAN needs a careful frame budget. If the host ECU also has to handle other traffic on the same bus, the radar's frame allocation has to be designed jointly, not decided afterwards. Send us your bus load and target count and we will tell you honestly whether CAN is adequate or you need CAN-FD.

2. Forgetting the ground reference

RS485 and CAN are differential and forgiving. UART is not. On a vehicle with a switching power supply, alternator noise and a long harness, a single-ended UART link without proper filtering will drop frames — intermittently, which is the hardest kind of bug to diagnose. If UART is the only option, specify the filtered variant and add a pull-up.

3. Assuming the radar can output raw point clouds over a low-bandwidth bus

A 4D imaging radar producing 20,000 points per second simply cannot ship that over CAN. There are three legitimate answers: use Ethernet, downsample and cluster on the radar side, or configure the radar to output a compact object list instead of a raw cloud. What does not work is designing the product then discovering the limitation late.

A practical integration checklist

  1. Confirm the host controller's supported protocols, including the transceiver it uses.
  2. Share the bus topology and existing load so frame allocation can be planned.
  3. Agree the message set: which target fields, at what rate, in which frame IDs.
  4. Confirm the power supply and inrush behaviour, and the connector and harness length.
  5. Request a sample and validate on the bench before committing to a moulding tool.
Tell us your interface requirement. Send the protocol, target count, message rate and connector you need. We will confirm feasibility, propose the closest standard model, and flag anything that will not work — before you order.

Frequently asked questions

Can one radar output both CAN and RS485 at the same time?

On several platforms yes, and we can also configure a single physical port to carry either. For the highest-volume custom programmes, specifying both in parallel is usually the cheapest way to cover multiple vehicle variants or two different customers from the same tooling.

Is CAN-FD worth it if I only need 16 targets?

Usually not. Classic CAN comfortably carries 16 tracked targets at 20–50 Hz if the message set is designed properly. CAN-FD earns its cost when you need substantially more targets, higher refresh, or richer per-target data such as classification and confidence.

What about PoE for traffic deployments?

For traffic and ITS installations, Power over Ethernet is a very practical choice because it removes the separate power cable and simplifies field maintenance. We can supply Ethernet-output radar configured for PoE integration. See the traffic radar page for the available configurations.

Do you deliver a documented protocol?

Yes. Every module ships with a protocol specification document covering message IDs, scaling, byte order, update rate and status codes, plus a reference parser you can use for bench validation.

No exact spec match?

We can customize to your detection range, form factor and interface protocol.

Start a custom inquiry