C306 Joint

C306A0 Critical error

A critical error occurred in a Joint

Try the following actions to see which resolves the issue: (A) Conduct a complete rebooting sequence, (B) Update software

C306A1 Not stopping fast enough

Joint was unable to come to a full stop fast enough.

Try the following actions to see which resolves the issue: (A) Either an incorrect payload is mounted, or an external force is pushing the robot, (B) Conduct a complete rebooting sequence, (C) Update software

C306A2 Velocity failed to pass sanity check

C306A3 Acceleration failed to pass sanity check

C306A4 Joint does not have a stored id

Joint was unable to locate an assigned id, most likely because it has never been used in a robot.

New Joint ID assignment should happen aautomatically

C306A5 Joint ID could not be stored

Something went wrong while trying to store the Joint ID, new ID verification will be needed.

Try the following actions to see which resolves the issue: (A) Conduct a complete rebooting sequence, (B) Update software

C306A6 control-package sequence number mismatched with expected sequence number

C306A7 {unsigned} instances of mismatched control-package sequence numbers within last second

C306A8 Sanity check of control-package sequence numbers recovered after detecting {unsigned} bad sequence numbers

C306A9 Joint moved more than allowable limit

Potential mechanical failure of the joint's brakes

Try the following actions to see which resolves the issue: (A) Conduct a complete rebooting sequence, (B) Update software

C306A10 Current detected in motor exceeded limits, current was {float}A

C306A11 PWM duty cycle for motor phase A is {float}

C306A12 PWM duty cycle for motor phase B is {float}

C306A13 PWM duty cycle for motor phase C is {float}

If you are unable to resolve the issue, login or create an account at http://myUR.universal-robots.com and post a new ticket