Timeline for How can I control a multi-axis arm by giving "target middle link position" instead of the end effector?
Current License: CC BY-SA 4.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Dec 27, 2023 at 2:02 | comment | added | user55147 | I solved the problem. Thank you for all the tips. | |
Dec 27, 2023 at 0:09 | answer | added | user55147 | timeline score: 1 | |
Dec 24, 2023 at 14:06 | comment | added | Mike973 | Please edit your post to show us the yaml you used to define the smaller move_group, and format it using the Code Sample button. Another possibility: How much time are you giving the IK solver to find a solution? (The default timeout value is often too short.) | |
Dec 24, 2023 at 0:30 | comment | added | user55147 | 1) Yes. 2) I'm using kdk_kinematics_plugin. 3) Not yet. | |
Dec 24, 2023 at 0:17 | comment | added | user55147 | I updated post about arm structure. I tried move_group consisting of 1 to 5 links, but IK solver failed too. | |
Dec 24, 2023 at 0:05 | history | edited | user55147 | CC BY-SA 4.0 |
added 145 characters in body
|
Dec 23, 2023 at 21:53 | comment | added | Mike973 | Please edit your post to tell us: 1) Is "camera_link" a direct child of a rotating arm joint? If not, I would try using the actual name of the arm link in setEndEffectorLink(), 2) Which IK solver are you using now?, 3) Have you looked at generating a custom Fast IK solver? | |
Dec 23, 2023 at 18:20 | comment | added | Mike973 | Have you tried creating a move_group with only the joints you care about, then asking IK to solve for the cartesian goal? (this approach is a guess, I've not tried it myself.) | |
Dec 23, 2023 at 4:13 | history | edited | user55147 | CC BY-SA 4.0 |
added 251 characters in body
|
Dec 21, 2023 at 7:35 | history | edited | user55147 | CC BY-SA 4.0 |
edited body; edited title
|
S Dec 21, 2023 at 7:28 | review | First questions | |||
Dec 21, 2023 at 14:00 | |||||
S Dec 21, 2023 at 7:28 | history | asked | user55147 | CC BY-SA 4.0 |