Kuka merge krl component error

[rajgardon]

Hello everyone, I am using the Robots Grasshopper plugin with a KUKA robot. Everything was working perfectly before, but suddenly all of my past, previously working definition files have started throwing this error on the merge krl component

:1. Solution exception: Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection.

Since this is happening across all my old programs without me changing the Grasshopper logic, I am confused about what triggered it. Has anyone encountered this sudden array index error before? Could this be related to a recent plugin update, a change in the robot library, or a Rhino/Grasshopper update? Any advice on how to debug or fix this would be greatly appreciated. Thank you!

[visose]

Thanks for the report. Just to clarify, Merge KRL is not a component from the Robots plugin, so it may belong to another Grasshopper plugin or to a custom definition.

Robots has had some recent updates with breaking changes, so it is possible that the component or plugin providing Merge KRL now needs an update as well. I would first check which plugin provides that component and whether a newer version is available.

If the issue still seems to come from Robots after that, please share a minimal Grasshopper file that reproduces it, along with the Robots and Rhino versions you are using, and I can take a closer look.

[rajgardon]

Thank you for the quick response and all the help.
I talk about this component. maybe i labelled it wrong but it appears in the robots plugin tab.

[visose]

Thanks, that screenshot helps. Even though the component appears under the Robots tab, it is not a component from the Robots plugin.

Grasshopper plugins can place their components on any tab, including tabs created by another plugin, so the tab location does not necessarily identify which plugin owns the component. In this case, Merge KRL is likely coming from another plugin or a custom component.

Since Robots has had recent updates with breaking changes, that other plugin may need to be updated as well if it depends on Robots types or APIs.

[rajgardon]

Understood, thank you for clarifying that! I didn't realize third-party components could map themselves into your tab layout. In that case, would you happen to have a standard example file for working with KUKA robots using your native workflow? Specifically, I am looking for the proper way to convert the program data coming out of the Create Program component into the final .src files without relying on external merging tools. I am well-versed with using the Robots plugin for other robot brands, but I couldn't find an example file or documentation specifically tailored to setting up the KUKA file export structure. Any guidance or sample definition you could share would be highly appreciated!.

[visose]

Yes, for the native Robots workflow you should not need an external KRL merge component.

Create the program with the Create Program component, then use Save Program to export it. For KUKA, Robots writes the required .SRC and .DAT files, including the main .SRC file and any numbered subprogram files. Copy the generated files/folder to the controller and load the main .SRC file.

I am not familiar with what that external merge component does internally, but it should not be required for the standard Robots KUKA export path.