Skip to main content
Version: 9

Upgrading Software & Changing License Keys

There are two ways to upgrade the software. For most release versions of MoveIt Pro, we recommend the Upgrade in Place approach. Alternatively, if needed you can choose the Full Re-Install approach.

note

Our versioning uses an X.Y.Z syntax where X is the major version, Y is the minor version, and Z indicates a patch release.

Upgrade to 9.4.2​

MoveIt Pro 9.4.2 uses stable host hardware to identify each computer for licensing. This is not a workspace migration, but it can require a new activation and prevent startup if the container cannot access the selected hardware source.

When upgrading from 9.4.1 or earlier, the license identity changes even when MoveIt Pro selects the same network interface. An online installation re-activates on its first start with 9.4.2 when it can reach the license server. An explicitly offline installation needs a new request and response because its existing offline response remains bound to the previous identity. An installation already running 9.4.2 retains its identity when its persistent data and selected hardware source remain available.

For an air-gapped installation, plan the license exchange as part of the maintenance window. Before generating the new request, move the pre-upgrade offlineRequest_*.dat and offlineResponse_*.dat files out of ~/.local/share/moveit_pro/. Keep them only as archived support evidence; do not copy them back or reuse them. Install 9.4.2, generate a new offline request, obtain the corresponding response on a connected computer, and apply it before returning the installation to service.

Stop MoveIt Pro cleanly before upgrading. A clean shutdown releases a hosted-floating seat, but it does not remove a node-locked activation. Contact support@picknik.ai before upgrading if the key has no available activation capacity.

Upgrade Fleets Carefully

MoveIt Pro 9.4.1 and earlier could assign the same fallback identity to multiple computers, particularly when their permanent network interfaces were not named eth0. MoveIt Pro 9.4.2 identifies each computer separately, so each computer needs its own activation. Ask support to review the license before upgrading a fleet that may have shared one identity.

Keep ~/.local/share/moveit_pro/ persistent and preserve access to the selected TPM or permanent network interface across the upgrade. See Configure Licensing for the complete identity, permissions, and persistence contract.

To leave MoveIt Pro workspace and robot config packages unchanged:

  • Run the latest install script from the Install MoveIt Pro guide.
  • Run moveit_pro build or moveit_pro run to upgrade and re-build your workspace.
  • If performing a major upgrade, reference the Migration Guides in the Release Notes to upgrade your robot config packages through each major release, as there may be breaking changes that require manual migration steps.

Full Re-Install​

If your upgrade is unsuccessful for any reason, you can do a full re-install. This option is ideal if you are only using our example workspace, without any additions or changes. The example workspace will be re-downloaded automatically when you run MoveIt Pro.

warning

This will delete your ~/moveit_pro folder, so if your custom workspace is located within the folder back it up to another location before proceeding!

Changing Licenses Keys​

To change your MoveIt Pro license key, perhaps because your previous one expired or was copied in incorrectly, there are two approaches:

  1. Run moveit_pro configure and it will re-step you through all the configuration steps, including entering your license key.
  2. Run gedit ~/.config/moveit_pro/moveit_pro_config.9.yaml and find the line called MOVEIT_LICENSE_KEY