RTos error multiprocessor sharing

    I have a KR240PA robot where the SmartHMI software won't load on the control PC and won't connect to the smart pad.

    I added a GPU and a screen and found that when VXwork and RTOS are loading it detects that Windows is using all CPU cores.
    In dual-core systems, Windows should be using one core and RTOS the other core.
    Does anyone know where to fix that? The bios has a lot of options greyed out, saying you need to contact your administrator. There is a disable multicore option in the bios but no way to change it.

    please check READ FIRST...

    any software issues - state software versions

    any hardware issues - state hardware version

    whatever you added, you probably had drivers installed and that may have ruined things.

    KSS and RTOS are proprietary so not much can be done there. users need to practice due dilligence and have good backup. In this case i would say remove whatever you added and restore HDD from a good backup image.

    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

    Quote from Nicolas Molina Methfessel

    In dual-core systems, Windows should be using one core and RTOS the other core.

    And this information is based on what? This is definetly not the case for KRC and never has been. They share a single CPU but RTOS has higher priority and is in worst case able to block windows completely.

    But as Panic said. Restore backup or install anew. Your did install something that corrupted the system. Even if some people think its different KUKA Windows is no out of the box standard windows but specially modified by KUKA to allow coexistence of Windows and RTOS. Hence one should be careful with adding and installing freely.

    Fubini

    Sorry, my first time posting.
    KSS version 8.2.16
    Hardware KRC4. With the control computer motherboard D2608-K, that doesn't have a display output. Motherboard D3076-K and D3236-K have DVI-I

    The problem started after a power loss. The smartpad would not connect and on the CSP the first (green) LED blinks and the Sixth LED (red) is on.

    So I added a low-power GPU with a DVI-I output. Like the other Kuka control pc motherboards have. Connected a display to see what is going on.
    I reinstalled Kuka's software from the KUKA_release file on drive D:
    But still, I get the error that RTOS cant load.
    Before seeing the RTOS cmd window I get another error that a library cannot be loaded.

    I would have tried with the KUKA USB but I don't have one and don't know where to get one. I live in Bolivia.

    Since RTOS is installed with KUKA Windows its not surprising that reinstalling KRC did not fix it. I am afraid you would have to reinstall Windoes embedded. Unfortu atly this requires a Kuka usb stick and the installation image. Both can only be obtained from KUKA. I recommend talking to a Kuka branch near you. Just look at kuka homepage for contact data.

    Fubini

    I will have to find a way to buy a KUKA USB. And having the USB I can replace the HDD with an SSD (this KRC4 came with an HDD)

    The corruption surely happened because of bad batteries or even the CMOS battery on the motherboard.

    This robot was not being used. I am installing 3 robots and setting them up. Installed and connected them. Replaced batteries, but the store had only 4, I replaced the first 2 robots, those were already mounted. I mounted this robot later. and had the batteries ready to change and did not do it. I am still beating myself for it. I even took the drives from the other two robots and have a restore image saved. I didn't even know that this had an HDD and not an SSD like the other 2.
    Thank you, now I know that the only probable way out is the KUKA USB .

    Like having the mastering kit, better to not need it, but essential when you do, or set up a new robot.

    KUKA USB Stick is just a tool to create and restore image of HDD or SSD. It is nice, convenient, fast and compresses image too for smaller footprint. But it does not come with an image already. To restore image using this tool, you need to have already collected the image for that specific robot using same kind of tool. If you did not do that, you do not have backup image.

    In that case you will need to contact KUKA to also get default image for your KSS as well as USB Stick. USB will be pricey but the image could/should be free if you provide them with robot info.

    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

    default image will not have your robot, tech options, settings, programs etc.

    so first you need to collect all needed files and transfer them some place safe. a good idea is to make an image of current state too (even though it is corrupt - you can delete it later after everything is back in order).

    Since you cannot get HMI running, at the very least get:

    a) all tech packages from D:\

    b) WoV project(s) from C:\KRC\USER\

    c) Create fresh KRCDiag

    d) manually collect anything else that may be of use like ConfigMon.INI and and things that ares tech package specific, such as KFD, icons and menu configurations for UserTech (if you have it), etc.

    e) INTERN.ZIP from D:\

    The better you are prepared the fewer surprises and disappointments will be faced later.

    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

    Thank you for the recommendation. I will install it on a new drive, so I will have all the data on the old HDD and I have an image of the drive on a server just in case.
    Can I update de KSS version? (within the 8.2.xx) that is great I have another robot on kss8.2.18 I would update that one too. And I have on Kss8.3.17 maybe I could ask for the latest Kss8.3.xx

    I am guessing those 8.Y.xx updates are mainly bug fixes?

    I also read that on the Kuka recovery USB there is a BIOS update for exactly this motherboard D2608-K. So that will surely be some bug fix.

    P.S. I found where to buy a recovery USB 3.0 from a spare parts reseller. On Kukas website, there is a new 4.0 but there is no information to know if it is compatible with these older robots

    Within a release lets say 8.2.xxx you are always able to update free of charge. Just need to ask KUKA for the software. As you said its mainly bug fixes. Updating from 8.2 to 8.3 (if possible on your controller) requires to buy a new license from KUKA.

    KUKA Recovery Sticks do not have any restrictions in relation to the kss releases afaik. You only need to be able to boot from usb. Its just some hdd imaging software inside a bootable windows. If I remember correctly difference between 3.0 stick (8gb?) and 4.0 (16gb?) is only capacity. Size for newer kss release images starting from 8.5 I think just were to big to fit on the old one.

    Fubini

    KUKA also has software updates allowing upgrade of USB Recovery sticks to newer software stand (more features) but obviously it cannot increase capacity.

    however, newer software can still give a new lease on life for old sticks even when they are smaller in size. they may not have enough of space to collect both partitions in one go, but ... could do so one partition at a time (key is C:\), can be used to backup restore to a different storage, can be used on your PC to backup/restore media taken out of KPC etc.

    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

    So it would be better (futureproof) if I get the Kuka recovery USB 4.0.
    Do you know how long it takes for a Kuka account to be verified?

    It has been 9 days and I still can't order anything directly from Kuka. I gave them my company's website address, physical address, and all.
    And on the Upgrade link, you sent me I get an empty folder message, maybe because my account isn't verified yet.

    Quote from Nicolas Molina Methfessel

    My account just got Verified. I am ordering the recovery usb 4.0

    The KSR will let you make full hard-drive images backups and restorations. So, the next thing you'll need, as Panic has already described, will be a "factory image" of the robot. You can get this from KUKA tech support, if you provide them the serial number of your robot and KRC. Placing this image into the correct directory on the KSR stick will allow you to rebuild the robot by using the Restore function.

    The procedure should go mostly as follows:

    1. Using the KSR stick, make a backup image of the robot as-is
    2. The image files (usually C.WIM and D.WIM, one for each hard drive partition) will be in the Images directory of the KSR stick. Move these files to someplace safe, with a note describing them (date, time, condition, etc)
    3. With the Image directory empty, copy the "factory image" .WIM files from KUKA into this directory.
    4. Use the KSR stick's Restore function

    At this point, the robot should be 100% "factory new". If you have a regular Archive backup, or a good WorkVisual project file, you can now load that onto the robot. This process should bring the robot back to the condition it was in when the Archive or Project were created.

Advertising from our partners