Radio link for UAV, UGV, and robotic platforms
Rebhu Radio CY-2 is a radio link for UAV, UGV, and robotic platforms: carrying video, telemetry, serial data, and IP tunnel traffic.
Read this guideRebhu Radio · CY-2 · Mission Data Link
Built for the link
between vehicle
and operator.
One radio path for video, telemetry, serial data, and IP traffic: between an air unit on the platform and a ground unit on the operator side.
Scroll to begin
New Tool
Check out our new link budget estimator.
Estimate reliable range, link margin, throughput, Fresnel clearance, and horizon limits before you take the radio into the field.
Architecture
Two units. One link.
CY-2 is a two-radio system. An air unit rides on the vehicle, a ground unit sits with the operator. Scroll through to see how the pieces come together.
On the vehicle: the air unit.
Rides on the UAV or UGV. Compact enough for tight payload bays and rugged enough for field conditions.
On the operator side: the ground unit.
Sits with the operator. Connects to the GCS laptop, the display, and any dashboards or APIs you already run.
Between them: one wireless link.
A single radio path covers the air-to-ground gap. No second link to maintain, no protocol bridge in the middle.
Carrying everything at once.
Video, telemetry, serial passthrough, IP tunnel: all riding the same link without splitting your stack across radios.
Traffic
What rides the link.
Four traffic types share the same radio path. Each one fits a different operational need: video for visibility, telemetry for state, serial for legacy devices, IP for everything else.
HD video, continuously.
USB and Ethernet cameras, plus streams from onboard compute: H.264 or H.265, carried as a continuous bitrate without splitting onto a separate radio.
Vehicle state, frame by frame.
MAVLink, custom autopilot frames, navigation data, health information, and command acknowledgements: periodic and reliable.
UART, paired across the link.
Autopilots, payload controllers, sensors, and custom mission devices ride a transparent serial bridge: works as if locally wired.
IP tunnel for everything else.
Dashboards, IP cameras, REST APIs, diagnostics, onboard services: subnet-transparent bridging across the link.
Interfaces
Plug in.
Both ends of the link expose the same connector layout: antennas, Ethernet, UART, USB, and DC power. No asymmetric SKUs, no special cabling rules between the air unit and the ground unit.
Antennas: dual diversity.
Two SMA connectors for the air-ground link. Run with omnis for general operations or directional patches for range-critical missions.
Ethernet: for everything IP.
RJ-45 gigabit. Plug in IP cameras, onboard compute, mission dashboards, and the operator-side GCS laptop on the other end.
UART: paired serial.
A pinned header connects autopilots, payload controllers, and serial sensors. The matching port on the ground unit acts as a transparent extension.
USB and power.
Type-C for USB cameras and peripherals; DC in for vehicle power. Both ends use the same connector layout: no asymmetric SKUs to track.
Interfaces
Antennas
Dual SMA
Ethernet
RJ-45
UART
Pinned header
USB + Power
Type-C / DC in
Explore by Need
Explore by platform and workflow.
Start with the operating context you actually care about: broad mixed-platform use, UAV integration, or ground-robot and rover workflows.
UAV radio link for video, telemetry, and IP data
UAV radio link for camera video, telemetry, UART payload data, and IP traffic: between an air unit and a ground unit.
Read this guideUGV radio link for robots, rovers, and ground vehicles
UGV radio link for robot and rover platforms carrying telemetry, serial payload data, video, and IP tunnel traffic.
Read this guideResources
More deployment guides, comparisons, and workflow references
Browse the full resource library for UAV, UGV, telemetry, video, Ethernet, and IP tunnel topics.
Read moreNext Step