Kuka servo pack internal error

First: "Motion Enable" means you are missing an input signal, $MOVE_ENABLE. You need to map it to an input that can be set True, or to $IN[1025], which is a special always-True input.

Second: 50mV? That's nothing. Unless you are also getting error messages relating to the servo pack, I doubt this is an issue.

Third: show your actual list of status and error messages.

so you still have not connected or resolved safety circuit... it clearly shows that external ESop is holding you back.

you can login as Expert, enable Start-Up mode and try jogging. if it moves, hardware is ok.

Read on how to jog the robot. In StartUp Mode you can only jog. To jog press enabling switch on smart pad in middle position. The menue you shared is irrelevant for jogging.

this is KRC5... not sure if 600V is supported without transformer but i would dare a guess that things are more or less like on KRC4:

most of the world uses 400VAC 3P so transformer is usually not needed. and if supply voltage is different one can pick hardware from catalog for different voltages. this way one can still go transformerless on 380V, 400V, 440V or 480V.

but for 600V mains, transformer before KRC4 is required (either one integrated by KUKA or - external one that is user supplied).

btw, when transformer is used, secondary is 400V so KRC4 hardware is picked from 400V catalog.

Quote from automatisation

We also found that the KSP is faulty (The internal voltage {A}mV differs by more than 50mV from the target value of 0volts) in the EtherCat topology. We have checked the wiring several times, and couldn't find the problem.

that message is not useful since it is unclear what device is meant by {A}. but it also says that it is internal voltage to something (KPP/KSP) so you would not be able to measure it anyway or correct by re-seating external cabling. If anything one should check KSB wiring (green ECAT cables) to ensure all ECAT connections are solid and retention caps are in locked position.

Quote from automatisation

I already pressed the enabling switch several times in startup mode, nothing happens.

sure but ... did you wire the safety interfaces? without them robot cannot move. StartUp mode can only bypass some of the circuits. others, like external drive enable still must be wired.

Quote from automatisation

I have attached the list of errors, nothing related to the KSP. Also, I have set the $MOVE_ENBALE to True, but the motion conditions are still not enabled.

Your message list shows that $MOVE_ENABLE is not True. How did you "set" it?

Your other two messages indicate that the safety circuits on not wired. Panic Mode has already addressed this, but Startup Mode will only bypass the E-Stops, and only for jogging in T1 mode. $MOVE_ENABLE is not part of the Safety subsystem, and as such is not bypassed by Startup Mode.