RockREMOTE UAV OEM

It depends on the device selected. With the RockREMOTE UAV OEM, many small UAVs connect the module directly to the flight controller over UART, while larger RPAS or docking systems use a companion computer to manage packet formatting, logging or routing over IP. The ideal setup depends on how much control logic you want to run off-board.

For airborne use, integrators typically choose a lightweight, low profile Certus antenna mounted externally. The MMCX port supports these flight antennas. The stub antenna included with some developer kits is intended for bench use and is not recommended for flight, especially on SWaP-constrained airframes.

The unit includes pre-drilled mounting points for secure internal installation. Integrators commonly use vibration-resistant standoffs and ensure strain relief on power and RF cabling. Placement inside composite or carbon fuselages should consider antenna positioning (requires a clear view of the sky) and heat dissipation.

The module does not parse, generate or interpret MAVLink. It transports data via UART or IP exactly as received. MAVLink formatting, routing or telemetry shaping must be performed on the autopilot or companion computer.

Yes. The module passes through any custom format over UART or IP. For routine telemetry, many integrators choose IMT because it avoids continuous IP session overhead and provides more predictable, cost efficient message delivery. IP is typically used when working with companion computers or when larger payloads are required.

The module operates from 10-30 V DC and is designed for UAV electrical systems. UAVs with high-current propulsion or noisy ESCs may benefit from additional filtering or power conditioning to ensure clean supply under load.

Cloudloop Device Manager provides message logs, status information and diagnostics. Early testing is typically done using the developer kit interface board to validate wiring, message flow and power behaviour before installing the module inside the airframe.

For most UAV missions, IMT is the more cost efficient choice. It delivers message-based telemetry without the overhead of maintaining an IP session, making it ideal for routine BVLOS updates, position reporting and system health messages.

IP is typically used when working with a companion computer, sending larger or less frequent payloads, or when you need bidirectional IP-based interactions on the ground. Both interfaces are supported, but IMT generally offers predictable costs and simpler integration for flight telemetry.