Skip to main content

Update

Finding out about a new release​

PLEM tells you about a new release in two places.

  • When you run plem and a new release exists, it asks whether to update now. If you decline or do not answer, the Start session screen opens as usual.
  • The top line of the TUI shows the new version next to the current one.

If both lookups fail, nothing is shown, so a missing notice does not prove you are up to date.

plem version prints the installed version in X.Y.Z form.

Updating​

Stop the robot stack first. If a session is running, the update does not start. Quit the TUI normally, and if processes are left over, clean them up with plem kill.

plem update

plem update runs these steps.

  1. Downloads the latest update procedure and runs that. If it cannot (no internet connection, for example), it continues with the procedure installed on the device. Because the latest procedure runs, skipping several releases still goes through every step added in between.
  2. Checks that no session is running.
  3. Shows the installed and new versions and asks whether to continue.
  4. Installs the packages. If the update leaves a package unused, it prints the name and a cleanup command. It does not remove the package.
  5. Adds the operator account to the realtime (real-time control) and plem (credentials) groups, if it is not in them yet.
  6. On JetPack 6 devices, fills in missing parts of the collision avoidance component (cuMotion).
  7. If the device's robot model differs from its registration, asks for approval and makes them match.

When it finishes, launch again with plem. The update does not start the stack for you.

A device with 0.7.0 or later can update straight to the latest release without intermediate versions. Which procedure runs on the first update depends on the installed version.

Installed versionFirst update
Before 0.7.0Contact support
0.7.xRuns the procedure on the device. It may stop once; if it does, see Stops because a component must be removed
0.8.0 to 0.9.0Runs the procedure on the device
Later than 0.9.0Downloads and runs the latest procedure
The update does not back up your data

The update neither backs up nor restores anything under ~/.plem. Copy whatever you need to keep before you update.

Stops with 401​

A 401 while plem update downloads the package list means this device's token was revoked or its license expired. What to do for each case is in Troubleshooting › Token rejected.

Stops because a component must be removed​

Sometimes an update has to remove an installed component. It goes ahead only if the new release declares that component retired. If something not declared would have to go, the update changes nothing and stops.

The older procedure on 0.7.x devices cannot make this call and stops even for a retired component. In that case, run the latest procedure directly once. After that, plem update works normally.

curl -fsSL https://depot.wimcorp.dev/jetson/update.sh | sudo bash

If the latest procedure stops with the same message, contact support.

Stops because another package job is running​

While another package job runs (an automatic update, for example), the package install step waits up to 5 minutes. The step that downloads the package list does not wait and stops with Could not get lock. Run the update again a little later.

After updating​

  1. Log in again. If the update added the operator account to the realtime or plem group, the change applies after you log in again or reboot. Check with id -nG.
  2. Run ros2 daemon stop once in a new terminal. A ros2 daemon that was already running may still hold the old network settings. The next ros2 command restarts it with the new ones.
  3. Remove any export of ROS_DOMAIN_ID, CYCLONEDDS_URI or RMW_IMPLEMENTATION from ~/.bashrc and similar files. plem does not read them and sets the same values in each new terminal itself. If you leave them, only that shell's ros2 drifts away from the robot. Change the domain in the TUI settings (,).
  4. Read the compatibility notes in the Changelog. Changes that require you to adjust external programs or settings are listed there.

Good to know​

Remote ROS 2 clients​

The device's ROS 2 traffic stays on the device by default. PLEM_CYCLONEDDS_SYSTEM_DEFAULT=off is no longer read; to reach the device from another computer, follow ROS 2 interfaces.

The license stays valid​

License checks do not look at the software version, so you do not need a new license after an update. For an expired license, see Stops with 401.

Custom torque controllers​

A plugin you already built keeps working as long as the major version of the plugin interface (C-ABI) is unchanged. Rebuilding it may still need source changes, so read the "Developer SDK" entries in the Changelog before updating. When an update raises the PLEM major version, the update notice also warns that plugins may need a rebuild.

No rollback​

PLEM cannot downgrade or undo an update. If something is wrong after an update, contact support. You can also recover by removing PLEM with plem uninstall --keep-license and installing again; the device is already registered, so the kept license is used as is.