Hi guys , i am a beginner for ROS. i write a urdf robot and attach diff_drive and hokuyo_laser plugin on it , with configure and use slam_gmapping i can teleop my 'robot(urdf)' in gazebo and build map . but still can't navigation in gazebo , i don't know ho w to do it .
the question is ,when i spawn my model i see some warn ,i don't know.......
[ INFO] [1422432448.072115642, 0.023000000]: waitForService: Service [/gazebo/set_physics_properties] is now available.
[ INFO] [1422432448.133383656, 0.081000000]: Physics dynamic reconfigure ready.
[ INFO] [1422432497.779480058, 49.026000000]: Laser Plugin (robotNamespace = /), Info: Using the 'robotNamespace' param: '/'
[ INFO] [1422432497.779620674, 49.026000000]: Starting Laser Plugin (ns = /)!
[ INFO] [1422432497.847324932, 49.026000000]: Laser Plugin (ns = /) , set to ""
[ INFO] [1422432497.908139397, 49.026000000]: Starting plugin DiffDrive(ns = //)!
[ WARN] [1422432497.908227139, 49.026000000]: DiffDrive(ns = //): missing default is na
[ INFO] [1422432497.910157650, 49.026000000]: DiffDrive(ns = //): =
[ WARN] [1422432497.910608101, 49.026000000]: DiffDrive(ns = //): missing default is false
[ WARN] [1422432497.910649709, 49.026000000]: DiffDrive(ns = //): missing default is false
[ WARN] [1422432497.910940987, 49.026000000]: DiffDrive(ns = //): missing default is 0
[ WARN] [1422432497.910981351, 49.026000000]: DiffDrive(ns = //): missing default is 5
[ WARN] [1422432497.911654704, 49.026000000]: DiffDrive(ns = //): missing default is 1
[ WARN] [1422432497.912120315, 49.026000000]: GazeboRosDiffDrive Plugin (ns = ) missing , defaults to 1
[ INFO] [1422432497.925900930, 49.026000000]: DiffDrive(ns = //): Try to subscribe to cmd_vel!
[ INFO] [1422432497.932386235, 49.026000000]: DiffDrive(ns = //): Subscribe to cmd_vel!
[ INFO] [1422432497.933865558, 49.026000000]: DiffDrive(ns = //): Advertise odom on odom !
↧
navigation in gazebo
↧
how do i simulate the writing motion of my robot in gazebo?
I want to simulate a robotic arm in gazebo that can write. however how do i create an effector that will leave a mark on a surface in the gazebo world (much like a pen) ?
↧
↧
Gazebo + ros_control
I have been trying to get the LWR KUKA robot to be controlled in Gazebo through ROS (simulation only at this stage).
I have been following this tutorial [gazebo_ros_control](http://gazebosim.org/tutorials?tut=ros_control) which achieves
the wanted effect with the rrbot. The controller in the tutorial is an effort_controllers/JointPositionController.
I have reproduced the same steps of the tutorial on my own KUKA model, but the results differ and I am unable to have
to robot maintain a specific joint configuration (I have also tried to change the pid gains, but with no success).
I have uploaded my [KUKA package](https://github.com/gpldecha/LWR_KUKA_ROS) on git.
I can move the robot with little difficulty in Rviz with Moveit but I have been running into difficulties with Gazebo control
for some time. I am not sure if I have to write my own control plugin for gazebo or what I should do. The documentation
on the web is at some times quite overwhelming.
Any help to get a position control working on my Gazebo + ROS KUKA model would be very welcome.
↧
trouble building ROS package lwr_robot
When building lwr_robot I get the following error:
[ 0%] Built target rosbuild_precompile
make[3]: Entering directory `/home/alexander/fuerte_workspace/lwr_robot/lwr_simulation/build'
make[3]: Leaving directory `/home/alexander/fuerte_workspace/lwr_robot/lwr_simulation/build'
make[3]: Entering directory `/home/alexander/fuerte_workspace/lwr_robot/lwr_simulation/build'
[100%] Building CXX object CMakeFiles/lwr_controller.dir/src/lwr_controller.o
/home/alexander/fuerte_workspace/lwr_robot/lwr_simulation/src/lwr_controller.cpp: In member function ‘virtual void gazebo::LWRController::Load(gazebo::physics::ModelPtr, sdf::ElementPtr)’:
/home/alexander/fuerte_workspace/lwr_robot/lwr_simulation/src/lwr_controller.cpp:100:49: error: ‘class gazebo::math::Angle’ has no member named ‘Radian’
/home/alexander/fuerte_workspace/lwr_robot/lwr_simulation/src/lwr_controller.cpp: In member function ‘virtual void gazebo::LWRController::UpdateChild()’:
/home/alexander/fuerte_workspace/lwr_robot/lwr_simulation/src/lwr_controller.cpp:169:116: error: ‘class gazebo::math::Angle’ has no member named ‘Radian’
make[3]: *** [CMakeFiles/lwr_controller.dir/src/lwr_controller.o] Error 1
make[3]: Leaving directory `/home/alexander/fuerte_workspace/lwr_robot/lwr_simulation/build'
make[2]: *** [CMakeFiles/lwr_controller.dir/all] Error 2
There seems to be an issue with the gazebo package.
Do you have any experience with this?
Regards,
Alex
↧
Roslaunch Error
Hi guys, i'm trying to run a URDF on my workspace on Ros Hydro, and i'm getting some errors. I will give a link with my .launch, my .URDF and the error.
Some knows what should I do?
I really need to run this...
This URDF was exported form a Solid Works draw with Export Urdf plugin, if someone knows a better way to do this or should help me with this exportation... I have all the files in solid works to try to export again.
I'm desesperated...
Link to files: https://gist.github.com/anonymous/751b0435785d5e331b32
↧
↧
simulated robot in real environment?
Is it possible to work with a simulated robot in real environment?
I want to do pick and place operation using a robot (for example PR2). It requires point cloud processing in PCl to detect objects and position them. However, the environment with specific objects are real. As I don't have a robot, is it possible to use simulated robot to do pick and place task of real objects?
Is it possible to generate a world in gazebo that resembles my real environment. Than simulated robot can work with simulated world?
Anyone can please describe how to do this?
↧
linear actuator simulation in gazebo?
i want to simulate a linear actuator on a robot in gazebo. Anyone gives me an advice please?
↧
Sleep time is larger than clock resolution, skipping sleep
Hello,
I am using Ubuntu14. Everytime i launch turtlebot(gazebo) in ROS Indigo, i am constantly getting the following warning:
"warning [Time.cc.205] Sleep time is larger than clock resolution, skipping sleep"
Does anyone know why?
Thanks,
Emre
↧
How to use irobot create in gazebo with ROS hydro?
As I could see the ROS hydro version has the packages for irobot create:
ros-hydro-create-dashboard
ros-hydro-create-description
ros-hydro-create-driver
ros-hydro-create-gazebo-plugins
ros-hydro-create-node
But I couldn't manage to find a tutorial of how to run Create in gazebo simulator.
↧
↧
joint controller in gazebo
i created a linear joint . basically, it is like a linear actuator only can move up and down like the pr2 torso. but i stuck at making it moves in gazebo. Is there any gazebo plugin for it ? or do i have to write a controller? Thanks
↧
Unmet dependencies installing gazebo_ros_pkgs
Hello Everybody,
I am relatively new to ROS and Gazebo, so you will most likely be seeing my questions here a lot. Anyway, I was trying to set up ROS and Gazebo on a new computer, a LATITUDE | D830 from Used Computer Warehouse. I installed 14.04 Ubuntu in place of Windows, and proceeded to install ROS Indigo and Gazebo. While following the instructions at http://gazebosim.org/tutorials?tut=ros_installing, I got this long error message upon the input of the command sudo apt-get install `ros-indigo-gazebo-ros-pkgs ros-indigo-gazebo-ros-control`:
skyguyjedi@skyguyjedi-Latitude-D830:~$ sudo apt-get install ros-indigo-gazebo-ros-pkgs ros-indigo-gazebo-ros-control
[sudo] password for skyguyjedi:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
ros-indigo-gazebo-ros-control : Depends: gazebo2 but it is not going to be installed
Depends: libsdformat1 but it is not going to be installed
Depends: ros-indigo-gazebo-ros but it is not going to be installed
ros-indigo-gazebo-ros-pkgs : Depends: ros-indigo-gazebo-plugins but it is not going to be installed
Depends: ros-indigo-gazebo-ros but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
As far as I can tell, I'm missing some dependencies that these files need to be installed, but I cannot figure out what these dependencies are, or where to find them. Any assistance, of course, extremely appreciated. I know that this is a rookie problem, but my limited googling skills were unable to turn up another error of this type.
Thanks,
↧
robot doesnt move straight
i have attached differential driver to my custom robot. however, i notice it doesnt move straight when i publish to cmd_vel topic. How can i fixgo about this?
↧
Spawning hector quadrotor crashes gazebo on indigo
Hi,
I was trying to start hector quadrotor demo launch files and keep getting gazebo segmentation faults when the script tries to spawn quadrotor. After some time I have tried to spawn it on my own using these launch files:
roslaunch gazebo_ros empty_world.launch
roslaunch hector_quadrotor_gazebo spawn_quadrotor.launch
But even then the gazebo server crashes with following error:
spawn_model script started
[INFO] [WallTime: 1423382867.059244] [0.000000] Loading model xml from ros parameter
[INFO] [WallTime: 1423382867.061820] [0.000000] Waiting for service /gazebo/spawn_urdf_model
[INFO] [WallTime: 1423382867.064229] [0.000000] Calling service /gazebo/spawn_urdf_model
[INFO] [WallTime: 1423382867.111548] [0.000000] Controller Spawner: Waiting for service controller_manager/load_controller
Segmentation fault (core dumped)
Service call failed: transport error completing service call: unable to receive data from sender, check sender's logs for details
[gazebo-1] process has died [pid 24654, exit code 139, cmd /opt/ros/indigo/lib/gazebo_ros/gzserver worlds/empty.world __name:=gazebo __log:=/home/rokas/.ros/log/25359450-af08-11e4-930f-fcf8ae311424/gazebo-1.log].
The log files after the error is empty, so I can't traceback what happening. But it seems like spawning quadrotor crashes the gzserver.
I have tried using the packages installed via `apt-get` and then tried with latest version of `hector_quadrotor` from github and the problem persists. Maybe some of you will have some ideas on this problem?
↧
↧
Spawning Robot in Gazebo Problem
Currently I have a robot which I made the URDF file for. I wrote the file with all the joints in the XY plane to make the 3D coordinates simpler, if you can imagine a standing human pose, it is something similar. The actual pose the robot sits in is close to a kneeling position for a human so I have set some of the joints to revolute with very close upper and lower limits to "fix" the joint in the position I want. My problem is that when the robot is spawned into Gazebo it spawns in its fully upright (standing) position and quickly moves the joints to the angle determined by the revolute joints in the following frames. This seems to be causing many errors as it is causing momentum in the links that are moving in the robot causing it to flip over.
Is there a simpler way to fix this problem rather than re-writing the URDF file in the kneeling position rather than the standing?
Thanks in advance,
Adam
↧
ros_control questions
I have been studying ros_control and how to use it for a while now, but I still have a few questions. I have made a list of the questions I have been unable to answer, and I would appreciate it someone could help me find answers.
1. The velocity and position controllers are listed twice here: http://wiki.ros.org/ros_control#Controllers. (Both are under "effort_controllers", and then each is under their own section.) Is that just a typo, or am I missing something?
2. I was not planning to have sensors that could feed a JointStateInterface implementation. (My robot is car-like, and I believe that higher-level feedback from IMU and GPS sensors will be sufficient.) I'm thinking that I will write my hardware interface implementation to just echo the set point back as the current state. Should that work? Has anyone else done that before?
3. I have had a difficult time understanding the role of transmissions with regards to Gazebo. The [Gazebo documentation](http://gazebosim.org/tutorials/?tut=ros_control#AddtransmissionelementstoaURDF) seems to suggest that a transmission is required for each joint. I think it's because the Gazebo plugin is unable to read the YAML file used by ROS controller manager to determine whether to use a velocity, effort, or position controller. Do I have that right?
Thanks,
Sam
↧
Failed to load plugin libgazebo_ros_create.so
I am following the [Explore the Gazebo world](http://wiki.ros.org/turtlebot_simulator/Tutorials/indigo/Explore%20the%20Gazebo%20world) tutorial of turtlebot_simulator in ROS Indigo. Whenever I try to launch roslaunch turtlebot_gazebo turtlebot_world.launch I get the following error
Error [Plugin.hh:156] Failed to load plugin libgazebo_ros_create.so: libgazebo_ros_create.so: cannot open shared object file: No such file or directory
I have ros-indigo-gazebo-ros-control installed. What do I do to fix this?
↧
Gmapping without landmarks
I am running gmapping on husky bot with hokoyo scanner in gazebo simulation environment.
I am experimenting with gmapping in an empty world.
Gmapping does not create any map and the map frame jumps around.
Why does gmapping not create a map or mark cells as vacant if the laser scanner is not detecting any obstacles. And if the laser scanner can't see any landmarks, why is the map frame not equal to odom frame?
↧
↧
Launching Kinect on PR2 Gazebo to get same topics like openni_launch?
Hi all,
Information has been updated, but this documentation doesn't mention Gazebo:
http://ros.org/wiki/openni_camera
http://ros.org/wiki/openni_launch
To test a real OpenNI device, I can run:
$ roslaunch openni_launch openni.launch which will produce all the topics listed below.
If you launch a PR2 or Turtlebot in Gazebo simulation, it only outputs the raw data. So there are no topics like: > /camera/rgb/image_color
What's the best way to launch image_proc & depth_image_proc nodelets? Will this work? $ roslaunch openni_launch openni.launch load_driver:=false depth_registration:=true (I can't test anything at the moment)
Are there any plans to include this with the PR2 or Turtlebot simulators?
(*turtlebot_bringup/launch/3dsensor.launch* gave me some ideas, but I guess it's only for the real robot) Thanks,
David.
**Topics published from real OpenNI device:** /camera/depth/camera_info /camera/depth/disparity /camera/depth/image /camera/depth/image/compressed /camera/depth/image/compressed/parameter_descriptions /camera/depth/image/compressed/parameter_updates /camera/depth/image/compressedDepth /camera/depth/image/compressedDepth/parameter_descriptions /camera/depth/image/compressedDepth/parameter_updates /camera/depth/image/theora /camera/depth/image/theora/parameter_descriptions /camera/depth/image/theora/parameter_updates /camera/depth/image_raw /camera/depth/image_raw/compressed /camera/depth/image_raw/compressed/parameter_descriptions /camera/depth/image_raw/compressed/parameter_updates /camera/depth/image_raw/compressedDepth /camera/depth/image_raw/compressedDepth/parameter_descriptions /camera/depth/image_raw/compressedDepth/parameter_updates /camera/depth/image_raw/theora /camera/depth/image_raw/theora/parameter_descriptions /camera/depth/image_raw/theora/parameter_updates /camera/depth/image_rect /camera/depth/image_rect/compressed /camera/depth/image_rect/compressed/parameter_descriptions /camera/depth/image_rect/compressed/parameter_updates /camera/depth/image_rect/compressedDepth /camera/depth/image_rect/compressedDepth/parameter_descriptions /camera/depth/image_rect/compressedDepth/parameter_updates /camera/depth/image_rect/theora /camera/depth/image_rect/theora/parameter_descriptions /camera/depth/image_rect/theora/parameter_updates /camera/depth/image_rect_raw /camera/depth/image_rect_raw/compressed /camera/depth/image_rect_raw/compressed/parameter_descriptions /camera/depth/image_rect_raw/compressed/parameter_updates /camera/depth/image_rect_raw/compressedDepth /camera/depth/image_rect_raw/compressedDepth/parameter_descriptions /camera/depth/image_rect_raw/compressedDepth/parameter_updates /camera/depth/image_rect_raw/theora /camera/depth/image_rect_raw/theora/parameter_descriptions /camera/depth/image_rect_raw/theora/parameter_updates /camera/depth/points /camera/depth/rectify_depth/parameter_descriptions /camera/depth/rectify_depth/parameter_updates /camera/depth_registered/camera_info /camera/depth_registered/disparity /camera/depth_registered/image /camera/depth_registered/image/compressed /camera/depth_registered/image/compressed/parameter_descriptions /camera/depth_registered/image/compressed/parameter_updates /camera/depth_registered/image/compressedDepth /camera/depth_registered/image/compressedDepth/parameter_descriptions /camera/depth_registered/image/compressedDepth/parameter_updates /camera/depth_registered/image/theora /camera/depth_registered/image/theora/parameter_descriptions /camera/depth_registered/image/theora/parameter_updates /camera/depth_registered/image_raw /camera/depth_registered/image_raw/compressed /camera/depth_registered/image_raw/compressed/parameter_descriptions /camera/depth_registered/image_raw/compressed/parameter_updates /camera/depth_registered/image_raw/compressedDepth /camera/depth_registered/image_raw/compressedDepth/parameter_descriptions /camera/depth_registered/image_raw/compressedDepth/parameter_updates /camera/depth_registered/image_raw/theora /camera/depth_registered/image_raw/theora/parameter_descriptions /camera/depth_registered/image_raw/theora/parameter_updates /camera/depth_registered/image_rect /camera/depth_registered/image_rect/compressed /camera/depth_registered/image_rect/compressed/parameter_descriptions /camera/depth_registered/image_rect/compressed/parameter_updates /camera/depth_registered/image_rect/compressedDepth /camera/depth_registered/image_rect/compressedDepth/parameter_descriptions /camera/depth_registered/image_rect/compressedDepth/parameter_updates /camera/depth_registered/image_rect/theora /camera/depth_registered/image_rect/theora/parameter_descriptions /camera/depth_registered/image_rect/theora/parameter_updates /camera/depth_registered/image_rect_raw /camera/depth_registered/image_rect_raw/compressed /camera/depth_registered/image_rect_raw/compressed/parameter_descriptions /camera/depth_registered/image_rect_raw/compressed/parameter_updates /camera/depth_registered/image_rect_raw/compressedDepth /camera/depth_registered/image_rect_raw/compressedDepth/parameter_descriptions /camera/depth_registered/image_rect_raw/compressedDepth/parameter_updates /camera/depth_registered/image_rect_raw/theora /camera/depth_registered/image_rect_raw/theora/parameter_descriptions /camera/depth_registered/image_rect_raw/theora/parameter_updates /camera/depth_registered/points /camera/depth_registered/rectify_depth/parameter_descriptions /camera/depth_registered/rectify_depth/parameter_updates /camera/driver/parameter_descriptions /camera/driver/parameter_updates /camera/ir/camera_info /camera/ir/image_raw /camera/ir/image_raw/compressed /camera/ir/image_raw/compressed/parameter_descriptions /camera/ir/image_raw/compressed/parameter_updates /camera/ir/image_raw/compressedDepth /camera/ir/image_raw/compressedDepth/parameter_descriptions /camera/ir/image_raw/compressedDepth/parameter_updates /camera/ir/image_raw/theora /camera/ir/image_raw/theora/parameter_descriptions /camera/ir/image_raw/theora/parameter_updates /camera/ir/image_rect /camera/ir/image_rect/compressed /camera/ir/image_rect/compressed/parameter_descriptions /camera/ir/image_rect/compressed/parameter_updates /camera/ir/image_rect/compressedDepth /camera/ir/image_rect/compressedDepth/parameter_descriptions /camera/ir/image_rect/compressedDepth/parameter_updates /camera/ir/image_rect/theora /camera/ir/image_rect/theora/parameter_descriptions /camera/ir/image_rect/theora/parameter_updates /camera/ir/rectify_ir/parameter_descriptions /camera/ir/rectify_ir/parameter_updates /camera/projector/camera_info /camera/rgb/camera_info /camera/rgb/debayer/parameter_descriptions /camera/rgb/debayer/parameter_updates /camera/rgb/image_color /camera/rgb/image_color/compressed /camera/rgb/image_color/compressed/parameter_descriptions /camera/rgb/image_color/compressed/parameter_updates /camera/rgb/image_color/compressedDepth /camera/rgb/image_color/compressedDepth/parameter_descriptions /camera/rgb/image_color/compressedDepth/parameter_updates /camera/rgb/image_color/theora /camera/rgb/image_color/theora/parameter_descriptions /camera/rgb/image_color/theora/parameter_updates /camera/rgb/image_mono /camera/rgb/image_mono/compressed /camera/rgb/image_mono/compressed/parameter_descriptions /camera/rgb/image_mono/compressed/parameter_updates /camera/rgb/image_mono/compressedDepth /camera/rgb/image_mono/compressedDepth/parameter_descriptions /camera/rgb/image_mono/compressedDepth/parameter_updates /camera/rgb/image_mono/theora /camera/rgb/image_mono/theora/parameter_descriptions /camera/rgb/image_mono/theora/parameter_updates /camera/rgb/image_raw /camera/rgb/image_raw/compressed /camera/rgb/image_raw/compressed/parameter_descriptions /camera/rgb/image_raw/compressed/parameter_updates /camera/rgb/image_raw/compressedDepth /camera/rgb/image_raw/compressedDepth/parameter_descriptions /camera/rgb/image_raw/compressedDepth/parameter_updates /camera/rgb/image_raw/theora /camera/rgb/image_raw/theora/parameter_descriptions /camera/rgb/image_raw/theora/parameter_updates /camera/rgb/image_rect /camera/rgb/image_rect/compressed /camera/rgb/image_rect/compressed/parameter_descriptions /camera/rgb/image_rect/compressed/parameter_updates /camera/rgb/image_rect/compressedDepth /camera/rgb/image_rect/compressedDepth/parameter_descriptions /camera/rgb/image_rect/compressedDepth/parameter_updates /camera/rgb/image_rect/theora /camera/rgb/image_rect/theora/parameter_descriptions /camera/rgb/image_rect/theora/parameter_updates /camera/rgb/image_rect_color /camera/rgb/image_rect_color/compressed /camera/rgb/image_rect_color/compressed/parameter_descriptions /camera/rgb/image_rect_color/compressed/parameter_updates /camera/rgb/image_rect_color/compressedDepth /camera/rgb/image_rect_color/compressedDepth/parameter_descriptions /camera/rgb/image_rect_color/compressedDepth/parameter_updates /camera/rgb/image_rect_color/theora /camera/rgb/image_rect_color/theora/parameter_descriptions /camera/rgb/image_rect_color/theora/parameter_updates /camera/rgb/rectify_color/parameter_descriptions /camera/rgb/rectify_color/parameter_updates /camera/rgb/rectify_mono/parameter_descriptions /camera/rgb/rectify_mono/parameter_updates /rosout /rosout_agg /tf
http://ros.org/wiki/openni_camera
http://ros.org/wiki/openni_launch
To test a real OpenNI device, I can run:
$ roslaunch openni_launch openni.launch which will produce all the topics listed below.
If you launch a PR2 or Turtlebot in Gazebo simulation, it only outputs the raw data. So there are no topics like: > /camera/rgb/image_color
What's the best way to launch image_proc & depth_image_proc nodelets? Will this work? $ roslaunch openni_launch openni.launch load_driver:=false depth_registration:=true (I can't test anything at the moment)
Are there any plans to include this with the PR2 or Turtlebot simulators?
(*turtlebot_bringup/launch/3dsensor.launch* gave me some ideas, but I guess it's only for the real robot) Thanks,
David.
**Topics published from real OpenNI device:** /camera/depth/camera_info /camera/depth/disparity /camera/depth/image /camera/depth/image/compressed /camera/depth/image/compressed/parameter_descriptions /camera/depth/image/compressed/parameter_updates /camera/depth/image/compressedDepth /camera/depth/image/compressedDepth/parameter_descriptions /camera/depth/image/compressedDepth/parameter_updates /camera/depth/image/theora /camera/depth/image/theora/parameter_descriptions /camera/depth/image/theora/parameter_updates /camera/depth/image_raw /camera/depth/image_raw/compressed /camera/depth/image_raw/compressed/parameter_descriptions /camera/depth/image_raw/compressed/parameter_updates /camera/depth/image_raw/compressedDepth /camera/depth/image_raw/compressedDepth/parameter_descriptions /camera/depth/image_raw/compressedDepth/parameter_updates /camera/depth/image_raw/theora /camera/depth/image_raw/theora/parameter_descriptions /camera/depth/image_raw/theora/parameter_updates /camera/depth/image_rect /camera/depth/image_rect/compressed /camera/depth/image_rect/compressed/parameter_descriptions /camera/depth/image_rect/compressed/parameter_updates /camera/depth/image_rect/compressedDepth /camera/depth/image_rect/compressedDepth/parameter_descriptions /camera/depth/image_rect/compressedDepth/parameter_updates /camera/depth/image_rect/theora /camera/depth/image_rect/theora/parameter_descriptions /camera/depth/image_rect/theora/parameter_updates /camera/depth/image_rect_raw /camera/depth/image_rect_raw/compressed /camera/depth/image_rect_raw/compressed/parameter_descriptions /camera/depth/image_rect_raw/compressed/parameter_updates /camera/depth/image_rect_raw/compressedDepth /camera/depth/image_rect_raw/compressedDepth/parameter_descriptions /camera/depth/image_rect_raw/compressedDepth/parameter_updates /camera/depth/image_rect_raw/theora /camera/depth/image_rect_raw/theora/parameter_descriptions /camera/depth/image_rect_raw/theora/parameter_updates /camera/depth/points /camera/depth/rectify_depth/parameter_descriptions /camera/depth/rectify_depth/parameter_updates /camera/depth_registered/camera_info /camera/depth_registered/disparity /camera/depth_registered/image /camera/depth_registered/image/compressed /camera/depth_registered/image/compressed/parameter_descriptions /camera/depth_registered/image/compressed/parameter_updates /camera/depth_registered/image/compressedDepth /camera/depth_registered/image/compressedDepth/parameter_descriptions /camera/depth_registered/image/compressedDepth/parameter_updates /camera/depth_registered/image/theora /camera/depth_registered/image/theora/parameter_descriptions /camera/depth_registered/image/theora/parameter_updates /camera/depth_registered/image_raw /camera/depth_registered/image_raw/compressed /camera/depth_registered/image_raw/compressed/parameter_descriptions /camera/depth_registered/image_raw/compressed/parameter_updates /camera/depth_registered/image_raw/compressedDepth /camera/depth_registered/image_raw/compressedDepth/parameter_descriptions /camera/depth_registered/image_raw/compressedDepth/parameter_updates /camera/depth_registered/image_raw/theora /camera/depth_registered/image_raw/theora/parameter_descriptions /camera/depth_registered/image_raw/theora/parameter_updates /camera/depth_registered/image_rect /camera/depth_registered/image_rect/compressed /camera/depth_registered/image_rect/compressed/parameter_descriptions /camera/depth_registered/image_rect/compressed/parameter_updates /camera/depth_registered/image_rect/compressedDepth /camera/depth_registered/image_rect/compressedDepth/parameter_descriptions /camera/depth_registered/image_rect/compressedDepth/parameter_updates /camera/depth_registered/image_rect/theora /camera/depth_registered/image_rect/theora/parameter_descriptions /camera/depth_registered/image_rect/theora/parameter_updates /camera/depth_registered/image_rect_raw /camera/depth_registered/image_rect_raw/compressed /camera/depth_registered/image_rect_raw/compressed/parameter_descriptions /camera/depth_registered/image_rect_raw/compressed/parameter_updates /camera/depth_registered/image_rect_raw/compressedDepth /camera/depth_registered/image_rect_raw/compressedDepth/parameter_descriptions /camera/depth_registered/image_rect_raw/compressedDepth/parameter_updates /camera/depth_registered/image_rect_raw/theora /camera/depth_registered/image_rect_raw/theora/parameter_descriptions /camera/depth_registered/image_rect_raw/theora/parameter_updates /camera/depth_registered/points /camera/depth_registered/rectify_depth/parameter_descriptions /camera/depth_registered/rectify_depth/parameter_updates /camera/driver/parameter_descriptions /camera/driver/parameter_updates /camera/ir/camera_info /camera/ir/image_raw /camera/ir/image_raw/compressed /camera/ir/image_raw/compressed/parameter_descriptions /camera/ir/image_raw/compressed/parameter_updates /camera/ir/image_raw/compressedDepth /camera/ir/image_raw/compressedDepth/parameter_descriptions /camera/ir/image_raw/compressedDepth/parameter_updates /camera/ir/image_raw/theora /camera/ir/image_raw/theora/parameter_descriptions /camera/ir/image_raw/theora/parameter_updates /camera/ir/image_rect /camera/ir/image_rect/compressed /camera/ir/image_rect/compressed/parameter_descriptions /camera/ir/image_rect/compressed/parameter_updates /camera/ir/image_rect/compressedDepth /camera/ir/image_rect/compressedDepth/parameter_descriptions /camera/ir/image_rect/compressedDepth/parameter_updates /camera/ir/image_rect/theora /camera/ir/image_rect/theora/parameter_descriptions /camera/ir/image_rect/theora/parameter_updates /camera/ir/rectify_ir/parameter_descriptions /camera/ir/rectify_ir/parameter_updates /camera/projector/camera_info /camera/rgb/camera_info /camera/rgb/debayer/parameter_descriptions /camera/rgb/debayer/parameter_updates /camera/rgb/image_color /camera/rgb/image_color/compressed /camera/rgb/image_color/compressed/parameter_descriptions /camera/rgb/image_color/compressed/parameter_updates /camera/rgb/image_color/compressedDepth /camera/rgb/image_color/compressedDepth/parameter_descriptions /camera/rgb/image_color/compressedDepth/parameter_updates /camera/rgb/image_color/theora /camera/rgb/image_color/theora/parameter_descriptions /camera/rgb/image_color/theora/parameter_updates /camera/rgb/image_mono /camera/rgb/image_mono/compressed /camera/rgb/image_mono/compressed/parameter_descriptions /camera/rgb/image_mono/compressed/parameter_updates /camera/rgb/image_mono/compressedDepth /camera/rgb/image_mono/compressedDepth/parameter_descriptions /camera/rgb/image_mono/compressedDepth/parameter_updates /camera/rgb/image_mono/theora /camera/rgb/image_mono/theora/parameter_descriptions /camera/rgb/image_mono/theora/parameter_updates /camera/rgb/image_raw /camera/rgb/image_raw/compressed /camera/rgb/image_raw/compressed/parameter_descriptions /camera/rgb/image_raw/compressed/parameter_updates /camera/rgb/image_raw/compressedDepth /camera/rgb/image_raw/compressedDepth/parameter_descriptions /camera/rgb/image_raw/compressedDepth/parameter_updates /camera/rgb/image_raw/theora /camera/rgb/image_raw/theora/parameter_descriptions /camera/rgb/image_raw/theora/parameter_updates /camera/rgb/image_rect /camera/rgb/image_rect/compressed /camera/rgb/image_rect/compressed/parameter_descriptions /camera/rgb/image_rect/compressed/parameter_updates /camera/rgb/image_rect/compressedDepth /camera/rgb/image_rect/compressedDepth/parameter_descriptions /camera/rgb/image_rect/compressedDepth/parameter_updates /camera/rgb/image_rect/theora /camera/rgb/image_rect/theora/parameter_descriptions /camera/rgb/image_rect/theora/parameter_updates /camera/rgb/image_rect_color /camera/rgb/image_rect_color/compressed /camera/rgb/image_rect_color/compressed/parameter_descriptions /camera/rgb/image_rect_color/compressed/parameter_updates /camera/rgb/image_rect_color/compressedDepth /camera/rgb/image_rect_color/compressedDepth/parameter_descriptions /camera/rgb/image_rect_color/compressedDepth/parameter_updates /camera/rgb/image_rect_color/theora /camera/rgb/image_rect_color/theora/parameter_descriptions /camera/rgb/image_rect_color/theora/parameter_updates /camera/rgb/rectify_color/parameter_descriptions /camera/rgb/rectify_color/parameter_updates /camera/rgb/rectify_mono/parameter_descriptions /camera/rgb/rectify_mono/parameter_updates /rosout /rosout_agg /tf
↧
Launching Simulated Kinect on Pr2/Gazebo and get same topics as in openni_launch
Hey Guys,
i have pr2 running in simulation with gazebo and I am trying to get /head_mount_kinect/rgb/image_color or /head_mount_kinect/depth/image
using the command below
roslaunch openni_launch openni.launch load_driver:=false depth_registration:=true camera:=head_mount_kinect
but that are no messages when I echo these topics (no messages received and simulated time is active).
Is there another way to get these data in simulated environment/simulated kinect? I can get the raw images but not the ones that I want to use image_proc_nodelets.
Thanks!
↧
run Gazebo in ROS indigo in Virtualbox with libGl and openGl errors
Error [gazebo.cc:220] Waited 11 seconds for namespaces. Giving up;
libGL error: pci id for fd 10: 80ee:beef, driver (null);
OpenGL Warning: Failed to connect to host. Make sure 3D acceleration is enabled for this VM;
libGL error: core dri or dri2 extension not found;
libGL error: failed to load driver: vboxvideo;
Error [Node.cc:90] No namespace found;
Like I said, first run Gazebo, I see some error like that. any problem?
I just follow steps in http://gazebosim.org/tutorials?tut=ros_installing
which is "Test that stand-alone Gazebo works"
↧