G.A. vd. Hoorn

> one doubt: in universal_robot folder there are urX_moveit_config(X be some numer) is it moveit config folder or we should generate the moveit configuration file through moveit "setup_assistant" The packages...

Yes, that's why I wrote you shouldn't do that, unless you have experience and would be able to edit the new configuration to work with the files we have here...

This looks like a nice cleanup. Thanks for that @jwhendy. :+1: I'm still a bit foggy on why that offset is needed, but I think I'll just have to re-read...

Thanks for the PR. I'm wondering though: this seems to duplicate quite a bit of information which is already part of the various `.mps` files and the existing visual studio...

So to get it clear: this adds a CMake macro which generates command lines to instruct `mpbuilder.exe` (from the MotoPlus SDK) to build MotoROS. Correct? > Originally, I wrote this...

I'm not sure I follow @Julien-Livet and @Gaspard-Bourgeois: why did you close the PR?

Asking KUKA for these directly is most likely the best way. Unless someone has these lying around, of course. Getting the models from KUKA would also be a guarantee that...

I just checked the KUKA [download site](https://www.kuka.com/en-de/services/downloads), and if you filter for the `KR 210-2`, you should get robots, not pedestals.

@jwhendy wrote: > SolidWorks doesn't let me import the existing `.dae` visual models to try and modify those. No, that won't work. For modifying Collada, I always use Blender.

Always preferable to get this sort of info from the mfg itself. +1 for asking them. re: create both variants: yes, that would be an option, although it would lead...