库卡机器人kuka---故障信息与故障处理

1、Systemmeldungen 05.03.01 en1 of 322 SOFTWARE KR C. System Messages KUKA System Software (KSS) Issued: 18 May 2006Version: 01 2 of 322Systemmeldungen 05.03.01 en e CopyrightKUKA Roboter GmbH Thisdocumentationorexcerptstherefrommaynotbereproduced ordisclosed tothird partieswithout theexpress permissionof thepublishers. Other functions not described in this documentation may be operable in the controller. The user has no claims to these functions, however, in the case of a replacement or service wo

2、rk. We have checked the content of this documentation for conformity with the hardware and software described. Nevertheless, discrepancies cannot be precluded, for which reason we are not able to guarantee total conformity. The information in this documentation is checked on a regular basis, however, and necessary corrections will be incorporated in subsequent editions. Subject to technical alterations without an effect on the function. 3 of 322Systemmeldungen 05.03.01 en Contents 1System messag

3、es4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Messages 4 of 322 Systemmeldungen 05.03.01 en 3 1System messages This table contains an overview of the system messages that can be displayed in the mes- sage window of the graphical user interface. A system message consists of the following items of information: 12:18:021342Work envelope exceededKCP C. TimeNo.SourceMessage 12:18:031376KCPActive commands inhibited Message group Message time

4、Message number Originator of the message Message text Message group The message group is the category to which a system message belongs. It is represented by a small icon. Notification message Notificationmessagescontaininformationorindicateoperatoractions, programming errors and operator errors. Notification messages are purely for information purposes and do not interrupt program execution. Status message Status messages indicate the status of the system. Status messages are also informational

5、 in character, but can interrupt the application program to a certain extent. A status message is automatically deleted as soon as the status that triggered the message is no longer applicable. Acknowledgment message These frequently appear following a status message (e.g. “EMERGENCY STOP”) and must be confirmed by means of a softkey. An acknowledgment message may interrupt an application program or disable jog mode. It indicates disruption to program execution. Dialog message The operator must

6、respond to these messages using a softkey. A dialog message stopsarunningprogram.Itisautomaticallydeletedwhenoneofthesoftkeysoffered is pressed. The program is then resumed. 1System messages (continued) 5 of 322Systemmeldungen 05.03.01 en Message time The message time indicates the system time at which the message was generated. Message number Withtheaidofthemessagenumber,thecorrespondingcause,effectandany available remedy can quickly be located in the list of system messages. Originator of the

7、message The module responsible for the system message is indicated in this column. Message text The active system message is described here in greater detail. Please note: Each system message is most easily found using the message number. For this purpose, all the messages have been arranged here in a tabular structure. 1EMERGENCY STOP Message number Message textType of message Cause Describes the reason for the current system message. Describes the response of the controller when the system mes

8、sage in question is generated. Describes the remedial measure(s) that can be takento eliminate the problem. Effect Remedy Lines are only included in the table where necessary. When a message is generated, placeholders such as “” are replaced with relevant values. System Messages 6 of 322 Systemmeldungen 05.03.01 en 1 EMERGENCY STOP Cause EMERGENCY STOP button pressed. EMERGENCY STOP circuit broken. EMERGENCY STOP triggered by program. Effect Path-maintaining braking. All active commands inhibite

9、d. Remedy Release the EMERGENCY STOP pushbutton. Check EMERGENCY STOP pushbutton and EMERGENCY STOP cir- cuit. Rectify and acknowledge the signalled fault. 2 Internal error CauseInternal test of KRC software. Effect Ramp-down braking. All active commands inhibited. RemedyAcknowledge message. 3 Message buffer overflow Cause The message buffer containing the messages that are currently active (acknowledgement and status messages) has reached a certain capacity limit. Effect Ramp-down braking. All active commands inhibited. RemedyRectify and acknowledge the signalled faults. 4 Buffer battery voltage low CauseThe voltage of the backup battery is too low. Effect Next time the controller is switched off, it will no longer be possible to write completely to the hard disk the robot data that need to be saved. RemedyExchange the battery. 1System messages (continued) 7 of 322Systemmeldungen 05.03.01 en 5 Malfunction CauseKCP defective. Effect Path-maintaining braking. All active commands inh

《库卡机器人kuka---故障信息与故障处理》由会员suns****4568分享，可在线阅读，更多相关《库卡机器人kuka---故障信息与故障处理》请在金锄头文库上搜索。