abb_libegm: EGM causes robot controller shutdown with error message "10014 System Failure" on IRB14000

Hi,

in a project in which we are integrating the IRB 14000 YuMi with ROS2, motion control of YuMi is handled via the abb_libegm library and the EGM interface of the robot controller.

A fully functioning system was achieved with ROS2 Dashing. However, when transitioning to ROS2 Eloquent, the same code crashes the robot controller.

When a motion command is issued (joint position reference) to the robot controller, it activates the joint brakes on both arms and freezes for a couple of seconds before crashing (FlexPendant reboots etc). It then automatically reboots, but gets stuck trying to connect to the robot controller. When manually powered down and restarted, the FlexPendant informs us the robot controller is in a System Failure state.

Error messages read from FlexPendant , in order of occurrence

Event Message 20192 "System data from last shutdown is lost" Event Message 20193 "Robot data update warning"

– It gets stuck rebooting, we manually reboot –

Event Message 10056 "System restarted" Event Message 10014 "System failure state"

The robot controller is running a StateMachine Add-In instance for both arms. Same issue have occurred with the following configurations:

  • RW 6.08.00.01 and StateMachine 1.0
  • RW 6.09.02 and StateMachine 1.0
  • RW 6.10.01 and StateMachine 1.1

Desktop PC: Ubuntu 18.04 with today’s (and several older) build(s) of abb_libegm.

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 15 (10 by maintainers)

Most upvoted comments

Here’s a video of the joint demo motions (RobotStudio EGM demo motions video.zip).

A 🕺 YuMi. Nice.