Skip to content

Upgrades

Keep the rover-agent up to date to get the latest features and fixes.

Before you upgrade

  • Note the currently installed version.
  • Confirm the robot is enrolled and reporting normally (see Health monitoring).
  • Plan for a brief teleop and telemetry interruption while the service restarts.

Upgrade mechanism

You don't build or compile anything to upgrade. The detailed upgrade procedure is coming soon; for upgrade assistance in the meantime, contact [email protected].

The general shape of an upgrade is:

  1. Stop the service, apply the update, and start it again:

bash sudo systemctl stop rover-agent # apply the update sudo systemctl start rover-agent

  1. Confirm the new version is running:

bash sudo systemctl status rover-agent journalctl -u rover-agent -f

What is preserved

Upgrades do not change your robot's identity or local data. The device certificate, key, and the local SQLite database stay in the state directory (default /var/lib/rdyn/robot), so the robot stays enrolled and scheduled missions and stored assets survive the upgrade. See Configuration and Enrollment.

Rollback

Because upgrades preserve your robot's identity and local data, rolling back to a previous version does not require re-enrollment. The supported rollback procedure is coming soon; for help, contact [email protected].

Verify after upgrading

  • Check that the robot reconnects and reports telemetry and health.
  • Confirm teleop video still works.
  • See Verify agent connectivity.