Delete write-protected karel file

    The robot that I'm using still has several KAREL programs from an old discontinued project that I would like to delete since I am running into some memory issues on TEMP. Some of these programs are write-protected, and since they're KAREL programs I can't just turn off the write protection. Any ideas on how to get rid of these programs?

    What I've tried without success:

    - delete via a karel program (DELETE_FILE), gives write protection error

    - delete via KCL (DELETE FILE), gives write protection error

    - create a new karel program with the same name, only without any protection error. This won't let me compile and overwrite in roboguide

    Hi hoitzing,

    don't struggle with that!

    Do a INIT start !! (and maybe upgrade software)

    This way you'll avoid a lot of problems!

    (you have to know what to do after init start!)

    For me it turns out that this is the easiest and shortest way to get an old robot running, because you don't have to care about old sysvar settings and progs!

    Best

    Hi hoitzing,

    the INIT start will do a "factory reset"!

    This comes in handy when one is in situations like yours.

    First:

    AOA and IMAGE backup of your system to return back to.

    At startup press [PREV]+[NEXT] or [F1]+[F5](depends on controller version) to access boot/config menu.

    choose INIT start

    When done load/restore you're saved "sysmast.sv" because the robot won't be mastered anymore.


    Since this topic is more advanced please check posts and manuals for this!

    best

    I agree, an Init start seems like overkill. It sounds like you have lot's of stuff already setup on this robot that would be a real waste to just throw away.

    Have you tried deleting the files from a controlled start?

    You could also try to use the COPY_FILE command with the overwrite switch enabled.

    KCL commands can be debugged pretty easily through the Telnet interface. Just set a password for the KCL user from the teach pendant and login through your favorite terminal.

    Hi pdl Hi hoitzing,

    too much overkill? I agree with you in part!

    I have "re commissioned" at least 15 old robots in the past.

    Some of them had some system variables set so, that the strangest things happened!

    One notices this only later. And in the end you have to make an INIT start.


    The most curious and at the same time most dangerous happened on a LRMATE100::

    CODE:

    Code
    L P[1] 250mm/s FINE
L P[2] 250mm/s FINE

    But the robot behaved as if the following code was executed:

    Code
    R[1] = 250
LBL[1]
R[1] = R[1]+100
L P[1] R[1]mm/s FINE
L P[2] R[1]mm/s FINE
JMP LBL[1]

    This is not a joke! He got faster and faster in T1(!) until he got off with an OVC alarm!

    ---

    If you get a used Windows PC (from wherever) you would reset it too right?

    ---

    So maybe:

    Make AOA

    Perform INIT start

    restore/perfom mastering (sysmast.sv)

    restore backup except system/sysvar.sv

    ----


    Best regards

    I've seen a fanuc robot moving at automatic speed being in T1... (not T2, T1, I ensured of that) people called me crazy, but nope, it was real... that was with one robot with a Rj3 controller, the ones that trimmed the path a lot on automatic.

    Also seen robots that gave collisions mid air because someone loaded the sysvars.sv from another controller with same mechanical unit and firmware version, I had to restore the original image and do all config from scratch, after doing it it worked perfectly... it seems that inside the sysvar file is the info about the maximum amperage a motor should draw, also the coll detect configuration.

    I've needed to restore original images on various ocassions, and that solved much issues... tgats what you do when you are desperate and cannot find any other solution, and it often works.

Advertising from our partners