Hello
They are used for KRC32
Hello
They are used for KRC32
Try to use the newer driver
[DRIVERS]
DEVNET=2,dnInit,dn2drv.o
the first number is the module adress in this example 5
[DEVNET]
INW0=5,0
INW2=5,2
INW4=5,4
INB6=5,6
OUTW0=5,0
OUTB2=5,2
Hi
here is APS arch for your robot.
You can use notepad to edit your robot files
hello
The ni-cd battery is'nt the reason that you have lost the Machinedata. If these batteries are worn out the robot will lose the axiscallibration if you power off the robot.
It's the 3 AA battery's on the powersupply-card.
I will have a look in my old backups to see if I can help you.
Hi
If you Palletize with robot flange poimting downwards you could try to use pallet mode.
$PAL_MODE=TRUE
Hi
I had a look at your pictures. I don't see any extension on the robotarm. The previous owner might have shortened it for some reason.
in that case the maschinedata has to be changed. Post a better picture of the robotarm.
How did you define your TCP?
Hello
Go to Regedit
Hkey_current_user\software\KukaRoboterGmbH\KukaBof\OcxControls\Usermode\Password.
Take away the secons passwort but leave the default password.
Write CONTINUE on the line before IF
CONTINUE
IF $TIMER[3] > 0 THEN
OnEkiIntrpt1()
$TIMER[3] = -10
ENDIF
I have had a similar problem. in my case it turned out that the project was corrupt in some way. I had KUKA support to lock at it but they had no solution. If you have a backup of your files you can use one of the other projects rename it and add your files to it.
Batteries in the cabinet is probably worn out.
Have you tested to change the network cables.
Select a program that contains a homeposition, mark that line and touch up the homeposition.
Hi
The signals are declared in steu/mada/$machine.dat.
If you are using the Cell program then you may add some data to R1/system/$config.dat in the folder Autoext globals
Can it be that you did the same mistake as when you described it. counter6530 = couter6530+1
in that case couter6530 is the problem.
In office lite there is a map called allmada witch contains machine data for the different robot types. try to find it there.
Sorry I made a mistake there. In Office Lite I would use Outputs instead of Inputs.
If you have an inword (IW_PLC_Recipe_Number) make it an outword (OW_PLC_Recipe_Number) then you can modify the outword and look at the value of it.
A possible way to do it is to link outputs to inputs in the SPS.sub and put a value to the outputs
In $Config.dat
DECL SIGNAL IW_PLC_Recipe_Number $IN[201] TO $IN[216]
DECL SIGNAL OW_PLC_Recipe_Number $OUT[201] TO $OUT[216]
in Sps.sub
IW_PLC_Recipe_Number = OW_PLC_Recipe_Number
You only have to put the machine data files from the robot backup into the corresponding map in Office-Lite