Thanks,
I stand corrected
Thanks,
I stand corrected
It was the complaint that they didn't want to use floppies or CD that got me. The autoload you refer to is the RS232 communications software that enables the robot to run gcode milling applications direct from a pc using kss4.2 I take it if I am not mistaken?
Kuka KRC1 running windows 95 networked to pc running windows xp either native or emulated in a virtual machine for file transfer.
The reason for my post was so it would register if anyone did a search my answer would show up. I've got 11 KRC1 kr150 machines and keep sixty year old Kombis and Mercedes heckflosse as daily drivers. I have been helped by others on this forum so I would like to help others if possible in return.
I have this working perfectly, anyone needs a helping hand please give me a call out
I am a data communications pro and robot amateur
https://wiki.hackerspace.pl/_media/projects:kuka:krc1_hardware.pdf
The book for the extra axis
Wish you luck!
Let me know if you need different details.
Hope these are some use to you. Mods please delete if I'm using too much space
I have a couple of seven axis controllers so if you need photos or pictures of how to connect the add on cabinet just ask
I should also have added that a second level switch or even a hub should be used when working things out as it removes even more complexity as they will provide hardware level connections between the devices without adding software/firmware complications .I believe the VXD to Windows connectivity is made inside the Kuka robot and can be tested by pinging the VXD fixed ip address from within the Kuka windows installation. I have done this on my krc1/win95 installation and another KRC2/Windows XP installation. with newer Kuka robots your mileage may vary. You are 100% correct, tracert can be slow / is slow
Dont know if you have found a solution yet but here is some troubleshooting advice from a very very old network guy. assign all IPV4 network addresses to the devices you wish to connect manually as a purely local network (no DNS server involved). go to the cmd window on your windows computer or robot that looks like dos and type tracert followed by the ip address of your target device (you can see how it works by typing tracert google.com or tracert microsoft.com on a machine connected to the internet though this will use DNS to resolve the IP addresses concerned- you dont need this added level of complexity if just hooking up a couple of devices locally)
The tracert command will give you the ip addresses that the data packets will follow to get to the target device. if you have the average ADSL internet connection that you are testing on it will return the ip address of your router followed by the router it is connected at the organization supplying your internet connection followed by others till either you get to microsofts spoof address or 30 hops.
Hope this helps
Mudpig
My Hero!
I have an EMT but no cable. Thanks for posting the diagram. Do you perhaps have the part number for the male connector on the cable that plugs into the RDC box of the KRC2 and Krc1? I have obtained the male connector that plugs into the EMT.
Thanks in Advance
Mudpig.
Display Morei would just temporarily deactivate all filedbus drivers for now, basically first get robot operational and then worry about interfacing with other things.
in the IOSYS.INI , in the DRIVERS section, place semicolon in front of driver that shows errors (this will comment it out).
example with profibus driver enabled and all other drivers disabled:Code Display More[DRIVERS] ;CNKE2=21,cnke2CPInit,cnke2drv.o ;DNSC6=20,dnsc6Init,dnsc6drv.o ;DNSC5=19,dnsc5Init,dnsc5drv.o ;DNSC4=18,dnsc4Init,dnsc4drv.o ;DNSC3=17,dnsc3Init,dnsc3drv.o ;CNKE1=16,cnke1CPInit,cnke1drv.o ;INTERBUSPCI=15,ibsCPPciInit,ibpcidrv.o ;DSEIO=14,dseIoInit,dseiodrv.o ;DNSC2=13,dnsc2Init,dnsc2drv.o ;DNSC1=12,dnsc1Init,dnsc1drv.o PBMASL=11,pbmsInit,pfbmsdrv.o ;DEVNET=2,dnInit,dn2drv.o ;INTERBUS=1,ibusInit,ibusdrv.o ;MFC=0,mfcEntry,mfcdrv.o
so just place semicolon in front of the PBMASL=11 line...
To get past move enable, login as Expert, go to AutoExternal configuration and change $MOVE_ENABLE to 1025.
inputs 1025 and 1026 are special - 1025 is always true, while 1026 is always false."programming manual for system integrators" and "system variables manual" are your friends.
to power up drives and do something (anything) with the robot, you need to hold enabling switch in mid-position. SIR status indicators on the bottom part of the screen need to have both S and I green. only then try pressing jog keys etc. if you are trying to run program, R in SIR also must be color other that gray (program must be selected, not open). however, before you can run programs or move robot in any way (other than axis specific), you must get robot mastered...