David Dudas

@ZhengQiushi, MoveIt's default IK is for 6DoF arms and it cannot resolve any pose where the end effector should be rotated around yaw or roll axis. Until ROBOTIS doesn't release...

This issue is still valid and has to be re-opened.

Thank you @ROBOTIS-Will, I can understand that MoveIt doesn't want to develop IK solvers for every custom arm, but MoveIt makes it possible to USE a custom IK solver, so...

You might misunderstand me, I'm aware the custom GUI tools, but could you please check out your own ROBOTIS video on this link: https://www.facebook.com/watch/?v=2198266990449746 From 0:28 you can see OpenMANIPULATOR-X...

@PaulDebus99 I was wondering on a workaround without any custom solver, but I couldn't find any spare time to spend on it yet. I'm planning to modify the urdf to...

Not yet, I didn't built MoveIt from source in the past few years. I checked out the debug log though: ```console ... [DEBUG] [1621498426.986322400, 134.889000000]: Input: [ -1.11591 2.36105 2.29294...

Sure, this is an example desired pose:  I cannot reach this if I set a pose target, because I got the error above. ```python # x, y, z position...

FYI, @felixvd I just built MoveIt (master branch) from source and I experience the exact same issue.

Based on the modification that you had to make on the launchfile names, could you please let me know which branch do you use from `unversal_robot` repo? I'm using a...

On Melodic I'm using binary install of MoveIt (ros-melodic-moveit/bionic 1.0.7-1bionic.20210421.070859 amd64), I'll build MoveIt master from source later, by the way is it possible to use the master on Ubuntu...