Hello,
KRC4 does not recognize src,dat and sub formats.
Please see the attachment.
KRC4 does not recognize src format
-
elenamitovska1 -
June 12, 2017 at 1:46 PM -
Thread is marked as Resolved.
-
-
Are those files unique in your system? What are the error messages? What did you do before zthis happened? ...
https://www.robot-forum.com/robotforum/kuk…rum/read-first/
If my car does not run I usually do not just send a picture of my car to my dealers workshop and expect usefull answers.
Fubini
-
Hey,
so we have activated dozen different configurations from WoV, suddenly, after the last activation of a WoV configuration it showed that.
So there is no error message, the only error message is that it cannot find the submit interpreter. However it is there but only shown as a txt file.
Actually the extension is not txt it is sub but KRC4 does not recognize that, it opens the file as a text file. This is for every other file, src and dat.
All files are opened as a text files. -
Already tried a "Cold boot" with -reread all files- (the second term is not literally) ??
-
yes , we did tried with reload files and cold start..
-
What changed between the last working WV download, and this one?
I've never seen this come from WV before -- only when loading large numbers of module through the Navigator. Generally, when a large number of modules show this kind of behavior, something caused the compiler to choke early in the load process.
One thing to check is the current size of your KRC/R1 directory on the robot hard drive. If it's close to or over 10MB, that could be part of the issue. Overloading the RAM drive is one of the things that can cause this.
Failing that, my first suggestion is to go into these files in WV and make a small change -- add a blank line or comment, then re-deploy. Sometimes the compiler needs to be forced to recognize a change and re-compile the module.
If that doesn't work... hm. It's a bit of a brute force solution, but you could try removing all of your modules from /R1/Programs. Then work through /R1/TP, /R1/SYSTEM, and so on -- open each module in the Editor, make a minor change, and approve the edit. Unless there's some external factor screwing with things, this should at least get the unmodified system modules recognized again. Once that's complete, load your /R1/Program modules one at a time over the network or from a USB drive. With any luck, whichever module is causing the problem should reveal itself.
-
isn't this the same thing:
https://www.robot-forum.com/robotforum/kuka-robot-forum/kss00070-no-more-user-memory-available/
I see that TRACE folder again...
Simple solution is to restore backup image using Recovery USB Stick but ... i would be surprised if someone actually created that backup before making changes to the system. Do you have recovery stick?
Another option is to get someone (knowledgeable) to fix this. Is there a nearby KUKA tech? He/She will have right tools and skill to get you out of this.[/size]My guess is that someone pasted (or dragged) folders to wrong location. Either way, if you are considering doing something about it yourself I would say:
1. MAKE FULL BACKUP NOW - yes i know your system is already a mess, but i am confident you are capable of making so much more . so... at least make sure to be able to get back to THIS state
2. PLAN before you do anything (ask yourself how can each of your actions be reverted and get you back to previous state)
3. It may be a simple fix too... Generate list of all files and directories for comparison with other robots. For example try command line like "DIR C:\KRC\ROBOTER\*.* /S > D:\KRC_FILES.TXT", and post it here and wait for help.
Also you may try to replace WoV project directly from HMI (do not use WorkVisual). Make a copy of Base project (if not altered yet) and activate it. Then login as expert and delete C:\KRC\ROBOTER\KRC\R1\TRACE and reboot. If you still see KRC:\R1\TRACE after reboot, your CURRENT WoV project(s) are corrupt
-
I realise this is a pretty old thread but I came here looking for help because we had the same issue occur yesterday so I thought I would share our experience in case it can help the next person!
After a power failure we had this issue. We solved the problem by deleting a diagnostic archive zip folder sitting in a sub folder of KRC\R1 that was created about a month prior. The archive has a copy of the R1 directory and so none of the programs were unique, as the guys above indicated could be a problem.
Cheers!