G.A. vd. Hoorn

O and since the plugin has been released with support for the prefix, _and_ is checking for it in LTS releases, a warning about it being ignored in the new...

@Jmeyer1292 wrote: > Which is exactly what every other IKFast plugin but this particular one does. The only problem I see with this PR is that it will bring this...

Interesting. Is this a tool which is the result of a sort of consensus in the KUKA/KRL community, or the collected opinions of the author? Either way would be fine...

@simonschmeisser: did you get a chance to test `krllint`?

Is this still something you want to do @simonschmeisser ?

@shaun-edwards: do you remember why you closed this? The current driver cannot use any other names than `joint_N_L` because of #111. If that gets fixed, then the specific naming scheme...

I've got fixes for just about all the outstanding old bugs locally, including #111. There are some places where things happen I do not fully understand though. So if I...

@thiagodefreitas: I'd like to make use of your offer to look at your notes. Could you take a look at #226?

@MarqRazz wrote: > If you look in [joint_trajectory_action.cpp line 240](https://github.com/ros-industrial/industrial_core/blob/a85789b6b33bd0a460c236a6b89c14dbf125e2c0/industrial_robot_client/src/joint_trajectory_action.cpp#L240) you will see that this is where the action server is checking to see if the arm has made it...

@Pranav186: unless you either have a multi-group system or are trying to run trajectories at almost max robot performance with no stops in between them I'm not sure you are...