-
Notifications
You must be signed in to change notification settings - Fork 311
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
aruco single not working on indigo #38
Comments
Not really...Actually the current version should support Indigo more and is
less ideal for Kinetic.
…On 13 December 2017 at 01:34, Vivek Annem ***@***.***> wrote:
This was working fine on kinetic. I needed it on indigo. Here are the
launch files and the errors i am getting.
Anyone know what the issue might be?
Thanks in advance.
[image: main_error]
<https://user-images.githubusercontent.com/14225433/33917351-a19d7c28-df62-11e7-9134-970a85c67bb3.png>
[image: single_and_usbcamstream]
<https://user-images.githubusercontent.com/14225433/33917352-a1b51e64-df62-11e7-9f7c-d392ed202a06.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#38>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADXH4cYQ74QPUUto9Ns8zT2QOzUqyOYiks5s_ymRgaJpZM4Q_4hJ>
.
|
Hi there, I am doing some experiments with aruco on PR2(indigo). After launching "single.launch", I got exactly the same error. Did you guys already have solution for this problem? ;) |
Hi guys, I might have figured out the reason for this problem. It seems that we clone the pkg from kinetic branch instead of indigo branch. So the codes will not work in indigo. Just try the following command to clone the correct branch to workspace and compile again. It works for me. ;) $ git clone -b indigo-devel https://github.com/pal-robotics/aruco_ros.git |
This was working fine on kinetic. I needed it on indigo. Here are the launch files and the errors i am getting.
Anyone know what the issue might be?
Thanks in advance.
The text was updated successfully, but these errors were encountered: