Raspberry family, model-specific video
UAS4G5G LTE is offered for Raspberry Pi boards through the Raspberry image family. The documented camera workflows cover Pi Zero 2 W, Pi 3, Pi 4 and Pi 5. Physical connectors, camera support and performance differ; confirm your exact board and camera combination before building around it.
Pi Zero 2 W and Pi 3 use the program’s single CSI-camera workflow. General USB camera detection in this program is intended for Pi 4 and Pi 5. This is an application support distinction, not a claim that the smaller boards have no USB capability.
Pi 4 and Pi 5 are different video platforms
| Area | Raspberry Pi 4 | Raspberry Pi 5 |
|---|---|---|
| H.264 output | Hardware encoder in the supported pipeline | Software encoder |
| Pocket H.265 output | Not offered | Software; maximum configured live resolution 960 × 540 |
| Pocket camera source | DJI Pocket 1: 1920 × 1080; DJI Pocket 2: 1280 × 720 | Same camera source; output depends on the selected codec |
| General USB camera | One program channel | One program channel |
| CSI / HDMI adapter | Compatible CSI camera or supported HDMI-to-CSI adapter | Compatible camera and Pi 5 cable/adapter configuration required |
Pi 5’s CPU performance does not replace a dedicated encoder. Its Pocket H.265 profile deliberately uses lower resolution and 24 fps to keep the stream usable. H.264 Pocket streaming remains a separate 30 fps configuration.
Use each camera from Cockpit or its tab
In Cockpit, choose Rspi Cam for a compatible CSI sensor, CSI to HDMI Cam for the supported capture adapter, or USB Cam on Pi 4 and Pi 5. Apply stream settings there and use Play to view the selected source beside the flight instruments.
The same CSI/HDMI sources also have the Rpi/HDMI-Camera tab, and the USB stream has USB-Camera. Those tabs let you operate the camera and set its local or external destination. When Cockpit selects that shared source, both panels refer to the same camera configuration.
Pocket cameras use their dedicated Pocket live view and camera/gimbal controls. Source options remain model-dependent; an unsupported input does not become available merely because another board’s interface has it.
Keep the workload realistic
Start with one stream. When adding a second supported source, observe system load and end-to-end delay under the intended operating conditions. Reduce resolution before accepting a stream that accumulates delay. Cooling, power and the input format all influence the result.