ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
Maybe there is a newer version of the bumblebee2
package, I don't know.
That dependency is now out of date. There does still exist a libdc1394v2 package in camera_drivers_experimental
, but it is no longer maintained. You may be able to download and compile that package from SVN, but I do not recommend it.
The simplest solution is probably to replace the <depend package="libdc1394v2"/>
in the package manifest with a <rosdep name="libdc1394-dev"/>
. To resolve that dependency either install ros-cturtle-camera-drivers
or else create a rosdep.yaml
in that package with these stanzas:
libraw1394-dev:
ubuntu: libraw1394-dev
fedora: libraw1394-devel
libdc1394-dev:
ubuntu: libdc1394-22-dev
arch: libdc1394
fedora: libdc1394-devel
macports: libdc1394
If you need more details, post a follow-on comment.
2 | add camera permissions pointer |
Maybe there is a newer version of the bumblebee2
package, I don't know.
That dependency is now out of date. There does still exist a libdc1394v2 package in camera_drivers_experimental
, but it is no longer maintained. You may be able to download and compile that package from SVN, but I do not recommend it.
The simplest solution is probably to replace the <depend package="libdc1394v2"/>
in the package manifest with a <rosdep name="libdc1394-dev"/>
. To resolve that dependency either install ros-cturtle-camera-drivers
or else create a rosdep.yaml
in that package with these stanzas:
libraw1394-dev:
ubuntu: libraw1394-dev
fedora: libraw1394-devel
libdc1394-dev:
ubuntu: libdc1394-22-dev
arch: libdc1394
fedora: libdc1394-devel
macports: libdc1394
Your problem with coriander
is most likely a common Ubuntu device permissions problem. See: bus permissions troubleshooting.
If you need more details, post a follow-on comment.
3 | respond to follow-on questions |
Maybe there is a newer version of the bumblebee2
package, I don't know.
That dependency is now out of date. There does still exist a libdc1394v2 package in camera_drivers_experimental
, but it is no longer maintained. You may be able to download and compile that package from SVN, but I do not recommend it.
The simplest solution is probably to replace the <depend package="libdc1394v2"/>
in the package manifest with a <rosdep name="libdc1394-dev"/>
. To resolve that dependency either install ros-cturtle-camera-drivers
or else create a rosdep.yaml
in that package with these stanzas:
libraw1394-dev:
ubuntu: libraw1394-dev
fedora: libraw1394-devel
libdc1394-dev:
ubuntu: libdc1394-22-dev
arch: libdc1394
fedora: libdc1394-devel
macports: libdc1394
Your problem with coriander
is most likely a common Ubuntu device permissions problem. See: bus permissions troubleshooting.
If you need more details, post a follow-on comment.
[Edit: responses to follow-on questions posted as an "answer"]
If you updated the rosdep.yaml
, you should no longer need the libdc1394v2
package.
The reference to <camera_info_manager/camera_info.h>
is out of date (predating cturtle). The released version should include <camera_info_manager/camera_info_manager.h>
, which is part of the camera_drivers
stack in cturtle (moved to image_common
in diamondback). I think you have that already.
The dependencies on camera_info_manager
are package dependencies, they use the <depends>
tag in the manifest.xml
, not <rosdep>
. The (obsolete) camera_info.h
does not belong in the include file of the bumblebee2
package.
You are correct that the inability of Ubuntu to find your camera is a separate problem.