v23 for Raspberry Pi — UAS4G5G LTE

What is new in v23

Current production image: v23l. This channel describes the current release and replaces the old v20 instructions.

What is new and improved

DJI Osmo Pocket 1 and Pocket 2 integration, with model detection, live video and camera/gimbal controls.
A redesigned dark interface with clearer, raised buttons, selected states, action displays and consistent layouts across tabs.
Improved USB-camera format selection, video buffering/packetization and supported camera reconnection workflows.
More reliable playback recovery and camera status/control feedback, including shared USB Camera-1 and Cockpit controls.
An included trial, started by the user from the activation screen.
Signed updates from the Update tab: supported routine releases no longer require rewriting the SD card.

The notes below explain the actual platform limits and the full workflow. The same interface does not mean every board has the same video hardware.

Raspberry models and video capabilities

Use the Raspberry image. Camera options are selected for the detected Pi model.

Pi 4

General USB camera, supported Raspberry CSI camera / HDMI-to-CSI workflow and DJI Pocket 1/2.
H.264 hardware encoding. Supported H.264 inputs use hardware decoding in the optimized Pi 4 paths; other formats depend on available decoders.
Pocket video is H.264 only; the H.265 control is unavailable.

Pi 5

General USB camera, supported CSI/HDMI-to-CSI workflow and DJI Pocket 1/2.
Video encoding runs in software. The dedicated Pocket module offers H.264 and H.265 with different output limits; this does not add H.265 to every USB/CSI workflow.

Pi Zero 2 W / Pi 3

Retain the more limited, single-stream CSI/HDMI-to-CSI workflow.
The current general USB-camera and Pocket workflows described for Pi 4/5 are not provided on these models.

Use the choices shown for the detected board. See Raspberry CSI / HDMI and USB Camera 1 for the camera-specific controls.

See the current Pocket controls

Wait for phone mode AND the detected camera name first. Then follow 1 → 2 → 3, use 4 when reinitialization is required, and 5 to start/stop the live picture. Raspberry Pocket receiver: 127.0.0.1:8021, separate from the general Cockpit receiver. Pi 4: H.264; Pocket 1 up to real 1080p (900p also available), Pocket 2 up to native 720p. Pi 5: H.264 up to 1080p/30 for Pocket 1 or 720p/30 for Pocket 2. H.265 for either camera is limited to 540p/24 and lower resolutions at 24 fps. The screenshot shows Pi 4, where H.265 is unavailable. Use the menu enabled for the detected board/camera. Live bitrate includes 0.25 Mb/s.

DJI Osmo Pocket 1 and Pocket 2

Use the shared Dji Pocket 2 & 1 tab. Connect the camera through the configured USB data/phone-mode path, confirm the detected model and set codec, live resolution, bitrate and destination before PLAY.

Pi 4 — hardware H.264 path

Pocket 1: real native 1080p is available, with 900p, 720p and lower output choices.
Pocket 2: native 720p maximum; no 1080p upscale option.
Hardware H.264 decode/encode is used in the supported Pocket path, with hardware resizing when required.

Pi 5 — software encoding

H.264: Pocket 1 up to 1080p at 30 fps; Pocket 2 up to 720p at 30 fps.
H.265: either Pocket camera up to 540p at 24 fps. Lower H.265 modes also use 24 fps.
Codec/resolution menus follow the detected board and camera.

Both camera workflows include live bitrate choices down to 0.25 Mb/s, stream PLAY/STOP and supported gimbal/camera controls. Recording resolution/FPS controls refer to camera recording, not the transmitted live picture. Pocket 1 exposes fewer camera functions than Pocket 2. Automatic subject tracking and adaptive bitrate are not enabled features of this release. Illustrated Pocket guide: DJI Pocket 1 and 2.

Cameras, destinations and lower-latency video

USB camera detection: the current detector examines advertised formats/resolutions/frame rates, then selects a suitable board-specific pipeline. General USB output is capped at 1080p and 30 fps; a camera that supplies fewer frames cannot provide additional real frames. Hardware processing is preferred where supported.

Cockpit and the camera tabs operate the same source. When Cockpit is set to USB Cam, it shares the first USB camera’s settings/pipeline with Usb-Camera. CSI/HDMI-to-CSI controls belong to their selected source. The action displays show requested changes, detection and stream settings.

Local or external destination

Cockpit Play selects the local browser receiver. General camera streams use 127.0.0.1:8020 for that receiver.
The dedicated camera tab can send the stream to another reachable receiver IP/port. Redirecting one stream is not creating a second copy.
Pocket uses its own live-view receiver and controls.

Multicamera: Pi 4/5 can use supported separate sources such as CSI or HDMI-to-CSI plus USB, within CPU/USB/network limits. Use distinct receivers/ports. CSI camera and HDMI-to-CSI are alternative modes of that CSI input.

Video paths were refined to reduce avoidable buffering and packet overhead for mobile links. Bitrate is manually selected; actual network traffic also includes protocol/VPN overhead. Choose a sustainable uplink and compatible receiver. Guides: Video destinations · USB Camera 1.

Flight workspace and MAVLink

Cockpit brings the live picture, HUD, map and controller tools together.

HUD: attitude, heading, air/ground speed, GPS, altitude, battery and efficiency/statistics. Roll, pitch and compass animation smooth the display between incoming messages; this does not create extra telemetry measurements.
Navigation map with aircraft position, zoom/layers and fullscreen.
Video fullscreen and browser Picture-in-Picture where supported.
Read/search flight-controller parameters, set values and confirm the reply; change supported flight modes and send supported aircraft actions.
Battery type/cell-count display selections are retained after restart. These settings do not configure the FC battery monitor.

Fly Controller tab

Discover a supported ArduPlane controller over USB or the board’s configured telemetry UART. Check the heartbeat, then configure up to three MAVLink destination slots, each with its own receiver IP/UDP port. Video destinations are separate.

Use controller acknowledgement and live data to confirm changes. Ground-test modes, actions and parameter changes with the aircraft secured. Guides: Cockpit · Flight controller.

System, connectivity and equipment controls

Dashboard: CPU/RAM/temperature, board information, uptime, network/MAVLink state, video/telemetry destinations and Autocast video/telemetry controls.

UAS Settings: Wi-Fi scan/client setup, hotspot, Wi-Fi disable, ping, internet/bandwidth/MAVLink tests, restart and shutdown. ZeroTier and Tailscale have connection/status controls and a shared console. A VPN login alone does not prove video or telemetry is reaching its receiver.

Modem: HiLink or Stick workflow, with APN/credentials where required. Supported Brovi reconnection handling has been improved. Compatibility still depends on the actual modem, firmware, USB driver and carrier.

Relay: four GPIO-backed ON/OFF channels and a separate timed Reset pulse. Indicators follow reported output state; boot initializes the configured outputs LOW. Physical relay activation depends on the connected interface and board-specific wiring.

Guides: Trial and activation · UAS Settings · Modem setup · Relay. VPN tutorials: Tailscale · ZeroTier.

Included trial and local activation

Choose when to try it. Press Trial UAS4g5gLTE on the activation screen to start the included 15-minute, one-use trial. Opening the interface or booting the board does not start it. Expiry returns to activation; restarting the board ends the trial and does not grant another session.

Buy and activate whenever you are ready. Send the displayed Device ID privately to Julliano, enter the matching UAS license and activate. Allow the board to restart. Permanent activation remains available before or after the trial.

The main UAS license is lifetime, board-bound and has no subscription. Validation runs locally; UAS does not need an activation server to validate it. Remote internet operation, VPN services and updates have their own network requirements.

Pocket 1 and Pocket 2 are separately licensed camera modules with their own validity dates. A license for one camera model does not activate the other. A matching Pocket-model license works on Raspberry and Radxa. Ask privately for the modules required by your setup. Illustrated activation guide: Trial and activation.

Download once, update from the program

Initial installation / recovery: use the current v23l Raspberry production image in Raspberry download. Extract the image, flash it and allow verification to finish.

Already running a supported release?

Obtain the supplied signed .uas package for Raspberry.
Keep stable power and internet on the board. Open Update.
Check the version, select the package from your computer and press Update.
Read the result; reconnect if the interface reloads.
Confirm Actual, Next and History.

Numbered updates follow their supplied sequence. A replacement package for the current version can be reapplied. History keeps the latest successful entry per version, up to ten distinct versions. An upload alone is not installation success.

The image filename v23l identifies this production build; the updater’s numbered version may display v23. An image ZIP is not a .uas update package.

Update walkthrough: Update. For purchase/support, message Julliano privately with your board model and Device ID; include the camera model when requesting a Pocket license.

v23 for Raspberry Pi.