Skip to content
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

Make turtlebot_kinect_arm_calibration generic #1

Open
shaun-edwards opened this issue Jan 14, 2013 · 4 comments
Open

Make turtlebot_kinect_arm_calibration generic #1

shaun-edwards opened this issue Jan 14, 2013 · 4 comments

Comments

@shaun-edwards
Copy link

The turtlebot kinect to arm calibration package is useful for many different camera robot combinations. It would be nice if this package could be made more generic (i.e. remove turtlebot references and update wiki to describe application of this tool to any robot).

@mikeferguson
Copy link
Contributor

Just a note, the original code which this was based on can be found in the vanadium-ros-pkg qnd_calibration (https://code.google.com/p/vanadium-ros-pkg/source/browse/#svn%2Ftrunk%2Fsandbox%2Fqnd_calibration). I'm not sure how much stuff was added into the turtlebot code, but the original code might serve as some reference.

@corot
Copy link
Contributor

corot commented Sep 18, 2014

@mikeferguson, I have a question marginally related with this issue: I have updated the block manipulation demo for indigo/moveit, but I have some problems with the precision of blocks location, I imagine related to the camera calibration. My question is: the calibration process provides the tf from the robot to the camera_link, but uses the RGB images (referenced with rgb_optical_frame) as input. So I assumed that the calibration must do some internal frame conversions, but I cannot find such a thing within the code! So how the calibration "knows" where the camera_link must be if it only uses RGB images (with a different reference)? I wonder if my imprecision problems come from the fact that kinect internal frames on fuerte where different from the current ones provided on turtlebot_description kinect.urdf.xacro file.
Thanks!

PS: btw, the calibration and block manipulation work fine if I use my onboard Creative Senz3D!!!

@mikeferguson
Copy link
Contributor

@corot It is possible the link name is wrong -- this code is >3 years old, and was unused for at least 1-2 years until recently, further it pre-date openni_launch being split into rgbd_launch, so it is possible that frame name defaults have changed.

@corot
Copy link
Contributor

corot commented Sep 20, 2014

Right, you need to add an intermediate tf to deal with the new frames structure of the kinect. Added that, it works quite well, so I'll release with a warning in the wiki explaining what to do. Thanks!

corot added a commit that referenced this issue Mar 5, 2017
Adding support for PhantomX Pincher gripper
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants