Hi, I am having a problem with getting gazebo and player to talk to eachother. gazebo compiles and runs fine standalone, and I have had player and stage talking with no problems also. I am using the latest SVN of everything. Firstly I run gazebo with the pioneer2at.world which says its succesfully initialized. Secondly I run player with the following config file ...
driver ( name "gazebo" provides ["simulation:0"] plugin "libgazeboplugin" server_id "default" ) driver ( name "gazebo" provides ["position2d:0"] gz_id "position_iface_0" ) driver ( name "gazebo" provides ["laser:0"] gz_id "laser_iface_0" ) driver ( name "vfh" provides ["position2d:1"] requires ["position2d:0" "laser:0"] cell_size 0.1 window_diameter 61 sector_angle 1 safety_dist_0ms 0.2 safety_dist_1ms 0.4 max_speed 0.3 max_turnrate_0ms 75 max_turnrate_1ms 50 weight_desired_dir 5.0 weight_current_dir 3.0 ) driver ( name "gazebo" provides ["fiducial:0"] gz_id "fiducial_iface_0" ) The output from player is ... invoking player_driver_init()... invoking player_driver_init()... * Part of the Player/Stage Project [http://playerstage.sourceforge.net] * Copyright 2000-2006 Richard Vaughan, Andrew Howard, Brian Gerkey, Nathan Koenig * and contributors. Released under the GNU General Public License v2. success Gazebo Plugin driver creating 1 device 6665.31.0 is a simulation interface. opening /tmp/gazebo-ben-0 opening /tmp/gazebo-ben-0/simulation.default 112 33842332 opening /tmp/gazebo-ben-0/simulation.default +112 33842332 Gazebo Plugin driver creating 1 device 6665.4.0 is a position2d interface. Gazebo Plugin driver creating 1 device 6665.6.0 is a laser interface. Gazebo Plugin driver creating 1 device 6665.10.0 is a fiducial interface. create_and_bind_socket():bind() failed; socket not created.: Address already in use error : create_and_bind_socket() failed error : failed to listen on requested TCP ports It says that the address is already in use. I use netstat before running to check whats available, and port 6665 is free. When player/gazebo are running 6665 is being used both by a TCP and a UDP process. Is this expected? Does anyone have any idea what could be blocking the port? Any ideas would be much appreciated. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Playerstage-gazebo mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/playerstage-gazebo
