-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connect OpenRAVE grasping module via YARP somehow #3
Comments
From @jgvictores on November 24, 2017 10:18 Sounds good. A couple of comments:
|
Some important information about thats points: |
From @jgvictores on November 29, 2017 21:4 Ran the example you mention, here's some relevant output:
|
From @jgvictores on November 29, 2017 21:41 As spoken this evening, the target is a Cartesian-space pose specified by a Regarding the output waypoints, I can make some pretty certain assumptions given my experience displayed in #29. 😂 Let's look at the first waypoint:
There are 18 numbers here. Waypoints in trajectories usually use the last field as a plain In conclusion, and based on this set of comments from #29, for each waypoint my assumption is:
Note 1: My count started at a c-style 0, so there is no element 18. Corollary: These values are in joint space. This is good, they can be sent directly to the robot in more or less sophisticated ways. A crude implementation would be solely via |
Thanks @jgvictores. This this can be a very important advance and very useful information. |
As @AlvaroMartinezR noted, the values are in radians. |
We are progressing in this fields. I've done a bit example with the WayPoint: 48
Joint number 0 value: -40.388129702571327
Joint number 1 value: 2.9747920777798509
Joint number 2 value: -26.875009609536988
Joint number 3 value: 0.037173734430287882
Joint number 4 value: -8.9038939102282786
Joint number 5 value: -66.351233738028654
Joint number 6 value: -86.438450209396066
Joint number 7 value: -57.777798437040772 The first two joints are from |
In fact also blocked by roboticslab-uc3m/kinematics-dynamics#134, where we're developing But no worries: It's WIP and on the way to be shipped ASAP! |
From @rsantos88 on November 23, 2017 15:48
After doing totally functional the simulation of the teo-grasping example in OpenRave, I am thinking to create a new YarpPluging, passing the python code to C++ and adapting it.
The purpose is to create a Yarp port which sends the information of the trajectory calculated by OpenRave to the robot.
@jgvictores do you think it's ok?
Copied from original issue: roboticslab-uc3m/openrave-yarp-plugins#40
The text was updated successfully, but these errors were encountered: