VKRC2 V3.3.5 windows 95
I cannot switch to auto external mode. All cabling from X11 seems all OK . Manual mode we can do everything.
X4 connector: when we short circuit pins 5-6 we can switch to T2 mode.
X4 connector: when we short circuit pins 5-8 we can't switch to auto mode. ( driver on /clear messages/external start signals we sent from devicenet modul from the same input 3 times)
vkrc2 auto external mode
-
hasan ekim -
March 10, 2016 at 3:39 PM -
Thread is marked as Resolved.
-
-
You talk about X11 so i presume you are not working with a standard vkrc cabinet, or you somehow modified one.This is how it should work:
I don't know the pin numbers on X11, but i do know them on XS2 (or XS5 if you have a different cabinet). which is the connector on bottom of the cabinet. You should make 3 different connections.- E7 key D11+D12
- E2 key D7+D8 D9+D10
E2 is a double channel system so those connections should be made at the same time.You have to connect only E2 to get tot T1 when the KCP is in manual
Leave both connections open to switch on the KCP to automatic external -
we have standard vkrc2 with xs2.
(we use jumper cables on x9/x10/x11 since we could not find xs2 special connector)Thanks we can switch to aoto external mode now
But now we have message : Ackn E2- switch open.
-
And if you acknowledge the message it doesn't go away? Because that is what supposed to happen. What could happen because E2 is a double channel systems that i won't acknowledge because both channels did not open at the same time. In that case you would have to either restart the controller or reset the ESC card in the kabinet. I am not sure that that is the problem though.
-
yes when we acknowledge(external button or from screen) the message it doesn't go away.
We connected E2 channels to a double contact manual button .
even we restart the controller or reset the ESC card in the kabinet the message does not go away. -
I am not quite sure what could cause this. The problem for me is that i work with vkrc controllers, but we had them refitted with the standard krc software. So i dont know how this changes things.
What happens if you close E2? and go to T1. does the message then disappear? and are you able to move?
-
when we close E2, we are out of EXT mode (? appears)
E2 message disappers.
Not able to move. -
That is correct. so E2 is working. the (?) appears because you tell the controller by closing E2 to go to T1 but if you leave the kcp switch on Auto the controller doesn't not know what to do.
Back to the problem, When you put the controller in T2 by putting the switch on the kcp to manual and leaving E2 open. Can you then move the robot and run a program?
Also i just remembered that you have to put the kcp to manual to acknowledge some messages with the kcp. after that you can switch to auto to let for instances a PLC give that signal. -
We can put the controller in T2 by putting the switch on the kcp to manual and leaving E2 open(E7 closed).
We can move the robot and run a program.
Yes we have to put the kcp to manual to acknowledge some messages with the kcp.
Still can not switch to AUTO EXT mode.
Would you recommend us to update the system to KRC2 and upgrade to Windows XP?
-
well upgrading should not be necessary, we only did it to make programming easier. We also did not upgrade to windows xp only to standaard krc2 software. The windows 95 version runs fine.
The strange thing is that your wiring for E2/E7 seems to be oke. you can move a program in T2 but not in auto external. so there can't be to much wrong.
How have you wired your automatic external? you should give at least 4 signals in the right order.
1.) move release (this one could be always activated, depends on your needs. i also don't know if i translated this correct. so i could be named something else in your case)
2.) Confirm messages
3.) drives on, and wait for drives on output
4.) start. -
1 move release ( move enable ınp13 always active)
2 Confirm messages ( ınp15 on_off) Even I make it on can not quit from STOP_MESSAGE
3 drives on, and wait for drives on output (drıve_on ınp14 /drıve_on out =out1012) even when I start form KCP drives sesmm to be ON but can not quit from STOP_MESSAGE, no movement because of E24 start ( not possible external start)
Manual mode: there is STOP_MESSAGE when I do not press KCP safety buttons, When I press clears STOP_MESSAGEExternal mode: even DRIVE ON since there is STOP_MESSAGE and E2 no movement
Sequence till $CONF_MESS starting seems OK
even I press $CONF_MESS button; $STOPMESS (STOP_MESSAGE) is not turning to off
Might be a problem regarding $IN_HOME (seems 0 now)?? Referencing_status seems 1 .Should be absolute home position in order to start externally?
-
trial photos
-
external photo
-
As far as i know you don't need to be in the home position to start a program, maybe in the vkrc software you do, but i don't know that. The thing that interest me is that in T2 you do have the message, but it disappears when you hold one of the safety buttons. I don't think that this is normal behavior, i haven't seen it on 1 of our robots that's for sure.