Error messages / troubleshooting KUKA System Software (KSS)

1 Fehlermeldungen en1 of 135 SOFTWAREKR messages / troubleshootingKUKA System Software (KSS)Issued: : 012 of 135 Fehlermeldungen eneCopyrightKUKA Roboter GmbHThis documentation or excerpts therefrom may not be reproduced or disclosed to third parties without the express permission of the functions not described in this documentation may be operable in the controller. The user has no claim to these functions, however, inthe case of a replacement or service have checked the content of this documentation for conformity with the hardware and Software described.

2 Nevertheless, discrepanciescannot be precluded, for which reason we are not able to guarantee total conformity. The information in this documentation is checked on aregular basis, however, and necessary corrections will be incorporated in subsequent to technical alterations without an effect on the Interleaf3 of 135 Fehlermeldungen enContents1 Error messages / of Error messages / troubleshooting4 of 135 Fehlermeldungen en1 Error messages / troubleshootingMessages of all categories are displayed in the message window.

3 These can be eitherinformative messages that do not need to be acknowledged or messages that have to message consists of the following items of information, for example:Message groupMessage timeMessage numberOriginatorMessage textACTIVE COMMANDS INHIBITEDCOMMAND ACCELERATION EXCEEDED Message groupsHint messagesprovide the operator with explanatory information, for example, if an illegal key has messagessignal the status of thesystem thathas led to a control reaction, Emergency Stop. Themessage is cleared once its cause has been eliminated.

4 In some cases, a secondary signalthat has to be acknowledged is set for reasons of messagesindicate a situation that must in all instances be recognized and acknowledged with theacknowledge key. They are often a consequence of a status (operational) message. Anacknowledgement message stops a movement or prevents further messagesrequire confirmation by the operator ( Yes or No softkeys). The message is cleared afterit has been Message timeThe message time indicates the time at which the message was Error messages / troubleshooting (continued)

5 5 of 135 Fehlermeldungen Message numberWiththeaidof themessagenumber, thecorrespondingcause, effect andremedy canquicklybe located in the list of Error OriginatorThe origin of the Error is indicated in this Message textThe text of the Error message is shown List of Error messagesTo make it easier to find Error messages in the following list, the message number is shownfirst, unlike on the display. By referring to this message number, it is possible to obtain furtherinformation on an Error and the appropriate remedial action.

6 This information is subdividedinto:Message textis the actual text of the Error message as a detailed description of the cause of the when the conditions for generation of the message are how the controller reacts to the what action the user can take to eliminate the messages / troubleshooting6 of 135 Fehlermeldungen en1 Message textEMERGENCY STOPC ause-- Emergency Stop pushbutton Emergency Stop initiated by the Path--maintaining All active commands Check the Emergency Stop pushbutton and Emergency Stop Release the Emergency Stop Rectify

7 And acknowledge the signalled textInternal errorCause-- Internal KRL Software Within the KRL All active commands Acknowledge textMESSAGE BUFFER OVERFLOWC ause-- The message buffer, which contains the currently active messages (acknowledgement and status messages ), is full up to a specific Ramp--down All active commands Rectify and acknowledge the signalled textBUFFER BATTERY VOLTAGE LOW xxCause-- Voltage of the backup battery too At Power off .-- The battery voltage is checked when the power is switched off.

8 Whenthe message is displayed, it is necessary to wait until the battery hasrecharged. Only then may the controller be switched Cyclic --> Change the After the battery has been charged, the message Ackn. batt. voltage is displayed --> textMalfunction <HPU or RCP>Cause-- KCP Ramp--down All active commands Replace Error messages / troubleshooting (continued)7 of 135 Fehlermeldungen en6 Message textTransmission Error <HPU or RCP>Cause-- Fault in KCP Ramp--down All active commands Check the KCP textTPBASISC ause-- The point could not be created8 Message textSystem time invalidCause-- The System time is invalid after TIME_HW_FAILURE and has beenset to the initial When the controller is The System time is initialized with 00:00:00, Update the System time with the form systime.

9 9 Message textMFC overtemperatureCause-- The temperature sensor on the MFC has been Path--maintaining Check fan. Exchange MFC if textERROR DIGITAL OUTPUTS @P1@Cause-- Short circuit at outputs 1--8 or Maximum textPROGRAM STACK OVERFLOWC ause-- KRL program contains too many nested structures or too many recur-sive subprogram calls! The C--stack of the R--INT would In program Ramp--down Change the structure of the textTOO MANY MESSAGESC ause-- Too many messages havebeen cyclically When a message is All active commands are cancelled and cannot be The KRC has to be messages / troubleshooting8 of 135 Fehlermeldungen en13 Message textERROR SAFETY LOOPC ause-- A channel has failed or more than one enabling switch has Path--maintaining braking, active commands textSOFTPLC.

10 @P1@Cause--Monitor--Effect--Remedy--15 Message textOUTPUT MONITORING DC BUS VOLTAGE KPS: @P1@Cause-- DC bus voltage of a KPS textError while reading O file Cause-- Error during loading/reading of : memory or file not In the write function w_ident_state .Effect-- Jump to the end in load data Copy the file to the directory /ir_spec/l_ident ,or increasememory by changing thevalue VxWinRAM in textWRONG/UNKNOWN HARDWARE FOUNDC ause-- During setup, the wrong control hardware (KR C1, KR C1A, KR C2)was selected or the hardware configuration is The controller is Robot traversing not Carry out setup again or make appropriate changes tohardware textServobus DSE--No.