KRC2 booting issues

    Quote from pipo

    There is an option to uninstall GT.

    Quote from javaman

    ninstall the antivirus software does not give any protection only makes troubles.

    pipo, javaman,

    This proved to be great advice! I did run Uninstall.exe that resides in Ikarus -> Guard95 folder, it took 1 min and Cross3 is no longer stalling!!!! With this the system is back to a state before things went wrong. Pendant lighting on 2nd attempt still persists but that is a separate discussion.

    I will perform mastering, then work for a week or so and if this version of system proves to be stable I will make a clone of current cloned ESD, hopefully without using pins :winking_face: as proper IDE sockets are on the way :smiling_face:

    to pipo, panic mode, javaman, MOM, sjx,

    with deep respect, gratitude and really from the bottom of my hart - thank you! With a lot of patience you guided someone without basically any knowledge in industrial robots through the process of getting the robot back in operational state! This was quite an educational journey, we went from MB battery change, starting up the board, checking ATX, loading KUKA profile in BIOS, performing EDC clone, re-installation and finally uninstallation :smiling_face: I tried to document it with maximum detail as my own small humble way of paying it forward to other readers of this forum who may stumble upon same or similar issues. But it is you who really did it!!! Thank you!

    D.S.

    I am glad that the problem is solved!

    I don't know why, but I had the same or a similar problem. A series of startup errors. Most of ini files cannot be read. This happened 10 minutes ago.

    I'm going to get a big hammer to show the robot where the INI files are

    :uglyhammer2:

    Edited once, last by pipo (August 19, 2020 at 7:31 PM).

    I had this feeling - will this really be the end of the story? Apparently no :smiling_face:

    I was about to load code to KRC2 via CD and realized there is no CD Drive recognized :smiling_face:

    A few things I checked:

    • On startup screen PC is recognizing CD drive in the same way as always (see pic)
    • In BIOS I found nothing suspicious, apart from that I live in 2001 :smiling_face: (see pic)
    • CD drive itself is lighting up and ejecting, etc
    • CD drive is not displayed by Windows Explorer (and KSS)
    • I tried playing with SMART option for HDD in BIOS did not help (though historically SMART was never enabled)
    • I tried Add New Hardware, but Windows did not see CD Drive as new hardware so there was nothing to add
    • I even put original primary EDC card in (source of clone), no difference.
    • Secondary IDE Controller is shown in Device Manger with exclamations, primary, too (see pic). I do not know if historically this has always been like this

    I was not brave enough to remove IDE controllers (impossible to remove one it says need to remove all), shall I?

    I sense that there is some very simple solution for getting CD Drive back visible in Win, but what is it? :smiling_face:

    Assume it will be visible in KSS whet it is visible in Win 95.

    MOM thanks for reminding about #98

    on the cloned EDC (the one in the controller):

    KUKADISK VOLUME

    - no viruses by Panda

    - volume was 70% fragmented I de-fragmented it by Defraggler.

    - CHKDSK found issues and corrected them

    KUKADATA VOLUME had no viruses, no fragmentation and no sector issues

    I put EDC back into controller - no change, CD Drive not visible in Windows Explorer, config.sys file empty.

    Shall I reinstall KSS in your opinion? I amkind of reluctant as missing CD Drive seems Windows, not KSS problem.

    your screenshots of device manager show that bunch of devices have icons with yellow exclamation points. this means no correct drivers are loaded. and if devices have no correct drivers, they cannot work. this is why devices connected to IDE such as CD drive are not detected - because IDE controllers are inoperable.

    they are normally part of Windows so this suggest that those files are corrupt or missing or something of that kind is going on.

    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

    Hi,

    to summerize:

    you have3 a kr c2 (because of the 133 main board)

    you have a mfc2 card (pci)

    Exclamation marks does not mean that the driver are not working, they may work but probably not working as expected!

    can you show the complete device list (searching for mfc2)

    regards

    MOM

    Hi

    to solve problems try this:

    1. Start pc and go to device manager

    2. On the firs yellow row ( driver for floppy disk) click with right mouse button and select to reinstall driver. I do not remember exatly how to you must proceed in Win95 with the reinstall.

    3. On the next yellow rows make the same

    May be you need to find how to reinstall drivers with google search

    somehow managed to solve the problem.
    My CD ROM is NEC CD-3002A, so I found driver here: https://download.cnet.com/s/nec-cd-3002a/

    • unpacked it and manually placed NEC_IDE.SYS file on C:
    • added to autoexec.bat file this line: LH C:\Windows\COMMAND\MSCDEX.EXE /D:MSCD0001
    • added to config.sys file this line: DEVICEHIGH=C:\NEC_IDE.SYS /D:MSCD0001

    CD Drive appeared in Win and KSS and I was able to copy files over it!

    Thanks indeed for pointing towards autoexec.bat and config.sys

    The only thing that I do not know weather I should add also this line "DEVICE=HIMEM.SYS" to config.sys file?

    that works though it is a workaround. MSCDEX.EXE and HIMEM.SYS are 16-bit drivers created for DOS. HIMEM.SYS allows DOS to get access to memory above 640k limit. Windows has own driver to manage memory using 32-bit so do not add it. the only time you may want it is if you don't start windows GUI and boot to command line prompt ... for example to play some DOS game.

    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

    panic mode, thanks!

    Regarding subject of arm extension (KUKA KR 150-2K -> 3500mm)

    I saw that reinstalled KSS is not keeping Z axis correctly, remembered your advice #87 to keep $MACHINE.DAT and $ROBCOR.DAT files. I made comparison of both files to original disk I cloned. Even as I was electing during the installation to keep old R1, I was surprised to find that $MACHINE.DAT had indeed a few different values (see pic). File $ROBCOR.DAT had exactly the same content. Naturally I did copy original MACHINE file to current installation, restarted (including cold restart), right version of file is on C: but robot is still moving strange on Z.

    The size and number of files in MADA folder now is exactly the same for source and clone, could there be another file in another folder that holds changes that relate to extension of the arm?

    qou1UnCJAHZfwICUOZIdz3uVJBv8y1KJeU89kk82wdJ2Lp1th3WN1Do4gZ4ZhWIVwTqA0BILd7BDdBt3j5KI2ZP0UAZR0lXpXyZJuRDs1F6taZMn7umpUm3boSr4qScnl2EEuatF

    Hi,

    what is the robot type shown in BOF

    what was the length of the other robot?

    I quickly trying to check the machine data KUKA KR 150-2K (sadly there is no KUKA KR 150-2K, KUKA KR 150-2 only)

    I only found

    KUKA KR 150-2 with 3500 mm

    and

    KUKA KR 150 with 3000 mm

    regards

    MOM

    mentioned two files are MADA for the manipulator arm.

    there should be folder on D: with MADA for every supported manipulator.

    this can be useful to get to know what is inside MADA. sure you may need to learn some German too but basically compare standard MADA for manipulator arms with and without wrist extension. when extension is used, robot rated payload is reduced and model is named differently.

    for example if you have basic robot (without extension), it may be called something like KR150. if extension is added that robot model becomes something like KR150L120. The L120 means arm is longer and payload is no longer 150kg, now it is 120kg

    Various suffixes may exist too and K is "Konsole" or shelf-mounted robot. They have lower but wider carousel (compared to standard arm).

    about replacing MADA... there is a process to it. no files must be in use or locked. you can only replace MADA when no interpreter is active (robot or submit). if you choose wrong MADA, of course robot will not move correctly.

    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

Advertising from our partners