Skip to main content

Troubleshooting

Start from the symptom.

SymptomWhat to do
The robot list in Start session is emptyThe profile set up at delivery is not visible. Contact support. Screen reference: Start session
You pressed s but the stack does not come upLaunching the stack
Right after plem starts, the robot stack and server stop with error creating nodeUpdate 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.core.rmem_max, run sudo sysctl --system or reboot
The robot stopped (Protective Stop) and will not moveRecover 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_NOT_OPERATIONALRight 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 clearPLEM 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 openWeb tools do not open
No camera imageZED X Mini camera not detected
ros2 topic list in a terminal does not show the robotros2 cannot see the robot
A PLEM is locked page opens instead of the Pendant or Lab, or a token is rejectedLicense and token errors
You lost the license file or the plem code device keyLost license file or device key
plem will not start and shows a ros_domain_id errorSet ros_domain_id in ~/.plem/settings.yaml 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 emptyCheck 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 updateRead the Changelog. There is no rollback (Update)

Web tools do not open​

Check in this order.

CheckIf not
The stack is running. The web tools start with itLaunch 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 itFix 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=okIt needs a Firefox that is not the snap build, or a browser set in PLEM_BROWSER

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
Do not trust the camera vendor's "OK"

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_serialization.so: cannot open shared object file, run sudo /usr/share/plem/setup-cumotion.sh once. Only devices upgraded with apt directly need this; plem update already applies it.

ros2 cannot see the robot​

  1. If this is the first time since an update, run ros2 daemon stop once in a new terminal. A ros2 daemon that remembers the old settings hides the robot.
  2. If ~/.bashrc or a similar file has export lines for ROS_DOMAIN_ID, CYCLONEDDS_URI or RMW_IMPLEMENTATION, delete them and open a new terminal. Otherwise that shell's ros2 drifts away from the robot. Change the domain in the plem settings (,).

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 pageWhat to do
ExpiredAsk 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_control.soReinstall with sudo apt install --reinstall plem-core
Cannot open libethercat.so.1The IgH EtherCAT master is not installed. Contact support
Cannot open a library (*.so) with any other nameFind the package that provides that file
Abnormal exit or timeout with no library nameReinstall 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.

CauseWhat it meansWhat to do
Token revokedRevocation is permanent. Deleting a device also revokes the token used for itA 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 expiredA 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/plem/license.key) and registration (/etc/plem/depot.json) 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/plem/ by hand.

What you lostWhat to do
License file (/etc/plem/license.key)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/plem/code/plem-code-key.json)Run sudo plem-register --reissue-plem-key on the device. See the notes below

Install a reissued license_file 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/plem/depot.json) must still be on the device. If they are missing, the command tells you what to do.
  • 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 ~/.plem/log. Sending that folder speeds up diagnosis.

tar czf plem-log.tar.gz -C ~/.plem log
LogLocation
TUI (operations, launch, stop, robot events)~/.plem/log/plem_tui_<time>.log (a new file each time plem starts)
Robot stack (launch, node and server output)~/.plem/log/<time>/ (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.