Firmware updates

Firmware reaches devices through Formcloud, staged by group and with a signed rollback path. This page lists what is current and what changed.

Delivery
Formcloud, over the air
Staging
Canary group first, automatic halt
Rollback
Signed, within the support window
Security fixes
Within 30 days of confirmation

Current firmware

As of October 2026. Formcloud shows what each of your devices is actually running.

DeviceCurrentReleasedLattice OSNotes
Axon Sense 22.14.1Sep 15, 20264.2Recommended for all devices
Axon Sense 33.0.4Sep 30, 20264.2Limited release customers only
Corta bedside reader1.8.3Aug 25, 20264.1Applies automatically overnight
Fieldmesh G44.6.0Oct 1, 20264.2Adds reading backfill priority
Fieldmesh G33.9.4Oct 1, 20263.8Clinical parity with G4 4.6.0
Fieldmesh G22.12.7Jun 3, 20263.8Security fixes only until Dec 2026
Nexa Edge (all variants)5.2.0Sep 8, 20264.2Vehicle: faster 12-lead resend
Lattice Bench LB-8, LB-322.8.0Jul 13, 20264.1Pairs with Studio 2.8

Recent release notes

Fieldmesh G4 4.6.0 and G3 3.9.4, October 1, 2026

  • Added: after a long outage, gateways now send the most recent readings first and backfill older ones behind them, so a clinician sees current values within a minute of reconnection.
  • Fixed: a gateway re-homing to a neighbor could briefly report a device as offline.
  • Changed: environmental sensor alarms at the local station now repeat every ten minutes until acknowledged.

Axon Sense 2 2.14.1, September 15, 2026

  • Fixed: under rare conditions, a skin contact flag could be raised for one sample when the adhesive carrier was changed. No measurement data was affected. See advisory NXA-2026-006.
  • Changed: battery estimate shown in Formcloud now accounts for the transmission schedule.

Nexa Edge 5.2.0, September 8, 2026

  • Vehicle: a 12-lead ECG held while out of coverage is now resent within 5 seconds of signal returning, down from 30.
  • Home: the status light now shows a distinct pattern when the hub is on battery backup.

How an update reaches a device

The same steps for every device family.

01

Published

A release is published to Formcloud with its notes, SBOM and signatures. Nothing installs yet.

02

Canary group

Your administrator chooses a small group to go first. Formcloud watches their error rates.

03

Staged rollout

Remaining groups follow on the schedule you set, inside the maintenance windows for each site.

04

Rollback if needed

Any group can return to its previous version, with a signed record of every transition.

Need to hold a version?

Some validated environments cannot take updates on our schedule. Formcloud can pin a group to a version for as long as that version is supported.