Replace batery then in bios loaf default settings. If controller does not boot , you may need to force start using jumper as as "power on" button. Read motherboard manual for details
Posts by panic mode
-
-
Define "stopped"
If you mean robot not moving, there is a system variable for that - check AutoEcternal outputs configuration.
If you are interested in program state, check $pro_state1
-
that will work fine, i use it all the time to make sequencers in KRL. you may have an issue with robot stopping at each point (advance run pointer stops). this can be remedied the conventional way as presented in programming courses.
-
that is just one message (KSS00404 - Safety Stop), and it is general one associated with safety not being ok. what are the other messages?
you may have a problem with external enable not wired in, wrong WoV configuration etc. -
here you go...
-
right on...
-
robot must have safety interface and it must be happy in order to enable drives.
on KRC4 that interface is either hardwired to X11 or it is created through network with SafetyPLC.
check download section for X11 examples (make sure to pay attention and look at the one matching your controller) -
rotary axis can be either endless (no soft limits) or must have soft limits that are within +/-358deg
-
What makes you think that can work?
-
All robots are sold with drawings and software. If you lost it contact Kuka. If you bought it second hand talk to your seller. Do not ask for software here...
-
I would not do that unless both robots are same sw/hw.
Some of settings are in $config.dat
Most are in r1/steu/$machine.dat -
if you get diagnostics point at ESC internal error, ESC replacement is the best thing you can try next.
-
while at it, why not go to 8.3.22?
-
http://www.kuka-robotics.com/en/support/
make sure to have info such as robot and cabinet serial number.
-
make sure that array index is valid (in range).
note that arrays in KRL start with index 1
so if you declare array of something that is 5 element long, then you can only use elements 1,2,3,4,5
any other index value will cause this message.... -
that is only static load.... your issue occurs when robot moves fast (dynamic load)
-
sounds like your cell safety circuit is not commissioned properly.
-
is the file write protected?
-
there is not much info but based on what is shown so far, problem appears safety circuit related. this means it could be wiring, KSP600 or ESC board.
please show other messages and take a look at ESC diagnostics. -