No. Never had one, actually.
No. Never had one, actually.
And inside the SYS folder on robot backup You can also find a *.bk4 file, that is a previous saved version of the *.c4g file.
If the .c4g file isn't good for any reason, You can change the extension from .bk4 to c4g and load it on the robot.
Since the the bk4 is a backup, You will maybe need to make some adjustments/configurations on your robot.
You can find this file on robot backup, normally at .../UD/SYS/...
I also vote for an specific topic at Manuals section. And a zip file would be fine.
I have also observed this behavior while doing Virtual Commissioning with Process Simulate, with other robot brands.
At that time we consulted Siemens, but had no good answer about this. On our case, we had a huge cell, with lots of robots and devices.
Anyway, the clock on path editor was showing the "right" time in the end of the simulation, so we were using it as our reference.
I'm moving this thread to Process Simulate board, as look as this is a Process Simulate, and not a KUKA problem.
I like the idea.
Unfortunately, I don't have any program sample of these robots.
Maybe someone else here can help.
I had the same problem here. Maybe the installer is missing some files. Or maybe is too old to run on newer operating systems.
Anyway, SRXMONIE.EXE is opening on my machine (Windows 7).
If it is working properly, I cannot say.
The link is working, and the LUNA software (very old stuff, I think) can be downloaded clicking in this link
But I didn't find any manuals there.
For KRC4 You will need WorkVisual.
If I recall correctly, there was some dip switchs that must be configured if the robot was a KRC1 or KRC2.
But I'm not sure if this applies to the labelled KUKA adapters, or to the generic ones.
When using N++ what language coding do you use in order to get the best TP code visibility?
And second issue: which encoding do you use?
I use my own syntax highlighting set. With N++ is pretty easy create a new one.
Some years ago I uploaded my .xml file here on the forum.
The current one is different. Simpler, I think. Follows attached.
Regarding the syntax highlight, my biggest concerns are: what is a instruction, what is a comment, and, in FANUC case, what is a commented instruction.
And, about encoding, N++ can handle this very well.
But if You are creating a program from scratch, what You must observer isn't encoding, but line endings. Newer robots normally handle this well, but older robots wants UNIX (LF) line endings.
Notepad++, then Roboguide, then real robot.
Notepad++ (or any other text editor) is used to start the project and do the heavy lifting. Scratch, copy, paste, etc. I know Roboguide has an internal (and somewhat hidden) text editor, but I prefer N++ because it is faster.
With the raw program(s) written, is time to upload it to Roboguide and debug. Maybe teach some basic positions, etc.
With these more "mature" programs, is time to upload in the robot itself, touch up the rest of the path and make tests.
But this happens mostly on small projects with single/few robots. Big deployments normally have virtually commissioned OLP programs that in theory are plug and play.
Emphasis on "In theory"...
This WorkVisual is the one that came with the robot? 6.0.5 was released some time ago.
If Yes, I would suggest download the newer one (6.0.15) from KUKA website.
About the all in one solution for KRL/KUKA development, In the KRC2 ed05 days, there was another WorkVisual, called WorkVisual Process, that I never seen personally, but have a 3D environment in it.
And I remember seeing a thing called Visual Process in the first KRC4 brochures, from 2010/2011.
Basically, a 3D environment inside WorkVisual (the KRC4 WoV).
I always wondered why this didn't succeed further.
But, to be fair, RobotStudio is still light-years ahead of any other industrial robotics IDE/Simulator.
I don't remember if these older versions have the Backup Cell option, where the cell is saves as a single .rgx file, that can be after (re)imported.
I think this was introduced only on later V8 revisions. Anyway, If You version have this feature, You can try to make an .rgx and reopen it.