Modifying modules offline with a text editor is perfectly fine, as long as you do not tamper with the file names, the DEFDAT, or the first DEF in the .SRC file -- that one has to match the name of the module. Also, do not tamper with any of the header lines prefixed with &.
The free OrangeEdit program is very helpful with things like this.
You can also use workvisual to transfer the whole project and edit the program files over network.
But many prefer to use orangeedit, where you can import archives, edit, export and load onto controller with backup -> restore.
The problem you describe can be fixed by just rebooting the controller. when you ad a new program to the robot folder it won't be loaded in until the robot is rebooted. Someone from kuka explained to me that the kuka software only works from the RAM memory not the hard drive, so during start up everything is loaded in to the RAM memory. This problem always occurs when you make changes outside of the Kuka software.
The problem you describe can be fixed by just rebooting the controller. when you ad a new program to the robot folder it won't be loaded in until the robot is rebooted. Someone from kuka explained to me that the kuka software only works from the RAM memory not the hard drive, so during start up everything is loaded in to the RAM memory. This problem always occurs when you make changes outside of the Kuka software.
Hello,
Same kind of advice, you can copy the file from the pc to the D drive of the robot, then copy from the D drive to the program folder on the smartpad. That will force the controller to read the file. It's quicker than to reboot the controller.
Alex
Untrue -- if you copy&paste a module into the /R1 directory on the teach pendant navigator, that is the RAM drive. The module will be subjected to an immediate syntax and compile check, and if it passes, everything will be fine. No reboot is required. A reboot would only be necessary if you copy your modules directly to the /R1 directory on the hard drive -- then you would have to perform a cold boot to force the RAM drive to be reloaded from the hard drive.
There can be issues when copying multiple modules at once, especially if they have interdependencies with each other. Then it might be necessary to load in a certain order, or perform small edits on them to force a re-compile if they have linking errors.
Untrue -- if you copy&paste a module into the /R1 directory on the teach pendant navigator, that is the RAM drive. The module will be subjected to an immediate syntax and compile check, and if it passes, everything will be fine. No reboot is required. A reboot would only be necessary if you copy your modules directly to the /R1 directory on the hard drive -- then you would have to perform a cold boot to force the RAM drive to be reloaded from the hard drive.
There can be issues when copying multiple modules at once, especially if they have interdependencies with each other. Then it might be necessary to load in a certain order, or perform small edits on them to force a re-compile if they have linking errors.
I've encountered a few situations in my experience where modules that have a lot of subroutine calls (specific example, I had a switch with 12 subroutine calls) will not pass the syntax/compile check UNTIL the robot is rebooted.
Hi all,
An advice, at least, in krc4 do not put the programs in the work directory. If the file doesn't exist the controller doesn't recognize as a program, if it's already in there, the controller will replace your changed file by the last file that was working there.
Regards
Neranol
"work" directory? What is this? The robot's directory tree generally goes /R1/Programs/, or /R1/SYSTEM, or R1/TP, or R1/MADA. I don't recall a directory called "Work" anywhere in that tree.
Hi,
When i say work directory is R1. For several time times i had the problem this.
I'm trying to save your time. But if any of you want to try go ahead.
Regards
Neranol
I copy&paste modules into /R1/ on a regular basis without any trouble, as long as I don't create linking errors by the paste sequence. I've never had a new file overwritten by the older one. There will be paste failures if the file being replaced is linked to the SPS, or if the new file does not have a fully valid syntax structure.
