Skip to content
LAYER400AIRSPACE INTELLIGENCE NETWORK
Chat with us
Contributors / Field guide

Keep your receiver up to date

Use the receiver’s Updates page for online releases or a signed update file downloaded on another device.

Update online

  1. Open your Pi’s local page and sign in with its receiver password.
  2. Open Updates, then select Check for updates.
  3. Review the offered version and compatibility information.
  4. Confirm the installation when you are ready. Keep power connected and let the receiver finish.
  5. Reconnect if the page reloads or the receiver restarts, then check the installed version and reception.

Automatic checks discover available releases; they are not permission to install one. Use the controls shown by your installed version.

Install a signed update file

  1. Download the .layer400update file from the official receiver downloads page.
  2. Open Updates on the receiver, choose the file and select Upload and verify.
  3. Wait for verification to finish. Review the version, then confirm Install.
  4. Keep the receiver powered on. Check the resulting version after it returns.

A local-file update does not need the Pi to download the release from the internet. It still checks the signature and compatibility. The receiver itself continues to need the connectivity required by its normal operation.

Know which file you have

.tar.gz

The fresh-install archive. Follow its installation instructions on the Pi.

.layer400pi

The private account setup file. Import it in receiver setup, not Updates.

.layer400update

The signed software update. Upload it on the Pi’s Updates page.

If the update is interrupted

Don’t pull the power to make a slow installation finish. If the browser loses connection, allow the receiver to return, sign in again and inspect the installed version and update result before trying another installation.

The update process protects the receiver’s identity and settings and can restore the previous version when its installation checks fail. Recovery is not a reason to interrupt power deliberately.

If it reports a failure or rollback, keep that message. If it rejects a signature, version or compatibility check, use the matching official file—don’t disable verification or force an arbitrary package.

Need a hand? Talk to Layer400.