SkyeFire I know it's been a few years, but did you find any more info on this?
We've got issues where the "condition handler" doesn't turn off during recoveries, You can select "cancel and recover" and it continues to alarm for vacuum not made, even thought the outputs are off.
I understand this is the opposite to what your original issue was, but the info may still be relevant.
KSB?
KSB is Kuka System Bus and EthernetIP is not part of it...
EIP and PNET are using virtual5 of KLI. they both have drivers using same resource so they are not compatible...
my guess is that you tried to do everything in one step - simply switch WoV project from EIP to PNET or the other way around. the issue is that installing/uninstalling driver needs reboot too so it would be safer to do an intermediate step where active WoV project uses neither EIP nor PNET... and then uninstalling driver should be not an issue (no errors). and then (after reboot), installing the other one should work
but that is just a guess. you also did several things that i would not go for such as making backup(s) of everything before making any changes. and one after another you did even more changes. there is a saying that once you find yourself in a hole, maybe it is not bad idea to stop digging. for example deleting of "C:\KRC\USER\ProjectRoot"...
Both Communication protocols are children of the "Bus Structure" node in WV, which is why I said KSB. There's no doubt you know these things better than me, and I'll take your word that "Bus Structure" and "Kuka System Bus" are unrelated.
Your guess is correct, I attempted to make the switch in one step.
I had previously viewed the KSR as a nicety, whereas now I view it as a necessity. This robot is a rental from Kuka where the project is a Proof of Concept. I didn't think I'd be needing to take/use an image. I thought wrong.
Display MoreThat image only gets created when you are making a backup with the KSR stick, and have the option selected while doing so.
There might be a "factory image" in that directory, made when the KRC shipped from Germany, but you'd still need the KSR stick to restore it.
If you don't have a KSR stick... well, you can pull the SDD from the KRC, connect it to a regular PC using a SATA-to-USB adapter, and use CloneZilla or Acronis or some other disk-cloning software on it. This will only clone the drive as it is now, of course, but it would make a safe-ish rollback for trying anything, like what I'm about to suggest.
To wit, finding the hidden directory, opening the .WIM files (use 7Zip, the .WIM image files are just a type of Zip file), and overwriting the files in the C: partition with the contents of the C.WIM file. If it worked, this would restore the robot to factory-new, after which you could install your last working WV project.
NOTE: I've never tried this, and have no idea if it would work (theoretically it should, BUT....), hence you shouldn't even try it without making a complete backup image first. It's definitely a high-risk procedure. Hence, don't try it without making a solid full-drive image (even of the robot's current broken condition) first.
Honestly, though, i would recommend working with KUKA tech support first, they might have a better solution. The above is a very speculative idea.
Thanks!
I've put the call into KUKA to purchase a KSR, but I don't like sitting here with a robot I can't move. I've also reached out to friends to borrow one if the timeline is too much from Kuka.
I don't want to make more work for myself, but I appreciate your response. It's nice to know there is an alternative path, albeit risky.
You may have a backup on the hidden partition, with a kuka recovery stick you will be able to restore from it.
If not kuka can provide you with a download of fresh wim image files
make sure you take a backup of your broken system but dont over write the ones on hidden partition if you have them, you will be able to take out the KOP files for the tech packs if you dont already have them backed up
I did pull the KOPs before any of this happened. I might need to get a fresh image from Kuka, but I'll cross that bridge when I get to it.
@everyone:
What types of errors would I have gotten if I left the Ethernet KOP active in the project and only removed the EthernetIP from the KSB? Or if I had pushed both EthernetIP and ProfiNet options to the controller? Or if I left both EthernetIP and ProfiNet on the KSB? I know that I did not install the Profinet Option using the smart HMI before I deployed the project in WV.
I'm curious what I might have done to cause this error.
The Addition of the ProfiNet Option was the only change from the previous project. I'm trying to diagnose where I went wrong, or does this seem like an external problem?
Thanks everyone!
Do you also have searched in files?
I searched in files where I thought it might be, but I'll take a shot at GREP/some other solution to search inside files.
Do you have a KSR image backup? Because that's about the only idea I have.
I've heard about a "ghost image hidden in the D:\ drive" is this easily accessible with a recovery USB?
Better restore the system with an image backup.
Rather than wov, uninstall ethernet IP from Smartpad/ additional softwares
Again install Profinet technology pack.
Then perform necessary modification in workvisual.
This will be the safest procedure.
Smart HMI is not functioning, that is my issue.
No, he has no image.
Call Kuka hotline. I see no other chance.
KRCDiags went into my contact on Friday, We'll see if I can beat them to a solution.
Cheers!
Yesterday I deployed a project, changing from EthernetIP to ProfiNET.
WV didn't have any issues/Errors. Controller looked like it rebooted to initialize drivers and such.
KSS splash screen came up, then it took a KRCDiag, and popped the error message.
"Unhandled Error
The following error occurred while communicating with the kernel system:
$CONFIG not correct ($CONFIG |/R1/System/Collmonlib.dat/LEARN_MODE)
The application must be shut down."
KSS 8.6.6
HMI 8.6 B0296
Kernel KS V8.6.296
I have included images of the error, I typed it out so it's searchable in the future.
I am unable to deploy a new project. I removed the projects in C:\KRC\USER\ProjectRoot\ and ran C:\KRC\UTIL\InitalProjectSetup\InitalProjectSetup.exe as admin. This succeeded from what I can tell, but the error remains.
I've looked for the Collmonlib.dat, I've looked for LEARN_MODE...
I'm out of ideas, and I know the answer is going to be to use the USB... which I don't have.
Thanks in advance SkyeFire & panic mode!
Cheers!
