Starting of KUKA HMI is not possible

    The message is not very specific. It just states that no communication between windows side and rela-time OS is possible. I am guessing the real-time OS did not start. Restore your system from the last working image backup.


    Fubini

    to make a cold boot, you can get to windows level, navigate to C:\KRC\UTIL\REGUTIL, and doubleclick on registry file for cold start. next boot should be a cold boot.


    but to me:

    severe internal error = restore HDD from last known good backup.


    one should have at least one known good backup and it is a really good idea to make new backup(s) before making any changes.


    trying to recover non-functional system without backups is usually extremely unreliable, complicated (requires insider knowledge), expensive and very time consuming. on the other hand making archive takes only a minute. creating HDD image takes 15 min.


    which is i do both on EVERY robot - even the brand new one that just arrived from KUKA.


    btw. KUKA recommends getting replacement HDD after 5 years or so since the risk of corruption and drive failure is much greater. judging by incomplete screenshot you have an ancient (15 year old?) system which is a literal time bomb.


    btw entering BIOS and resetting CMOS settings has nothing to do with the content of the HDD.

    1) read pinned topic: READ FIRST...

    2) if you have an issue with robot, post question in the correct forum section... do NOT contact me directly

    3) read 1 and 2

    Thanks,


    I tray with cold start from registy didnt help. Image file I dont hae but i find some folder with some instalations files, please see the picture in attach.


    From log file I get this:


    09:24:10 .Getting version from registry

    09:24:10 .Version: "V5.6.12"

    09:24:10 .KRCVersion: "KR C"

    09:24:11 .Reading "timeOut" = "120"

    09:24:11 .Reading "trayIcon" = "true"

    09:24:11 !Cannot find path: "//configuration/kukaroboter.startkrc/kukaVga"

    09:24:11 !Cannot find path: "//configuration/kukaroboter.startkrc/kukaVga"

    09:24:11 .Starting KRC

    09:24:11 .Running "C:\KRC\BIN\KukaDb.exe"

    09:24:11 .CreateProcess succeeded

    .Commandline: "C:\KRC\BIN\KukaDb.exe "

    .Directory: "C:\KRC\BIN"

    09:24:11 .Running "C:\KRC\HMI\KUKA_HMI.exe"

    09:24:11 .CreateProcess succeeded

    .Commandline: "C:\KRC\HMI\KUKA_HMI.exe "

    .Directory: "C:\KRC\HMI"

    09:24:11 .Waiting 120 secs ...

    09:24:17 .WM_COPYDATA received: "Init"

    09:24:17 .WM_COPYDATA received: "Start 10%"

    09:26:03 .WM_COPYDATA received: "Init 20%"

    09:26:11 .Timeout for splash screen

    09:26:19 .Running "C:\KRC\BIN\LTCserver.exe"

    09:26:19 .CreateProcess succeeded

    .Commandline: "C:\KRC\BIN\LTCserver.exe "

    .Directory: "C:\KRC\BIN"

    09:26:19 .Starting service "KrcWmiProviderSvc"

    09:26:21 .Service start pending...

    09:26:22 !Service not started.

    09:26:22 Current State: 2

    09:26:22 Exit Code: 0

    09:26:22 .Starting service "EscService"

    09:26:23 .Service start pending...

    09:26:24 .Service started successfully

    09:26:24 .Starting service "KUKA Scheduler Service"

    09:26:24 .Service start pending...

    09:26:25 .Service started successfully

    09:26:25 .Start sequence finished

    09:30:09 .WM_COPYDATA received: "Init Softkeys 30%"

    Still looks as if the VxWorks (Real-time OS) did not start. If that's really the case you need to setup from scratch starting from the KUKA Windows Embedded Image. But before doing this you could try only to reinstall KRC software (the one you probably found somewhere on d:). Also checking your HDD before starting to setup anew or switching to a brand new one might be useful. Since when its damaged, you will probably have similar issues soon again.


    If VxWorks is started or not can be seen by trying to open a telnet connection


    Post
    RE: KRC2 Cross3 error
    I try Telnet 192.0.1.1 and it have some error ?

    Is this VXWorks?

    robot-forum.com/attachment/32549/
    Atanas Goranov


    Command might be telnetk instead telnet in some versions.


    As always before starting anything make a backup image!


    Fubini

    I have another hard disk, from working controler.

    If I changed/copy RDC file from old one (not working),

    can this help? I need to change SafeRDW file also, where I cane find him?


    Thanks,

    Marko

    there should be more log files (and event logs - kuka log viewer)


    in your post #5

    Quote from marko05nikoic

    09:26:19 .Starting service "KrcWmiProviderSvc"

    09:26:21 .Service start pending...

    09:26:22 !Service not started.

    09:26:22 Current State: 2

    09:26:22 Exit Code: 0

    vxworks should be running (normally after reaching 10% you can connect to base system)

    Thanks to all, at the end reinstalation off KSS helps

    It was located on D drive.


    But like Fubini says :


    Since when its damaged, you will probably have similar issues soon again.


    Working for now, we will see.


    Thanks one more time.


    Marko

Advertising from our partners