Skip to content 
A ZLYTR20 radar sensor should not be connected directly to LED digits. The correct signal path is ZLYTR20 radar -> RS485 or 3.3V TTL UART -> display controller or microcontroller unit (MCU) -> LED driver -> LED speed display. The radar measures vehicle speed and transmits data; the controller validates that data, applies display rules, and drives the sign.
Use 3.3V Transistor-Transistor Logic Universal Asynchronous Receiver-Transmitter (TTL UART) for a short internal connection, or RS485 when the radar is separated from the controller or operates in a noisier electrical environment.
How Does an LED Radar Speed Sign Work?
An LED radar speed sign combines several functional blocks:
- ZLYTR20 radar sensor: Detects moving vehicles, measures radial speed, filters target information, and sends a speed result.
- Display controller or MCU: Receives the radar data, validates the data frame, selects an acceptable speed, and applies warning and display logic.
- LED driver circuit: Provides the electrical switching or current-control functions needed by the LED panel.
- LED display panel: Presents the measured speed and, when designed into the sign, an overspeed warning.
- Power system and enclosure: Supply the separate loads, protect the electronics, and provide stable radar mounting.
A vehicle enters the detection area, the radar sends a speed result, and the controller illuminates the required digits. It later clears or updates the value according to its programmed timing.
Basic ZLYTR20 Connection Architecture
Approaching Vehicle
|
v
ZLYTR20 24GHz CW Speed Radar
|
| RS485 or 3.3V TTL UART speed data
v
Display Controller / MCU
|
v
LED Driver Circuit
|
v
LED Speed DisplayData and power wiring are separate. The serial link carries information, not LED power. The ZLYTR20 operates from 9–24V DC and draws approximately 50 mA at 12V; 3.3V describes its UART logic level, not its supply voltage.
Choosing RS485 or 3.3V TTL UART
Both interfaces carry speed data, but they solve different physical connection problems.
| Item | 3.3V TTL UART | RS485 |
|---|---|---|
| Best use | Short board-level connection | Longer or exposed equipment connection |
| Typical arrangement | Radar and MCU inside one enclosure | Radar separated from the controller |
| Signal type | Single-ended logic | Differential serial signaling |
| Noise immunity | Lower | Generally higher |
| Host hardware | Compatible 3.3V UART | RS485 transceiver or converter |
| Voltage check | Essential; confirm 3.3V compatibility | Confirm the controller’s RS485 port and wiring convention |
| Wiring | TX, RX if required, and common ground | Differential A/B pair and system grounding as designed |
| Main advantage | Simple, low-cost embedded integration | Better suited to longer and electrically noisy runs |
| Main limitation | Not intended for long outdoor cabling | Requires correct polarity, topology, grounding, and possible termination |
When to Use 3.3V TTL UART
TTL UART suits a radar and controller mounted close together. Connect radar TX to controller RX; connect controller TX to radar RX only when bidirectional configuration is required, and provide a common ground. The host must accept 3.3V logic. A 5V MCU may require level conversion, and TTL must never connect directly to RS232. Keep the cable short and away from high-current wiring.
When to Use RS485
RS485 is preferable when the radar is separated from the controller or the cable faces electrical noise. Use a twisted pair and verify A/B polarity; also evaluate termination, shielding, grounding, topology, and surge protection. A/B labels are not perfectly consistent across vendors. RS485 does not guarantee a fixed distance: performance depends on the cable, baud rate, topology, transceivers, termination, grounding, and environment. PC testing normally requires a USB-to-RS485 converter.
Power Supply, Grounding, and Protection
The LED panel can draw far more current than the radar. Use separately sized power branches and never route LED current through the radar connector. Provide the ZLYTR20 with regulated 9–24V DC and confirm the controller and display requirements independently. Consider branch fusing, reverse-polarity and transient protection, earthing, and weather exposure. Keep switching and LED-current loops away from communication wiring; do not assume protection features that the radar specification does not confirm.
Connecting the Communication Interface
The following diagrams are conceptual. Use the current ZLYTR20 datasheet and communication protocol to confirm the actual connector orientation and terminal assignments before applying power. Never identify a function from wire color alone.
Conceptual RS485 Connection
9-24V DC supply ---> ZLYTR20 power input
ZLYTR20 RS485 A ---> Controller RS485 A*
ZLYTR20 RS485 B ---> Controller RS485 B*
System reference ---> Grounding/reference arrangement defined by the designer
Controller ---> LED driver ---> LED display
*Confirm polarity and labeling in both manufacturers' documents.Conceptual TTL UART Connection
9-24V DC supply ---> ZLYTR20 power input
ZLYTR20 UART TX ---> 3.3V-compatible controller RX
Controller UART TX ---> ZLYTR20 UART RX, if configuration is required
ZLYTR20 GND ---> Controller signal ground
Controller ---> LED driver ---> LED displayBefore power-up, check voltage, polarity, and ground with a meter. Test the radar-controller link before attaching the full LED load.
Configuring Useful Display Logic
The controller turns a valid measurement into a driver-friendly message. Typical settings include:
- Minimum display speed: Prevents very slow movement or nearby activity from activating the sign.
- Speed-limit threshold: Determines when the display changes mode.
- Display and overspeed modes: Define steady display, flashing, or other warning behavior.
- Hold time and refresh rate: Keep the value readable without making updates sluggish.
- Direction selection: Allows approaching-only, departing-only, or both-direction output where supported and properly configured.
- Unit selection: Ensures the radar data and sign use the same unit, such as km/h or mph.
- Invalid-data handling: Rejects partial frames and applies a defined blanking state.
The uploaded ZLYRADAR controller supports adjustable overspeed value, angle compensation, sensitivity, screen-on time, display behavior, and refresh frequency. A third-party controller may differ and must be designed around the ZLYTR20 protocol.
Radar Installation and Alignment Guidelines
Give the ZLYTR20 a clear view of the target lane. Keep metal out of the antenna’s forward field, use a 24GHz-compatible cover, and mount the radar rigidly. Because it measures radial velocity, excessive angular offset can make the reading lower than true road speed; alignment and approved compensation must match the geometry.
The nominal 3 dB beam width is approximately ±20 degrees horizontally and ±8 degrees vertically. Detection also depends on the target, mounting, sensitivity, surroundings, and environment. More than 180 meters is possible under suitable conditions, but verify the required activation distance on site. Avoid unrelated moving targets and test representative vehicles in the intended lane.
Ten-Step Integration Process
- Define the application: lane geometry, vehicles, sign position, units, and warning behavior.
- Confirm radar suitability: range, beam coverage, and 1–240 km/h speed range.
- Choose the interface: short 3.3V TTL UART or equipment-level RS485.
- Review current documents: terminals, serial settings, and frames.
- Design power: size and protect radar, controller, LED, battery, and solar branches.
- Connect communication: verify polarity, voltage, reference ground, routing, and termination.
- Develop the parser: validate frames and extract speed and direction.
- Configure the display: units, threshold, hold, refresh, blanking, and warnings.
- Install and align: provide a clear 24GHz path and rigid mounting.
- Road-test: check representative vehicles, adjacent lanes, sensitivity, and timing.
Common Problems and Troubleshooting
| Symptom | Possible cause | Recommended check |
| No radar data | No power, wrong interface, reversed RS485 A/B, or missing TTL ground | Verify voltage and current first, then interface selection and wiring |
| Garbled serial data | Incorrect baud rate, electrical mismatch, noise, or frame-handling error | Confirm 9600 bps and current protocol; inspect the raw byte stream |
| Display remains blank or zero | Parser rejects frames, direction filter excludes target, or LED control fault | Test radar output separately, then test the LED board with known values |
| Speed changes too rapidly | No hold logic, excessive refresh, or multiple targets | Adjust controller filtering, refresh rate, and target-selection rules |
| Speed is consistently low | Radar beam is not aligned with vehicle travel | Measure the installation angle and correct mechanical alignment or approved compensation |
| Direction is wrong | Plus/minus interpretation or radar orientation is reversed | Compare raw frames for known approaching and departing vehicles |
| RS485 works on the bench but fails outdoors | Cabling, grounding, termination, surge, or electrical noise issue | Inspect topology, twisted pair, shielding strategy, power noise, and protection |
| TTL stops when connected | 3.3V/5V incompatibility, TX/RX error, or missing common ground | Confirm logic thresholds, cross TX/RX correctly, and verify the reference ground |
| Display does not clear | Timeout or vehicle-presence logic is missing | Check the controller’s hold and blanking state machine |
| Adjacent-lane vehicles trigger the sign | Beam placement, sensitivity, or site geometry is unsuitable | Reposition and realign the radar; validate sensitivity with real traffic |
Why ZLYTR20 Fits LED Radar Speed Signs
The ZLYTR20 is a 24GHz continuous-wave radar for LED speed signs, road warnings, and traffic monitoring. It offers RS485 and 3.3V TTL UART, a 1–240 km/h range, and more than 180 meters of detection under suitable conditions. Specified error is within ±1 km/h when target movement aligns with the beam; finished-system performance still depends on installation.
Frequently Asked Questions
Can the ZLYTR20 connect directly to an LED display?
No. It outputs speed data through RS485 or 3.3V TTL UART. A controller must interpret the data, apply warning rules, and operate the LED driver; the serial output cannot drive a large LED panel.
Is RS485 or TTL better for an LED radar speed sign?
Use 3.3V TTL UART for a nearby compatible controller in the same enclosure. Prefer RS485 when the radar is separated or exposed to more electrical noise. Layout, grounding, protection, and host hardware determine the final choice.
Does the ZLYTR20 output the measured speed directly?
Yes. It outputs a speed value in a defined serial frame. The controller must still validate the complete frame, interpret direction and units, apply limits, and decide when to update or clear the display.
How do I connect the 3.3V TTL output to a 5V controller?
Verify the controller’s UART thresholds; a 5V-powered MCU is not automatically 3.3V compatible. If needed, use a suitable bidirectional level converter. Cross TX/RX as required, share a reference ground, and never connect TTL directly to RS232.
Why does the displayed speed jump or change rapidly?
Check for multiple vehicles, adjacent-lane detections, excessive sensitivity, vibration, invalid frame parsing, or missing hold logic. Inspect raw frames first, then alignment and site conditions, before adjusting display timing, direction, and sensitivity.
Can I connect the ZLYTR20 to a computer for testing?
Yes. Use USB-to-RS485 for RS485 or a 3.3V-compatible USB-to-TTL adapter for UART. Confirm the adapter voltage and configure the test software according to the current ZLYTR20 protocol.
Conclusion
The radar measures speed, RS485 or 3.3V TTL UART carries the result, the controller validates it and applies warning logic, and the LED driver controls the display. Choose TTL for short embedded wiring and RS485 for longer or noisier links. Power, parsing, timing, alignment, and road testing are equally important.
Discuss Your LED Radar Speed Sign Project
For integration guidance, send ZLYRADAR your required detection range, lane layout, target vehicle type, radar mounting position, cable length, controller or MCU model, preferred interface, power supply, display size, speed threshold, warning logic, and operating environment.
Zilai Technology (Shenzhen) Co., Ltd. can provide the current ZLYTR20 datasheet, communication protocol, sample evaluation support, integration guidance, and a project-based quotation.
Contact ZLYRADAR at lanbing@zlyradar.com or visit https://www.zlyradar.com/.
