Hi,
I was trying to calibrate my usb camera using the chessboard based camcalibrator.
The camcalibrator node is not showing the calibration results in the terminal after I press the calibrate button.
Also when I press on COMMIT, it closes displaying the calibration result in the terminal. And when I echo the /camera_info it shows no update in calibration parameters D, K, etc.
The rxgraph shows connection error with camcalibration node after I press the calibrate button.
I am using camera_info_manager in the camera driver node to advertise the set_camera_info service.
But I am using the camcalibrator node from a different node, I think there is a problem when it tries to parse the calibrated parameters back to the camera.
↧
problem with camcalibrator
↧
camera calibration and ROI
Hi there,
i've just a litte question regarding calibration of a camera and ROI.
If i have calibration values for a camera and change the roi?
Does this affect the calibration values in anyway and do i have to do the calibration again?
I thought that i don't have to recalibrate the camera if i just change the ROI since it can be calculated based on the calibration values of the full resolution image.
The reason why i'm asking is the camera_info_manager.
I've implemented it and it works quite good.
However if change the ROI it does not affect the camera_info message in terms of ROI.
I can either add the ROI to my camera_name and force the user to recalibrate the camera every time a different ROI is set or i modify my camera_info message from manager regarding ROI values.
what's the best solution?
cheers Mimax
↧
↧
different resolutions and camera_info_manager/openni (e.g. kinect camera)
After the calibration and using the camera_calibration_parsers, I get a rgb_A00363A22671047A.yaml file. This file can be placed in /home/username/.ros/camera_info/.
But I can chance the resolution anytime(e.g. 640x480 -> 1280x1024).
How is it possible to store different calibrations, one for every supported resolution?
↧
Error in compiling uvc_cam
Hi !
I am using ROS Fuerte on my system running Ubuntu 12.04 . i am trying to build [uvc_cam](http://www.ros.org/wiki/uvc_camera) but i am getting errros, here are the steps i performed:
rosws set uvc_cam https://github.com/ericperko/uvc_cam.git --git
rosws update uvc_cam
rosmake uvc_cam
And after running make command i got some errors, here's the output of the terminal.
usama@ubuntu:~/fuerte_workspace$ rosmake uvc_cam
[ rosmake ] rosmake starting...
[ rosmake ] Packages requested are: ['uvc_cam']
[ rosmake ] Logging to directory /home/usama/.ros/rosmake/rosmake_output-20120717-201232
[ rosmake ] Expanded args ['uvc_cam'] to:
['uvc_cam']
[rosmake-0] Starting >>> roslang [ make ]
[rosmake-1] Starting >>> geometry_msgs [ make ]
[rosmake-2] Starting >>> rosbuild [ make ]
[rosmake-3] Starting >>> roslib [ make ]
[rosmake-0] Finished <<< roslang No Makefile in package roslang
[rosmake-1] Finished <<< geometry_msgs No Makefile in package geometry_msgs
[rosmake-0] Starting >>> roscpp [ make ]
[rosmake-1] Starting >>> sensor_msgs [ make ]
[rosmake-2] Finished <<< rosbuild No Makefile in package rosbuild
[rosmake-3] Finished <<< roslib No Makefile in package roslib
[rosmake-2] Starting >>> rosconsole [ make ]
[rosmake-3] Starting >>> message_filters [ make ]
[rosmake-0] Finished <<< roscpp No Makefile in package roscpp
[rosmake-0] Starting >>> opencv2 [ make ]
[rosmake-1] Finished <<< sensor_msgs No Makefile in package sensor_msgs
[rosmake-2] Finished <<< rosconsole No Makefile in package rosconsole
[rosmake-3] Finished <<< message_filters No Makefile in package message_filters
[rosmake-1] Starting >>> bullet [ make ]
[rosmake-2] Starting >>> pluginlib [ make ]
[rosmake-3] Starting >>> angles [ make ]
[rosmake-0] Finished <<< opencv2 ROS_NOBUILD in package opencv2
[rosmake-0] Starting >>> cv_bridge [ make ]
[rosmake-3] Finished <<< angles ROS_NOBUILD in package angles
[rosmake-2] Finished <<< pluginlib ROS_NOBUILD in package pluginlib
[rosmake-3] Starting >>> rospy [ make ]
[rosmake-2] Starting >>> image_transport [ make ]
[rosmake-1] Finished <<< bullet ROS_NOBUILD in package bullet
[rosmake-1] Starting >>> rostest [ make ]
[rosmake-2] Finished <<< image_transport ROS_NOBUILD in package image_transport
[rosmake-3] Finished <<< rospy No Makefile in package rospy
[rosmake-0] Finished <<< cv_bridge ROS_NOBUILD in package cv_bridge
[rosmake-0] Starting >>> roswtf [ make ]
[rosmake-3] Starting >>> common_rosdeps [ make ]
[rosmake-1] Finished <<< rostest No Makefile in package rostest
[rosmake-2] Starting >>> rosservice [ make ]
[rosmake-1] Starting >>> diagnostic_msgs [ make ]
[rosmake-0] Finished <<< roswtf No Makefile in package roswtf
[rosmake-0] Starting >>> tf [ make ]
[rosmake-2] Finished <<< rosservice No Makefile in package rosservice
[rosmake-3] Finished <<< common_rosdeps ROS_NOBUILD in package common_rosdeps
[rosmake-1] Finished <<< diagnostic_msgs No Makefile in package diagnostic_msgs
[rosmake-1] Starting >>> camera_calibration_parsers [ make ]
[rosmake-3] Starting >>> dynamic_reconfigure [ make ]
[rosmake-2] Starting >>> std_msgs [ make ]
[rosmake-0] Finished <<< tf ROS_NOBUILD in package tf
[rosmake-3] Finished <<< dynamic_reconfigure ROS_NOBUILD in package dynamic_reconfigure
[rosmake-2] Finished <<< std_msgs No Makefile in package std_msgs
[rosmake-1] Finished <<< camera_calibration_parsers ROS_NOBUILD in package camera_calibration_parsers
[rosmake-1] Starting >>> camera_info_manager [ make ]
[rosmake-3] Starting >>> diagnostic_updater [ make ]
[rosmake-1] Finished <<< camera_info_manager ROS_NOBUILD in package camera_info_manager
[rosmake-3] Finished <<< diagnostic_updater ROS_NOBUILD in package diagnostic_updater
[rosmake-3] Starting >>> self_test [ make ]
[rosmake-3] Finished <<< self_test ROS_NOBUILD in package self_test
[rosmake-3] Starting >>> driver_base [ make ]
[rosmake-3] Finished <<< driver_base ROS_NOBUILD in package driver_base
[rosmake-3] Starting >>> uvc_cam [ make ]
[ rosmake ] Last 40 linesc_cam: 21.7 sec ] [ 1 Active 28/29 Complete ]
{-------------------------------------------------------------------------------
make[3]: Leaving directory `/home/usama/fuerte_workspace/uvc_cam/build'
make[3]: Entering directory `/home/usama/fuerte_workspace/uvc_cam/build'
[ 66%] Building CXX object CMakeFiles/uvc_cam.dir/src/uvc_cam/uvc_cam.o
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam/uvc_cam.cpp: In member function ‘int uvc_cam::Cam::grab(unsigned char**, uint32_t&)’:
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam/uvc_cam.cpp:459:20: warning: unused variable ‘pyuv_last’ [-Wunused-variable]
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam/uvc_cam.cpp: In member function ‘void uvc_cam::Cam::display_formats_supported()’:
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam/uvc_cam.cpp:529:39: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam/uvc_cam.cpp:536:60: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam/uvc_cam.cpp:543:76: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
Linking CXX shared library ../lib/libuvc_cam.so
make[3]: Leaving directory `/home/usama/fuerte_workspace/uvc_cam/build'
[ 66%] Built target uvc_cam
make[3]: Entering directory `/home/usama/fuerte_workspace/uvc_cam/build'
Scanning dependencies of target uvc_cam_node
make[3]: Leaving directory `/home/usama/fuerte_workspace/uvc_cam/build'
make[3]: Entering directory `/home/usama/fuerte_workspace/uvc_cam/build'
[100%] Building CXX object CMakeFiles/uvc_cam_node.dir/src/uvc_cam_node.o
In file included from /home/usama/fuerte_workspace/uvc_cam /src/uvc_cam_node.cpp:50:0:
/opt/ros/fuerte/stacks/vision_opencv/cv_bridge/include/cv_bridge/CvBridge.h: In static member function ‘static sensor_msgs::Image_>::Ptr sensor_msgs::CvBridge::cvToImgMsg(const IplImage*, std::string)’:
/opt/ros/fuerte/stacks/vision_opencv/cv_bridge/include/cv_bridge /CvBridge.h:408:55: warning: ‘static bool sensor_msgs::CvBridge::fromIpltoRosImage(const IplImage*, sensor_msgs::Image&, std::string)’ is deprecated (declared at /opt/ros/fuerte/stacks/vision_opencv/cv_bridge/include/cv_bridge/CvBridge.h:307) [-Wdeprecated-declarations]
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam_node.cpp: At global scope:
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam_node.cpp:83:2: error: ‘CameraInfoManager’ does not name a type
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam_node.cpp: In constructor ‘UVCCamNode::UVCCamNode()’:
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam_node.cpp:96:3: error: class ‘UVCCamNode’ does not have any field named ‘cinfo_’
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam_node.cpp:97:17: warning: ‘sensor_msgs::CvBridge::CvBridge()’ is deprecated (declared at /opt/ros/fuerte/stacks /vision_opencv/cv_bridge/include/cv_bridge/CvBridge.h:64) [-Wdeprecated-declarations]
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam_node.cpp: In member function ‘bool UVCCamNode::openCamera(UVCCamNode::Config&)’:
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam_node.cpp:157:10: error: ‘cinfo_’ was not declared in this scope
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam_node.cpp: In member function ‘bool UVCCamNode::read()’:
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam_node.cpp:207:51: warning: ‘static sensor_msgs::Image_>::Ptr sensor_msgs::CvBridge::cvToImgMsg(const IplImage*, std::string)’ is deprecated (declared at /opt/ros/fuerte/stacks/vision_opencv/cv_bridge/include/cv_bridge/CvBridge.h:405) [-Wdeprecated-declarations]
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam_node.cpp: In member function ‘void UVCCamNode::publish()’:
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam_node.cpp:232:15: error: ‘cinfo_’ was not declared in this scope
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam_node.cpp: In member function ‘void UVCCamNode::reconfig(UVCCamNode::Config&, uint32_t)’:
/home/usama/fuerte_workspace/uvc_cam/src/uvc_cam_node.cpp:376:8: error: ‘cinfo_’ was not declared in this scope
make[3]: *** [CMakeFiles/uvc_cam_node.dir/src/uvc_cam_node.o] Error 1
make[3]: Leaving directory `/home/usama/fuerte_workspace/uvc_cam/build'
make[2]: *** [CMakeFiles/uvc_cam_node.dir/all] Error 2
make[2]: Leaving directory `/home/usama/fuerte_workspace/uvc_cam/build'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/usama/fuerte_workspace/uvc_cam/build'
-------------------------------------------------------------------------------}
[ rosmake ] Output from build of package uvc_cam written to:
[ rosmake ] /home/usama/.ros/rosmake/rosmake_output-20120717-201232/uvc_cam/build_output.log
[rosmake-3] Finished <<< uvc_cam [FAIL] [ 21.81 seconds ]
[ rosmake ] Halting due to failure in package uvc_cam.
[ rosmake ] Waiting for other threads to complete.
[ rosmake ] Results:
[ rosmake ] Built 29 packages with 1 failures.
[ rosmake ] Summary output to directory
[ rosmake ] /home/usama/.ros/rosmake/rosmake_output-20120717-201232
Any idea, how can i resolve this error ?
regards
usama
↧
Bumblebee xb3 and stereo_image_proc
Hello everybody!
I have a question about stereo_image_proc and camera info manager.
I am using the Bumblebee xb3 camera, wich have 3 lenses. I need to get two pairs of images from the camera. One pair with the right and the center lenses (namespace=xb3_short), and another with right and left lenses (namespace=xb3_wide).
In order to run stereo image proc i need this topics:
xb3_short/left/image_raw
xb3_short/left/camera_info
xb3_short/right/image_raw
xb3_short/right/camera_info
xb3_wide/left/image_raw
xb3_wide/left/camera_info
xb3_wide/right/image_raw
xb3_wide/right/camera_info
But actually xb3_short/right/image_raw and xb3_wide/right/image_raw are the same images. This will result a extra space when i need to record bag files with the camera. Is there a way to record only 3 images instead of 4?
↧
↧
Error in rosmake bumblebee2 under fuerte
I met a problem to install bumblebee2 package in ROS.
In the fist try, the error is:
fatal error: camera_info_manager/camera_info.h: No such file or directory
Then, I follow the suggestion by Pulkit to replace camera_info.h to camera_info_manager.h.
The old problem is solved, but there is a new issue. The definition of "CameraInfoManager *cinfo_;" is wrong. Pulkit suggested that "Replace the places where the variable cinfo_ is declared/initialized to camera_info_manager::cinfo_h". I am not quite sure what this mean as cinfo_h is not the member of camera_info_manager. Does anyone know how to solve this issue?
Thank you and Happy new year to all the ROSers.
↧
Unable to load calibration file in uvc_camera over network
I tried to launch a node over the network with the following code:
↧
cannot svn camera_info_manager package from source
Does anyone can svn camera_info_manager package from source? I need electric version for Gumstix Overo. I tried this link https://code.ros.org/svn/ros-pkg/stacks/image_common/tags/image_common-1.6.1 , but it seems not exist.
Anyone can help me? Thanks in advance!
↧
Read images from disk, publish as camera
I have a dataset of images on disk, along with a set of camera parameters (though they are not in ROS camera_info file format). I am trying to make a node that reads and publish de images in round robin (when it finishes reading the images in the folder, it starts again). My main objective is to make it in such a way that I can "fool" other nodes, making them think that the node is a camera.
I have being trying to do it in the following way:
- Publish the images in a topic `/camera/image_rect_color`
- Publish `sensor_msgs/CameraInfo` in the topic `/camera/camera_info`
- I have tried to visualize the images in rviz using a camera display, but rviz complains because it says no `/camera_link` frame is published
At this point I believe there has to be an easier way to do this... Does anybody has suggestions about how to achieve this?
Thanks in advance!
↧
↧
Error with the bumblebee2 package
Hi guys !
I am getting this error when i try to compile the bumblebee2 package of Columbia University :
*********************************************************************************
[ rosmake ] All 32 linesumblebee2: 4.2 sec ] [ 1 Active 45/46 Complete ]
{-------------------------------------------------------------------------------
mkdir -p bin
cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=/opt/ros/groovy/share/ros/core/rosbuild/rostoolchain.cmake ..
[rosbuild] Building package bumblebee2
[rosbuild] Cached build flags older than manifests; calling rospack to get flags
Failed to invoke /opt/ros/groovy/bin/rospack cflags-only-I;--deps-only bumblebee2
Package camera_info_manager was not found in the pkg-config search path.
Perhaps you should add the directory containing `camera_info_manager.pc'
to the PKG_CONFIG_PATH environment variable
No package 'camera_info_manager' found
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.7/rosdep2/rospack.py", line 45, in call_pkg_config
value = subprocess.check_output(['pkg-config', option, pkg_name])
File "/usr/lib/python2.7/subprocess.py", line 544, in check_output
raise CalledProcessError(retcode, cmd, output=output)
subprocess.CalledProcessError: Command '['pkg-config', '--cflags-only-I', 'camera_info_manager']' returned non-zero exit status 1
[rospack] Error: could not call python function 'rosdep2.rospack.call_pkg_config'
CMake Error at /opt/ros/groovy/share/ros/core/rosbuild/public.cmake:129 (message):
Failed to invoke rospack to get compile flags for package 'bumblebee2'.
Look above for errors from rospack itself. Aborting. Please fix the
broken dependency!
Call Stack (most recent call first):
/opt/ros/groovy/share/ros/core/rosbuild/public.cmake:227 (rosbuild_invoke_rospack)
CMakeLists.txt:12 (rosbuild_init)
-- Configuring incomplete, errors occurred!
-------------------------------------------------------------------------------}
[ rosmake ] Output from build of package bumblebee2 written to:
[ rosmake ] /home/anis/.ros/rosmake/rosmake_output-20130329-160036/bumblebee2/build_output.log
[rosmake-1] Finished <<< bumblebee2 [FAIL] [ 4.22 seconds ]
[ rosmake ] Halting due to failure in package bumblebee2.
[ rosmake ] Waiting for other threads to complete.
[ rosmake ] Results:
[ rosmake ] Built 46 packages with 1 failures.
[ rosmake ] Summary output to directory
[ rosmake ] /home/anis/.ros/rosmake/rosmake_output-20130329-160036
*********************************************************************************
I already installed the camera_info_manager package and it compiles without any failure.
This is what i get with the roscd pkg :
*********************************************************************************
anis@anis-Precision-M4500:~/rgbdslam_workspace$ roscd camera_info_manager
anis@anis-Precision-M4500:~/rgbdslam_workspace/sandbox/image_common-groovy-devel/camera_info_manager$
*********************************************************************************
I looked for the "camera_info_manager.pc" file in all my system and i don't find it.
↧
Undefined reference when compiling camera_info_manager
I'm compiling camera_info_manager on Ubuntu 13.10 (armhf) and receiving undefined reference to camera_calibration_parsers::readCalibration.
See details below:
$ catkin_make_isolated --pkg camera_info_manager --install
....
==> Processing catkin package: 'camera_info_manager'
==> Building with env: '/home/ilagi/ros_catkin_ws/install_isolated/env.sh'
Makefile exists, skipping explicit cmake invocation...
==> make cmake_check_build_system in '/home/ilagi/ros_catkin_ws/build_isolated/camera_info_manager'
==> make -j4 -l4 in '/home/ilagi/ros_catkin_ws/build_isolated/camera_info_manager'
[ 33%] Built target gtest
[ 66%] Built target camera_info_manager
Linking CXX executable /home/ilagi/ros_catkin_ws/devel_isolated/camera_info_manager/lib/camera_info_manager/unit_test
/home/ilagi/ros_catkin_ws/devel_isolated/camera_info_manager/lib/libcamera_info_manager.so: undefined reference to `camera_calibration_parsers::readCalibration(std::string const&, std::string&, sensor_msgs::CameraInfo_>&)'
/home/ilagi/ros_catkin_ws/devel_isolated/camera_info_manager/lib/libcamera_info_manager.so: undefined reference to `camera_calibration_parsers::writeCalibration(std::string const&, std::string const&, sensor_msgs::CameraInfo_> const&)'
collect2: error: ld returned 1 exit status
make[2]: *** [/home/ilagi/ros_catkin_ws/devel_isolated/camera_info_manager/lib/camera_info_manager/unit_test] Error 1
make[1]: *** [CMakeFiles/unit_test.dir/all] Error 2
make: *** [all] Error 2<== Failed to process package 'camera_info_manager':
Command '/home/ilagi/ros_catkin_ws/install_isolated/env.sh make -j4 -l4' returned non-zero exit status 2
What is funny that I remember that I had the same issue when I was compiling for Raspberry Pi and resolved it somehow, but it seems I can't remember how.
Any idea is appreciated.
Edit: camera_calibration_parses package is installed, that was the first thing I checked
Edit2: just realized that last time I raised a ticket in github against camera_info_manager, but then the issue got resolved on its own, so I just reopen the ticket. See make verbose output on the link: https://github.com/ros-perception/image_common/issues/23
↧
How start the nao_camera node?
$ I am able to use the Python Nodes with the robot NAO using:
$ export PYTHONPATH="$PYTHONPATH:$HOME/path/to/pynaoqi/"
and
$ roslaunch nao_driver nao_driver.launch force_python:=true nao_ip:=192.168.1.206
if I want to check which nodes are running:
$ rosnode list
and I obtained the next list:
/nao_behaviors
/nao_controller
/nao_leds
/nao_sensors
/nao_speech
/nao_tactile
/nao_walker
How can I start or launch the nao_camera, because I going to need the image since i work in Computer Vision? I tried with:
$ roslaunch nao_driver nao_camera.launch nao_ip:=192.168.1.206
but I got the next error: (copy-paste of the terminal)
pablo@pabloNao:~$ roslaunch nao_driver nao_camera.launch force_python:=true nao_ip:=192.168.1.206
... logging to /home/pablo/.ros/log/1340b312-b510-11e3-9391-24b6fd11a455/roslaunch-pabloNao-6138.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://pabloNao:33756/
SUMMARY
========
PARAMETERS
* /nao_camera/calibration_file_bottom
* /nao_camera/calibration_file_top
* /nao_camera/color_space
* /nao_camera/fps
* /nao_camera/resolution
* /rosdistro
* /rosversion
NODES
/
nao_camera (nao_driver/nao_camera.py)
ROS_MASTER_URI=XXX
core service [/rosout] found
process[nao_camera-1]: started with pid [6156]
Traceback (most recent call last):
File "/opt/ros/hydro/lib/nao_driver/nao_camera.py", line 38, in
import camera_info_manager
ImportError: No module named camera_info_manager
================================================================================REQUIRED process [nao_camera-1] has died!
process has died [pid 6156, exit code 1, cmd /opt/ros/hydro/lib/nao_driver/nao_camera.py --pip=192.168.1.206 --pport=9559 __name:=nao_camera __log:=/home/pablo/.ros/log/1340b312-b510-11e3-9391-24b6fd11a455/nao_camera-1.log].
log file: /home/pablo/.ros/log/1340b312-b510-11e3-9391-24b6fd11a455/nao_camera-1*.log
Initiating shutdown!
================================================================================
[nao_camera-1] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done
pablo@pabloNao:~$
I will really appreciate any advise, thank you!
↧
Linking camera_info_manager fails on OSX
Hello,
following the installation instructions for hydro on OSX I encounter this linking error.
How can I fix this?
==============
cd /Users/tatsch/ros_catkin_ws/build_isolated/camera_info_manager && /Users/tatsch/ros_catkin_ws/install_isolated/env.sh make
Linking CXX shared library /Users/tatsch/ros_catkin_ws/devel_isolated/camera_info_manager/lib/libcamera_info_manager.dylib
Undefined symbols for architecture x86_64:
"ros::console::print(ros::console::FilterBase*, log4cxx::Logger*, ros::console::levels::Level, char const*, int, char const*, char const*, ...)", referenced from:
camera_info_manager::CameraInfoManager::setCameraInfoService(sensor_msgs::SetCameraInfoRequest_>&, sensor_msgs::SetCameraInfoResponse_>&) in camera_info_manager.cpp.o
camera_info_manager::CameraInfoManager::loadCalibration(std::__1::basic_string, std::__1::allocator> const&, std::__1::basic_string, std::__1::allocator> const&) in camera_info_manager.cpp.o
"ros::console::print(ros::console::FilterBase*, log4cxx::Logger*, ros::console::levels::Level, std::__1::basic_stringstream, std::__1::allocator> const&, char const*, int, char const*)", referenced from:
camera_info_manager::CameraInfoManager::loadCalibration(std::__1::basic_string, std::__1::allocator> const&, std::__1::basic_string, std::__1::allocator> const&) in camera_info_manager.cpp.o
camera_info_manager::CameraInfoManager::getPackageFileName(std::__1::basic_string, std::__1::allocator> const&) in camera_info_manager.cpp.o
camera_info_manager::CameraInfoManager::resolveURL(std::__1::basic_string, std::__1::allocator> const&, std::__1::basic_string, std::__1::allocator> const&) in camera_info_manager.cpp.o
camera_info_manager::CameraInfoManager::loadCalibrationFile(std::__1::basic_string, std::__1::allocator> const&, std::__1::basic_string, std::__1::allocator> const&) in camera_info_manager.cpp.o
camera_info_manager::CameraInfoManager::saveCalibration(sensor_msgs::CameraInfo_> const&, std::__1::basic_string, std::__1::allocator> const&, std::__1::basic_string, std::__1::allocator> const&) in camera_info_manager.cpp.o
camera_info_manager::CameraInfoManager::saveCalibrationFile(sensor_msgs::CameraInfo_> const&, std::__1::basic_string, std::__1::allocator> const&, std::__1::basic_string, std::__1::allocator> const&) in camera_info_manager.cpp.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [/Users/tatsch/ros_catkin_ws/devel_isolated/camera_info_manager/lib/libcamera_info_manager.dylib] Error 1
make[1]: *** [CMakeFiles/camera_info_manager.dir/all] Error 2
make: *** [all] Error 2
↧
↧
Explicit address for camera calibration file
I have a few different platforms that are all using the same package. Each platform has a different stereo camera calibration file.yaml
Each platform has its own launch file, which gets called (roughly) this way:
↧
Multiple CameraInfoManagers in same node?
It seems like this ought to be possible (https://github.com/ros-industrial/human_tracker/blob/master/packages/aravis_camera_driver/src/nodes/basler_multi_node.cpp shows an example though there is a lot going on)- but when I try to do it the set_camera_info topics are colliding:
Tried to advertise a service that is already advertised in this node [/set_camera_info]
Should the name parameter passed into CameraInfoManager(nh, "foo") be putting the /set_camera_info into /foo/set_camera_info ?
This is Indigo with Ubuntu 14.04.
↧
camera_info override
Hi! I've been using an android app to pipe the camera image into ROS.
This works moderately well, even though there is some lag to get the image.
The problem is that the published /camera/camera_info is all empty. (see below)
Is there a way I can override the camera_info topic with the calibration data I've gathered, and bypass what the AndroidCameraViewer driver reports ?
Thank you
Output of :
$ rostopic echo /camera/camera_info
header:
seq: 7485
stamp:
secs: 1412290798
nsecs: 453000000
frame_id: camera
height: 960
width: 1280
distortion_model: ''
D: []
K: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
R: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
P: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
binning_x: 0
binning_y: 0
roi:
x_offset: 0
y_offset: 0
height: 0
width: 0
do_rectify: False
↧
ROS hydro build fails on camera_info_manager
I'm trying to build ROS since [iai_kinect2](https://github.com/code-iai/iai_kinect2) needs it. I'm following instructions given [here](http://wiki.ros.org/hydro/Installation/Trusty) and at `catkin_build` command it's failing with the following error:
[camera_info_manager] ==> '/home/anshulvj/ros_hydro/build/camera_info_manager/build_env.sh /usr/bin/make --jobserver-fds=3,5 -j' in '/home/anshulvj/ros_hydro/build/camera_info_manager'
[ 50%] Built target camera_info_manager
Linking CXX executable /home/anshulvj/ros_hydro/devel/lib/camera_info_manager/unit_test
/usr/local/lib/libgtest.a(gtest-all.cc.o): In function `llvm::raw_ostream::raw_ostream(bool)':
gtest-all.cc:(.text._ZN4llvm11raw_ostreamC2Eb[_ZN4llvm11raw_ostreamC5Eb]+0x14): undefined reference to `vtable for llvm::raw_ostream'
/usr/local/lib/libgtest.a(gtest-all.cc.o): In function `llvm::raw_os_ostream::raw_os_ostream(std::ostream&)':
gtest-all.cc:(.text._ZN4llvm14raw_os_ostreamC2ERSo[_ZN4llvm14raw_os_ostreamC5ERSo]+0x28): undefined reference to `vtable for llvm::raw_os_ostream'
/usr/local/lib/libgtest.a(gtest-all.cc.o): In function `llvm::convertible_fwd_ostream::~convertible_fwd_ostream()':
gtest-all.cc:(.text._ZN4llvm23convertible_fwd_ostreamD1Ev[_ZN4llvm23convertible_fwd_ostreamD1Ev]+0x44): undefined reference to `llvm::raw_os_ostream::~raw_os_ostream()'
collect2: error: ld returned 1 exit status
make[2]: *** [/home/anshulvj/ros_hydro/devel/lib/camera_info_manager/unit_test] Error 1
make[1]: *** [CMakeFiles/unit_test.dir/all] Error 2
make: *** [all] Error 2
[camera_info_manager] <== '/home/anshulvj/ros_hydro/build/camera_info_manager/build_env.sh /usr/bin/make --jobserver-fds=3,5 -j' failed with return code '2'
Starting ==> actionlib
Failed <== camera_info_manager [ 1.4 seconds ]
Finished <== image_view [ 1.4 seconds ]
Starting ==> nodelet_topic_tools
Finished <== polled_camera [ 2.0 seconds ]
Finished <== actionlib [ 3.1 seconds ]
Finished <== nodelet_topic_tools [ 2.9 seconds ]
[build] There were '1' errors:
Failed to build package 'camera_info_manager' because the following command:
# Command to reproduce:
cd /home/anshulvj/ros_hydro/build/camera_info_manager && /home/anshulvj/ros_hydro/build/camera_info_manager/build_env.sh /usr/bin/make --jobserver-fds=3,5 -j; cd -
# Path to log:
cat /home/anshulvj/ros_hydro/build/build_logs/camera_info_manager.log
Exited with return code: 2
[build] Runtime: 2 minutes and 21.2 seconds
I tried googling it but noone's apparently gotten this error. I also tried to see if it can be built without the erroneous package but all I found was how to install one single package, not without. Am I missing something obvious. This is the first time I'm installing ROS. Any suggestions are appreciated. Thanks
↧
↧
do rviz need urdf file for viewing camera feed?
I am trying to create a stereo camera, I know that the feed can be viewed in `rviz` using `image` display type.But other than that i want to know how can we succesfully view camera feed using `camera` display type
- i was successful in calibrating and publishing the `image_info` topic
- but when try to view the camera using `camera` type i get warning status saying no image was received but i successfully gets the image via the `image` display type 
- so my suspicion is if I am missing something on the Fixed_frame or target_frame or something like that
↧
image_view stereo_view do not show image or disparity
I have been trying to view my stereo disparity image using `image_view stereo_view` but whenever i run it i get two blank left and right windows with the following error in terminal> init done
opengl support available
(stereo_view:14758): GLib-GObject-WARNING **: invalid uninstantiatable type '(null)' in cast to 'GtkWidget'
(stereo_view:14758): GLib-GObject-WARNING **: instance of invalid non-instantiatable type '(null)'
(stereo_view:14758): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(stereo_view:14758): GLib-GObject-WARNING **: invalid uninstantiatable type '(null)' in cast to 'GtkWidget'
(stereo_view:14758): GLib-GObject-WARNING **: instance of invalid non-instantiatable type '(null)'
(stereo_view:14758): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(stereo_view:14758): GLib-GObject-WARNING **: invalid uninstantiatable type '(null)' in cast to 'GtkWidget'
(stereo_view:14758): GLib-GObject-WARNING **: instance of invalid non-instantiatable type '(null)'
(stereo_view:14758): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
[ INFO] [1453739975.777426383]: Subscribing to:
* /camera/left/image_rect_color
* /camera/right/image_rect_color
* /camera/disparity
- I was able to get the images in rviz using `camera` display
- I am using ubuntu 14.04 with indigo distro
- how can i fix this problem?
**anybody please help me**
↧
pointcloud2 problem
I know that there are lots of question on his topic but after going through most of them i was not able to find solution for my problem
- I am using `stereo_image_proc` for getting point cloud from stereo cam driver as i have provided below, i successfully gets both left and right camera output but i cant see pointcloud2 in rviz
- I tried echoing the `camera/point2` topic but the result seems weird[**or is it ok ,I am new to these stuffs?**]
- is my output ok?if yes then what might be the reason i dont get pointcloud in rviz(I have tried rotating the window)
**Edit:** sorry after i again tried rotating i got the cloud but it seems weird 
↧
Use C++ camera_info_manager yamls with camera_info_manager_py, and vice versa?
I'd like to run [camera_info_manager_py](http://wiki.ros.org/camera_info_manager_py) saveCalibrationFile in a python file and then load the same yaml in in C++, but it appears the yaml dump is saving like this:
!!python/unicode 'camera_matrix':
!!python/unicode 'data': [1059.8847344712244, 0.0, 636.6932553292625, 0.0, 1058.8956875577258,
470.30001700247, 0.0, 0.0, 1.0]
!!python/unicode 'camera_name': camera
!!python/unicode 'distortion_coefficients':
...
as opposed to the cleaner C++ output:
image_width: 640
image_height: 480
camera_name: image_publisher
camera_matrix:
rows: 3
cols: 3
data: [500.0, 0, 320, 0, 500.0, 240, 0, 0, 1]
distortion_model: plumb_bob
distortion_coefficients:
...
Loading the C++ yaml in python doesn't generate an error, but the camera info is blank, while loading the python yaml in C++ generates
```
[ERROR] [/cam/image_pub1] [/tmp/binarydeb/ros-jade-camera-calibration-parsers-1.11.10/src/parse_yml.cpp]:[221] [Exception parsing YAML camera calibration:
yaml-cpp: error at line 0, column 0: bad conversion]
```
Is this a bug or am I doing something wrong on the python side?
↧
↧
Zoom camera calibration in ROS?
How would you tackle the task of zoom camera calibration using standard ROS tools? Both the calibration process itself, and `camera_info` publication afterwards? I haven't found anything in `camera_calibration` or `camera_info_manager`.
If I understand it correctly, you have to estimate the dependency of the `K` matrix on the current zoom level using a function. The dependency of `K` on focal length is IMO linear (as long as we ignore skew and the other odd terms).
There are several quantities that can be reported by the camera:
- "zoom ratio": then I'd just multiply the `f_x` and `f_y` terms of the `K` matrix with this ratio (assuming the camera was calibrated with ratio 1)
- focal length: I'd simply put the focal length in the matrix
- field of view: I can estimate sensor width from the calibration, and then use it to get the focal length (`2*atan(0.5*width/f)`).
This of course ignores radial (and other) distortion, which may also by influenced by the focal length (at least so do I think).
Then I'd publish the updated camera matrix to the appropriate `camera_info` topic.
What do you think about this approach? Has there already been something doing a similar task?
↧
error when install usb_cam
Hi,
I am installing usb_cam and get this error:
CMake Error at /opt/ros/indigo/share/catkin/cmake/catkinConfig.cmake:75 (find_package):
Could not find a package configuration file provided by
"camera_info_manager" with any of the following names:
camera_info_managerConfig.cmake
camera_info_manager-config.cmake
Add the installation prefix of "camera_info_manager" to CMAKE_PREFIX_PATH
or set "camera_info_manager_DIR" to a directory containing one of the above
files. If "camera_info_manager" provides a separate development package or
SDK, be sure it has been installed.
Call Stack (most recent call first):
usb_cam/CMakeLists.txt:7 (find_package)
Please let me know how to fix this.
↧
Could not find configuration package "camera_info_manager" upon build
I am a beginner and I am trying to install autoware from this link: https://github.com/CPFL/Autoware I followed the following commands on my virtual machine with ros indigo:
cd $HOME
$ git clone https://github.com/CPFL/Autoware.git
$ cd ~/Autoware/ros/src
$ catkin_init_workspace
$ cd ../..
$ ./catkin_make_release
This last command produces the following error:
CMake Error at /opt/ros/indigo/share/catkin/cmake/catkinConfig.cmake:83 (find_package):
Could not find a package configuration file provided by
"camera_info_manager" with any of the following names:
camera_info_managerConfig.cmake
camera_info_manager-config.cmake
Add the installation prefix of "camera_info_manager" to CMAKE_PREFIX_PATH
or set "camera_info_manager_DIR" to a directory containing one of the above
files. If "camera_info_manager" provides a separate development package or
SDK, be sure it has been installed.
↧
Publishing cameraInfo
I'm trying to publish a CameraInfo message so that I can (eventually) use image_proc. I tried to write the subscriber/publisher from scratch and ran into the issue with filling in entries in the D matrix of the CameraInfo message (segfaults caused by allocation issues).
I looked around and found the camera_info_manager package but I can't figure out how to use it. I've tried to copy/paste what I could from the [camera1394 drivers](https://github.com/ros-drivers/camera1394/blob/master/src/nodes/driver1394.cpp) recommended by [this](http://answers.ros.org/question/11361/how-to-publish-sensor_msgscamerainfo-messages/) thread but I can't figure out how to initialize it--the references for the initialization are missing.
The basic structure is fairly simple but I don't know how to fill in the middle block.
//includes and whatnot
class publishCameraInfo
{
public:
publishCameraInfo()
{
//Topic you want to publish
image_pub_ = n_.advertise("snap_cam_camInfo/CameraInfo", 1);
//Topic you want to subscribe
sub_ = n_.subscribe("snap_cam_highres_publisher/image", 1, &publishCameraInfo::callback, this);
}
void callback(const sensor_msgs::Image& imgmsg)
{
????
image_pub_.publish(imgmsg, ci);
}
private:
ros::NodeHandle n_;
ros::Publisher image_pub_;
ros::Subscriber sub_;
};//End of class
int main(int argc, char **argv)
{
ros::init(argc, argv, "publishCameraInfo");
publishCameraInfo cameraPubObject;
ros::spin();
return 0;
}
↧
↧
CameraPublisher without transports
Hi,
I'm using the CameraPublisher class in image_transport to publish `image_raw` and `camera_info`. However, I do not want all the transports such as `compressed`, `theora` etc. How can I set that to not publish?
Thank you
↧
How to publish multiply images using webcam?
Hello,
My program takes the capture image from a webcam and dividing it into 4 images by splitting the main capture.
I want to publish those 4 images in a 4 different topics in the same ros package, same cpp file, but when I try to do that with creating 4 different camera_info_manager I get the error: ' Tried to advertise a service that is already advertised in this node [/camera/set_camera_info]'
Any ideas how to solve my issue and how to create 4 different rostopics ?
thanks.
↧
How to use camera_info_manager to publish camera_info
I am trying to calibrate my ov7251 camera using the camera_calibration package. I adapted a sample camera driver that I found which use the UV4L API so that I can try to publish images to the ROS topic /camera/image. I am also publishing to /camera/camera_info. However, what I need now is to be able to run the /camera/set_camera_info service so that I can use the calibration package.
Here is my code for publishing to /camera/image and /camera/camera_info:
int main(int argc, char **argv) {
dev_name = "/dev/video2";
namedWindow( "Camera Preview", WINDOW_AUTOSIZE );// Create a window for display.
ros::init(argc, argv, "image_publisher");
ros::NodeHandle nh;
image_transport::ImageTransport it(nh);
image_transport::Publisher pub = it.advertise("camera/image", 1);
ros::Publisher pub_info = nh.advertise("camera/camera_info", 100);
sensor_msgs::CameraInfo cam_info;
open_device();
init_device();
start_capturing();
while (nh.ok()) {
read_frame();
if (!prev.empty()) {
cv::Mat image = prev;
sensor_msgs::ImagePtr msg = cv_bridge::CvImage(std_msgs::Header(), "bgr8", image).toImageMsg();
ros::Rate loop_rate(5);
cam_info.header.stamp = ros::Time::now();
pub_info.publish(cam_info);
pub.publish(msg);
ros::spinOnce();
loop_rate.sleep();
}
}
...
return 0;
}
When I ran rostopic list, this is what I get:
/camera/camera_info
/camera/image
/camera/image/compressed
/camera/image/compressed/parameter_descriptions
/camera/image/compressed/parameter_updates
/camera/image/compressedDepth
/camera/image/compressedDepth/parameter_descriptions
/camera/image/compressedDepth/parameter_updates
/camera/image/theora
/camera/image/theora/parameter_descriptions
/camera/image/theora/parameter_updates
/camera/image_raw
/rosout
/rosout_agg
/statistics
/svo/dense_input
/svo/image
/svo/image/compressed
/svo/image/compressed/parameter_descriptions
/svo/image/compressed/parameter_updates
/svo/image/compressedDepth
/svo/image/compressedDepth/parameter_descriptions
/svo/image/compressedDepth/parameter_updates
/svo/image/theora
/svo/image/theora/parameter_descriptions
/svo/image/theora/parameter_updates
/svo/info
/svo/keyframes
/svo/points
/svo/pose
/svo/remote_key
/tf
And when I run rosservice list:
/camera/image/compressed/set_parameters
/camera/image/compressedDepth/set_parameters
/camera/image/theora/set_parameters
/image_publisher/get_loggers
/image_publisher/set_logger_level
/rosout/get_loggers
/rosout/set_logger_level
/rqt_gui_py_node_13721/get_loggers
/rqt_gui_py_node_13721/set_logger_level
/rqt_gui_py_node_13807/get_loggers
/rqt_gui_py_node_13807/set_logger_level
/svo/get_loggers
/svo/image/compressed/set_parameters
/svo/image/compressedDepth/set_parameters
/svo/image/theora/set_parameters
/svo/set_logger_level
As you can see, I don't have a /set_camera_info service, which I think is the main problem I am having with trying to run the camera_calibration package. If anyone can please provide me with a simple sample code for using the camera_info_manager, it would be much appreciated.
EDIT: For now, I wish to simply initialize a camera_info_manager object so that I can use its functions to run the set_camera_info service, but I am not well-versed with C++ so I am having some problems understanding the tutorial for camera_info_manager.
↧
Ros (kinetic) fails at installing camera_info_manager due to internal errors with gtest
Simply put, I get a few errors when the ros installer gets to camera_info_manager.
I have gtest 1.7.0 installed.
[ 50%] Built target camera_info_manager
Scanning dependencies of target unit_test
[ 75%] Building CXX object CMakeFiles/unit_test.dir/tests/unit_test.cpp.o
In file included from /Users/redacted/ros_catkin_ws/src/image_common/camera_info_manager/tests/unit_test.cpp:44:
In file included from /usr/local/include/gtest/gtest.h:62:
/usr/local/include/gtest/gtest/internal/gtest-internal.h:642:9: error: use of undeclared identifier 'StripTrailingSpaces'
StripTrailingSpaces(GetPrefixUntilComma(test_names)).c_str(),
^
/usr/local/include/gtest/gtest/internal/gtest-internal.h:678:29: error: use of undeclared identifier 'StripTrailingSpaces'
std::string test_name = StripTrailingSpaces(
^
/usr/local/include/gtest/gtest/internal/gtest-internal.h:890:36: error: expected parameter declarator
GTEST_DISABLE_MSC_WARNINGS_PUSH_(4244)
^
/usr/local/include/gtest/gtest/internal/gtest-internal.h:890:36: error: expected ')'
/usr/local/include/gtest/gtest/internal/gtest-internal.h:890:35: note: to match this '('
GTEST_DISABLE_MSC_WARNINGS_PUSH_(4244)
^
/usr/local/include/gtest/gtest/internal/gtest-internal.h:890:3: error: C++ requires a type specifier for all declarations
GTEST_DISABLE_MSC_WARNINGS_PUSH_(4244)
^
/usr/local/include/gtest/gtest/internal/gtest-internal.h:890:41: error: expected ';' at end of declaration list
GTEST_DISABLE_MSC_WARNINGS_PUSH_(4244)
^
/usr/local/include/gtest/gtest/internal/gtest-internal.h:893:3: error: C++ requires a type specifier for all declarations
GTEST_DISABLE_MSC_WARNINGS_POP_()
^
/usr/local/include/gtest/gtest/internal/gtest-internal.h:893:36: error: expected ';' at end of declaration list
GTEST_DISABLE_MSC_WARNINGS_POP_()
^
/usr/local/include/gtest/gtest/internal/gtest-internal.h:897:45: error: no member named 'value' in 'ImplicitlyConvertible'
const bool ImplicitlyConvertible::value;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
In file included from /Users/redacted/ros_catkin_ws/src/image_common/camera_info_manager/tests/unit_test.cpp:44:
/usr/local/include/gtest/gtest.h:690:30: error: out-of-line declaration of 'MakeAndRegisterTestInfo' does not match any declaration in namespace 'testing::internal'
friend TestInfo* internal::MakeAndRegisterTestInfo(
^~~~~~~~~~~~~~~~~~~~~~~
10 errors generated.
make[2]: *** [CMakeFiles/unit_test.dir/tests/unit_test.cpp.o] Error 1
make[1]: *** [CMakeFiles/unit_test.dir/all] Error 2
make: *** [all] Error 2
↧
↧
How to configure CameraInfoManager set_camera_info service name?
How do I configure CameraInfoManager to publish the correct set_camera_info services?
I am working on a very simple node to take stereo images produced by a stereo USB camera where the images come in as a single double-wide image consisting of left/right images concatenated. The node simply splits the incoming image down the middle and republishes on left and right image topics. I am trying to add the appropriate CameraInfoManager machinery to load/save calibration data. The current code is in the branch 'cam_info' at https://github.com/dbc/side_x_side_stereo
I create two pointers to CamInfoManager instances:
// Camera info managers.
camera_info_manager::CameraInfoManager *left_cinfo_;
camera_info_manager::CameraInfoManager *right_cinfo_;
Allocate and init:
// Allocate and initialize camera info managers.
left_cinfo_ =
new camera_info_manager::CameraInfoManager(nh, "left_camera");
right_cinfo_ =
new camera_info_manager::CameraInfoManager(nh, "right_camera");
left_cinfo_->loadCameraInfo("");
right_cinfo_->loadCameraInfo("");
But I don't see 'left_camera' or 'right_camera' associated set_camera_info services being advertised:
dave@ai1:~/catkin_ws$ rosservice list
/cameracalibrator/get_loggers
/cameracalibrator/set_logger_level
/image_raw/compressed/set_parameters
/image_raw/compressedDepth/set_parameters
/image_raw/theora/set_parameters
/libuvc_camera/get_loggers
/libuvc_camera/set_logger_level
/libuvc_camera/set_parameters
/rosout/get_loggers
/rosout/set_logger_level
/rqt_gui_cpp_node_5296/get_loggers
/rqt_gui_cpp_node_5296/set_logger_level
/rqt_gui_py_node_5296/get_loggers
/rqt_gui_py_node_5296/set_logger_level
/set_camera_info
/side_by_side_stereo_splitter_node/get_loggers
/side_by_side_stereo_splitter_node/set_camera_info
/side_by_side_stereo_splitter_node/set_logger_level
/stereo/left/image_raw/compressed/set_parameters
/stereo/left/image_raw/compressedDepth/set_parameters
/stereo/left/image_raw/theora/set_parameters
/stereo/right/image_raw/compressed/set_parameters
/stereo/right/image_raw/compressedDepth/set_parameters
/stereo/right/image_raw/theora/set_parameters
There is /side_by_side_stereo_splitter_node/set_camera_info, but I am confused as to what is creating that.
So, I am clearly not setting up the CameraInfoManagers correctly to get the topics that camera_calibration expects. It is kind of whiney:
Traceback (most recent call last):
File "/opt/ros/melodic/lib/python2.7/dist-packages/camera_calibration/camera_calibrator.py", line 247, in on_mouse
if self.do_upload():
File "/opt/ros/melodic/lib/python2.7/dist-packages/camera_calibration/camera_calibrator.py", line 207, in do_upload
response = self.set_left_camera_info_service(info[0])
File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 439, in __call__
return self.call(*args, **kwds)
File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 499, in call
service_uri = self._get_service_uri(request)
File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 467, in _get_service_uri
raise ServiceException("service [%s] unavailable"%self.resolved_name)
rospy.service.ServiceException: service [/left_camera/set_camera_info] unavailable
What do I need to do to get CameraInfoManager to advertise sensible services?
↧