–

 
 
  • Mission Planner send telemetry and video:
     

   — With Uas4g5gLte, you can send both telemetry and video to one or multiple ground stations. The telemetry part is quite easy to use and does not involve any issues: the flight controller is detected automatically, and to send telemetry you only need to set the correct IP and port of the ground station.
   — Telemetry can be sent simultaneously to up to three ground stations. It’s recommended to use different IP addresses (when you have multiple devices). If you receive telemetry on the same device (same IP), then use different ports for each connection so they don’t conflict.

  • Sending the video stream to Mission Planner in H.264 and H.265:

    — Regarding receiving the video stream in Mission Planner, I have some very important notes to start with: you can receive the video stream in Mission Planner in both H.264 and H.265, with one condition—you must use different receiving pipelines in Mission Planner. In the video, I showed very clearly how to set these pipelines, so please watch it.
    — However, in my personal opinion, you should not use video reception in the Mission Planner HUD because the quality will not be very good. It will be acceptable, but that’s all. The best option is to install GStreamer and use its native reception with the command-line player. I will explain this option in another video tutorial below, in the GStreamer Video Reception section.
    — If you still want to use reception in the Mission Planner HUD, I am leaving below the pipelines for both H.264 and H.265. To set them, follow the instructions from the video above.

    — H264 pipeline video reception in Mission Planner HUD:

udpsrc port=5604 caps="application/x-rtp, media=video, clock-rate=90000, encoding-name=H264, payload=96" ! rtpjitterbuffer latency=200 ! rtph264depay ! h264parse ! avdec_h264 ! queue max-size-buffers=30 leaky=2 ! videoconvert ! video/x-raw,format=BGRA ! appsink name=outsink sync=false

   — H265 pipeline video reception in Mission Planner HUD:

udpsrc port=5604 caps="application/x-rtp, media=video, clock-rate=90000, encoding-name=H265, payload=96" ! rtpjitterbuffer latency=200 ! rtph265depay ! h265parse ! avdec_h265 ! queue max-size-buffers=30 leaky=2 ! videoconvert ! video/x-raw,format=BGRA ! appsink name=outsink sync=false

If you use a different port, change 5604 to the port you are using. You can do some tests by changing the value of rtpjitterbuffer latency=200, trying other values like 50, 150, 250, etc., depending on what works best for you. A value between 100 and 200 is generally a good choice.

  • Video reception method using GStreamer (Best Option for quality and latency).

  • GStreamer video reception:

    — In the video, I showed how to receive video using the native GStreamer method. You need to download the installer from the GStreamer website, in the Download section, and install the package for Windows (or your operating system). For the .bat file I showed in the video to work, it’s important to install GStreamer in C:/gstreamer—choose exactly this folder as in the video. If you install it somewhere else, edit the .bat files with the new location.

If you choose to start it from the command line, or if you need the receiving pipelines for the stream, I will post them below for both H.264 and H.265.

  • Starting pipelines from the command line.

   — Reception pipeline gstreamer for H264:

gst-launch-1.0 -v udpsrc port=5604 buffer-size=3145728 caps="application/x-rtp,media=video,clock-rate=90000,encoding-name=H264,payload=96" ! rtpjitterbuffer latency=200 ! rtph264depay ! h264parse ! avdec_h264 ! queue max-size-buffers=30 leaky=2 ! videoconvert ! autovideosink sync=false

   — Reception pipeline gstreamer for H265:

gst-launch-1.0 -v udpsrc port=5604 buffer-size=3145728 caps="application/x-rtp,media=video,clock-rate=90000,encoding-name=H265,payload=96" ! rtpjitterbuffer latency=200 ! rtph265depay ! h265parse ! avdec_h265 ! queue max-size-buffers=30 leaky=2 ! videoconvert ! autovideosink sync=false

NOTE: If you use different ports, change the port number in the pipeline.

   — I will post below the contents of the .bat files for both H.264 and H.265. All you have to do is copy the content into a Notepad file, save it, and change the file extension from .txt to .bat. This way, anytime you simply double-click the .bat file, the video will start—provided you have GStreamer installed in the location shown in the video, namely C:/gstreamer. This applies only to Windows users.

   — Contents of the h264.bat file:

@echo off
REM Uas4g5gLte - GStreamer H264 Receiver (UDP 5604)
cd /d C:/gstreamer/bin

gst-launch-1.0 -v ^
udpsrc port=5604 buffer-size=3145728 caps="application/x-rtp,media=video,clock-rate=90000,encoding-name=H264,payload=96" ^
! rtpjitterbuffer latency=50 ^
! rtph264depay ^
! h264parse ^
! avdec_h264 ^
! queue max-size-buffers=30 leaky=2 ^
! videoconvert ^
! autovideosink sync=false

pause
@echo off
REM Uas4g5gLte - GStreamer H265 Receiver (UDP 5604)
cd /d C:/gstreamer/bin

gst-launch-1.0 -v ^
udpsrc port=5604 buffer-size=3145728 caps="application/x-rtp,media=video,clock-rate=90000,encoding-name=H265,payload=96" ^
! rtpjitterbuffer latency=200 ^
! rtph265depay ^
! h265parse ^
! avdec_h265 ^
! queue max-size-buffers=30 leaky=2 ^
! videoconvert ^
! autovideosink sync=false

pause

    — Important note: You can change certain things inside the file, such as the port, latency, etc., by editing it, but in general you have no reason to change anything except the port—and only if you use a port other than 5604. You can also change the path to the GStreamer directory if you installed it in a different location than the recommended one—just change the path here: C:gstreamerbin