in mode t1,how enable drives that's mean
S I R T1
in mode t1,how enable drives that's mean
S I R T1
look like this photo.S I R T1
I select auto mode
drives not active
what's happened?tell me plz
does anyone know why there is a safety stop here?
fubini
Panic mode
Sky fire
Read this message
message 404 is very generic. there should always be another message showing more details.
do enable drives safety circuit need to be ok. requirements are the same for all modes except that operator safety is ignored in manual modes. your previous posts show that you are trying to use AUT mode but the message tells that operator safety is open. cannot have that. if you want to use robot in AUT or EXT mode, you must close the cell and acknowledge operator safety.
or at least that is the case if the robot cell is operational (commissioned correctly).
one important aspect of commissioning cell is making sure that safety is done properly. robot is part of it. on the robot end that means (among other things) wiring correctly safety interface, activating safety configuration and having no configuration plugin active/open on smartPad.
the "other things" include matching correct WoV project meaning that configured robot, controller, fieldbus networks etc match actual system.
Robot will not move without all permissives satisfied. to get a clue of what may be wrong. click on drives icon (1) and see which of four indicators are not green (2,3,4,5).
how do I solve this problem?
There is another one on the Shutdown page, called Drive bus. It must be turned on (press on button "I" next to it)
how do I solve this problem?
Any way you like...
Some people take training or read manuals, some call KUKA or hire contractor, some rely on faith/deities/vodoo ... You seem to be in the last group.
What do you think proper next step should be in this case? I think taking look at those indicators and finding out which ones are not green is a good step. but you are either not looking, or choosing to take care of it yourself without any help. if you wanted help and suggestions of others, you would share with us what you saw.
your posts only show inputs to robot. you may also want to check controller status.
panic mode I don't know the reason of your speaking like this. I feel that you don't even understand my question because you give an answer that is not related at all, my question is how can I solve that problem (safety stop) and you say trust in God I am posting the photo so that you can understand that the answers are not related at all
In the picture above, the axes are activated but through service > startup. But I still have those two errors and I don't want the axes to be activated in this way. Like you, I don't have a remote software and I work with a pendant.In this case, when the axes are activated with startup, there is no more safety stop error
In the picture above, the axes are activated but through service > startup. But I still have those two errors and I don't want the axes to be activated in this way. Like you, I don't have a remote software and I work with a pendant.In this case, when the axes are activated with startup, there is no more safety stop error
This is the picture of the display output, as you can see, when the axes are not active, $peri_rdy is not activated and $alarm_stop is off. My friend, my problem is that I cannot activate my axes without using service>startup. Please, if you know how to help, I can take any picture for you. I only work with pendant, consider this
yes, there was misunderstanding too due typos in posts and poor explanation. last few posts were helpful.
if you can use robot in Start-Up mode (IBN) then you can be sure that robot system is ok and you just need to ensure correct wiring of the safety circuit.
your last post shows that your X11 jumper plug wiring is incomplete. all safety circuits need to be wired (safe stop, safe stop 2 etc.). you are missing some 10 wires there. this is an circuit style i like because both channels are grouped according to function. but you need to make sure that connector pinout is correct for your controller type and X11 style. refer to KUKA documentation.
also make sure your controller batteries are wired up. this is part of commissioning and in case of KRC4 it is the X305 inside cabinet. that should get rid of remaining messages and everything should be working ok