G.A. vd. Hoorn

Just thought I'd add this: this exact issue seems to also have been reported by @thiagodefreitas in https://github.com/ros-industrial/motoman/pull/42#issuecomment-54307172: > Although motoman joints are usually named as joint_letter, I have an...

@tanimfresh: first thing to make sure is you get this error from the driver and not from MoveIt itself. MoveIt has added a similar check. I would suggest to check...

> In this case, is the only solution at the moment the method you proposed of changing the driver source? No. The right thing to do would be to diagnose...

> I am indeed using a different urdf generated by MoveIt. This confuses me: MoveIt does not generate any urdfs. You'll have to clarify. And taking a step back, please:...

> I am referring to the following section of the MoveIt setup assistant: I would advise you to never use that functionality of the MSA. Due to the fact I...

For future comments: could you please avoid posting screenshots of code or terminals? It's all text. Just copy-paste it into the comment and use proper [code highlighting](https://help.github.com/en/github/writing-on-github/creating-and-highlighting-code-blocks). > We will...

Also: if you could share your own versions of the packages you linked to that would help. Right now I don't have a clear picture of what you changed or...

> I don't have the interactive markers, which I was hoping was a separate issue... but I am able to plan and execute random poses through RViz just fine. This...

I've just checked your wireshark capture but it does not seem to contain a message exchange for a failed attempt at trajectory execution. Is this the correct capture @tanimfresh?

> I saw a new error mentioning trajectory splicing was not implemented yet. After seeing this error this suggests your code submitted new trajectory goals before the previous one had...