UAS4G5G LTE · CAMERAS & VIDEO

Multiple cameras. Separate streams.

Keep camera controls and network endpoints distinct, while respecting the board’s available processing and USB connections.

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

Which combinations are available?

PlatformProgram workflow
Pi Zero 2 W / Pi 3One compatible CSI-based source
Pi 4 / Pi 5One general USB camera plus a separate compatible CSI / HDMI-to-CSI source
Supported Radxa boardsUSB camera 1 and USB camera 2 where physical connections permit
DJI PocketDedicated camera path; port roles and total workload determine what else can run beside it

Treat simultaneous stream counts as configuration-dependent. Test the actual cameras and resolutions together. Available USB sockets do not by themselves prove that every combination will work.

02

One destination per stream

Two independent video streams must not be sent to the same receiving IP address and UDP port. When two receivers run on the same computer, assign separate ports. On different computers, the same port number can be reused.

StreamExample destinationPurpose
Camera 1Ground-station A · UDP 5604First receiver
Camera 2Ground-station A · UDP 5606Second receiver on the same computer
Alternative camera 2Ground-station B · UDP 5604Receiver on a different computer
03

Route each stream deliberately

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

Image 1 — Radxa: select SEND UDP RTP, apply the receiver IP and port with their own SET buttons, then start H.264/H.265. Image 2 — Raspberry: detect the USB camera, apply its settings and Video Stream IP / Port, then Play. Raspberry has no equivalent RTSP selector in this tab. General Cockpit receiver: 127.0.0.1:8020 on both platforms. An external destination uses the receiving computer’s reachable LAN/VPN IP and its listening UDP port. That redirects the same stream; it does not duplicate it. Cockpit shares the selected Raspberry source / Radxa Camera-1 pipeline. Radxa Camera-2 remains separately controlled even if its picture is directed to Cockpit. Pocket uses its own receiver and panel: Raspberry 8021, Radxa 8023 in the supplied images. Do not confuse these with general camera port 8020. For simultaneous streams use distinct receiver endpoints and confirm each picture separately.

04

Choose which stream appears in Cockpit

Cockpit provides source selection for the sources supported by the board. On Raspberry, Rspi Cam, CSI to HDMI Cam and USB Cam select the corresponding camera path. The USB selection shares its stream with the first USB camera tab.

To change the source shown in Live Video, stop the camera currently feeding the local receiver, select the next source and start it. The other camera can use a different external destination if that simultaneous configuration is supported.

For Radxa USB Camera-2, you can use its dedicated tab to send video to 127.0.0.1:8020 for the local Cockpit view. Stop the previous stream to that endpoint first. Keep controlling that second camera from USB Camera-2; the shared first-camera controls still belong to camera 1.

05

Shared controls are not a second camera

A camera shown in Cockpit and its dedicated tab is not two independent sources. When Cockpit is set to USB Cam, its shared resolution, bitrate and image settings belong to the same first USB camera as the dedicated first-camera tab. The Raspberry CSI/HDMI selectors work with their matching CSI-based source.

A separate channel—such as USB camera 2—keeps its own pipeline and configuration. After changing physical cameras or USB ports, check the detected device in each channel before streaming.

06

Build up the load gradually

  1. Start camera 1 and verify its intended receiver.
  2. Start camera 2 on a different destination endpoint.
  3. Check CPU load, available bandwidth and whether either stream accumulates delay.
  4. Reduce the resolution or bitrate of the affected stream and retest the complete configuration.

Pi 5 uses CPU encoding, so two individually successful streams may overload it when combined. Radxa hardware encoding improves the processing budget but does not remove USB, network or receiver limits.

Program screenshotFull resolution ↗