"Which interface does your radar support?" is a question that sounds trivial until you are three weeks into integration and the target frames are not arriving. The interface determines how target data reaches your ECU or flight controller, and getting it wrong costs time you do not have.
The five interfaces we ship
| Interface | Typical use | Speed | Models |
|---|---|---|---|
| CAN 2.0 | Automotive and industrial ECUs, drone flight controllers | 500 kbit/s – 1 Mbit/s | UAV77-O, L7706, L5261, 24-FCW (also UART) |
| CAN-FD | Higher payload, modern vehicle networks | up to 8 Mbit/s data | L7733 passenger-car BSD, adaptive-cruise platform |
| UART | Simple point-to-point, hobby and lightweight controllers | 115200–921600 baud | 24-FCW, L6020 |
| RS485 | Long cable runs, industrial and traffic installations | up to 10 Mbit/s | L5261, T8000 |
| Ethernet | High-bandwidth data, traffic and imaging radar | 100/1000 Mbit/s | T8000 traffic radar, XD70 4D imaging |
How to choose in practice
1. Match what your controller already has
The cheapest integration uses the bus you already run. Most automotive ECUs and industrial controllers have CAN; most drones expose a UART or CAN port on the autopilot. If your platform is CAN-based, specify a CAN variant rather than adding a converter.
2. Consider cable length and noise
UART is fine for short runs inside an enclosure. For a radar mounted tens of metres away — a traffic pole, a harvester — RS485's differential signalling tolerates electrical noise and long cables far better. That is why the T8000 offers RS485 and Ethernet, and the L5261 offers CAN plus RS485.
3. Count your target data
A blind-spot radar reporting a handful of targets fits comfortably in classic CAN. A 4D imaging radar streaming 20,000 points per second needs Ethernet. Match the bus throughput to the data rate or you will bottleneck at the interface.
4. Plan the frame format early
Every module outputs a documented frame: target ID, range, velocity, azimuth, RCS and confidence. Ask for the protocol document at the sample stage and parse it into your stack before you freeze the PCB. We provide sample code and engineering support during this step.
Integration examples
Drone flight controller (UAV77-O, CAN)
The radar publishes a target list at ≥20 Hz; the flight controller reads range, azimuth and closing speed and feeds an obstacle-avoidance behaviour. Frame rate and CAN ID map are supplied in the protocol document.
Truck blind-spot system (L7701 / L7706, CAN)
Side radars detect objects in the blind zone and the ECU drives audible/visual alarms. Forward radar outputs up to 64 tracked targets for FCW.
Traffic speed measurement (T8000, Ethernet + RS485)
Ethernet carries per-vehicle records (speed, lane, timestamp); RS485 provides a robust configuration and control channel over long distances.
Can I change the interface on a custom project?
Often yes. Because we develop the signal processing in-house, interface and output format can be retuned for OEM programmes. See the customisation process or our 12-model product line.
Frequently asked questions
Which interface is easiest for a first prototype?
UART is simplest for bench work; CAN is the better choice if you plan to move to a vehicle or industrial ECU.
Do you provide protocol documents and sample code?
Yes — frame format, CAN ID map and parsing examples are supplied at the sample stage, with engineer support during integration.
Can one radar output both CAN and UART?
Several models do, including the 24-FCW motorcycle radar. Ask for the specific variant when requesting a quote.
How far can RS485 run reliably?
Typically up to 1,200 m at lower baud rates with proper termination — far beyond what UART can manage — which is why industrial and traffic installations use it.