Troubleshooting

Common issues you may run into while working with the GoFa CRB 15000 collaborative robot from ABB

SafeMove

SafeMove not calibrated

Safety controller not ready

Safety controller not synchronized

SafeMove not calibrated: This error indicates that no SafeMove Configuration is available yet.

Consequence: No possibility to use the robot in automatic mode. You can just jog the robot manually.
Possible causes: no SafeMove Configuration is available
How to avoid & solve:

Load: user defined SafeMove Configuration + Synchronize SafeMove
Load: the default

Safety controller not ready: An attempt to go to Motors on was rejected by the Safety Controller.

Consequence: The system goes to Guard stop state. Actions Check other elogs for more details.
Possible causes: Check if the robot with its tool center is in a safety zone (in the SafeMove window, see fig. below).
How to avoid & solve:

Switch to manual mode and move the robot axis wise out of the zone.

Safety controller not synchronized: This error indicates that no SafeMove Configuration is available yet.

Consequence:

The supervision functions can only be active while SafeMove is synchronized. When unsynchronized, only manual mode operation with reduced speed is possible until synchronization is executed successfully.
If SafeMove becomes unsynchronized, the robot will stop, and the Stand Still Supervision function will be deactivated. A movement with reduced speed is possible.

Possible causes: no synchronization of SafeMove.
How to avoid & solve:
After setting or loading a SafeMove configuration, please synchronize the SafeMove: e.g. use “MoveAbsJ” to move the robot in the synchronization position. This position is identified in RobotStudio under the tab “Synchronization”. The default values of these angles are zero, but the user can customize them.

After using MoveAbsJ, from the FlexPendant, access with admin user:

Settings -> Safety Controller -> Synchronization.

Safety Controller Wrong Synchronization Position

Safety Controller Automatic Mode Warning

SafeMove violated -> Safety guard stop state

Safety controller Servo-Lag Limit exceeded

Safety Controller Wrong Synchronization Position: The axis argument position does not match its synchronization position, as defined in the safety configuration for the safety controller on drive module argument available yet.

Consequence: Synchronization will not be performed, and the safety controller will go to the unsynchronized state. If SafeMove becomes unsynchronized, the robot will stop, and the Stand Still Supervision function will be deactivated. A movement with reduced speed is possible.
Possible causes: One or more axes are not in the correct synchronization position. The revolution counters or calibration values of the robot controller are not correct.
How to avoid & solve:

Check that the synchronization positions in the safety configuration are correct, and that all axes are in their synchronization position. Followed by a new synchronization of the safety controller. Check that the synchronization switch is working properly.
Sometimes it is necessary to Reset the SafeMove Configuration. Two options:
log in as Admin, than from RobotStudio -> Reset to Factory Settings.
OR
from the FlexPendant -> Settings -> Backup and Recovery -> reset user data -> reset safety settings

Safety Controller Automatic Mode Warning: This error indicates that no SafeMove Configuration is available yet or it has not been locked.

Safety Controller Synchronization auto mode setting

Consequence: No possibility to use the robot in automatic mode. You can just jog the robot manually.
Possible causes: The active safety controller configuration has not been locked OR Safe Configuration is missing.
How to avoid & solve:
or
Please lock the configuration: log in as Admin -> settings -> Safety controller: tick on “Locked"

SafeMove violated -> Safety guard stop state: The system is in the Guard stop state. It enters this state either after switching from Automatic- to Manual mode, or after the Motors ON circuit has been opened by an Emergency Stop or Automatic Stop, or in Manual mode if Enabling device was released.

Consequence: No operation will be possible until after closing the Motors ON circuit. The manipulator's axes are meanwhile held in position by mechanical holding brakes.
Possible causes: Any safety device connected to the system's stop inputs have been opened. These are shown in the Circuit Diagram.
How to avoid & solve:
- Check which safety device caused the stop
- Close the circuit.
- To resume operation, switch the system back to state Motors ON.

Safety controller Servo-Lag Limit exceeded: Possible collision has occurred, than SafeMove will detect this and initiate a stop.

Consequence: No operation will be possible until after closing the Motors ON circuit. The manipulator's axes are meanwhile held in position by mechanical holding brakes.
Possible causes: possible collision has occurred.
How to avoid & solve:
- Please jog in manual mode the robot from the collision area

Motion supervision

Safety controller Standstill violation

Safety Controller Tool Force violation

Safety Controller Tool Speed Violation

Motion supervision: Possible collision has occurred or the robot has entered a Safe Area.

Consequence: No operation will be possible until after closing the Motors ON circuit. The manipulator's axes are meanwhile held in position by mechanical holding brakes.
Possible causes: possible collision has occurred or robot has entered a Safe Area.
How to avoid & solve:
- Please jog in manual mode the robot from the collision/Safe area.

Safety controller Standstill violation: If the robot tries to move due to an error during active Stand Still Supervision, SafeMove will detect this and initiate a stop. Since there is a certain reaction time involved a slight jerk may occur.

Consequence: No operation will be possible until after closing the Motors ON circuit. The manipulator's axes are meanwhile held in position by mechanical holding brakes.
Possible causes: Someone forced the robot to move from the program causing possible collision.
How to avoid & solve:
- Please jog in manual mode the robot from the collision area.

Safety Controller Tool Force violation: Tool Force Supervision was violated in the safety controller for the drive module.

Consequence: If configured with a stop action, the safety controller will stop all robot movements, and no operation will be allowed until the violation has ceased or manual mode has been selected.

If “NoStop” is selected than you will get this event as a warning.
Possible causes: The force acting on the tool exceeded the configured maximum value.
How to avoid & solve:
Switch to manual mode, and jog the robot out of the violation area.

Safety Controller Tool Speed Violation: Tool Speed supervision was violated.

Consequence: If configured with a stop action, the safety controller will stop all robot movements, and no operation will be allowed until the violation has ceased or manual mode has been selected.
Possible causes: The speed of the tool exceeded the configured maximum value.
How to avoid this:
- Switch to manual mode, and jog the robot out of the violation area.

Lead-Through & ASI

Lead-Through doesn't work in Auto using ASI

Overspeed During teach mode

Lead-Through doesn't work in Auto using ASI: Pressing the predefined ASI button the Lead-Through is not activating.

Consequence: Not possible to activate the Lead-Through from the ASI buttons.
Possible causes: "Use buttons in auto mode" option not selected.
How to avoid & solve:

Click on the "ASI Setting" widget on the home screen (see first picture), then scroll all the way down until the checkbox "Use buttons in auto mode" appears (see second picture). This must be activated so that the ASI buttons, e.g. for lead-through, also work in auto mode.
Another procedure/option, different than the Lead-Through one, is selected.
Please switch off Robot and start it again
Safemove configuration + Synchronization is missing → ABB recommend to bring Robot in synchronization posItion.

Overspeed During teach mode: the robot will stop since some or all the joints exceeded the maxium speed allowed.

Consequence: No operation will be possible until after closing the Motors ON circuit. The manipulator's axes are meanwhile held in position by mechanical holding brakes.
Possible causes: using the LT, the robot has been moved too fast.
How to avoid & solve:

Please jog in manual mode the robot from the collision/Safe area more smoothly.

Wizard

Cannot load program due to syntax error

Cannot load program due to syntax error: There are some syntax errors in the RAPID program behind the wizard (see first figure).

Consequence: Not possible to run the program.
Possible causes: syntax errors in the RAPID program.
How to avoid & solve:

Either go to the code window on FlexPendant and click on "check program" (see second figure, step 1). Then the detailed error message will be shown (see second figure, step 2).
It is also possible to connect your Controller to RobotStudio and evaluate the RAPID code there.

FlexPendant

not responding OR Login failed

FlexPendant not responding OR Searching for controller OR Login to Controller Failed: FlexPendant is not responding.

Consequence: Not possible to use the FlexPendant.
Possible causes: Errors in the starting of the FlexPendant OR different users try to log in, e.g. one user on the FlexPendant and another one on RobotStudio
How to avoid & solve:

Please select the 3 dots in the upper right part of the FP and press “Restart the application”.

❖ Shut down the robot

❖ Remove the main power plug from the controller

❖ Reconnect and restart

❖ Resetting the FlexPendant: there is a small reset button net to the USB slot, you might need a pen to press it.

❖ Reset the security communication certificates via robot studio.

❖ The FlexPendant should have fix IP: 192.168.125.250 but some have DHCP active  Please change the TPU's IP address to fixed in Windows on the TPU.

General

Emergency socket x14 is not plugged

SafetyProtectiveStop Triggered

System Failure:

Robot close to singularity

Robot is not running because of broken brake on an Axis

Cannot access with RobotStudio

Emergency socket x14 is not plugged: Robot can’t move since the emergency socket is not connected. the following errors will appear:

Protective Stop Open
SafetyController Emergency Stop Triggered

Consequence: Not possible to move or use the robot.
Possible causes: emergency socket is not connected.
How to avoid & solve:

Turn off the controller, connect the pinned emergency stop x14 (as shown in the image) and Restart the controller.

SafetyProtectiveStop Triggered: only ES1 and ES2 bridges are connected and you try to go in Auto mode.

Consequence: Not possible to run robot in automatic mode (automatic mode should only be used with valid safemove configuration).
Possible causes: Pins in the Emergency socket are not connected.
How to avoid & solve:

Turn off the controller, connect the pinned emergency stop x14 and Restart the controller. Then synchronize the Safety controller

Cobot Trouble Shooting - general - SafetyProtectiveStop

System Failure: A Fatal error occurred.

Consequence: Not possible to use move and use the robot.
Possible causes: Cables or pins not plugged/insert correctly, wrong installation of the RobotWare.
How to avoid & solve:

Power off -> Wait 10 sec -> Power on
Restart of the controller
Check both robot and controller cabling
Check the connection of the I/O device to which the system signal Is connected
Check the configuration of the IO device.
Start RobotWare install utilities from FlexPendant
Try loading a backup.

Typical errors arised:

Start of a Safety Controller failed
No System Output Signal
System Signal configuration: MechUnitNotMoving

Robot close to singularity: axis 5 aligned with axis 4.

Consequence: Not possible to use move and use the robot.
Possible causes: The robot has to reach position in which its axis are aligned.
How to avoid & solve:

Use the RAPID command “SingArea/Off“
Change the orientation of the axes.

Robot is not running because of broken brake on an Axis: one brake is broken.

Consequence: Not possible to use move and use the robot.
Possible causes: mechanical issue.
How to avoid & solve:

Ping robot via WAN but cannot access with RobotStudio: Communication problem.

Consequence: Not possible to connect to RobotStudio.
Possible causes: Grants or some options are missing.
How to avoid & solve:

Check if option “RobotStudio Connect” Option is included.
Settings -> Network -> Public Network -> Allow Robotstudio connection on public network

abb.com privacy settings

Our website uses cookies which are necessary for running the website and for providing the services you request. We would also like to set the following optional cookies on your device. You can change these settings any time later by clicking "Change cookie settings" at the bottom of any page. For more information, please read our privacy notice.

Analytics

We collect statistics to understand how many visitors we have, how our visitors interact with the site and how we can improve it. The collected data does not directly identify anyone.

Preferences

We store choices you have made so that they are remembered across visits in order to provide you a more personalized experience.

Advertising and tracking

Your browsing behavior is tracked across websites by advertising and social network service providers. You may see tailored advertising and content on other websites based on your browsing profile.

Show details

Hide details

privacy notice.

Accept selected

Refuse all

Accept all