C297 Joint validation

C297A0 Critical error

A critical error occurred during Joint validation

Try the following actions to see which resolves the issue: (A) Conduct a complete rebooting sequence, (B) Check that SD card and robot type match, (C) Update software

C297A1 Received Node ID from an unexpected device ({unsigned})

The Safety Control Board received a message from a device other than A or B

Try the following actions to see if it resolves the issue: (A) Conduct a complete rebooting sequence, (B) Ensure that the robot configuration is correct, (C) Update software

C297A2 Received Node ID an unexpected node ({unsigned})

The Safety Control Board received a message from a node outside the expected range of Node IDs.

Try the following actions to see if it resolves the issue: (A) Conduct a complete rebooting sequence, (B) Ensure that the robot configuration is correct, (C) Update software

C297A3 Joint processors disagree on Joint Size ({hex})

There is a mismatch between the Joint Size reported from A and B. byte0: A, byte1: B

 

C297A4 Joints disagree with configuration on Joint Size ({hex})

There is a mismatch between the Joint Size and the configuration, byte0: Joint, byte1: Configuration

Try the following actions to see if it resolves the issue: (A) Conduct a complete rebooting sequence, (B) Ensure that the robot configuration is correct, (C) Update software

C297A5 Found ({unsigned}) Joint disabled in configuration

There is a mismatch between joints attahced and the configuration

Try the following actions to see if it resolves the issue: (A) Conduct a complete rebooting sequence, (B) Ensure that the robot configuration is correct, (C) Update software

C297A6 Joint processors disagree on Joint ID. Diagnostic data: {hex}

There is a mismatch between reported Node ID from A and B, byte0: A, byte1: B

Try the following actions to see if it resolves the issue: (A) Conduct a complete rebooting sequence, (B) Run Joint ID assignment, (C) Update software.

C297A7 Node ID differs from the stored ID. Diagnostic data: {hex}

There is a mismatch between current Node ID and the expected ID, byte0: Current, byte1: Stored

Try the following actions to see if it resolves the issue: (A) Conduct a complete rebooting sequence, (B) Run Joint ID assignment, (C) Update software

C297A8 Invalid robot configuration

The robot does not match Robot Configuration

Try the following actions to see if it resolves the issue: (A) Conduct a complete rebooting sequence, (B) Ensure that the robot configuration is correct, (C) Update software

C297A9 Joint IDs need updating

The stored Node ID differs from the current ID on one or more joints and needs to be updated

Try the following actions to see if it resolves the issue: (A) Conduct a complete rebooting sequence, (B) Run Joint ID assignment, (C) Update software

C297A10 Timeout while waiting for Node IDs

One or more of the configured devices are not responding with Node IDs

Try the following actions to see if it resolves the issue: (A) Conduct a complete rebooting sequence, (B) Ensure that the robot configuration is correct, (C) Update software

C297A11 The Robot arm does not match the Control Box

One or more joints do not match stored Robot Configuration

Try the following actions to see if itresolves the issue: (A) Conduct a complete rebooting sequence, (B) Check that SD card and robot type match, (C) Update software

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