Resources
Robot telemetry radio for mobile ground systems.
Ground robots often start with telemetry as the main requirement, but the real workflow usually includes more than status data alone. CY-2 fits mobile systems that need telemetry, serial device traffic, diagnostics, and operator-side visibility in one compact link.
Where this use case fits
Where it fits.
This guide fits mobile ground systems where the operator needs vehicle state, serial sensor data, and practical access back to the platform during setup or deployment. That can include tracked robots, wheeled rovers, and compact service robots working with embedded controllers and payload devices.
In those systems, telemetry is still central, but the radio often ends up carrying more than telemetry. That is where a robot telemetry radio starts to overlap with video, diagnostics, and IP-based service access.
Typical robot telemetry setup
Typical architecture.
Robot-side installation
Mounted beside controllers, telemetry sources, serial sensors, and payload devices on the robot.
Operator-side console
Connected to the laptop, display, or control interface used during testing and field use.
Expanded data path
Telemetry can sit alongside serial data, diagnostics, and video where the workflow demands it.
Interfaces for robot telemetry workflows
Supported interfaces.
UART matters for many robot telemetry and embedded-control paths, but Ethernet and USB also become important when diagnostics, cameras, or service interfaces need to share the same link.
- UART for telemetry and serial sensors
- Ethernet for diagnostics, compute, and IP payloads
- USB for host-side integration where needed
- Web UI for local status review
Integration examples
Integration examples.
Mobile robot with telemetry, serial sensors, and operator-side diagnostics.
Rover with status data, payload logic, and ground-side visibility.
Field robot where telemetry and video share one practical operator link.
Why CY-2 for robot telemetry workflows
Why CY-2.
CY-2 works well when telemetry is the starting point but the team also wants room for diagnostics, payload traffic, or operator video without rebuilding the communication architecture later.
- Supports telemetry-led ground-robot workflows
- Leaves room for diagnostics, video, and service access
- Works with embedded serial and Ethernet devices
- Useful for operator-side setup and validation
FAQ
Questions buyers ask.
Can CY-2 be used as a robot telemetry radio?
Yes. It can support telemetry-led robot workflows and still carry adjacent serial, video, or IP traffic when needed.
Is it only useful when the robot has a camera?
No. Video is optional. CY-2 is still relevant when telemetry, serial devices, diagnostics, and operator-side access are the main requirements.
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 pageUGV 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 resourceAir-ground data link for UAV and UGV platforms
Air-ground data link for UAV, UGV, and robotic platforms carrying video, telemetry, serial data, and operator-side IP access.
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