UAS4G5G LTE · FLIGHT & TELEMETRY

QGroundControl setup.

Match the telemetry listener and video source to the stream sent by UAS4G5G LTE.

THE CONNECTED FLIGHT PLATFORMv23Raspberry Pi
Radxa ROCK 4D
Radxa ZERO 3W / 3E
01

Keep the addresses and ports separate

SettingValue to enterMeaning
Open the UAS browserhttp://BOARD_VPN_IP:3000/uaslte/Address of the companion computer
UAS telemetry endpointGROUND_STATION_IP + its UDP listener, e.g. 14550Sends MAVLink to the ground computer
UAS video endpointGROUND_STATION_IP + its video listenerSends RTP video to that receiver
Video in local Cockpit127.0.0.1:8020General camera stream stays on the board for browser delivery

Replace the example addresses with real reachable LAN/VPN addresses. A local listening address such as 0.0.0.0 belongs in the receiver; it is not the remote destination to put into UAS.

02

On the UAS side: configure the telemetry destination

Current UAS interface with numbered annotations. Open at full resolution to read the controls; follow the corresponding explanation below.

Raspberry Pi & Radxa — same panel workflow; wiring differs.

1 Start detection if needed. 2 Confirm FC Heartbeat is online; Telemetry ON by itself does not prove a working controller link. 3 Enter receiver IP and listening UDP port in a chosen endpoint row, then SET. Repeat for Endpoint 1/2 if needed. 4 Confirm destination and response. 5 Controls telemetry operation. Stop Autodetect stops discovery; it is different from Telemetry OFF. Erase EndPoint clears only that destination. These endpoints route MAVLink, not video. Use the correct board’s UART pin mapping or USB connection. For parameter read/write, flight modes, aircraft actions and battery display, follow the Cockpit guides.

03

Receive telemetry

  1. Set a UAS MAVLink endpoint to the ground station’s reachable IP and an unused listening UDP port.
  2. In QGroundControl, open Settings → Comm Links. Use the existing UDP link if it matches; otherwise add a UDP link with the chosen local port.
  3. Connect that link and enable telemetry in UAS. Confirm the vehicle and live data.

Official QGroundControl 5.1 Comm Links reference ↗. Menu labels can vary with the installed version.

04

RTP and RTSP are different workflows

The program’s camera IP/port controls describe its configured outgoing stream. Do not substitute an RTSP URL unless an RTSP service and path have actually been configured for that stream. Choosing RTSP in the receiver does not create such a service on the board.

05

Receive video

  1. In UAS, send the camera to the ground computer’s IP and video port; this is separate from the MAVLink endpoint.
  2. Open QGroundControl Settings → Video. Select UDP h.264 or UDP h.265 to match the sender.
  3. Set the UDP listener to the selected port. The documented default is 0.0.0.0:5600; configure UAS to the ground computer’s real IP and port 5600 when using that default.
  4. Start the stream and verify video. Codec support depends on the installed QGC build and platform.

For the Radxa RTSP option, choose RTSP and enter rtsp://BOARD_IP:8554/live for Camera-1 or /live2 for Camera-2. Select SEND TCP RTSP in the corresponding UAS camera panel first.

Official QGroundControl 5.1 video settings ↗.

06

Official receiver documentation

QGroundControl application and video settings ↗

Program screenshotFull resolution ↗