Software Request to KUKA - the robot forum wish list

  • Post here your suggestions to KUKA for the improvement of the robot software.


    The KUKA development looks in here to implement ideas for updates from operators and programmers!


    Thanks for your suggestions, maybe they will be included in the next update. :blumen: :love24::yesyesyes:

  • Editing ConfigMon.ini on HMI is slow and difficult but sometimes still the quickest way to get something displayed.


    This can be much quicker if:


    1. When saving edited VARIABLE field should check if "Name" field is still empty, simply copy variable name there. but only if field is still empty. This way one only need to type it once....


    2. Set refresh as default. One only goes through trouble of typing some entry to see the value. It makes no sense to manually add refresh each and every time.


    3. Try to reuse height of already entered entry as default. Nobody want to waste time formatting each and every new entry from ground up.


    4. One day it would be nice to see intelisense offer suggestions as one is typing (why not popup a window and let user pick variable from list of declared variables).

    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

  • 5. Dialog messages that accept keyboard input, like ABB RAPID already accepts (without having to buy the OrangeApps add-on).


    6. A more standardized user interface across all the different windows and workspaces of WorkVisual. Right now, some things you access via double-clicking in one menu have to be accessed via right-click in another. And trying to manually select a directory forces you to click-click-click your way through entire directory trees, rather than typing or pasting a long path.


    7. Memory. Being limited to less than 10MB of programs on a modern controller is ridiculous.


    8. Something similar to Fanuc's PCDK


    9. An option to make Archives (locally or via WV) with date&time stamps as part of the file name, so as to enable "rolling" backups, and

    10. An option, when Restoring, to select an Archive to restore


    11. Better Space Visualization for SafeOp (that "ROBOT CAN MOVE!" floating tag gets completely in the way of what I need to see).


    12. SafeOp visualization in WorkVisual, before deploying a project, to save time on the testing cycle for Safety WorkSpaces


    13. Some kind of tool for SafeOp to make it easier to predict where the robot will encounter Velocity Reduction near the edges of Safety WorkSpace boundaries -- as it stands, the only way is to try moving the boundary, reboot, and test in automatic or T2 -- there's no way to see it happen in T1.


    14. A way to make changes to SafeOp settings without requiring a 5-minute reboot cycle (or two of them!).

  • 15. WoV need auto-save option so one can focus on work rather than time tracking and clicking Ctrl+S.


    16. When program has fault, Teach pendant should open fold(s) and display line with error directly. Manually opening closing folds and scrolling up and down just to resolve some bugs is very inefficient. More over, in KSS8.5 does not even bring faulty line into view. It is always one or two line below displayed code. One does not even see the cursor and good luck finding it by scrolling


    17. Use different color for comments. When one opens fold, everything is green. One cannot easily tell comment lines and code lines apart. Also top closed fold color is too dark, specially red. Makes it next to impossible to see if sharing something on most projectors (training session or project discussion for example).

    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

  • 18. a way to configure a smartHmi button also in relase 8.3 [in the 8.5 has already been implemented]

    19. a way to use the debug mode in WoV also in automatic mode [now is possible only in T1/2] [in my opinion the ABB RobotStudio is the overall complete Robot suite]

  • 20. A way to dynamically create spline blocks without using DirLoader.

    21. In Actual position window, either additionally display Status and Turn in decimal or only in decimal. I can think of uses that need binary, but those are rare (at least for me). Could also show current tool and base.

    22. Option turn off space mouse indefinitely without having to edit text files tucked away in the controller.

    23. A bit of a pie in the sky, but how about object oriented programing?

    24. Position of not only flange and TCP, but all the other joints too. Something we can do ourselves, but nice if it were included.

    25. Interrupts returning variables without needing those variables to be global.

    26. Structures that can have arrays in them of not just char type.

    27. Native linux version of Workvisual?:whistling:

  • 29. Capability to use constants in array declarations, e.g.


    decl const int cint_ComNameLen = 60

    Decl char ComName[cint_ComNameLen]



    30. Forward() and Inverse() could take Tool and Base as parameters instead of using active ones.

    Edited once, last by Mentat ().

  • 31. allow folding of long lines. most languages use underscore as continuation character. simply wrapping long lines creates a lot of mess that is next to unreadable. i would prefer to have control over how things are presented on HMI


    32. allow ILFs to access ANY valid position declaration. Even if it is an array element for example.... or part of structure.


    33. allow choosing default data type for ILF motions. why it has to be E6POS and not AXIS or E3AXIS or E3POS or whatever...? of course one can manually declare them in DAT file and then call them up in ILF but that defeats points to use ILFs. I run into this with client using bunch of 5axis robots (agilus and Quantecs that are not operated in PAL mode), and they found this very challenging. Part of the problem is that with PAL mode off, robot will move unpredictably and it will collide with surroundings when data points are declared as Cartesian, even if tool and base are correct and point is taught correctly. Yet KSS will happily offer Cartesian data types for any new ILF point, no matter what. don't shoot the messenger, I did not choose or recommend those systems, just had to deal with them and reporting the issue.


    34. Please change defaults in MsgLib so any message is always logged to database. by default Why the default setting is to NOT log messages? This is kinda important.


    35. allow monitoring of any task any time. switching interpreter and having to select robot program just to see what submit is doing is ridiculous and way too cumbersome. Should simply pick task and see what it does. right away... and have option to single step.


    36. HALT command should be available as ILF. I always add it on systems with UserTech and it is a life saver.


    37. Need debug option to step-over for subs and functions or better yet - "run to cursor". It is just not practical to single step though long loops just to get to some point line or two lower. Or have to abort debugging session, close program, mark some files as not visible, select program and again run to program just to get back to where one already was.


    38. Both WoV and KSS have hard time identifying mismatched quotation marks. Both generate tons of unrelated messages and none of them point at the bad program line that is the root problem.


    39. WoV Search Results window is not good. It is very difficult to resize and move around at least in Win10. The grabbing edges are some 20 pixels outside the window which is quite awkward. Also tab names of every search should only show search term. Extra wording such as "Search results" only limits what can be displayed. When several searches are done, one cannot even see search strings, only the prefix "Search results".. Search string is reduced to dots. Yes I am aware of the button on far right that can display the same as a list.

  • 40. The ability to call subroutines/functions, or access variables, using strings, would be very handy sometimes. ABB RAPID allows this. Right now, if I had a hundred subroutines called "MOVE_STATIONx_TO_STATIONy" (where x and y are integers representing station numbers, let's say 10 stations total), handling the various subroutine calls for all the possible combinations of x and y would require an enormous set of nested SWITCH or IF statements. But if I could call subroutines by a string representing their name, I could use two lines of code: an SWRITE to build the string, then a call using the string.


    I don't think this is really possible without completely changing how KSS handles compile-time linking, though, so I doubt it'll ever happen in KRL. Although it does appear to be possible in Java, so the iiWA can probably do it. And if Sunrise ever supplants KSS in the "main" robot product line....

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account
Sign up for a new account in our community. It's easy!
Register a new account
Sign in
Already have an account? Sign in here.
Sign in Now