Keep the addresses and ports separate
| Setting | Value to enter | Meaning |
|---|---|---|
| Open the UAS browser | http://BOARD_VPN_IP:3000/uaslte/ | Address of the companion computer |
| UAS telemetry endpoint | GROUND_STATION_IP + its UDP listener, e.g. 14550 | Sends MAVLink to the ground computer |
| UAS video endpoint | GROUND_STATION_IP + its video listener | Sends RTP video to that receiver |
| Video in local Cockpit | 127.0.0.1:8020 | General 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.
On the UAS side: configure the telemetry destination
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.
Connect MAVLink first
- Connect the board and ground computer through the same reachable LAN or VPN.
- In the program’s Fly Controller tab, set a telemetry endpoint to the ground computer’s address and listening UDP port.
- In Mission Planner, select the UDP connection workflow and use that same listening port.
- Enable telemetry in the program and confirm a live heartbeat and changing values.
UDP 14550 is a common example. Use the port configured for your receiver. If two applications on the same computer need separate feeds, give them separate receiving ports.
Video setup in Mission Planner
- Set the camera in UAS to send to the ground computer and your chosen video UDP port. Match the outgoing codec.
- In Mission Planner’s Data screen, right-click the HUD and choose Video → Set GStreamer Source.
- Paste the matching receiver pipeline below. Match its port and RTP payload to the sender, then start the UAS camera.
- Confirm moving video. A working MAVLink connection does not by itself start or route the video stream.
Configure the camera’s destination to the ground computer and its video UDP port. Mission Planner’s Set GStreamer Source workflow accepts a receiver pipeline when the required GStreamer components are available.
These examples assume RTP video, payload type 96 and UDP port 5604. Match those values to the sender. Use the H.264 pipeline for H.264 and the H.265 pipeline for H.265; they are not interchangeable.
H.264 · Mission Planner HUD
udpsrc port=5604 caps="application/x-rtp,media=video,clock-rate=90000,encoding-name=H264,payload=96" ! rtpjitterbuffer latency=100 drop-on-latency=true ! rtph264depay ! h264parse ! avdec_h264 ! queue max-size-buffers=2 max-size-bytes=0 max-size-time=0 leaky=downstream ! videoconvert ! video/x-raw,format=BGRA ! appsink name=outsink sync=false max-buffers=2 drop=trueH.265 · Mission Planner HUD
udpsrc port=5604 caps="application/x-rtp,media=video,clock-rate=90000,encoding-name=H265,payload=96" ! rtpjitterbuffer latency=100 drop-on-latency=true ! rtph265depay ! h265parse ! avdec_h265 ! queue max-size-buffers=2 max-size-bytes=0 max-size-time=0 leaky=downstream ! videoconvert ! video/x-raw,format=BGRA ! appsink name=outsink sync=false max-buffers=2 drop=trueStandalone GStreamer receiver
For a separate video window, run the matching command in a terminal where gst-launch-1.0 is available. The installation path depends on your operating system; it does not have to be a hard-coded C: drive folder.
H.264
gst-launch-1.0 udpsrc port=5604 caps="application/x-rtp,media=video,clock-rate=90000,encoding-name=H264,payload=96" ! rtpjitterbuffer latency=100 drop-on-latency=true ! rtph264depay ! h264parse ! avdec_h264 ! queue max-size-buffers=2 max-size-bytes=0 max-size-time=0 leaky=downstream ! videoconvert ! autovideosink sync=falseH.265
gst-launch-1.0 udpsrc port=5604 caps="application/x-rtp,media=video,clock-rate=90000,encoding-name=H265,payload=96" ! rtpjitterbuffer latency=100 drop-on-latency=true ! rtph265depay ! h265parse ! avdec_h265 ! queue max-size-buffers=2 max-size-bytes=0 max-size-time=0 leaky=downstream ! videoconvert ! autovideosink sync=falseTune buffering, not by guesswork
These examples use a 100 ms RTP jitter buffer as a starting point, not a measured optimum for your link. The bounded queue and bounded HUD sink limit frame accumulation in those receiver stages; they do not bound every buffer in the end-to-end path. Less buffering can reduce delay on a stable path; more buffering can tolerate greater jitter at the cost of delay.
If the receiver cannot decode in real time, buffer tuning alone will not solve it. Lower the workload or use an appropriate hardware decoder supported by that receiving system.
Mission Planner flight-data documentation ↗ · GStreamer jitter-buffer reference ↗