Error codes

What a robot’s error code means, from the maker’s own directory, with a link to the page where the maker says what to do about it.

Type the code from the teach pendant, or words from the message. Each directory is grouped the way the maker prints it: by robot generation, then by section.

Clear

1,223 codes from Universal Robots · page 13 of 31

C222A4 · Change in offset is too high to meet joint speed safety limit

Universal Robots · CB3 and Earlier Models

C222 Frame TrackingCause given

C222A5 · Change in offset is too high to meet tool speed safety limit

Universal Robots · CB3 and Earlier Models

C222 Frame TrackingCause given

C222A6 · Change in offset is too high to meet momentum safety limit

Universal Robots · CB3 and Earlier Models

C222 Frame TrackingCause given

C259A0 · Critical error

Universal Robots · e-Series and Later Models

C259 Filesystem-related issue

C259A80 · No title in the maker’s directory

Universal Robots · e-Series and Later Models

C259 Filesystem-related issueCause given

C259A89 · Failed to create a file with ID {unsigned}

Universal Robots · e-Series and Later Models

C259 Filesystem-related issueCause given

C260A0 · Critical error

Universal Robots · e-Series and Later Models

C260 Brake Release - old procedureCause given

C261A0 · Critical error

Universal Robots · e-Series and Later Models

C261 Temperature SensorCause given

C261A3 · Temperature changed more than allowed: {float} Celsius

Universal Robots · e-Series and Later Models

C261 Temperature SensorCause given

C261A4 · Temperature is too high ({float} degrees Celsius)

Universal Robots · e-Series and Later Models

C261 Temperature SensorCause given

C261A5 · Temperature is too low ({float} degrees Celsius)

Universal Robots · e-Series and Later Models

C261 Temperature SensorCause given

C261A21 · Safety Control Board temperature is too high: {float} Celsius

Universal Robots · e-Series and Later Models

C261 Temperature SensorCause given

C261A22 · Safety Control Board temperature is too low: {float} Celsius

Universal Robots · e-Series and Later Models

C261 Temperature SensorCause given

C261A23 · The Energy Removal power sensor temperature on the Power Board is too high: {float} Celsius

Universal Robots · e-Series and Later Models

C261 Temperature SensorCause given

C261A24 · The Energy Removal power sensor temperature on the Power Board is too low: {float} Celsius

Universal Robots · e-Series and Later Models

C261 Temperature SensorCause given

C261A25 · The Robot power sensor temperature on the Power Board is too high: {float} Celsius

Universal Robots · e-Series and Later Models

C261 Temperature SensorCause given

C261A26 · The Robot power sensor temperature on the Power Board is too low: {float} Celsius

Universal Robots · e-Series and Later Models

C261 Temperature SensorCause given

C261A29 · Unable to read the TOOL PCBA temperature for {float} ms.

Universal Robots · e-Series and Later Models

C261 Temperature SensorCause given

C262A0 · Critical error

Universal Robots · e-Series and Later Models

C262 CommunicationCause given

C262A17 · Failed to communicate with {deviceName} Joint

Universal Robots · e-Series and Later Models

C262 CommunicationCause given

C262A18 · Failed to communicate with TOOL

Universal Robots · e-Series and Later Models

C262 CommunicationCause given

C262A25 · Unexpected message version received: {unsigned}

Universal Robots · e-Series and Later Models

C262 CommunicationCause given

C262A27 · Failed to communicate with the Base Filter Board

Universal Robots · e-Series and Later Models

C262 CommunicationCause given

C262A28 · Failed to properly instantiate a multi-subscriber message or special command

Universal Robots · e-Series and Later Models

C262 CommunicationCause given

C262A29 · Failed to communicate with the Cable Extender with ID: {hex}

Universal Robots · e-Series and Later Models

C262 CommunicationCause given

C263A0 · Critical error

Universal Robots · e-Series and Later Models

C263 Motor EncoderCause given

C263A1 · Motor Encoder is unavailable

Universal Robots · e-Series and Later Models

C263 Motor EncoderCause given

C263A2 · Calibration has been invalidated and can lead to reduced performance.

Universal Robots · e-Series and Later Models

C263 Motor EncoderCause given

C263A21 · Validation of the detected Index Mark ({signed}) failed

Universal Robots · e-Series and Later Models

C263 Motor EncoderCause given

C263A26 · Failure to log missing Index Mark, index out of range: {unsigned}

Universal Robots · e-Series and Later Models

C263 Motor EncoderCause given

C263A27 · Failure to log index drift, position out of range: {unsigned}

Universal Robots · e-Series and Later Models

C263 Motor EncoderCause given

C263A38 · Time sanity check failed, difference is too great: {float}

Universal Robots · e-Series and Later Models

C263 Motor EncoderCause given

C263A39 · The motor encoder data CRC was invalid

Universal Robots · e-Series and Later Models

C263 Motor EncoderCause given

C263A41 · The rate of invalid samples is too high. Debt counter = {unsigned}

Universal Robots · e-Series and Later Models

C263 Motor EncoderCause given

C264A0 · Critical error

Universal Robots · e-Series and Later Models

C264 Task ManagerCause given

C264A7 · Start of Cycle pulse was required but did not occur after {unsigned}ms.

Universal Robots · e-Series and Later Models

C264 Task ManagerCause given

C264A8 · Systick timer and Start of Cycle pulse was misaligned by {float}us.

Universal Robots · e-Series and Later Models

C264 Task ManagerCause given

C264A9 · {signed} unexpected (+) or missing (-) Start of Cycle pulses was detected within a 1 second period.

Universal Robots · e-Series and Later Models

C264 Task ManagerCause given

C264A10 · {unsigned} invalid Start of Cycle pulses was detected within a 1 second period.

Universal Robots · e-Series and Later Models

C264 Task ManagerCause given

C264A11 · {unsigned} Start of Cycle pulses was lost in a row

Universal Robots · e-Series and Later Models

C264 Task ManagerCause given

Universal Robots C222A4

Change in offset is too high to meet joint speed safety limit

Cause, as the directory gives them

  • Tracking the moving external axis would result in the robot exceeding safety limits

From Universal Robots’s own error code directory. The steps to fix it are the maker’s and are on the page linked above, not copied here.