Posts by DS

    aha, now I understand, those INC_AXIS values were not changed by whoever installed extension but probably myself some time ago changing increments with pendant. This means that the only issue was my incorrectly done mastering and now it is solved.


    regarding $robcor.dat - I did not change that file after re-installation. It is a file with $MODEL_NAME[]="#KR2150L110K_2 S C2 FLR ZH150" inside. Is there some test I shall do to ensure it is correctly installed file?


    Thank you indeed! Without your great input and this superb forum I would be lost.

    MOM  panic mode,

    I apologize, I think I have caused some misunderstandings.

    • I just finished mastering and now robot moves correctly. From that I conclude it was at least one of the issues.
    • The label on the robot was put before it was extended. It just shows which robot was later extended :smiling_face: The distance between centre axis 3 and 5 is 150cm; there is 40cm piece that is in the middle of the arm in slightly different color :smiling_face:


    Now, I was wandering if that $MACHINE.DAT file from source disk that I copied now in current MADA directory (described in #117) is good file. It has $TRAFONAME[]="#KR2150L110K_2 S C2 FLR ZH150" but it also has these values below:

    $INC_AXIS[1]=10.0

    $INC_AXIS[2]=10.0

    $INC_AXIS[3]=10.0

    $INC_AXIS[4]=10.0

    $INC_AXIS[5]=10.0

    $INC_AXIS[6]=10.0

    REAL $INC_EXTAX[6] ;SCHRITTMASS ACHSSPEZIFISCH EXTERNE ACHSEN

    $INC_EXTAX[1]=10.0

    $INC_EXTAX[2]=10.0

    $INC_EXTAX[3]=10.0

    $INC_EXTAX[4]=10.0

    $INC_EXTAX[5]=10.0

    $INC_EXTAX[6]=10.0

    REAL $INC_CAR[6] ;SCHRITTMASS KARTESISCH WERKZEUGBEZOGEN

    $INC_CAR[1]=100.0

    $INC_CAR[2]=100.0

    $INC_CAR[3]=100.0

    $INC_CAR[4]=10.0

    $INC_CAR[5]=10.0

    $INC_CAR[6]=10.0


    And I could not see these values in KUKADATA\KRC1_CD\INTERNAT\MADA\KRC2\KR2150K_2_SSCBS\L110\FLOOR\R1\$MACHINE.DAT

    One of the ways, I guess, is to change values back and see if it spoils robot movement :smiling_face:

    Not sure what those variables stand for.

    MOM, thanks for pointing out my mistake, yes indeed there are KRC2 folders with L110 subfolder! :smiling_face:


    However, I inserted source EDC in the controller and I see that robot has the same Z problem (which it did not have before I took it out). From this I assume that I have perhaps made a mistake while doing mastering... I will re master robot!

    Thanks, this was useful!

    Did a few double-checks:

    • Booting from source disk, KSS was showing exactly the same model number.
    • Checked documentation this model (KR 150 L110-2 K) is indeed the only one from 150 range than can be extended to 3500 (see pic, D=total reach)

    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

    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?

    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.

    Autoexec.bat on C: attached

    Config.sys on C: is empty !!!

    Config.sys on D:\ENGLISH\WIN... attached.


    Shall I copy contents from D: to empty config.sys on C?


    I did remove Standard IDE/ESDI Hard Disk Controller. Powered off/on. The situation did not change. Device manager shows exact same screen.

    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.


    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.

    There is an option to uninstall GT.


    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:

    pipo,

    HDDRawCopy is what was needed! It worked! And it produced EDC copy that was recognized by system with no changes in BIOS necessary! Great! Thank you!


    During installation, the only decision I was not sure about was weather to leave R1, Mada, and one more folder settings from previous installation when it asked. I decided to leave all 3 of them.


    Once the installation was finished, when booting controller, it still did not go past Cross3 screen (same issue). CTRL+ALT+DEL indicated that Cross3 [Not responding]. Instead of End Tasking Cross3, I End Tasked 2 apps - Guard9x and Guardtray. Then Cross3 rebounded and KSS loaded.


    Do you have any idea if I shall I try installation without keeping old R1, Mada, ....?

    pipo, thanks for advice!


    Original EDC starts OK and I double-checked that EDC model supports LBA (Logical Block Addressing).


    I did clone the whole disk (with both partitions) but obviously I have to search for an alternative way of making a clone as Acronis DD neither gave me the option to preserve LBA, nor it has any documentation that even mentions this acronym. Acronis DD did not mention MBR but the disk was supposedly bootable. I assume I need another software product, perhaps older :smiling_face: for making a clone.


    If other clones will not work I will follow instruction with BIOS, thanks!

    Shortly after powering on controller (with cloned EDC in), pendant shows "Invalid system disk. Replace the disk, and then press any key". In the screen I see that Pri. Master Disk: LRG, ATA 33, .... When I compare this to some historical screen photos I see that back in old times it was LBA, ATA 33, ....


    I checked in BIOS, did not see an option to activate LRG. Do you agree that this is they likely reason for controller PC to not recognized cloned EDC?


Advertising from our partners