Declaration of arrays in KRL with constants

    Hi!

    In C and other languages you can declare array sizes by using named constants instead of hardcoded numbers. I have tried to do the same in Kuka KRL in both the data list and in the source file without success. I can only declare arrays by using hardcoded numbers. This makes a maintenance problem if you have multiple arrays that should be the same size and you need to change the size in the future.

    What I try to do (but, it's not working):

    CONST INT MY_CONSTANT= 5

    DECL INT firstArray[MY_CONSTANT]

    DECL INT secondArray[MY_CONSTANT]


    I repeat that this is about declaring arrays, not initializing them. Is this not possible in KRL or is there som alternative way I should use?

    Thanks!

    Not a supported feature, unfortunately.

    A workaround I have found so far for non-runtime arrays is to write a sort of house keeping procedure that makes sure the arrays that should be of either same size and/or bigger/smaller than other arrays, are.

    Alternatively and what I am more inclined towards now, is to write exhaustive tests, that would find this and other errors.

    Writing tests would probably be the way to go then. I guess workvisual doesn't have a testing framework either or version control. The project-files are stored as single file *.wvs which makes them hard for tracking in git. Great if there are any tips on this. Export project as single files and then import them each time also seems cumbersome. Suggestions?

    Thanks!!

    In most projects I have worked so far installed modules, I/O mapping and hardware didn't change much or at all beyond the first few starting stages. Afterwards, the changes were made mostly in KRC/R1 and KRC/STEU folders. So I copy only those and they contain only simple text files; which is what Git is really good at tracking.

    In WorkVisual, if you open View->"Programing and Diagnosis" tab, you can see all KRL programs/modules in the project. If you can't- click over a yellow icon that says "Display module nodes instead of file nodes".

    Then, if you place mouse cursor over a white triangle on the left side of the project name and click the left mouse button, the project will expand to show KRC directory. If you mouse over the KRC directory and click right mouse button, a popup context menu will appear that has an option to Copy the KRC folder. Left click on the Copy option and then you can paste KRC folder in a directory in a File Explorer (or some other file manager program) window.

    Far from Git integration, but one can automate the process from there.

    Alternatively, there is Documents->WorkVisual x.x (x.x-WV version)->Repositories where I assume the latest version of KRC directory contents are held. However, WorkVisual has plenty of bugs and occasionally messes up in a quite spectacular fashion (I don't mean just crashing or freezing), I don't have enough faith to trust WV will work in the kind of simple deterministic way, that I would expect of it. Therefore, copying KRC folder manually seems like a safer bet.

Advertising from our partners