Software Updates
Update the whole robot with one signed file from the Updates page.
Asimov 1 updates as one unit: a single signed file updates the robot's apps and the RPU's firmware together. You install it from the Updates page in Asimov Manager, with no terminal needed.
Get the Update File
Updates come as a signed .mender file of up to 2 GB. Fetching updates online isn't available yet — Check Now is disabled — so add the file by hand.
Install an Update
- Support the robot and turn it off. The update restarts the RPU.
- Open Updates, select Choose File… and pick the
.menderfile. - Start the update. You can leave the page and come back — the progress card tracks the update either way.
An update isn't finished when it installs: the robot runs a health check on its services first, then reports the result.
| Result | Meaning |
|---|---|
| Updated to Robot Software <version> | Done. The services stayed healthy for the whole check |
| Update rolled back | Something failed the health check, and the robot returned to the previous version |
| Update undone or Update closed | The update was reversed or abandoned before it finished |
| Update failed | It didn't install. The log on the page says why |
Select OK to dismiss the result. If the page instead says an update was interrupted — for example The robot restarted during an update — select Finish Update to run the health check again.
Some messages are for a technician
Messages such as The controller kept the new version point to recovery steps that are run over SSH. If you see one without having done anything unusual, note the exact message and contact support rather than improvising.
Check Versions
- Updates → Installed lists Robot Apps and Controller (RPU) — the RPU's firmware.
- Overview's Software row shows the installed release.
- Account shows the console's own version, which matches the release.
Updates don't change actuator IDs, calibration or the assembly confirmation.
How is this guide?