Error codes

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.

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

C355A34 · The received hash does not match the hash from the installation

Universal Robots · e-Series and Later Models

C355 Safety APICause given

C355A35 · The identifier is incorrect

Universal Robots · e-Series and Later Models

C355 Safety APICause given

C355A36 · Validation of crc failed for message ID {unsigned}

Universal Robots · e-Series and Later Models

C355 Safety APICause given

C357A0 · Payload CoG is outside reach of robot

Universal Robots · e-Series and Later Models

C357 Too high static load on {deviceName}

C357A1 · Reorientation of tool causes load on joint to be too high

Universal Robots · e-Series and Later Models

C357 Too high static load on {deviceName}Cause given

C359A0 · Missing violation handler

Universal Robots · e-Series and Later Models

C359 Report systemCause given

C359A1 · Missing critical fault handler

Universal Robots · e-Series and Later Models

C359 Report systemCause given

C361A0 · Excessive gear torsion registered

Universal Robots · e-Series and Later Models

C361 Gear torsionCause given

C361A1 · State transition is not permitted following an excessive gear torsion

Universal Robots · e-Series and Later Models

C361 Gear torsionCause given

C362A1 · Unexpected state {unsigned} encountered

Universal Robots · e-Series and Later Models

C362 State MachineCause given

C362A2 · Registration of state {unsigned} have failed

Universal Robots · e-Series and Later Models

C362 State MachineCause given

C363A0 · Unexpected identifier {hex} read from the accelerometer

Universal Robots · e-Series and Later Models

C363 Tool Accelerometer

C363A1 · The configuration that was read back from the accelerometer does not match the expected configuration

Universal Robots · e-Series and Later Models

C363 Tool AccelerometerCause given

C363A2 · Failed to write to a configuration register with data {hex}

Universal Robots · e-Series and Later Models

C363 Tool AccelerometerCause given

C364A0 · Robot type mismatch between configuration and arm

Universal Robots · e-Series and Later Models

C364 Robot validationCause given

C364A1 · Robot type disagreement in the joints

Universal Robots · e-Series and Later Models

C364 Robot validationCause given

C364A2 · The robot type stored in the joints is {unsigned}

Universal Robots · e-Series and Later Models

C364 Robot validation

C364A3 · The robot type in the configuration is {unsigned}

Universal Robots · e-Series and Later Models

C364 Robot validation

C365A0 · Critical error

Universal Robots · e-Series and Later Models

C365 Teach Pendant RS485 communicationCause given

C366A0 · The panel interface output voltage of {float}V is too high while the voltage was not turned on

Universal Robots · e-Series and Later Models

C366 Tool panel interfaceCause given

C366A1 · The panel interface output voltage of {float}V is lower than allowed

Universal Robots · e-Series and Later Models

C366 Tool panel interfaceCause given

C366A2 · The panel interface output voltage of {float}V is higher than allowed

Universal Robots · e-Series and Later Models

C366 Tool panel interfaceCause given

C366A3 · A fault event was detected on supply to the panel interface

Universal Robots · e-Series and Later Models

C366 Tool panel interfaceCause given

C367A0 · Failed to initialize the robot power sensor

Universal Robots · e-Series and Later Models

C367 Power Control BoardCause given

C367A1 · Failed to initialize the ERD power sensor

Universal Robots · e-Series and Later Models

C367 Power Control BoardCause given

C367A2 · Failed to initialize the voltage monitor sensor

Universal Robots · e-Series and Later Models

C367 Power Control BoardCause given

C367A3 · Failed to read data from the robot power sensor

Universal Robots · e-Series and Later Models

C367 Power Control BoardCause given

C367A4 · Failed to read data from the ERD power sensor

Universal Robots · e-Series and Later Models

C367 Power Control BoardCause given

C367A5 · Failed to read data from the voltage monitor sensor

Universal Robots · e-Series and Later Models

C367 Power Control BoardCause given

C367A6 · Power Control Board revision invalid

Universal Robots · e-Series and Later Models

C367 Power Control BoardCause given

C367A7 · Power Control Board revision {unsigned} is not supported

Universal Robots · e-Series and Later Models

C367 Power Control Board

C367A9 · The voltage monitor chip is not responding

Universal Robots · e-Series and Later Models

C367 Power Control BoardCause given

C368A0 · Failed to communicate with power supply unit

Universal Robots · e-Series and Later Models

C368 Power Supply UnitCause given

C370A0 · When communicating with a an ethernet PHY, the command has timed out. command: {hex}

Universal Robots · e-Series and Later Models

C370 Ethernet MDIOCause given

C371A0 · Unable to read status from the End of Arm Ethernet

Universal Robots · e-Series and Later Models

C371 End of Arm EthernetCause given

C371A3 · Unable to establish link to the Control Box

Universal Robots · e-Series and Later Models

C371 End of Arm EthernetCause given

C371A4 · Unable to establish link to the Tool

Universal Robots · e-Series and Later Models

C371 End of Arm EthernetCause given

C371A5 · Validation of PHY device with ID: {hex} failed

Universal Robots · e-Series and Later Models

C371 End of Arm EthernetCause given

C373A0 · Failed to initialize the monitor sensors

Universal Robots · e-Series and Later Models

C373 Power Interface BoardCause given

C373A1 · Failed to initialize the battery interface sensor

Universal Robots · e-Series and Later Models

C373 Power Interface BoardCause given

Universal Robots C355A34

The received hash does not match the hash from the installation

What to do: p. 151 of Universal Robots’s directoryAll Universal Robots codes

MakerUniversal Robots

Applies toe-Series and Later Models

SectionC355 Safety API

Page151

Cause, as the directory gives them

• The hash from the installation must match the received hash

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.