The running state on KSP when the KUKA robot is debugged
The running state of KUKA robot during debugging. KUKA KUKA robot servo package KSP belongs to the drive regulator of the manipulator drive shaft. KSP has LED to display running status.
KUKA KSP robot KSP servo package maintenance models include:
KUKA KSP600-3 x40 maintenance
KUKA robot selection
Kuka robot ksp600-3x64 driver failure repair
Kuka ksp600-3x20 kuka robot servo package maintenance
KUKA KUKA robot servo package KSP has LED to show the running status. KUKA robot KSP/KPP faults include:
ERROR 26107 KSP intermediate circuit voltage is too high (axis)
ERROR 26108 KSP intermediate circuit voltage is too low (axis)
ERROR 26109 KSP logic circuit power supply voltage is too high (axis)
ERROR 26110 KSP logic circuit power supply voltage is too low (axis)
ERROR 26111 KSP equipment temperature is too high (axis)
ERROR 26122 KSP brake resistance ERROR (shaft)
I. KUKA KUKA robot failure and KUKA robot servo controller maintenance part of the common prompts and solutions:
1 prompt text failure
Reason -KCP is broken.
Query - dynamic.
Impact - signal ramp stop.
- blocks all active commands
Emergency measures - replace KCP.
Error prompt/troubleshooting
2 prompt text transmission error
Reason -KCP connection error.
Query - dynamic.
Impact - signal ramp stop.
- blocks all active commands.
Emergency measures - check the KCP wire.
3 prompt text TPBASIS
Reason - cannot establish this point.
The text system time is invalid
Reason - after TIME_HW_FAILURE and the initial value has been set, the system time is invalid.
Query - when the controller starts.
Impact - system time is initialized at 01.01.9300:00:00,00.
Emergency action - update system time with form "systime" (system time).
5 prompt text MFC overheating
Cause - the temperature sensor on the MFC has a trigger signal.
Query - dynamic.
Impact - the movement process will be stopped by an emergency shutdown following the trajectory.
Emergency measures - check fan and replace MFC if necessary.
The output error of alphanumeric signal @p@ is suggested.
Cause - outlet 1-8 or 9-16 short circuit.
Query - dynamic.
Impact - emergency braking
Emergency measures -
7 prompt text program stack overflow
Reason - KRL program has too many nested check structures or too many recursive subroutine calls! R-int c-stack will overflow otherwise.
Query - during program processing.
Influence - signal ramp braking.
Emergency measures - change the structure of the procedure.
Too many text prompts
Cause - the dynamic process suggests excessive accumulation.
Query - when prompted.
Impact - the current command will be cancelled and cannot be started again.
Contingency measures -KRC must be guided.
Text safety circuit failure
Cause - one or more enable switches are pressed down.
query-dynamic
The impact - movement process will be stopped by the emergency shutdown of the trajectory, and the activation command will be blocked. Emergency measures -
Prompt text PLC software: @ p1@
why
The query
impact
Emergency measures
Monitor dc bus voltage KPS: @p1@
Reason -KPS dc bus voltage overload.
Query -
Impact -
Emergency measures -
Error while reading "O file".
Ident - the storage or files were not found during the install/read of "ident-vx.o" :. Queries - when writing the "w-ident-state" feature.
Impact - in the load data program transition to the end.
Ident - copy the file "ident-vx.o" into the directory "/ir-spec/l-ident", or increase storage capacity by changing the value of "VxWinRAM" in the registry.
12 prompt text found broken or unknown hardware
Reason - the wrong hardware was selected (KR C1,KR C1A,KR C2) or was structurally damaged during installation.