We had someone load a service pack 2 into the krc2 controller and the controller only boots to the Cross software. We removed the service pack 2 and now the operating system will not boot. It was running krc version 5.2.15. How do we restore the operating system? By doing a Cntrl-Alt-Del, and when task manager comes up find our way through until we can see all the files on the system. Called hotline, but that was useless. Waiting for tech support to call back. Good luck with that.
killed operating system
-
plcguy -
February 23, 2012 at 12:20 PM -
Thread is marked as Resolved.
-
-
plug in a keyboard and at the first windows screen press an d hold CTRL key and keep held
This will boot to windows only
then if you go to windows explorer and look on the drive you will find the setup.exe file for the kuka software
-
We could not find the setup.exe anywhere so we reloaded the software. And quess what? Same problem. One of the guys is on the phone with KUKA. Reloading the operating system did not change anything, just wiped out our harddrive so now we have to figure out all the IO and other settings. What a mess
-
You didn't make backups of the robot when it was in operating condition?
Installing Windows service packs onto the robot is a bad idea. Probably the only way to fix it is to re-install Windows, followed by re-installing KSS. After that, if you have an Archive from that robot from when it was working properly, you should be able to restore your settings and programs without any trouble.
-
We had to reinstall windows and kss, palletizer and a few other programs. Good thing there was a backup of data. The backup contained the I/O mapping. All is working except there was a password for the ethernet connection to the PC and we do not know what it is. Other then that all is good. That was a hard lesson for maintenance not to install desktop software into the equipment.
-
Password for accessing the PC? You mean the PC in the robot? Are you trying to access it via FTP or SMB for file transfers?
The KRC2's default Windows username (for this version of KSS) is 'Administrator' and the default password is 'kukarobxpe2'
-
Hi Skyfire,
What is the username and password for accessing the shared D drive on KRC4?
Thanks
-
'administrator' '68kuka1secpw59'
Sent with my Windows Phone using Tapatalk
-
• WinXPe 1.0 User name = Administrator Password = KUKA
• WinXPe 1.1 (VKSS 5.4) User name = Administrator Password = KUKA
• WinXPe 2.0 (KSS 5.2, KSS 5.3, KSS 5.4, KSS 5.5, KSS 5.6 and KSS 7.0) User name = Administrator Password = KUKA
• WinXPe 2.2 (from KSS 5.2.19 Build85 HF03, KSS 5.5 and KSS 5.6) User name = Administrator Password = kukarobxpe2
• WinXpe 3.0 (KSS 8.0, KSS 8.1, KSS 8.2) User name = Administrator Password = 68kuka1secpw59
• WES7 4.0 (KSS 8.3) User name = KukaUser Password = 68kuka1secpw59 -
Do You know the password for the new 8.3.8? 68kuka1secpw59 doesn't work anymore. ..
-
Seems odd i dont have a version to try it on here but will try to find out
-
• WinXPe 1.0 User name = Administrator Password = KUKA
• WinXPe 1.1 (VKSS 5.4) User name = Administrator Password = KUKA
• WinXPe 2.0 (KSS 5.2, KSS 5.3, KSS 5.4, KSS 5.5, KSS 5.6 and KSS 7.0) User name = Administrator Password = KUKA
• WinXPe 2.2 (from KSS 5.2.19 Build85 HF03, KSS 5.5 and KSS 5.6) User name = Administrator Password = kukarobxpe2
• WinXpe 3.0 (KSS 8.0, KSS 8.1, KSS 8.2) User name = Administrator Password = 68kuka1secpw59
• WES7 4.0 (KSS 8.3) User name = KukaUser Password = 68kuka1secpw59printed , framed and on the wall , now i want to see which robot will not give me access
-
Do You know the password for the new 8.3.8? 68kuka1secpw59 doesn't work anymore. ..Works for me on 8.3.11.
-
And 8.3.9
Sent with my Windows Phone using Tapatalk
-
Works for me on 8.3.11.
o used that password with login 'kukauser' and worked! with 'administrator' doesn't work..