This documentation or excerpts therefrom may not bereproduced or disclosed to third parties without the express permission of the publishers.
Other functions not described in this documentation may be operable in the controller. The user has no claim to these functions, however, in
the case of a replacement or service work.
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.
1.6List of error messages5..........................................................
Fehlermeldungen 09.02.01 en
3 of 135
Error messages / troubleshooting
1Error messages / troubleshooting
Messages of all categories are displayed in the message window. These can be either
informative messages that do not need to be acknowledged or messages that have to be
acknowledged.
A message consists of the following items of information, for example:
Message group
Message time
Message number
Originator
Message text
COMMAND ACCELERATION EXCEEDED A2
ACTIVE COMMANDS INHIBITED
1.1Message groups
Hint messages
provide the operator with explanatory information, for example, if an illegal key has been
pressed.
Operational messages
signal the status of the system that has led to a control reaction, e.g. Emergency Stop. The
message is cleared once its cause has been eliminated. In some cases, a secondary signal
that has to be acknowledged is set for reasons of safety.
Acknowledgement messages
indicate a situation that must in all instances be recognized and acknowledged with the
acknowledge key. They are often a consequence of a status (operational) message. An
acknowledgement message stops a movement or prevents further operation.
Dialog messages
require confirmation by the operator (“Yes” or “No” softkeys). The message is cleared after
it has been confirmed.
1.2Message time
The message time indicates the time at which the message was generated.
4 of 135
Fehlermeldungen 09.02.01 en
1.3Message number
With the aid of the message number, the corresponding cause, effect and remedy can quickly
be located in the list of error messages.
1.4Originator
The origin of the error is indicated in this field.
1.5Message text
The text of the error message is shown here.
1.6List of error messages
To make it easier to find error messages in the following list, the message number is shown
first, unlike on the display. By referring to this message number, it is possible to obtain further
information on an error and the appropriate remedial action. This information is subdivided
into:
1Error messages / troubleshooting (continued)
Message text
is the actual text of the error message as displayed.
Cause
gives a detailed description of the cause of the error.
Monitor
indicates when the conditions for generation of the message are checked.
Effect
describes how the controller reacts to the error.
Remedy
describes what action the user can take to eliminate the error.
Fehlermeldungen 09.02.01 en
5 of 135
Error messages / troubleshooting
1Message textEMERGENCY STOP
Cause-- Emergency Stop pushbutton pressed.
-- Emergency Stop initiated by the software.
Monitor-- Cyclic.
Effect-- Path--maintaining stop.
-- All active commands inhibited.
Remedy-- Check the Emergency Stop pushbutton and Emergency Stop circuit.
-- Release the Emergency Stop pushbutton.
-- Rectify and acknowledge the signalled fault.
2
Message textInternal error
Cause-- Internal KRL software test.
Monitor-- Within the KRL software.
Effect-- All active commands inhibited.
Remedy-- Acknowledge message.
3
Message textMESSAGE BUFFER OVERFLOW
Cause-- The message buffer, which contains the currently active messages
(acknowledgement and status messages), is full up to a specific limit.
Monitor-- Cyclic.
Effect-- Ramp--down braking.
-- All active commands inhibited.
Remedy-- Rectify and acknowledge the signalled faults.
4
Message textBUFFER BATTERY VOLTAGE LOW xx
Cause-- Voltage of the backup battery too low.
Monitor-- At “Power off”.
-- Cyclic.
Effect-- The battery voltage is checked when the power is switched off. When
the message is displayed, it is necessary to wait until the battery has
recharged. Only then may the controller be switched off.
-- Cyclic --> none.
Remedy-- Change the battery.
-- After the battery has been charged, the message “Ackn. batt. voltage”
is displayed --> acknowledge.
5
Message textMalfunction <HPU or RCP>
Cause-- KCP defective.
Monitor-- Cyclic.
Effect-- Ramp--down braking.
-- All active commands inhibited.
Remedy-- Replace KCP.
6 of 135
Fehlermeldungen 09.02.01 en
1Error messages / troubleshooting (continued)
6Message textTransmission error <HPU or RCP>
Cause-- Fault in KCP connection.
Monitor-- Cyclic.
Effect-- Ramp--down braking.
-- All active commands inhibited.
Remedy-- Check the KCP cable.
7
Message textTPBASIS
Cause-- The point could not be created
8
Message textSystem time invalid
Cause-- The system time is invalid after TIME_HW_FAILURE and has been
set to the initial value.
Monitor-- When the controller is booted.
Effect-- The system time is initialized with 01.01.93 00:00:00,00.
Remedy-- Update the system time with the form “systime”.
9
Message textMFC overtemperature
10
11
12
Cause-- The temperature sensor on the MFC has been triggered.
Monitor-- Cyclic.
Effect-- Path--maintaining braking.
Remedy-- Check fan. Exchange MFC if necessary.
Message textERROR DIGITAL OUTPUTS @P1@
Cause-- Short circuit at outputs 1--8 or 9--16.
Monitor-- Cyclic.
Effect-- Maximum braking.
Remedy--
Message textPROGRAM STACK OVERFLOW
Cause-- KRL program contains too many nested structures or too many recur-
sive subprogram calls! The C--stack of the R--INT would otherwise
overflow.
Monitor-- In program processing.
Effect-- Ramp--down braking.
Remedy-- Change the structure of the program.
Message textTOO MANY MESSAGES
Fehlermeldungen 09.02.01 en
Cause-- Too many messages have been cyclically generated.
Monitor-- When a message is generated.
Effect-- All active commands are cancelled and cannot be restarted.
Remedy-- The KRC has to be booted.
7 of 135
Error messages / troubleshooting
13Message textERROR SAFETY LOOP
Cause-- A channel has failed or more than one enabling switch has been
pressed.
Monitor-- Cyclic.
Effect-- Path--maintaining braking, active commands inhibited.
Remedy--
14
Message textSOFTPLC: @P1@
Cause--
Monitor--
Effect--
Remedy--
15
Message textOUTPUT MONITORING DC BUS VOLTAGE KPS: @P1@
Cause-- DC bus voltage of a KPS overloaded.
Monitor--
Effect--
Remedy--
16
Message textError while reading “O file”
17
18
Cause-- Error during loading/reading of “ident_vx.o”: memory or file not found.
Monitor-- In the write function “w_ident_state”.
Effect-- Jump to the end in load data program.
Remedy-- Copy the file “ident_vx.o” to the directory “/ir_spec/l_ident”,
or increase memory by changing the value “VxWinRAM” in the registry.
Message textWRONG/UNKNOWN HARDWARE FOUND
Cause-- During setup, the wrong control hardware (KR C1, KR C1A, KR C2)
was selected or the hardware configuration is invalid.
Monitor--
Effect-- The controller is inoperable.
-- Robot traversing not possible.
Remedy-- Carry out setup again or make appropriate changes to
Cause-- An unknown device which cannot be supported has been inserted in
Interbus
Monitor-- DSE ID, device ID
Effect-- The robot can no longer be traversed
Remedy-- Remove unknown device from servo bus
8 of 135
Fehlermeldungen 09.02.01 en
1Error messages / troubleshooting (continued)
19Message textFAILURE OF MOTOR PHASE <axis>
Cause-- Power module, intermediate circuit voltage discharged.
Monitor-- Cyclic.
Effect-- Dynamic braking.
-- All active commands inhibited.
Remedy-- Switch on drives.
-- Check power module, DSE.
20
Message textEXTERNAL EMERGENCY STOP PRESSED
Cause-- Emergency Stop button pressed.
-- Emergency braking triggered by software.
Monitor-- Cyclic.
Effect-- Path--maintaining braking.
-- All active commands inhibited.
Remedy-- Check the Emergency Stop pushbutton.
-- Rectify and acknowledge the signalled fault.
21
Message textSecond motorcable not connected
Cause-- Second motor cable is not connected or is incorrectly connected; the
additional cable contains two wires which are connected to the robot;
the return signal is connected to the KPS X114, pin 7
Monitor-- Cyclic.
Effect-- The robot cannot be traversed
Remedy-- Check second motor cable and return signal at KPS X114, pin 7
Fehlermeldungen 09.02.01 en
9 of 135
Error messages / troubleshooting
100Message textRDW ** BOOT UP FAILURE
Cause-- The resolver/digital converter (RDW) could not be initialized when
the controller was booted.
Monitor-- At runup.
Effect--
Remedy-- Replace RDW, DSE or cable between RDW and DSE.
101
Message textDSE ** BOOT UP FAILURE
Cause-- The DSE could not be initialized when the controller was booted.
Monitor-- At runup.
Effect-- Maximum braking (dynamic braking).
Remedy-- Replace DSE, MFC or motherboard.
102
Message textENCODER CABLE FAILURE **
Cause-- Cable defective (e.g. loose connection).
-- RDW defective.
-- Encoder defective.
Monitor-- Cyclic.
Effect-- Maximum braking (dynamic braking).
-- Low signal at “$ALARM_STOP” output.
-- All active commands inhibited.
Remedy-- Check encoder cable.
-- Check motor, resolver.
-- Possibly replace RDW.
103
Message textWATCHDOG INTERPOLATION CYCLE **
104
Cause-- DSE has not triggered software watchdog in the DP--RAM.
Monitor-- Cyclic.
Effect-- Maximum braking.
-- Low signal at “$ALARM_STOP” output.
-- All active commands inhibited.
Remedy-- Replace DSE or MFC.
-- Software error.
Message textSYNCHRONIZATION ERROR WITH DSE **
Cause-- DSE has not received feed command value for 1 interpolation cycle
although servo--control is active.
Monitor-- Cyclic.
Effect-- Maximum braking.
-- Low signal at “$ALARM_STOP” output.
-- All active commands inhibited.
Remedy-- Error in the DSE or PC area.
-- Software error.
10 of 135
Fehlermeldungen 09.02.01 en
1Error messages / troubleshooting (continued)
105Message textTRANSMISSION ERROR DSE -- RDW **
Cause-- Open--circuit between RDW and DSE.
-- Transmission malfunctions.
Monitor-- Cyclic.
Effect-- Maximum braking.
-- Low signal at “$ALARM_STOP” output.
-- All active commands inhibited.
Remedy-- Check shielding of encoder cable.
-- Check serial interface DSE--RDW.
106
Message textPERFORM MASTERING ** !
Cause-- Position actual value difference after restart too great and sensor
mastering not possible because sensor location run has not been
performed.
Monitor-- At “Power on”.
-- During mastering.
Effect-- All active commands inhibited.
Remedy-- Perform mastering.
107
Message textEMERGENCY STOP DUE TO DIAL ADJUSTMENT
108
109
Cause-- Softkeys for dial adjustment pressed.
-- Value assignment “$TURN = 1”.
-- Encoder setting, absolute or incremental.
Monitor-- When “$TURN” instruction is executed.
Effect-- Dynamic braking.
-- 0 signal at “$ALARM_STOP” output
-- All active commands inhibited.
Remedy-- Leave the mastering menu by pressing the Recall key twice.
Message textDYNAMIC BRAKING ACTIVE
Cause-- If the controller detects a request for maximum (dynamic) braking, it
geneates the status (operational) message “DYNAMIC BRAKING
ACTIVE”, which remains active until all axies have stopped.
Monitor-- Cyclic.
Remedy-- The status message “DYNAMIC BRAKING ACTIVE” is reset by the
controller when the robot is at standstill without a secondary message
being generated.
Message textCLEAR FAST MEASURING INPUT @P1@
Cause-- Rapid gauging has been switched on.
Monitor-- During rapid gauging.
Effect-- Rapid gauging becomes active when measuring tool has been
moved free.
Remedy-- Move measuring tool free.
Fehlermeldungen 09.02.01 en
1 1 of 135
Error messages / troubleshooting
110Message textADVANCED PATH PROFILE NOT POSSIBLE WITH LINKED EXTER-
NAL AXES
Cause-- Coupling of external axes in higher motion profile.
Monitor-- During command and program execution.
Effect--
Remedy--
111
Message textTEPRO INACTIVE
Cause-- SBC no longer sending a signal to KRC.
Monitor-- Cyclic.
Effect-- SBC interface inoperable.
Remedy-- Re--initialize SBC program.
112
Message textINVALID $TOOL: WORKING ENVELOPE SURVEILLANCE NOT
POSSIBLE
Cause-- “$TOOL” invalid when working envelope monitoring is activated.
Monitor-- Cyclic.
Effect-- None.
Remedy-- Assign “$TOOL” or switch off working envelope monitoring.
113
Message textRANGE OVERFLOW ** **
114
115
Cause-- Overflow of the actual value of an endless axis: actual value > +/--
90*10E15 increments or --99999000 < $REVO_NUM < 999999000
Monitor-- Cyclic in the interpolation cycle.
Effect-- Path--maintaining Emergency Stop.
Remedy-- Turn back or remaster the axis concerned.
Message textWORKING ENVELOPE NO. @P1@ VIOLATED
Cause-- TCP is inside a working envelope with MODE INSIDE STOP or outside
a working envelope with MODE OUTSIDE STOP.
Monitor-- Cyclic.
Effect-- Path--maintaining braking;
-- All active commands inhibited.
Remedy-- Switch off working envelope or use key on the KCP to override work
envelope monitoring, move free in T1 mode.
Message textDRIVE FREE WORK ENVELOPE %1
Cause-- TCP is inside a working envelope with
MODE INSIDE STOP or outside a working envelope with MODE
OUTSIDE STOP and the working envelope monitoring is overridden.
Monitor-- Cyclic.
Effect--
Remedy-- Free work envelope.
12 of 135
Fehlermeldungen 09.02.01 en
1Error messages / troubleshooting (continued)
116Message textDSE WATCHDOG COMMAND **
Cause-- DSE has not executed a command.
Monitor
Effect-- Ramp--down braking.
Remedy-- Check hardware in the DSE, MFC area.
117
Message textTORQUE EXCEEDED AXIS @P1@
Cause
Monitor
Effect
Remedy
118
Message textHEAT SINK TEMPERATURE **
Cause-- Thermostatic switch on the heat sinks of the servo output stage is
tripped due to overheating of the output stage transistors.
Monitor-- Cyclic.
Effect-- Ramp--down braking. Program processing stopped.
Remedy-- Eliminate the fault and reset it by pressing the acknowledge key on the
KCP.
-- Clean the heat sinks.
119
Message textMOTOR TEMPERATURE **
120
121
Cause-- PTC thermistor (measuring shunt) in the motor winding has been
tripped (motor temperature too high).
Monitor-- Cyclic.
Effect-- Ramp--down braking. Program processing stopped.
Remedy-- Eliminate the fault and reset it by pressing the acknowledge key on the
KCP.
-- Program more movement breaks.
Message textACKN. MOTOR BLOCKED **
Cause-- As soon as the torque command value supplied by the speed controller
exceeds 30% of the max. torque command value, integration is
started, and when the value of i*t reaches approx. 0.75 [(torque
command value / max. torque command value) * sec] the control is
switched off (i*t -- monitoring).
Monitor-- Cyclic.
Effect-- Ramp--down braking. Program processing stopped.
Remedy-- Eliminate the fault and reset it by pressing the acknowledge key on the
KCP.
-- Check that the axis is moving freely.
Message textOVERCURRENT **
Cause-- The current of each axis is monitored and the amplifier--internal current
protection is tripped if the power consumption is too high.
Monitor-- Cyclic.
Effect-- Ramp--down braking. Program processing stopped.
Fehlermeldungen 09.02.01 en
13 of 135
Error messages / troubleshooting
Remedy-- Eliminate the fault and reset it by pressing the acknowledge key on the
122
Message textBRAKE FAULT **
Cause-- The brake cable is monitored for short--circuit, overload and cable
Monitor-- Cyclic.
Effect-- Ramp--down braking. Program processing stopped.
Remedy-- Eliminate the fault and reset it by pressing the acknowledge key on the
123
MeldungstextUNDERVOLTAGE <axis number>
Cause-- The internal operating voltage (+15V) of the servo output stage is
Monitor-- Cyclic.
Effect-- Ramp--down braking. Program processing stopped.
Remedy-- Eliminate the fault and reset it by pressing the acknowledge key on the
124
Message textOVERVOLTAGE <power module number>
KCP.
break.
-- With the PM6, all axes are supplied from one brake driver.
KCP.
monitored. Undervoltage results in power failure.
KCP.
125
126
127
Cause-- The intermediate--circuit voltage is too high. Possible causes are a de-
fective ballast (feedback) resistor or ballast fuse, a defective power
module, brake ramp too steep etc.
Monitor-- Cyclic.
Effect-- Ramp--down braking. Program processing stopped.
Remedy-- Eliminate the fault and reset it by pressing the acknowledge key on the
KCP.
Message texti2--t MONITORING, CURRENT LIMIT OF THE MOTOR CABLE
<string1> AFTER <string2> s EXCEEDED 100%
Cause-- Axis overloaded. The value for the maximum permissible limit current
is specified in the machine data by “$CURR_MON[]”.
Monitor-- Cyclic.
Effect-- Ramp--down braking, active commands inhibited.
Cause-- The drives contactor drops out. The energy in the intermediate circuit
is sufficient to ensure a path--maintaining stop. Caution: the
intermediate circuit is still charged! The intermediate circuit is
discharged after about 2 minutes. The message “DRIVES NOT
READY” is then displayed.
Monitor-- Cyclic.
Effect-- Path--maintaining Emergency Stop
Remedy-- Switch drives on again.
-- Check drives circuit for faults.
221
Message textMODE NOT ALLOWED
Cause-- E2 keyswitch in AUTO mode.
Monitor
Effect
Remedy
222
Message textPARITY ERROR POWERMODULE **
223
224
225
Cause-- A parity error has occurred more than five times in succession when
reading the power module register.
Monitor-- Cyclic.
Effect-- Ramp--down braking.
Remedy-- Too much interference at the power module interface, or power module
defective. Check cable, check shielding, replace power module.
Message textPOWER MODULE AXIS ** NOT OR WRONGLY PLUGGED
Cause-- The axis is incorrectly plugged into the power module or not connected
at all.
Monitor-- At runup.
Effect-- Active commands inhibited.
Remedy-- Connect the axis correctly (high or low power).
Message textPOWER FAIL
Cause-- The cabinet voltage has been switched off, the mains voltage is
interrupted.
Monitor
Effect-- Path--maintaining Emergency Stop, buffering of the mastering data,
saving all data on HDD.
Remedy-- Check the mains voltage.
Message textMOTOR CABLE **
22 of 135
Cause--
Monitor--
Effect--
Remedy--
Fehlermeldungen 09.02.01 en
1Error messages / troubleshooting (continued)
226Message textFAILURE OF HEAT SINK TEMPERATURE SENSOR **
Cause--
Monitor--
Effect--
Remedy--
227
Message textFAILURE OF CABINET INTERIOR TEMPERATURE SENSOR <AXIS
NUMBER>
Cause--
Monitor--
Effect--
Remedy--
228
Message textDRIVES PARAMETER DATA ** INVALID
Cause--
Monitor--
Effect--
Remedy--
229
Message textFAILURE OF MOTOR TEMPERATURE SENSOR <AXIS NUMBER>
Cause-- Machine datum $IFACE_DRV[6] has been assigned twice to a drive
interface, or a non--existent interface has been addressed.
-- KTL encoders have been entered in IFACE_DRV[6] without connecting APC interfaces, or ADAR axes have been entered in $ADAR_AXIS
without connecting ADAR interfaces.
Monitor-- At “Power on”.
-- After editing the machine data.
-- After loading the machine data.
Effect-- No RC ready.
Remedy-- Correct the machine datum.
254
Message textDSE FILE <program name> NOT AV AILABLE
Cause-- The DSE program entered in the RD_HWINF.INI file does not exist.
Monitor
Effect
Remedy-- Enter or alter the DSE program.
255
Message text<$ variable> INVALID VALUE
256
Cause-- The machine data loader has detected that a variable contains an
incorrect value:
a) Limit monitoring tripped.
b) Machine data not logically coherent.
Monitor-- At “Power on”.
-- After editing the machine data.
-- After loading the machine data.
Effect-- No RC ready.
Remedy-- Correct the value assignment.
Message textCHECK MACHINE DATA !
Cause-- It cannot be assured that the machine data loaded during a cold
start are valid for the connected robot.
Monitor-- Generated at cold start.
Effect-- No RC ready.
-- Controller is in its initial state, i.e. tasks dependent on machine data
are not generated.
Remedy-- Either edit or copy the machine data or option data file.
Fehlermeldungen 09.02.01 en
27 of 135
Error messages / troubleshooting
257Message textERRONEOUS USER DATA
Cause-- The user data loader has detected that a variable contains an incorrect
value:
a) Limit monitoring tripped.
b) Data not logically coherent.
Monitor-- At “POWER ON”.
-- After editing the user data.
-- After loading the user data (DEFDAT $CUSTOM PUBLIC).
Effect-- No RC ready.
Remedy-- Correct value assignment of the indicated variable.
258
Message textERRONEOUS OPTION DATA
Cause-- The option data loader has detected that a variable contains an incor-
rect value:
a) Limit monitoring tripped.
b) Data not logically coherent.
Monitor-- At “POWER ON”.
-- After editing the option data.
-- After loading the option data (DEFDAT $OPTION PUBLIC).
Effect-- No RC ready.
Remedy-- Correct value assignment of the indicated variable.
259
Message text** MACHINE DATA LOADER ABORTED
260
Cause-- The errors detected by the machine data loader exceed the capacity
of the message buffer.
Monitor-- At “POWER ON”.
-- After editing the machine data.
-- After loading the machine data.
Effect-- No RC ready.
Remedy-- Correct value assignment of the indicated variable.
Message textUSER DATA LOADER ABORTED
Cause-- The errors detected by the user data loader exceed the capacity of
the message buffer.
a) Limit monitoring tripped.
b) Data not logically coherent.
Monitor-- At “POWER ON”.
-- After editing the user data.
-- After loading the user data.
Effect-- No RC ready.
Remedy-- Correct value assignment of the indicated variable.
28 of 135
Fehlermeldungen 09.02.01 en
1Error messages / troubleshooting (continued)
261Message textOPTION DATA LOADER ABORTED
Cause-- The errors detected by the option data loader exceed the capacity of
the message buffer.
a) Limit monitoring tripped.
b) Data not logically coherent.
Monitor-- At “POWER ON”.
-- After editing the option data.
-- After loading the option data.
Effect-- No RC ready.
Remedy-- Correct value assignment of the indicated variable.
262
Message textERRONEOUS <path> MACHINE DATA
Cause-- The machine data loader has detected a variable with an illegal value.
a) Limit monitoring tripped.
b) Data not logically coherent.
Monitor-- At “POWER ON”.
-- After editing the machine data.
-- After loading the machine data.
Effect-- No RC ready.
263
Message textERRONEOUS CORRECTION DATA
264
265
Cause-- The correction data loader has detected a variable with an illegal value.
a) Limit monitoring tripped.
b) Data not logically coherent.
Monitor-- POWER ON after editing the correction data, after loading the
correction data (DEFDAT $ROBCOR).
Effect-- No RC ready.
Remedy-- Correct value assignment of the indicated variable.
Message text<path> CORRECTION DATA LOADER ABORTED
Cause-- The errors detected by the correction data loader exceed the capacity
of the message buffer.
Monitor-- At “POWER ON”.
-- After editing the correction data.
-- After loading the correction data.
Effect-- No RC ready.
Remedy-- Correct value assignment of the indicated variable.
Message textRDW FILE <program name> NOT AV AILABLE
Cause-- The RDW program entered in the RD_HWINF.INI file does not exist.
Monitor
Effect
Remedy-- Enter the RDW program correctly in the INI file.
Cause-- The ballast (feedback) resistor has overheated. In the motion program
the robot is cyclically accelerated and decelerated without a break.
Monitor-- Cyclic.
Effect-- Ramp--down braking.
Remedy-- Insert wait times into the program, reduce the acceleration.
267
Message textWATCHDOG POWER MODULE <power module number>
Cause-- The watchdog on the power module has dropped out. The watchdog
is triggered by the DSE every 0.125ms.
Monitor-- Cyclic.
Effect-- Dynamic braking.
Remedy-- Troubleshooting in the DSE and power module area.
268
Message textMEMORY TEST ERROR DSE <DSE number 1 --4>
Cause-- The memory test on the DP--RAM of the DSE detected an error.
Monitor-- Runup.
Effect-- Active commands inhibited.
Remedy-- Replace DSE or MFC.
269
Message textDSE <DSE number 1--4> NOT AVAILABLE
270
271
Cause-- The bit on the MFC indicating whether a DSE is inserted is not set
although axes are allocated to this DSE.
Monitor-- At runup.
Effect-- Active commands inhibited.
Remedy-- Insert DSE, replace MFC or DSE.
Message textINCORRECT POWER MODULE SETTING <axis>
Cause-- Double assignment of $PMCHANNEL or incorrect channel.
Monitor-- When loading the robot machine data.
Effect-- Machine data loader aborted.
Remedy-- Correct $PMCHANNEL.
Message textROBOT NO. ** DOES NOT CORRESPOND TO CALIBRATION FILE
**
Cause--
Monitor--
Effect--
Remedy--
30 of 135
Fehlermeldungen 09.02.01 en
1Error messages / troubleshooting (continued)
272Message textNO ROBOT NUMBER PROGRAMMED
Cause--
Monitor--
Effect--
Remedy--
273
Message textMORE THAN ONE CALIBRATION FILE AVAILABLE
Cause--
Monitor--
Effect--
Remedy--
274
Message textCheck robot number
Cause--
Monitor--
Effect--
Remedy--
275
Message textSET ROBOT NUMBER – PROGRAM ROBOT NAME
276
277
Cause--
Monitor--
Effect--
Remedy--
Message textWRONG MACHINE DATA FOR THIS ROBOT TYPE
Cause-- The machine data do not correspond to the robot type stored in the
robot base.
Monitor-- Run--up.
Effect--
Remedy-- Load the correct machine data.
-- Reprogram the robot type.
Message textAUTOMATIC REPOSITIONING
Cause-- $MOT_STOP_OPT = TRUE. Robot not on path.
In EXTERN, $MOT_STOP (flag that the robot is not on path) has
been set by the user (via the GUI) to FALSE, so that the robot automatically moves on path at process velocity.
Monitor--
Effect-- Only a message that the robot is moving on the path in EXTERN.
Remedy-- The message is deleted as soon as BCO is reached.
Fehlermeldungen 09.02.01 en
31 of 135
Error messages / troubleshooting
278Message textError Power Relay K1
Cause-- Correct program.
-- The contact in drive contactor K1 is stuck.
Monitor--
Effect-- Path--maintaining braking.
-- All active commands inhibited.
Remedy-- Change power module.
279
Message textFeedback switch too long on <KPS number> while charging
Cause--
Monitor--
Effect-- Maximum braking.
-- All active commands inhibited.
Remedy-- Check the hardware.
280
Message textOvervoltage <kps number> while charging
281
Cause--
Monitor--
Effect-- Maximum braking.
-- All active commands inhibited.
Remedy-- Check the hardware.
Message textCheck accumulator <kps number>
Cause-- Message comes directly from the KPS.
-- Accu voltage is under 19V.
-- The accu is not charged correctly anymore.
-- The accu is to old or broken.
Monitor--
Effect-- Eventually loss of reference.
-- Cold boot.
-- Active commands inhibited.
Remedy-- Exchange accu.
32 of 135
Fehlermeldungen 09.02.01 en
1Error messages / troubleshooting (continued)
282Message textUndervoltage <kps number> while charging
Cause-- Message comes directly from the KPS.
-- Intermediate circuit could not be charged correctly.
Monitor--
Effect-- Maximum braking.
-- All active commands inhibited.
Remedy-- Check supply voltages of KPS (especially three--phase current)
Cause-- An attempt was made to carry out BCO motion with START MINUS.
Monitor-- When START MINUS is pressed.
Effect-- The robot does not start.
Remedy-- Use START PLUS or set Implicit_BCO = TRUE in BACKWARD.INI.
1059
Message textFINISHED SUBROUTINE: SKIP MOTIONS
1060
1061
Cause-- During backward motion, the interpreter encounters a subprogram
which has already been completely executed.
Monitor-- Each time before backward motion is started.
Effect-- Active commands inhibited.
Remedy-- Acknowledge.
Message text$BWDSTART NOT IN FOLD. NO TOOL AND BASE INFORMATION
FOUND
Cause-- Backward motion in SCAN method: a $BWDSTART assignment must
be programmed as the first instruction in a motion fold. From this line
onwards, all following instructions up to the motion are executed before
backward motion is carried out.
Monitor-- Each time before backward motion is started.
Effect-- Active commands inhibited.
Remedy-- Correct program or set the entry BACKWARDSTART = FALSE in
BACKWARD.INI. In this case, however, BASE and TOOL changes
cannot be carried out during backward motion.
Message textRapid EMERGENCY STOP with fixed braking ramps
Cause-- In the event of EMERGENCY STOP with dynamic model, the fixed
braking ramp strategy is used as this brakes the robot significantly
more quickly
Monitor-- In the event of EMERGENCY STOP with dynamic model
Effect-- EMERGENCY STOP brakes the robot more quickly than the strategy
based on the dynamic model
Remedy-- Verify load data and correct if necessary
-- Verify machine data
Fehlermeldungen 09.02.01 en
45 of 135
Error messages / troubleshooting
1062Message textAckn. second motorcable not connected
Cause-- Second motor cable was not connected or was connected incorrectly
Monitor--
Effect--
Remedy-- Acknowledge message
1063
Message textAckn. over temperature feedback resistor %1
Cause-- The feedback resistor has got too hot
-- The robot is cyclically accelerated and braked in the motion program
without a pause
Monitor-- Cyclic.
Effect--
Remedy-- Acknowledge message
1064
Message textAckn.: over temperature fan %1
Cause-- One of the two fans in the cabinet is defective
Monitor-- Cyclic.
Effect-- Ramp--down braking
Remedy-- Acknowledge message
1065
Message textAckn. mainboard overtemperature
1066
1067
Cause-- The cabinet fan has failed
-- The ambient temperature is too high
Monitor-- Cyclic.
Effect--
Remedy-- Acknowledge message
Message textMainboard temperature reached warning level
Cause-- PC controller cooling is still sufficient, but could soon become critical
Monitor-- Cyclic.
Effect-- None
Remedy-- Check fan
-- Exchange fan filter
Message textMainboard temperature check not available
Cause-- Motherboard does not support temperature monitoring
Monitor--O n c e
Effect-- No monitoring
Remedy-- Exchange motherboard
-- Switch temperature monitoring off
46 of 135
Fehlermeldungen 09.02.01 en
1Error messages / troubleshooting (continued)
1068Message textINTERBUS: Watchdog Time expired!
Cause-- The Interbus driver read function was not called in the time defined
Monitor-- Cyclic.
Effect-- Inputs and outputs are not set
Remedy-- Terminate the Watchdog by reconfiguring the I/Os
-- De--energize controller board
-- Watchdog cycle time possibly set too low
-- Fault in the KRC system since the read function of the driver was not
called cyclically
1071
Message textMOTOR HOLDING TORQUE %1 EXCEEDED
Cause-- The motor holding torque of the axis is not sufficient to keep the robot
motion permanently stopped at a point.
Monitor-- Not cyclic, during path planning
Effect-- Interpreter stop
Remedy-- Correct or reduce load data
-- Verify machine data
1072
1073
Message textBRAKE HOLDING TORQUE %1 EXCEEDED
Cause-- The brake holding torque on the axis is not sufficient to keep the robot
motion permanently stopped at a point.
Monitor-- Not cyclic, during path planning
Effect-- Interpreter stop
Remedy-- Correct or reduce load data
-- Verify machine data
Message textCOMMANDED GEAR TORQUE %1
Cause-- Permissible gear torque exceeded, dependent on dynamic data
$DYN_DAT()
Monitor-- Cyclic.
Effect-- Path--maintaining braking
-- Output ”$ALARM_STOP” 0 signal
-- Active commands inhibited.
Remedy-- Verify load data and reduce if necessary, reduce programmed accel-
Message textACKN. HEATSINK TEMPERATURE <axis number: AX>
Cause-- A heat sink temperature fault is signalled by the DSE board if the
temperature exceeds 80 degrees.
Monitor-- Cyclic in the interpolation cycle.
Effect
Remedy-- Acknowledge message.
-- Clean heat sink.
Message textEMT MASTERING DISTANCE EXCEEDED
54 of 135
Cause-- Groove not located, axis position not before groove prior to start.
Monitor
Effect-- Axis stops.
Remedy-- Move axis into mastering position; check EMT and groove.
Fehlermeldungen 09.02.01 en
1Error messages / troubleshooting (continued)
1138Message textDYNAMIC BRAKING
Cause-- If during an activated Emergency Stop a fault occurs that permits only
maximum (dynamic) braking, this message is additionally displayed.
Monitor-- With the following messages: 100, 101, 102, 103, 104, 105, 110,
1 11, 114, 200, 202, 206, 1100, 1 108.
Effect-- Maximum braking.
Remedy-- Acknowledge message.
1139
Message textSYNACT NOT POSSIBLE <block number>
Cause-- The programming of synchronous actions with the variable $M_TIME
or $M_TIME_APO causes the message to be output when the
program is resumed after ramp--down braking, a path--maintaining
Emergency Stop ramp or maximum braking.
1140
Message textBLOCK CHANGE AT STOP
Cause-- Maximum braking or a path--maintaining stop and a simultaneous
block change which makes calculation of $POS_RET and the system
time impossible, with the result that the system time and $POS_RET
are determined by the beginning of a new block.
Monitor-- (e.g. cyclic; in command processing; in mastering).
Effect-- (e.g. ramp--down braking; program processing stopped; etc.).
Cause-- An attempt was made to carry out a sensor location search for an axis
on which initial mastering has not yet been performed.
Monitor-- When selecting the function “dat_ueb” for the corresponding axis.
Effect-- The sensor location search is not carried out.
Remedy-- Perform initial mastering (e.g. dial gauge or EMT mastering) for the
corresponding axis.
Message textINVALID AXIS COUPLING RATIO <axis number>
Cause-- An attempt was made to carry out “Extended sensor adjustment” for
an axis when the coupling axes are not in the same position as was
reported in the data transfer.
Monitor-- When selecting the function “Extended sensor adjustment” for the
corresponding axis.
Effect-- The function “Extended sensor adjustment” is not carried out.
Remedy-- Move coupling axes to the same position as in the data transfer.
Message textADJUSTMENT PROCEDURE NOT POSSIBLE <axis number>
Cause-- An attempt is made to carry out sensor adjustment or the axis is not
equipped with a KTL encoder and DSE.
Monitor-- When selecting the function “Extended sensor adjustment” for the
corresponding axis.
Effect-- The sensor adjustment is not carried out.
Remedy-- Cancel via Recall or master axis with EMT / dial gauge.
Message textDATA TRANSFER INVALID <axis number>
56 of 135
Fehlermeldungen 09.02.01 en
1151
1152
1153
1Error messages / troubleshooting (continued)
Cause-- An attempt is made to carry out a sensor location search for an axis
which is not equipped with a KTL encoder and DSE.
Monitor-- When selecting the sensor location search function for the correspond-
ing axis.
Effect-- The sensor location search for the axis is not carried out.
Remedy-- Cancel via Recall.
Message textPERFORM DATA TRANSFER <axis number>
Cause-- An attempt was made to carry out sensor adjustment for an axis on
which no sensor location search has been performed.
Monitor-- When selecting the function “Extended sensor adjustment” for the
corresponding axis.
Effect-- The function “Sensor location search” is not carried out.
Remedy-- Carry out sensor location search for the corresponding axis.
Message textDATA TRANSFER PERFORMED <axis number>
Cause-- The sensor location search has been properly carried out.
Monitor-- When the function “Sensor location search” for the corresponding
axis is selected and the Enter key is pressed.
Effect-- None.
Remedy--
Message textDEVIATION IN THE START POINT
1154
1155
Cause-- A PTP motion is to be executed with a sensor offset value.
Monitor-- Interpolator.
Effect-- Ramp--down braking.
Remedy-- Sensor offset must be eliminated before a PTP block is executed.
Message textSBC ERROR: <Watchd.,Transf.,Corr>
Cause-- Error in communication between SBC and KRC32.
Monitor-- Cyclic in the TEP task.
Effect-- Maximum braking.
Remedy-- Check SBC (SW, HW).
Message textAPPROXIMATION NOT POSSIBLE, TORQUE TOO HIGH
Cause-- For an approximate positioning block to be executed, the velocity must
already be reduced in the preceding block. However, this block is not
long enough to allow that.
Monitor-- Not cyclic, in motion planning.
Effect-- Interpreter.
Remedy-- Increase the length of the individual block by:
decreasing the approximate positioning radius at the end point of the
current motion block or, if the start point is approximated, by decreasing this approximate positioning radius.
Decreasing the velocity and acceleration of the individual block.
Fehlermeldungen 09.02.01 en
57 of 135
Error messages / troubleshooting
1156Message textAPPROX. NOT POSSIBLE INTERNAL ERROR IN PTP MOTION
PLAN
Cause-- Error in planning of the approximate positioning block.
Monitor-- Not cyclic, in motion planning.
Effect-- Approximate positioning is not executed; exact stop.
Remedy-- Modify profile data (rounding factor, velocity, acceleration). Please
consult KUKA.
1157
Message textOVERLOAD OF GEAR TORQUE <axis number> BY <percentage
value>
Cause-- The max. gear torque of the axis is statically exceeded by ....%.
Monitor-- Not cyclic, in motion planning.
Effect-- Interpreter stop.
Remedy-- Check load data (mass, center of gravity , moments of inertia).
1158
Message textSTATIC MOTOR TORQUE OVERLOAD <axis number> BY <percentage
value>
Cause-- The max. motor torque of the axis is statically exceeded by ....%.
Monitor-- Not cyclic, in motion planning.
Effect-- Interpreter stop.
Remedy-- Check load data (mass, center of gravity , moments of inertia).
1159
Message textINTERNAL ERROR IN PTP MOTION PLANNING <number>
1160
1161
Cause-- Error in planning of the PTP motion profile.
Monitor-- Not cyclic, in motion planning.
Effect-- Interpreter stop.
Remedy-- Modify profile data (rounding factor, velocity, acceleration). Please
consult KUKA.
Message textTRACE: RECORDING TIME IS TOO LONG
Cause-- The recording time in TRACE.DEF is too long. There is not enough
memory available for recording.
Monitor-- When starting the TRACE.
Effect-- TRACE is not recorded.
Remedy-- Shorten TRACE recording time or reduce the number of channels.
Message textACKN MONITORING OF THE ACTUAL VELOCITY **
Cause-- Fault in control loop:
-- motor cables of two axes interchanged;
-- error in the axis assignment;
-- power module defective;
-- resolver unmastered.
Monitor-- Cyclic.
Effect-- Robot remains motionless.
Remedy-- Rectify the corresponding error in the control loop.
58 of 135
Fehlermeldungen 09.02.01 en
1Error messages / troubleshooting (continued)
1162Message textSEPARATE BREAK CONTROL OF AUXILIARY AXIS NOT ENABLED
Cause--
Monitor--
Effect--
Remedy--
1163
Message textAXIS COUPLING NOT POSSIBLE (DSE/PM--CHANNEL ASSIGNMENT)
Cause--
Monitor--
Effect--
Remedy--
1164
Message textCOUPLE PROCESS ACTIVE
Cause--
Monitor--
Effect--
Remedy--
1165
Message textERROR ON AXIS COUPLING
1166
1167
1168
1169
Cause--
Monitor--
Effect--
Remedy--
Message textERROR ON AXIS DECOUPLING
Cause--
Monitor--
Effect--
Remedy--
Message text<axis> DECOUPLED AUXILIARY AXIS
Cause--
Monitor--
Effect--
Remedy--
Message text<axis> DECOUPLED AUXILIARY AXIS, MOVE NOT PERMITTED
Cause--
Monitor--
Effect--
Remedy--
Message text<axis> DECOUPLED AUXILIARY AXIS, MASTERING NOT PERMITTED
Fehlermeldungen 09.02.01 en
59 of 135
Error messages / troubleshooting
Cause--
Monitor--
Effect--
Remedy--
1170
Message textASYPTP COMMAND INCLUDES DECOUPLED AUXILIARY AXIS
Cause--
Monitor--
Effect--
Remedy--
1171
Message textVALUE O F $ASYNC_AXIS CONTAINS DECOUPLED AUXILIARY AXIS
Cause--
Monitor--
Effect--
Remedy--
1172
Message textVALUE CANNOT BE CHANGED, PROGRAM IS SELECTED
Cause-- Attempt to reference a non--incremental axis.
Monitor-- During single--axis referencing.
Effect-- The specified axis is not referenced.
Remedy-- Master the axis.
Message textRCP SWITCH POSITION INADMISSIBLE
Cause-- Too many transfer processes started (a maximum of 4 transfer pro-
cesses can be started.)
Monitor-- During transfer.
Effect-- None.
Remedy-- Wait until one process has been completed.
-- Stop one process.
Fehlermeldungen 09.02.01 en
69 of 135
Error messages / troubleshooting
1306Message textDEVICE NOT READY
Cause-- Cable defective or not connected.
-- Device switched off (e.g. printer).
Monitor-- During transfer.
Effect-- None.
Remedy-- Check cable and device.
1307
Message textFORMAT ERROR
Cause-- Hardware error of the interface on I--CPU.
Monitor-- During transfer.
Effect-- None.
Remedy-- If the error occurs repeatedly, change the board (interface CPU).
1308
Message textCHANNEL NOT ALLOWED IN COMMAND
Cause-- Command does not support any channels.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- None.
1309
Message textOBJECT IS NOT AVAILABLE
1310
1311
Cause-- Objects that are not available in the KRC cannot be addressed.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Wrong object selected.
Message textTOO MANY OBJECTS ARE SELECTED
Cause-- Too many objects selected.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Select only the permitted number of objects (approx. 150).
Message text<object name> NOT CORRECTLY COPIED
Cause-- Errors have been detected in the line analysis.
Monitor-- In command processing.
Effect-- Error token in the object.
Remedy-- Correct object.
70 of 135
Fehlermeldungen 09.02.01 en
1Error messages / troubleshooting (continued)
1312Message text<object name> ASSIGNED
Cause-- Object cannot be processed in this state (object already assigned).
-- Module package cannot be linked since at least one of the objects
of the module package is assigned.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- None.
1313
Message textINVALID STATEMENT
Cause-- The source and target specifications do not conform to the convention
for “COPY”.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Specify the source and target correctly.
1314
Message textDATA NOT ALLOWED
Cause-- Extension not compatible.
-- copy *.* (copy *.* is possible into a directory only).
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Specify extension correctly.
1315
Message text<module name> IS NOT A MODULE
1316
1317
Cause-- The name represents a directory.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Take a different module.
Message textRUNTIME VALUES FOR TRIGGER IN SUBROUTINES INADMISSIBLE
Cause-- In a subroutine a trigger is defined which is possibly not activated until
the main program. If runtime values are used in trigger assignment,
they are not valid at the time of activation.
Monitor-- During program execution.
Effect-- Ramp--down braking, all active commands inhibited.
Remedy-- Alter program, use only global variables, acknowledge message.
Message textDELETING OF SYSTEM FILES IS INADMISSIBLE
Cause--
Monitor--
Effect--
Remedy--
Fehlermeldungen 09.02.01 en
71 of 135
Error messages / troubleshooting
1318Message textFILE DESCRIPTION CANNOT BE PROCESSED
Cause-- Module information that cannot be evaluated has been received in a
COPY operation from an external source.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Check interface software.
1319
Message text<object> CANNOT BE CORRECTED
Cause-- An invalid extension has been specified (only “DAT” is allowed).
-- An attempt has been made to transmit or edit a protected file.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Select data list.
-- Set INIT switch on I--CPU to position 3.
1320
Message textEXTENSION NOT ALLOWED
Cause-- An extension has been specified in a command where it is not allowed
(e.g. analyse otto.src).
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Correct command.
1321
Message text<path> IS NOT A DIRECTORY
1322
1323
Cause-- Command contains an invalid subdirectory (e.g. dir /R1/otto/abc,
/abc not allowed).
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Correct command.
Message text<module> NOT LINKED
Cause-- “UNLINK” has been applied to an object that is not a program.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- None.
Message text<path> INVALID DATA MODULE NAME OR EXTENSION
Cause-- An invalid path, module name or extension has been specified.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Correct command.
72 of 135
Fehlermeldungen 09.02.01 en
1Error messages / troubleshooting (continued)
1324Message text<object> NOT AVAILABLE
Cause-- An object that is not available has been addressed.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Create the object.
1325
Message text<object> CANNOT BE PROCESSED
Cause-- An object that has already been assigned has been addressed.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Free the assignment (/R1/CONFIG>DAT).
1326
Message text<object> : <number of errors> COMPILATION ERROR
Cause-- The indicated number of errors have been detected in the indicated
object during total compilation.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Correct the errors.
1327
Message text<module> LINKING ERROR
1328
1329
1330
Cause-- One or more errors have been detected in the indicated module
during linking.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Using t he error list, correct the error(s).
Message textFAULTY FILE
Cause-- Module is not correct for TTS calculation.
Monitor-- In command processing.
Effect-- None.
Remedy--
Message textACCESS TO IMPORTED VARIABLE IS NOT POSSIBLE
Cause-- The search path has not been extended to the external data list.
Monitor-- In command processing.
Effect-- Command has not been executed.
Remedy-- Extend the search path.
Message textSOURCE AND TARGET OBJECT ARE IDENTICAL
Cause-- The source and target specifications define the same object.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Change target object.
Fehlermeldungen 09.02.01 en
73 of 135
Error messages / troubleshooting
1331Message text<module> NOT CORRECT
Cause-- An incorrect module has been selected in a linking operation.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Correct the error in the indicated module (perform ANALYSE).
1332
Message textLine selection not possible: too many Interrupts
Cause-- An attempt has been made to carry out a block selection in a local
subprogram that is not in the caller stack. At this point, the maximum
permissible number of interrupts that can be declared or activated was
exceeded.
Monitor--
Effect-- Block selection to the subprogram is not possible.
Remedy-- Reduce the number of KRL interrupts accordingly.
1333
Message text<object> CANNOT BE DELETED
Cause-- Object cannot be deleted because it is write--protected.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- None.
1334
Message textMORE THAN 16 INTERRUPTS DEFINED
1335
1336
1337
Cause-- Program instruction INTERRUPT ON can switch on a maximum of
16 defined interrupts but more than 16 are defined.
Monitor-- Program processing.
Effect-- Ramp--down braking.
Remedy-- Reduce number.
Message text<module> SELECTED
Cause-- Program cannot be unlinked; module is selected with “RUN”.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Terminate program run (CANCEL).
Message textCOR ARE FOR DATA LISTS ONLY
Cause-- COR is allowed for data lists only.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Select a data list.
Message textTOO COMPLEX
Cause-- Copying from one channel to another (not allowed in SWP1).
Monitor-- In command processing.
Effect-- Command is not executed.
74 of 135
Fehlermeldungen 09.02.01 en
1338
1339
1340
1341
1Error messages / troubleshooting (continued)
Remedy-- None.
Message textBLOCK CANNOT BE CORRECTED
Cause-- TTS or BASE calculation cannot be performed. (TTS = tool--based
Cause-- An attempt has been made to move an axis in the inhibited direction
(inhibited by software limit switch).
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Move axis off limit switch in other direction.
Message textKEY COMBINATION <KCP> INADMISSIBLE
Cause-- Simultaneous pressing of more than one key on the KCP.
Monitor-- Cyclic.
Effect-- KCP operation momentarily interrupted.
Remedy-- Release all keys on the KCP.
Message textDEADMAN SWITCH REQUIRED
Cause-- The safety (deadman) switch has not been pressed while actuating
the start or traversing key in mode T1 or T2.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Press safety switch.
Message textSTART KEY REQUIRED
Fehlermeldungen 09.02.01 en
Cause-- The “START” command has been entered textually.
-- Execution of the command requires the start key to be pressed.
Monitor-- In command processing.
Effect-- None.
77 of 135
Error messages / troubleshooting
Remedy--P r e s s s t a r t k e y .
1357
Message textRESET REQUIRED
Cause-- RUN has been applied to a process in the end state.
Monitor-- In command processing.
Effect-- In command processing
Remedy-- RESET program.
1358
Message textSELECTION REQUIRED
Cause-- Start key pressed without a program being selected.
Monitor-- When start key is pressed.
Effect-- Command is not executed.
Remedy-- Select program.
1359
Message textTTS CANNOT BE DETERMINED
-- External computer: check job identification.
-- In program processing.
-- Command is not executed.
-- In program processing
-- Ramp--down braking
-- All active commands inhibited.
-- In program processing the message has to be acknowledged.
-- “RUN” without path specification and no program is selected.
-- At RUN command.
1360
1361
1362
Cause-- Termination of search for the path direction point. (TTS = tool--based
technological system).
Monitor-- In command processing.
Effect-- None.
Remedy--
Message textSELECTION NOT ALLOWED
Cause-- Selected block does not exist in the program.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Select correct block number.
Message textSTOP DUE TO NODE SWITCHOVER
Cause-- The node setting has been changed during actuation of a traversing
key or execution.
Monitor-- In command processing.
Effect-- Ramp--down braking.
-- All active commands inhibited.
Remedy-- Acknowledge message.
Message textSTOP DUE TO OPERATING MODE CHANGE
78 of 135
Cause-- Active processes are stopped if the mode is changed.
Monitor-- Cyclic.
Fehlermeldungen 09.02.01 en
1363
1364
1365
1Error messages / troubleshooting (continued)
Effect-- Path--maintaining Emergency Stop.
Remedy-- Acknowledge message.
Message textOPERATOR CONTROL UNIT DISABLED
Cause-- Command cannot be executed because the KCP settings do not
fulfil the conditions.
a) For RCP and stationary KCP the mode AUT is required.
b) For non--stationary KCP the mode T1 or T2 is required.
c) For host computers the mode EXT is required.
Monitor-- In command processing.
Effect-- Command cannot be executed.
Remedy-- Fulfil the “active” conditions.
Message textOUT PARAMETERS INADMISSIBLE
Cause-- Trigger with subprogram call where reference parameters are trans-
ferred.
Monitor--
Effect--
Remedy-- Correct program, acknowledge.
Message textPATH TRIGGER WITH PTP MOTION INADMISSIBLE
1366
1367
1368
Cause-- Path triggers are not permissible with PTP motions.
Monitor--
Effect-- Program execution is stopped.
Remedy-- Correct program, acknowledge, reboot.
Message textCARTESIAN TARGET NOT POSSIBLE
Cause-- When using a 5--axis robot ($DEF_A4FIX=TRUE) and palletizing
mode is deactivated ($PAL_MODE=FALSE), only PTP motions with
an axis--specific target may be carried out.
Monitor-- In the line interpreter.
Effect-- Path--maintaining braking.
Remedy--
Message textACTIVE STATUS REQUIRED
Cause-- The command entered may only be issued from an active operator
control unit (modes T1, T2, AUT).
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Switch operator control unit to active status.
Message text<operator control device> IS ACTIVE
Fehlermeldungen 09.02.01 en
Cause-- Indicated operator control unit is active.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Switch indicated operator control unit to passive status.
79 of 135
Error messages / troubleshooting
1369Message textACTIVE ALLOWED IN <mode> ONLY
Cause-- For RCP and stationary KCP the mode AUT is required.
-- For non--stationary KCP the mode T1 or T2 is required.
-- For host computers the mode EXT is required.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Set the correct mode.
1370
Message textPASSIVE STOP
Cause-- Stop from a passive operator control unit (the message is displayed
only if an active process has been stopped).
Monitor-- Cyclic.
Effect-- Ramp--down braking.
-- All active commands inhibited.
Remedy-- Acknowledge message (acknowledgement possible only on the
originating unit, even in passive status).
1371
Message textSTOP DUE TO UNIT PASSIVE
1372
1373
Cause-- The operator control unit has been deactivated during actuation of
the start key or a traversing key in mode T1 or T2, or during the
BCO run.
Monitor-- In command processing.
Effect-- Ramp--down braking.
-- All active commands inhibited.
Remedy-- Switch operator control unit to active status.
-- Acknowledge message.
Message textPROCESS ACTIVE
Cause-- An attempt has been made to start an active command during an
active process.
Monitor-- In command processing.
-- In program processing.
Effect-- In command processing
-- Command is not executed.
-- In program processing
-- Ramp--down braking
-- All active commands inhibited.
Remedy-- Wait until end of processing.
-- Stop active processing.
-- In program processing the message has to be acknowledged.
Message textPROCESS BUSY
80 of 135
Cause-- Program already selected.
Monitor-- In command processing.
-- In program processing.
Fehlermeldungen 09.02.01 en
1374
1375
1376
1Error messages / troubleshooting (continued)
Effect-- In command processing
-- Command is not executed.
-- In program processing
-- Ramp--down braking
-- All active commands inhibited.
Remedy-- Deselect program already selected.
-- In program processing the message has to be acknowledged.
Message textPROCESS DISABLED
Cause-- All selected processes have the program mode “DISABLED” or a
non--disabled process is finished.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Alter program mode.
Message textCOMMAND NOT ALLOWED
Cause-- Impermissible or unknown command.
Monitor-- In command processing.
Effect-- None.
Remedy-- Enter command correctly.
Message textACTIVE COMMANDS INHIBITED
1377
1378
1379
Cause-- A message which causes the active commands to be inhibited has
been set.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Acknowledge active messages in the message window.
Message textCOMMAND EXECUTION NOT POSSIBLE
Cause-- A preceding command is still being processed.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Cancel command.
-- Wait until end of preceding command.
Message textCOMMAND NOT BEING PROCESSED
Cause-- The command that is to be cancelled has already been processed.
Monitor-- In command processing.
Effect-- None.
Remedy-- None.
Message textCOMMAND ABORTED
Fehlermeldungen 09.02.01 en
Cause-- The command has been cancelled.
-- During editing abort has been selected by the editor kernel before
the command concerned (ERASE,GET,FIND) is called.
81 of 135
Error messages / troubleshooting
Monitor-- In command processing.
Effect--
Remedy--
1380
Message textBACKGROUND PROCESS BUSY WITH <operator control device>
Cause-- The background is exclusively assigned to another operator.
Monitor-- In command processing.
Effect-- Background cannot be exclusively assigned.
Remedy-- Cancel the exclusive assignment of the indicated device.
1381
Message textBACKGROUND OCCUPIED
Cause-- A command is already being processed in the background.
Monitor-- In command processing.
Effect-- Command is not executed.
Remedy-- Cancel command.
1382
Message textABORTED
-- In editing.
-- Provide complete specifications in $OPTION.DAT.
-- Wait until command has been executed.
1383
1384
1385
Cause-- “BREAK” has been repeated.
Monitor-- In command processing.
Effect-- None.
Remedy-- None.
Message text** IS NOT A MEMORY DUMP
Cause-- When writing a data block (a file received from the controller or a
temporary file created by the server), it has been discovered that there
is not enough space available on the storage medium (hard disk).
Monitor
Effect-- The currently edited file is deleted.
Remedy-- Create space on the storage medium
(delete files that are no longer required).
Message textPARAMETER NOT PROCESSED
Cause-- A RUN command with a parameter has been executed for a program
that is already selected.
Monitor-- In command processing.
Effect-- The parameter is not evaluated.
Remedy-- Cancel and reselect the program.
Message textPROTOCOL ERROR
82 of 135
Cause-- Error in the protocol software of the operator control unit or output
Cause-- At least one argument in the function is inadmissible; e.g. SQRT
(negative value).
Monitor-- In interpretation of C functions.
Effect-- In command processing
-- Command is not executed.
-- In program processing
-- Ramp--down braking
-- All active commands inhibited.
Remedy-- Alter the program accordingly.
-- Acknowledge message.
1440
Message textMailbox identification not allowed
Cause-- An incorrect MBX_ID is specified in the C function “MBX_REC”.
Monitor-- In interpretation of “MBX_REC”.
Effect-- Ramp--down braking.
-- All active commands inhibited.
Remedy-- Alter the program accordingly.
-- Acknowledge message.
1441
Message textInterrupt priority not allowed
1442
Cause-- Interrupt priority greater than 128 or less than 1
Monitor-- In command processing.
-- In program processing.
Effect-- In command processing
-- Command is not executed.
-- In program processing
-- Ramp--down braking
-- All active commands inhibited.
Remedy-- Acknowledge message.
-- Alter the program accordingly.
Message textApproximation not allowed for instructions
Cause-- “DRIFT”, “$TOOL” or “$FIL TER” is programmed between two motion
instructions.
Monitor-- In program processing.
Effect-- Approximate positioning is not performed for the motion instructions.
Remedy-- Alter the program accordingly.
Fehlermeldungen 09.02.01 en
93 of 135
Error messages / troubleshooting
1443Message textStart movement not allowed
Cause-- The first motion instruction in the program is relative.
-- The first motion instruction in the program is not programmed
completely, e.g. PTP [33.33].
Monitor-- In program processing.
Effect-- No program motion.
Remedy-- Alter the program.
-- Acknowledge message.
1444
Message textArray index inadmissible
Cause-- An attempt has been made to access an array element that does
not exist.
Monitor-- In command processing.
-- In program processing.
Effect-- In command processing
-- Command is not executed.
-- In program processing
-- Ramp--down braking
-- All active commands inhibited.
Remedy-- Alter the program accordingly.
Acknowledge message.
1445
Message textAngle status inadmissible
1446
Cause-- After repositioning with LIN the angle status does not agree with the
status of the programmed block.
Monitor-- In program processing.
Effect-- Ramp--down braking.
-- All active commands inhibited.
Remedy-- Acknowledge message.
-- Perform repositioning with PTP.
Message textValue assignment not allowed
Cause-- Inadmissible value assignment for predefined variables,
e.g. $SPEED.ORI1 <= 0.0 or > $SPEED_MA.ORI1.
-- Assigned $BASE or $TOOL not possible for the kinematic system.
Monitor-- In command processing.
-- In program processing.
Effect-- In command processing
-- Command is not executed.
-- In program processing
-- Ramp--down braking
-- All active commands inhibited.
Remedy-- Alter the program accordingly.
-- Acknowledge message.
94 of 135
Fehlermeldungen 09.02.01 en
1Error messages / troubleshooting (continued)
1447Message textSoftware limit <motion direction> <axis number> out of range
Cause-- Target point cannot be reached due to a software limit switch.
Monitor-- In command processing.
-- In program processing.
Effect-- In command processing
-- Command is not executed.
-- In program processing
-- Ramp--down braking
-- All active commands inhibited.
Remedy-- Alter the program.
-- Acknowledge message.
1448
Message text<Name> ambiguous
Cause-- The specified memory dump name contains wildcards. Expansion of
these wildcards has resulted in more than one valid file name. This is
not allowed however.
Monitor
Effect-- Data transfer is not carried out.
Remedy-- Specify an unambiguous name.
1449
Message text<$variable> variable write protected
1450
Cause-- Write access to a write--protected variable e.g. “$POS_ACT”.
Monitor-- In command processing.
-- In program processing.
Effect-- In command processing
-- Command is not executed.
-- In program processing
-- Ramp--down braking
-- All active commands inhibited.
Remedy-- Alter the program.
-- Acknowledge message.
Message textTransformation not configured
Cause-- $BASE or $TOOL has been assigned although no transformation is
configured.
Monitor-- In command processing.
-- In program processing.
Effect-- In command processing
-- Command is not executed.
-- In program processing
-- Ramp--down braking
-- All active commands inhibited.
Remedy-- Alter the program.
-- Acknowledge message.
Fehlermeldungen 09.02.01 en
95 of 135
Error messages / troubleshooting
1451Message textDivision by 0
Cause-- An attempt has been made to divide a value by “0”.
Monitor-- In command processing.
-- In program processing.
Effect-- In command processing
-- In program processing
Remedy-- Alter the program.
-- Acknowledge message.
1452
Message textBackward motions not active
Cause-- Backward motion is deactivated ($VW_BACKWARD = FALSE).
Monitor-- When START MINUS key is pressed.
Effect-- Command is rejected.
Remedy-- Set variable $VW_BACKWARD to TRUE.
1454
Message textStart continue not possible
-- Command is not executed.
-- Ramp--down braking
-- All active commands inhibited.
1455
1456
Cause-- BSTEP
Monitor-- In command processing.
Effect-- None.
Remedy--
Message textInadmissible in this edit mode
Cause-- A command that would alter the object has been entered in the listing
mode of the editor.
-- An attempt has been made in the data correction mode to delete or
copy a range of blocks or to delete a block consisting of only one line.
Monitor-- In the editor.
Effect-- The attempted action is not executed.
Remedy-- Edit in full edit mode.
Message textStart point equal to end point
Cause-- Distance between start point and end point is too small.
Monitor-- During preparation.
Effect-- Ramp--down braking.
-- Active commands inhibited.
Remedy-- Reprogram start point and/or end point.
-- Acknowledge message.
96 of 135
Fehlermeldungen 09.02.01 en
1Error messages / troubleshooting (continued)
1457Message textStart point equal to mid point
Cause-- Distance between start point and auxiliary point is too small.
Monitor-- During preparation.
Effect-- Ramp--down braking.
-- Active commands inhibited.
Remedy-- Reprogram start point and/or auxiliary point.
1458
Message textMid point equal to end point
Cause-- Distance between auxiliary point and end point is too small.
Monitor-- During preparation.
Effect-- Ramp--down braking.
-- Active commands inhibited.
Remedy-- Reprogram auxiliary point and/or end point.
1459
Message textBackward motions not possible: finished subroutine
Cause-- An attempt was made to carry out backward a motion located inside
a subprogram which has already been executed.
Switching to forwards in this subprogram would not be possible.
Backward motion is thus also disabled.
Monitor-- When the “Start backwards” key is pressed.
Effect-- Command is not executed.
Remedy-- Forward motion.
1460
Message textDeleting Trace: no backward motions possible
1462
1463
Cause-- Editing was carried out or a block selection was made at a position
which causes the trace to be discarded.
From now on backward motion is no longer possible.
Monitor-- When the “Start backwards” key is pressed.
Effect-- Command is not executed.
Remedy-- Forward motion.
Message textCommand syntax error
Cause-- The command contains a syntax error.
Monitor-- In the editor.
Effect-- Command is not executed.
Remedy-- Correct the command.
Message textObject not ready
Cause-- Program cannot be processed by the editor.
Monitor-- In the editor.
Effect-- Command is not executed.
Remedy-- Select program with “Edit”.
Fehlermeldungen 09.02.01 en
97 of 135
Error messages / troubleshooting
1464Message text$OUT_C[N] IS NOT PERMISSIBLE IN SUBMIT
Cause-- Instruction not permissible here
Monitor--
Effect-- Interpreter stop
Remedy-- Revise SRC file and acknowledge message
1465
Message textONLY 8 $OUT_C[N] ASSIGNMENTS PER MOTION PERMISSIBLE
Cause-- Instruction not permissible here
Monitor--
Effect-- Interpreter stop
Remedy-- Revise SRC file and acknowledge message
1468
Message textKey not assigned
Cause-- An unassigned softkey or function key has been pressed during
prompted operation.
Monitor-- When a softkey is pressed.
-- When a function key is pressed.
Effect-- None.
Remedy-- None.
1472
Message textKey not allowed
1474
1477
Cause-- Impermissible key (e.g. softkey) pressed in textual operation.
-- Alphanumeric key pressed in prompted operation when no input field
is available.
Monitor-- When a key is pressed.
Effect-- Entry is ignored.
Remedy-- Acknowledge the message.
Message textChange of direction not possible
Cause
Monitor-- In command processing.
Effect-- None.
Remedy
Message textMain process not available
Cause-- Main run display (motion trace) selected but no main run block inter-
preted yet.
Monitor-- In command processing.
Effect-- None.
Remedy-- Start the program.
98 of 135
Fehlermeldungen 09.02.01 en
1Error messages / troubleshooting (continued)
1478Message textPre process not available
Cause-- Advance run display (program trace) selected but no program is in the
STOP or END state.
Monitor-- In command processing.
Effect-- None.
Remedy-- Start the program.
1481
Message textNo runtime data access
Cause-- Access to an invalid or non--existent object value memory or runtime
data area via the hierarchy table (search path).
Monitor-- In the interpreter (prim -- init).
Effect-- None.
Remedy-- Set the search path to the current interpreter environment.
1482
Message textVolume too small
Cause-- Monitoring of the dispensed volume has been triggered. Insufficient
adhesive has been dispensed.
Monitor-- From the PCL application program (bonding technology).
Effect-- Ramp--down braking. All active commands inhibited.
Remedy-- Check the adhesive application hardware, purge it if necessary.
1483
Message textExcessive volume
1484
1485
Cause-- Monitoring of the dispensed volume has been triggered. Too much
adhesive has been dispensed.
Monitor-- From the PCL application program (bonding technology).
Effect-- Ramp--down braking. All active commands inhibited.
Remedy-- Check the adhesive application hardware, purge it if necessary.
Message textWrong adhesive pressure
Cause-- The initial pressure of the adhesive is continuously monitored by the
PLC during dispensing. A pressure value outside the permissible
tolerance range has been detected. Possibly there are bubbles in the
adhesive supply line, or the outlet nozzle is clogged.
Monitor-- From the PCL application program (bonding technology).
Effect-- Ramp--down braking, all active commands inhibited.
Remedy-- Check the adhesive application hardware, purge it if necessary.
Message textOil filter dirty
Cause-- The hydraulic pressure is no longer adequate because the hydraulic
oil filter is dirty.
Monitor-- From the PCL application program (bonding technology).
Effect-- Ramp--down braking. All active commands inhibited.
Remedy-- Clean or replace oil filter.
Fehlermeldungen 09.02.01 en
99 of 135
Error messages / troubleshooting
1486Message textMax. oil temperature exceeded
Cause-- The maximum permissible hydraulic oil temperature has been ex-
ceeded.
Monitor-- From the PCL application program (bonding technology).
Effect-- Ramp--down braking. All active commands inhibited.
Remedy-- Wait until the hydraulic oil has cooled down.
-- If this situation occurs frequently , check the hydraulic unit.
1487
Message textGeneral system air pressure
Cause-- The required air supply pressure for the pneumatic valves is not
available.
Monitor-- From the PCL application program (bonding technology).
Effect-- Ramp--down braking. All active commands inhibited.
Remedy-- Ensure that the air pressure and quantity are sufficient.
1488
Message textVacuum error
Cause-- Vacuum missing or insufficient.
In the application of adhesive to glass, the glass is held in position by
means of a vacuum. If this vacuum is not available, the glass cannot
be held in position after it has been centered.
Monitor-- From the PCL application program (bonding technology).
Effect-- Ramp--down braking. All active commands inhibited.
Remedy-- Check the vacuum pump and hoses.
1489
Message textCentering error
1490
Cause-- The workpiece is not correctly positioned or clamped. There is possibly
a fault in the feed equipment, or the fixture is defective.
Monitor-- From the PLC application program (bonding technology).
Effect-- Ramp--down braking. All active commands inhibited.
Remedy-- Check fixture, feed equipment or workpiece position.
Message textComponent check error
Cause-- Component damaged or no longer clamped to the fixture.
-- In the application of adhesive to glass, the adhesive nozzle is pressed
onto the glass. If this pressure is missing during adhesive application,
the glass might be damaged or might no longer be clamped to the
fixture.
In this case, the robot motion and adhesive application must be
stopped immediately!
Monitor-- From the PLC application program (bonding technology).
Effect-- Maximum braking. All active commands inhibited. Emergency Stop.
Remedy-- Check the workpiece.
100 of 135
Fehlermeldungen 09.02.01 en
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.