Troubleshooting
Start from the symptom.
| Symptom | What to do |
|---|---|
| The robot list in Start session is empty | The profile set up at delivery is not visible. Contact support. Screen reference: Start session |
You pressed s but the stack does not come up | Launching the stack |
Right after plem starts, the robot stack and server stop with error creating node | Update with plem update. Installing and updating set and apply the kernel receive buffer size that ROS 2 needs. If the update warned could not apply net., run sudo sysctl --system or reboot |
| The robot stopped (Protective Stop) and will not move | Recover from the tool you are using. TUI: Stops and recovery. Teaching Pendant: Clearing a Protective Stop. Why it stopped, and what a ROS 2 client must do: Stops and safety |
Brake release is refused and the log shows [RT] SLAVE_ | Right after launch, wait a moment and release again. If it keeps happening, contact support with the output of sudo dmesg | grep -i ethercat |
| A drive stays stopped (quick stop, for example) and will not clear | PLEM has no command that clears it. Before shutting down the stack, check with your own eyes that the robot has stopped. See Stops and safety |
The web tools (:8080) do not open | Web tools do not open |
| No camera image | ZED X Mini camera not detected |
ros2 topic list in a terminal does not show the robot | ros2 cannot see the robot |
| A PLEM is locked page opens instead of the Pendant or Lab, or a token is rejected | License and token errors |
| You lost the license file or the plem code device key | Lost license file or device key |
plem will not start and shows a ros_ error | Set ros_ in ~/. to an integer from 1 to 101, or delete the line. The message shows the file path and the allowed range |
| The gripper or camera list is empty | Check that the PLEM environment is loaded and the robot packages are installed (run plem update if needed). If the list is still empty, contact support |
| Something behaves differently after an update | Read the Changelog. There is no rollback (Update) |
Web tools do not open
Check in this order.
| Check | If not |
|---|---|
| The stack is running. The web tools start with it | Launch it with s in Robot Control |
| The Teaching Pendant and Plem Lab components were on in Start session (both are on by default) | Stop the stack, turn them on, launch again |
The address is right, including the trailing slash (/web/, /lab/). ] in Robot Control shows it | Fix the address. From another computer, check that it is on the same network as the device and that nothing blocks port 8080 |
On the device's own screen, plem-pendant --check reports status=ok | It needs a Firefox that is not the snap build, or a browser set in PLEM_ |
If all of this is fine and the page still does not open, the web bridge probably failed alone: a bridge warning in the launch log means the rest of the stack can be fine while the web tools are down. Stop the stack and launch it again.
A PLEM is locked page means a license problem; see License and token errors.
ZED X Mini camera not detected
This camera connects over GMSL2, and it gives no image when the device's camera daemon gets into a bad state. Launching the robot stack checks and repairs this automatically, and you can also check it yourself. For other cameras, see the failure signals table in Launching the stack.
/usr/share/plem/plem-camera-recover.sh --check # check only, changes nothing
sudo /usr/share/plem/plem-camera-recover.sh # repair if needed
The camera vendor's diagnostic tool can report the device as fine and still miss this state. Use the script above to decide.
On a device with the collision avoidance component (Isaac ROS), if there is no image and the launch log shows libgxf_, run sudo /usr/ once. Only devices upgraded with apt directly need this; plem update already applies it.
ros2 cannot see the robot
- If this is the first time since an update, run
ros2 daemon stoponce in a new terminal. Aros2daemon that remembers the old settings hides the robot. - If
~/.or a similar file hasbashrc exportlines forROS_,DOMAIN_ ID CYCLONEDDS_orURI RMW_, delete them and open a new terminal. Otherwise that shell'sIMPLEMENTATION ros2drifts away from the robot. Change the domain in theplemsettings (,).
Changed settings, network interfaces and access from another computer: ROS 2 interfaces.
License and token errors
PLEM is locked page
If the device's license is missing, expired or cannot be checked, a PLEM is locked page opens on :8080 in place of the Pendant and Lab, and all server functions are blocked. The browser tab title is PLEM — License required. The page is in English: the reason is in a gray box, and the steps are under "What to do". Without a valid license the robot controller does not start either.
| Reason on the page | What to do |
|---|---|
| Expired | Ask your license contact to renew the license, then run sudo plem-register --refresh |
| Any other license reason (another device, failed check, damaged file, internal error and so on) | Contact your license contact |
Cannot open libplem_ | Reinstall with sudo apt install --reinstall plem-core |
Cannot open libethercat. | The IgH EtherCAT master is not installed. Contact support |
Cannot open a library (*.) with any other name | Find the package that provides that file |
| Abnormal exit or timeout with no library name | Reinstall with sudo apt install --reinstall plem-core. If it happens again, contact support |
If the reason text gives its own instruction, follow that as well. Changes take effect after you restart the robot stack from plem.
Token rejected
When plem update, plem-register or plem code gets a token rejection, the message shows the two common causes with what to do for each. The server does not tell them apart, so ask your license contact which one applies. plem-register exits with code 11 in both cases.
| Cause | What it means | What to do |
|---|---|---|
| Token revoked | Revocation is permanent. Deleting a device also revokes the token used for it | A revoked token cannot be restored. Ask your license contact to delete this device's registration and issue a new token. Then remove PLEM with plem uninstall and install again with the new token, because the installer stops on a device that is already registered |
| License expired | A device's token follows the license expiry date. After expiry plem update is refused, and plem code is refused from its next key renewal (plem remote for remote support still works) | Ask your license contact to renew, then run sudo plem-register --refresh to get the new license and restart the robot stack. Before the renewal, the command is refused with the same 401 |
Registration is per Depot
If you register an already registered device with a new token at a different Depot address, that Depot registers it as a new device. The device's license (/etc/) and registration (/etc/) are replaced. Before registering again, ask your license contact where the device is registered now.
Lost license file or device key
Do not edit files under /etc/ by hand.
| What you lost | What to do |
|---|---|
License file (/etc/) | Ask your license contact to reissue the license for this device; no deregistration is needed. Registering again does not help, because the device is already registered (plem-register exits with 16). A reissue signs the expiry date stored in Depot again, so if the registration has expired you need a renewal instead |
plem code device key (/etc/) | Run sudo plem-register --reissue-plem-key on the device. See the notes below |
Install a reissued license_ value with this one line, without decoding it, then restart the robot stack. If the file mode is not 0644, PLEM cannot read the file and refuses it.
printf '%s' '<license_file value>' | sudo install -m 0644 -o root -g root /dev/stdin /etc/plem/license.key
Before you reissue the device key:
- Reissuing revokes the device's old key at once. Any copy elsewhere, a backup for example, stops working too. If a working copy exists, do not reissue.
- The license and registration (
/etc/) must still be on the device. If they are missing, the command tells you what to do.plem/ depot. json - If the key file still exists, the command changes nothing and refuses. If the file is damaged, delete it and run the command again.
Removing and reinstalling
To update packages, use plem update instead of removing PLEM. By default plem uninstall also deletes the license and the device key; read plem uninstall before you run it. A license file cannot be copied to another device, because it is signed for this device's ID.
Remote support
Run this on the device to open a temporary channel a support engineer can connect through. Ending the command (Ctrl+C) closes the channel.
plem remote
Asking for support
Send questions to william@wimcorp.co.kr. If a message you have never seen appears while the robot is working, stop the robot first (Emergency Stop if needed), then report it.
The TUI and robot stack logs are in ~/.. Sending that folder speeds up diagnosis.
tar czf plem-log.tar.gz -C ~/.plem log
| Log | Location |
|---|---|
| TUI (operations, launch, stop, robot events) | ~/. (a new file each time plem starts) |
| Robot stack (launch, node and server output) | ~/. (a new folder each time the robot stack launches) |
For each kind, only the 20 most recent are kept, and older ones are deleted on the next run. Send the logs soon so the run with the problem is not deleted.
Add the output of plem version and what you were doing when the problem happened.