UAS4G5G LTE · PROGRAM & SUPPORT

Update from the program.

Apply the signed release package through the Update tab. Normal program updates no longer require rewriting the SD card.

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

Choose the correct package

  • Raspberry Pi: signed .uas file.
  • Radxa ROCK 4D / ZERO 3W/3E: signed .uas_rdx file supplied for the applicable release.

An SD-image ZIP is not an in-program update. Renaming another file does not make it a valid signed package.

02

Install a signed update: steps 1–4

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

Raspberry Pi & Radxa — same steps; Radxa shown.

1 Check Version → 2 Choose File → 3 Update → 4 confirm Actual and History after completion. The Update button remains disabled until an acceptable package is selected. Raspberry: .uas · Radxa: .uas_rdx. Use the signed package supplied for your release, not an image ZIP. The board itself needs internet, and its power must remain connected. Read progress or failure messages. Reconnect after the interface reloads, then verify the result. Apply numbered releases in order; a replacement of the current version may be reapplied. An upload alone is not confirmation of installation.

03

Apply an update

  1. Save the supplied update file on the computer/device running your browser.
  2. Ensure the board has internet and stable power. Stop operational streaming/flight activity before maintenance.
  3. Open Update and press Check Version.
  4. Press Choose File and select the package.
  5. Press Update and read the installation display. Without internet, the update is refused and a message is shown.
  6. Wait for completion. If the interface restarts, reconnect/refresh after it returns.
  7. Check Actual and History to confirm success.
04

What the controls show

  • Actual: v… = installed numbered version.
  • Next: v… = expected next numbered update.
  • History: latest successful installation per version, keeping the last ten unique successful version entries. Reinstalling the same version replaces its history entry rather than duplicating it.
  • The installation display shows progress, success or failure; an upload alone is not successful installation.
05

Release order and restart

Apply numbered releases in their supplied order. A replacement package of the current version can be reapplied; this does not permit skipping required versions. Some supplied maintenance packages update configuration/interface components without advancing the numbered version.

Updates that change Node-RED interface/configuration reload it after the changes. If a package reports failure, keep the displayed error and contact Julliano before assuming the system is updated.

Routine supported updates use this tab; you do not need to rewrite the whole SD image. Image flashing remains the procedure for an initial installation or recovery.

Program screenshotFull resolution ↗