C296 Start up check

C296A0 Critical error

A critical error occurred during startup

Try the following actions to see which resolves the issue: (A) Conduct a complete rebooting sequence, (B) Update software, (C) Contact your local Universal Robots service provider for assistance

C296A1 SCB IO failed to power on

Ensure the IO Power Connector on the Safety Control Board is connected to the 24VDC

C296A2 One or more Motor phases is short circuited to ground. Diagnostic data: {hex}

Bit 0 high indicates short circuit

Contact your local Universal Robots service provider for assistance.

C296A3 Motor Indication Signal does not work. Diagnostic data: {hex}

Bit 1 low indicates that the diagnostics feature is broken

Contact your local Universal Robots service provider for assistance.

C296A4 Phase 1 is not connected. Diagnostic data: {hex}

Bit pattern 0b0110 indicates that phase 1 is not connected

Make sure all Motor phases are connected correctly. Contact your local Universal Robots service provider for assistance.

C296A5 Phase 2 is not connected. Diagnostic data: {hex}

Bit pattern 0b1010 indicates that phase 2 is not connected

Make sure all Motor phases are connected correctly.Contact your local Universal Robots service provider for assistance.

C296A6 Phase 3 is not connected. Diagnostic data: {hex}

Bit pattern 0b0010 indicates that phase 3 is not connected

Make sure all Motor phases are connected correctly. Contact your local Universal Robots service provider for assistance.

C296A7 Motor test results were invalid. Diagnostic data: {hex}

Bit0 high indicates short circuit. Bit1 is phase 3 test. Bit2 is phase 2 test. Bit3 is phase 1 test

Make sure all Motor phases are connected correctly. Contact your local Universal Robots service provider for assistance.

C296A9 Robot Voltage was present during self-diagnostics

Robot Voltage rose above acceptable levels before both processors powered it on

Contact your local Universal Robots service provider for assistance.

C296A10 Time out during self-diagnostics

A processor timed out while waiting for the other processor to finish self-diagnotics

Contact your local Universal Robots service provider for assistance.

C296A11 Data was received while trying to disable communication

A validation that theof communication could be suppressioned failed to preventin preventing a message from passing through.

Contact your local Universal Robots service provider for assistance.

C296A12 Sequence number did not match expected sequence

After communication was disabled and reenabled the sequence number did not match what was expected

Contact your local Universal Robots service provider for assistance.

C296A15 Interval between messages did not match expectations

After communication was disabled and reenabled the message interval did not match what expectations

Contact your local Universal Robots service provider for assistance.

C296A23 Cross-monitoring data was invalid for too long while booting

uB timed out while waiting for cross-monitoring data to agree before changing from Booting to Idle state

Contact your local Universal Robots service provider for assistance.

C296A25 Diagnostics module was initialized with a NULL pointer, for a required callback function

Diagnostics module was initialized with a null pointer, for rotate com buffer callback

Contact your local Universal Robots service provider for assistance.

C296A33 Timeout while waiting for system to be ready to go to idle

Requirements for going to idle state were not met within the expected time frame

Contact your local Universal Robots service provider for assistance.

C296A36 The device initialization has failed.

The device initialization has failed. this can be caused by hardware failure

Try the following actions to see which resolves the issue: (A) Conduct a complete rebooting sequence, (B) Contact your local Universal Robots service provider for assistance.