Karel files

    I see in a backup of a controller that there are vr files. I suppose these are Karel variable files?
    I don't see any pc files. I suppose pc files contain the programm code of Karel programms?
    So, could this be right that a backup all of above contains vr files but no pc files?
    Do we need sources to be able to edit the vr files?
    What other Karel file types could there be? And for who of them do we need the sources?

    Quote from Plc_User


    I see in a backup of a controller that there are vr files. I suppose these are Karel variable files?

    Yes. As far as I know, they are Variable Records.

    Quote from Plc_User


    I don't see any pc files. I suppose pc files contain the programm code of Karel programms?

    Yes, those are the p-code files.

    Quote from Plc_User


    So, could this be right that a backup all of above contains vr files but no pc files?

    In my experience (R-30iA & B) an AoA also includes the .pc files, but it could depend on where they were located on the controller at the time of the backup (FR:, MD:, etc).

    Other posters may know more about this.

    Quote from Plc_User


    Do we need sources to be able to edit the vr files?

    Well, no, but I do not know whether you'll be able to 'edit' them without the .pc files either. You can load a .vr into a Roboguide cell, but without the associated .pc file, it won't show up as program variables under either the Variables section in the Cell Browser or when using the TP.

    If you have the sources of the program, you could use those to first compile the program and then load the .vr. Now the variables should show up in the normal places, but only if the sources are for a 'compatible version' of the program (ie: contain the same variable and type declarations and definitions).

    Quote from Plc_User


    What other Karel file types could there be? And for who of them do we need the sources?

    I can only think of .va files as being really related to Karel programs, but they are just the ASCII versions of the associated .vr files. You cannot use them to edit the .vrs: they're read-only and you can't reload them onto the controller after editing.

    Other files that people may associate 'with Karel' could be .etx (Error Dictionaries), .ftx (Form Dictionary), .utx (User Dictionary), .stm (Server Side Includes for the web server option that can 'reach into Karel') and .cf (KCL File).

    Those are all the source file extensions. Translated dictionaries end up with a .tx extension and are un-editable binaries. The other two are essentially text files, so they can be edited easily.

    Edited once, last by rf103 (April 23, 2015 at 9:11 AM).

    You are correct that an "All of the Above" backup (sometimes called a User backup) does NOT contain KAREL .pc files

    The KAREL files, among many others, and including system operating files, are contained in the Image Backup. The robot Image cannot be restored to the robot piecemeal. Image restorations are either all or nothing.

    any user generated *.PC files will be saved, as well as a select few from Fanuc. mostly built in macros for options installed. ie MATRIX.PC or IRSNAP.PC etc. There are a lot of them that are hidden however.

Advertising from our partners