Resources
Drone telemetry radio with UART and IP support.
Telemetry is often the first requirement teams mention, but in real drone systems it is rarely the only thing that needs to move. CY-2 fits cases where telemetry stays central while video, serial payload traffic, or operator-side access also matter.
Where this use case fits
Where it fits.
This guide fits projects where the core concern is telemetry: vehicle state, autopilot communication, navigation data, health signals, and serial payload workflows. In those programs, UART support matters because many autopilot and embedded control paths still rely on serial interfaces.
At the same time, the same aircraft may need to support camera transport or low-rate IP access. That is where a telemetry-led evaluation starts to overlap with a broader drone data-link workflow.
Typical telemetry-focused setup
Typical architecture.
Autopilot-side UART
The air unit sits beside autopilot telemetry and serial payload controllers.
Ground-side access
The operator side connects to the telemetry display, laptop, or control application.
Expanded support
The same link can also support camera video or IP-based services when needed.
Interfaces for telemetry workflows
Supported interfaces.
The key interface here is UART, but the platform often benefits from having Ethernet and USB available alongside it for related payload or ground-side workflows.
- UART for autopilot and serial telemetry
- Ethernet for IP payloads or compute
- USB for host-side camera or service access
- Web UI for local monitoring
Integration examples
Integration examples.
Drone carrying autopilot telemetry and ground-side status monitoring.
Aircraft with serial payload control plus operator video access.
Embedded flight platform where telemetry and diagnostics share the same air-ground link.
Why CY-2 for telemetry-led integration
Why CY-2.
CY-2 works well when telemetry is the anchor requirement, but the integration team does not want to paint itself into a corner if video, payload, or IP access needs grow later in the same platform.
- UART-friendly for autopilot and serial devices
- Can carry more than telemetry alone
- Ground-side visibility for test and validation
- Useful bridge between control and payload workflows
FAQ
Questions buyers ask.
Can CY-2 be used as a drone telemetry radio?
Yes. It supports UART-based telemetry workflows and is suitable where telemetry is a core requirement.
Does it only support serial telemetry?
No. It can also support video transport and IP tunnel traffic in the same radio architecture.
Related Resources
Continue exploring.
Start with the main radio-link page
See how CY-2 fits mixed video, telemetry, serial, and IP workflows across platforms.
Read the radio-link guideReview the product features
See specifications, interfaces, deployment model, and monitoring in one place.
Open the features pageDrone data link for video, telemetry, and IP tunnel traffic
Drone data link for moving video, telemetry, UART serial data, and IP tunnel traffic between the aircraft and the ground side.
Read this resourceUAV 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 resourceEthernet and UART radio link for embedded platforms
Ethernet and UART radio link for embedded platforms needing IP device access, autopilot telemetry, serial payload transport, and operator-side visibility.
Read this resourceTalk to Rebhu about your platform
Share your traffic types, interfaces, and operator-side requirements.
Start a technical discussion