v23 for Radxa — 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.

Supported Radxa builds and hardware video

Current boards: ROCK 4D, ZERO 3W and ZERO 3E. Use the dedicated ROCK 4D image or ZERO 3W/3E image, as appropriate. Their boot files and USB/OTG connections are board-specific even though the dashboard is shared.

H.264 and H.265 hardware encoding

The Rockchip video path provides hardware encoding for the supported camera workflows, with hardware decoding/resizing when the input and pipeline support it. This keeps substantially more video work off the CPU than software encoding.

Camera inputs

Compatible USB cameras and USB HDMI-capture devices through USB Camera-1 / Camera-2.
DJI Osmo Pocket 1 and Pocket 2 through their dedicated integration.
The current supported boards do not have native HDMI input. A visible shared Hdmi-Camera tab does not create an input port; use a supported USB HDMI capture device.

Network differences

ZERO 3W has built-in Wi-Fi. ZERO 3E uses built-in Ethernet; it does not have the W model’s built-in hotspot. Use the network hardware and ports present on your board. Downloads: ZERO 3W / 3E download · ROCK 4D download.

See the current Pocket controls

ROCK 4D / ZERO 3W / ZERO 3E: the same control sequence applies, while USB connection handling is board-specific. Use the port/cable arrangement supplied for your board. 1 H.264/H.265 → 2 live resolution/bitrate + SET → 3 endpoint + SET → 4 reinitialize when required → 5 PLAY/STOP below the feed. Radxa Pocket receiver: 127.0.0.1:8023. Pocket 1 reaches native 1080p; Pocket 2 reaches native 720p. Both codecs/cameras offer 630p, 540p and lower outputs, with the supported hardware video path. A valid license for the connected Pocket model is still required. Phone mode alone is not proof of a valid camera license or working stream.

DJI Osmo Pocket 1 and Pocket 2

Use the shared Dji Pocket 2 & 1 tab. The detected camera model is shown in the panel. Connection and phone-mode/reconnection handling follow the specific board’s USB setup.

Both H.264 and H.265 use the hardware video path.

Pocket 1: up to native 1920×1080 live output.
Pocket 2: up to native 1280×720 live output. The previous 1080p enlargement option is removed.
Both offer 630p (1120×630) and 540p (960×540), plus lower output choices. These change the transmitted resolution, not just the menu label.
Live bitrate options include 0.25 Mb/s. Choose bitrate/resolution for the available uplink and receiving device.

Camera controls

Stream PLAY/STOP sits under the live feed. Use supported gimbal movement/recenter, camera modes and recording controls. Pocket 1 has fewer camera functions than Pocket 2; available controls follow the detected model.

Camera RECORD-RESOLUTION/FPS is separate from live stream resolution. Automatic subject tracking and adaptive bitrate are not enabled in this release.

Pocket licenses are separate from the main UAS license. Phone mode alone is not confirmation of a valid camera license or a running video stream. Illustrated guide: DJI Pocket 1 and 2.

Independent cameras and shared Cockpit controls

USB Camera-1 and Cockpit share the first USB pipeline. Detect the camera, choose resolution/bitrate and start H.264 or H.265. Changes in either panel refer to that same source; the action displays report the changes.

USB Camera-2 is independent: its own capture device, settings and destination. Available USB ports/bandwidth and total processing/network load determine which simultaneous camera combinations fit your board. A Pocket connection can occupy a port needed by another camera.

Video destinations

SEND UDP RTP: use a reachable receiver IP and listening UDP port. The local Cockpit receiver is 127.0.0.1:8020.
SEND TCP RTSP: Camera-1 uses rtsp://BOARD_IP:8554/live; Camera-2 uses rtsp://BOARD_IP:8554/live2.
To view Camera-2 in Cockpit, stop the source already feeding the local receiver, then route Camera-2 there. Continue configuring it in its own tab.
Pocket retains its dedicated live-view receiver and panel.

General USB detection chooses from the camera’s advertised formats; output is limited to 1080p / at most 30 fps. Hardware processing is preferred where supported. Improvements address format choice, packet overhead, buffering, playback recovery and camera reconnection. Video bitrate remains manual; VPN/protocol overhead adds to network usage. Guides: Video destinations · USB Camera 1 · USB Camera 2.

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.

Correct image, signed in-program updates

Initial installation / recovery:

ZERO 3W / 3E production image: ZERO 3W / 3E download.
ROCK 4D production image: ROCK 4D download.

Use the correct board image, extract it, flash it and complete verification.

Routine supported releases

Obtain the supplied signed .uas_rdx update for your board/release.
Keep stable power and internet on the board; open Update.
Check the version, choose the file from your computer and press Update.
Read the result and reconnect if the interface reloads.
Confirm Actual, Next and History.

Routine updates use this tab instead of rewriting the SD card. Numbered updates follow their supplied sequence; a current-version replacement package can be reapplied. History retains the latest successful entry for each version, up to ten distinct versions.

The production image is labelled v23l; the updater’s numbered version may show v23. A shared .uas_rdx extension does not mean arbitrary board-specific changes can be installed on any board—follow the package’s supplied applicability. An image ZIP is not an update package.

Update guide: Update. For purchase/support, message Julliano privately with your board model and Device ID; specify Pocket 1/2 when requesting camera licenses.

v23 for Radxa.