When loading the KRC2ED05 robot cabinet, a message appears
When loading the KRC2ED05 robot cabinet, a message appears
-
Ryno -
April 22, 2022 at 7:32 PM -
Thread is Unresolved
-
-
After that, "kuka hmi" does not start
-
After that, "kuka hmi" does not start
Yes thats pretty much all this message says. Maybe corrupt HD. Maybe corrupt KSS installation.
-
Yes thats pretty much all this message says. Maybe corrupt HD. Maybe corrupt KSS installation.
The cabinet was functional, then I rearranged the Krc2 cabinet, messages came out that in the photo, then I rebooted the Krc2 cabinet again and the error "Kuka hmi" appeared
-
The message is only standard Windows if an application crashes nothing Kuka specific. So not much information there. Whatever rearrange means it might have corrupted something. If you can undo your rearrangement it's worth a try. Maybe also a look into windows event handler helps to get at least some direction. There are also HMI loggings containing caller stacks of crashes. Usually these can only be interpreted in detail by kuka but sometimes the called functions help to get also a direction for a deeper look.
-
The message is only standard Windows if an application crashes nothing Kuka specific. So not much information there. Whatever rearrange means it might have corrupted something. If you can undo your rearrangement it's worth a try. Maybe also a look into windows event handler helps to get at least some direction. There are also HMI loggings containing caller stacks of crashes. Usually these can only be interpreted in detail by kuka but sometimes the called functions help to get also a direction for a deeper look.
The problem is that the application "kuka hmi" does not load even when I try to launch it from disk "c" "kuka hmi.exe "
-
not unusual if HDD is corrupt...
-
not unusual if HDD is corrupt...
If the hard disk is damaged, then "windows" starts. Only "kuka" does not start hmi.exe " it tries to start but then freezes and a message comes out.
-
HDD is just storage media holding bunch of files. a very big bunch of files... some of them are part of windows... some are KSS...
HDD does not need to be damaged for files on it to be corrupted.
and just because Windows managed to boot to command line or GUI, it does not mean that everything with Windows is ok... or with KSS... there is a lot of files and anything could be corrupt. and this is a very very VERY common problem with systems that are not maintained properly.
properly maintained system will have regularly created backed up, regularly replaced batteries etc. people that do not do those things wake up one day with system not being able to run. the HDD may contain countless carcasses already but now the same ones that ignored system health are wonder which if the carcasses littering HDD is the one that stops system from running.
well it is simple really - nobody can tell you which specific file or files are bad. it is a lot of files that one would need to check and nobody has time to investigate. even if they had time, both Windows and KSS are proprietary and inner working of most of things is just not disclosed.
the fix is simple too... restore last good backup. it is 15min job and you can run again. and if you do not have a backup, sorry bit that is the problem you got yourself into.
-
HDD is just storage media holding bunch of files. a very big bunch of files... some of them are part of windows... some are KSS...
HDD does not need to be damaged for files on it to be corrupted.
and just because Windows managed to boot to command line or GUI, it does not mean that everything with Windows is ok... or with KSS... there is a lot of files and anything could be corrupt. and this is a very very VERY common problem with systems that are not maintained properly.
properly maintained system will have regularly created backed up, regularly replaced batteries etc. people that do not do those things wake up one day with system not being able to run. the HDD may contain countless carcasses already but now the same ones that ignored system health are wonder which if the carcasses littering HDD is the one that stops system from running.
well it is simple really - nobody can tell you which specific file or files are bad. it is a lot of files that one would need to check and nobody has time to investigate. even if they had time, both Windows and KSS are proprietary and inner working of most of things is just not disclosed.
the fix is simple too... restore last good backup. it is 15min job and you can run again. and if you do not have a backup, sorry bit that is the problem you got yourself into.
We have a hard disk image and a spare hard disk with an image. The robot's archive is also regularly produced. Thank you very much for the tips!!! I'll try to change the hard drive.