C338 PROFIsafe

C338A0 Critical error

A critical error occured in the PROFIsafe logic

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

C338A1 A hard error was triggered by the Siemens Profisafe Driver with instance ID {unsigned}

C338A2 A hard error was triggered by the Siemens Profisafe Driver at line number {unsigned}

C338A3 A hard error was triggered by the Siemens Profisafe Driver in file {unsigned}

C338A4 Invalid protocol version for PROFIsafe crosscommunication detected

C338A5 Invalid message length for PROFIsafe crosscommunication detected for msg id {unsigned}

C338A6 A PROFIsafe message was received, but there is no valid configuration

A PROFIsafe message was received before a valid safety configuration

Try the following actions to see which resolves the issue: (A) Verify the PROFIsafe Host settings and review the robot safety configuration, see PROFIsafe (B) Do not start a PROFIsafe host before the robot is ready (C) Conduct a complete rebooting sequence

C338A7 A PROFIsafe message was received and PROFIsafe was disabled.

A PROFIsafe message was received while PROFIsafe is disabled in the safety configuration

C338A8 The robot rejected the PROFIsafe F-Parameter set

A PROFIsafe F-Parameterset was received from the PLC but was not accepted

Try the following actions to see which resolves the issue: (A) Check the diagnosis messages from the PLC and set a valid F-Parameter configuration, (B) Conduct a complete rebooting sequence

C338A9 An error occured during param state with code {unsigned}

C338A10 An error occured during operational state with code {unsigned}

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