I downloaded and built PX4 source code. Then I ran the jMAVSim simulator with make px4_sitl jmavsim everything works fine. Then I tried to run the Gazebo simulator with make px4_sitl gazebo but I am receiving the following error: Makefile:197: recipe for target 'px4_sitl' failed make: *** [px4_sitl] Error 1 My ROS settings are: declare -x ROSLISP_PACKAGE_DIRECTORIES="/home/csgurel/catkin_ws/devel/share/common-lisp" declare -x ROS_DISTRO="kinetic" declare -x ROS_ETC_DIR="/opt/ros/kinetic/etc/ros" declare -x ROS_PACKAGE_PATH="/home/csgurel/catkin_ws/src:/opt/ros/kinetic/share" declare -x ROS_ROOT="/opt/ros/kinetic/share/ros" declare -x ROS_VERSION="1" and I am using **Ubuntu 16.04**. In case you want to see it, the full output is: [2/6] Performing configure step for 'sitl_gazebo' -- install-prefix: /usr/local -- Boost version: 1.58.0 -- Found the following Boost libraries: -- system -- thread -- timer -- filesystem -- chrono -- date_time -- atomic -- Boost version: 1.58.0 -- Found the following Boost libraries: -- thread -- system -- filesystem -- program_options -- regex -- iostreams -- date_time -- chrono -- atomic -- Boost version: 1.58.0 -- Looking for OGRE... -- Found Ogre Ghadamon (1.9.0) -- Looking for OGRE_Paging... -- Found OGRE_Paging: optimized;/usr/lib/x86_64-linux-gnu/libOgrePaging.so;debug;/usr/lib/x86_64-linux-gnu/libOgrePaging.so -- Looking for OGRE_Terrain... -- Found OGRE_Terrain: optimized;/usr/lib/x86_64-linux-gnu/libOgreTerrain.so;debug;/usr/lib/x86_64-linux-gnu/libOgreTerrain.so -- Looking for OGRE_Property... -- Found OGRE_Property: optimized;/usr/lib/x86_64-linux-gnu/libOgreProperty.so;debug;/usr/lib/x86_64-linux-gnu/libOgreProperty.so -- Looking for OGRE_RTShaderSystem... -- Found OGRE_RTShaderSystem: optimized;/usr/lib/x86_64-linux-gnu/libOgreRTShaderSystem.so;debug;/usr/lib/x86_64-linux-gnu/libOgreRTShaderSystem.so -- Looking for OGRE_Volume... -- Found OGRE_Volume: optimized;/usr/lib/x86_64-linux-gnu/libOgreVolume.so;debug;/usr/lib/x86_64-linux-gnu/libOgreVolume.so -- Looking for OGRE_Overlay... -- Found OGRE_Overlay: optimized;/usr/lib/x86_64-linux-gnu/libOgreOverlay.so;debug;/usr/lib/x86_64-linux-gnu/libOgreOverlay.so -- Found Protobuf: /usr/local/lib/libprotobuf.a (Required is at least version "2.3.0") -- Config-file not installed for ZeroMQ -- checking for pkg-config -- Checking for module 'libzmq >= 4' -- Found libzmq , version 4.1.4 -- Checking for module 'uuid' -- Found uuid, version 2.27.0 -- Checking for module 'tinyxml2' -- Found tinyxml2, version 2.2.0 -- Looking for dlfcn.h - found -- Looking for libdl - found -- FreeImage.pc not found, we will search for FreeImage_INCLUDE_DIRS and FreeImage_LIBRARIES -- Checking for module 'gts' -- Found gts, version 0.7.6 -- Checking for module 'libswscale' -- Found libswscale, version 3.1.101 -- Checking for module 'libavdevice >= 56.4.100' -- Found libavdevice , version 56.4.100 -- Checking for module 'libavformat' -- Found libavformat, version 56.40.101 -- Checking for module 'libavcodec' -- Found libavcodec, version 56.60.100 -- Checking for module 'libavutil' -- Found libavutil, version 54.31.100 -- Checking for module 'jsoncpp' -- Found jsoncpp, version 1.7.2 -- Checking for module 'yaml-0.1' -- Found yaml-0.1, version 0.1.6 -- Checking for module 'libzip' -- Found libzip, version 1.0.1 -- Building klt_feature_tracker without catkin -- Building OpticalFlow with OpenCV -- catkin DISABLED -- Found Protobuf: /usr/local/lib/libprotobuf.a Gazebo version: 9.6 -- Using C++14 compiler -- Configuring done -- Generating done -- Build files have been written to: /home/csgurel/src/Firmware/build/px4_sitl_default/build_gazebo [3/6] Performing build step for 'sitl_gazebo' FAILED: cd /home/csgurel/src/Firmware/build/px4_sitl_default/build_gazebo && /usr/bin/cmake --build . && /usr/bin/cmake -E touch /home/csgurel/src/Firmware/build/px4_sitl_default/external/Stamp/sitl_gazebo/sitl_gazebo-build [1/50] Building CXX object CMakeFiles/sensor_msgs.dir/Imu.pb.cc.o [2/50] Linking CXX shared library libmav_msgs.so [3/50] Linking CXX shared library libstd_msgs.so [4/50] Building CXX object CMakeFiles/sensor_msgs.dir/Range.pb.cc.o [5/50] Building CXX object CMakeFiles/sensor_msgs.dir/SITLGps.pb.cc.o [6/50] Building CXX object CMakeFiles/sensor_msgs.dir/OpticalFlow.pb.cc.o [7/50] Building CXX object CMakeFiles/nav_msgs.dir/Odometry.pb.cc.o [8/50] Linking CXX static library OpticalFlow/klt_feature_tracker/libklt_feature_tracker.a [9/50] Building CXX object CMakeFiles/physics_msgs.dir/Wind.pb.cc.o [10/50] Building CXX object OpticalFlow/CMakeFiles/OpticalFlow.dir/src/optical_flow.cpp.o [11/50] Building CXX object OpticalFlow/CMakeFiles/OpticalFlow.dir/src/px4flow.cpp.o [12/50] Building CXX object OpticalFlow/CMakeFiles/OpticalFlow.dir/src/flow_px4.cpp.o [13/50] Building CXX object OpticalFlow/CMakeFiles/OpticalFlow.dir/src/flow_opencv.cpp.o FAILED: /usr/bin/c++ -DLIBBULLET_VERSION=2.83 -DLIBBULLET_VERSION_GT_282 -Dphysics_msgs_EXPORTS -isystem /usr/include/gazebo-9 -isystem /usr/include/bullet -isystem /usr/include/simbody -isystem /usr/local/include -isystem /usr/include/sdformat-6.2 -isystem /usr/include/ignition/math4 -isystem /usr/include/OGRE -isystem /usr/include/OGRE/Terrain -isystem /usr/include/OGRE/Paging -isystem /usr/include/ignition/transport4 -isystem /usr/include/ignition/msgs1 -isystem /usr/include/ignition/common1 -isystem /usr/include/ignition/fuel_tools1 -I/home/csgurel/src/Firmware/Tools/sitl_gazebo/include -I. -I/usr/include/eigen3 -I/usr/include/eigen3/eigen3 -I/usr/include/gazebo-9/gazebo/msgs -I/home/csgurel/src/Firmware/mavlink/include -I/usr/include/Paging -isystem /opt/ros/kinetic/include/opencv-3.3.1-dev -isystem /opt/ros/kinetic/include/opencv-3.3.1-dev/opencv -I/home/csgurel/src/Firmware/Tools/sitl_gazebo/external/OpticalFlow/include -isystem /usr/include/uuid -isystem /usr/include/x86_64-linux-gnu -Wno-deprecated-declarations -fPIC -I/usr/include/uuid -I/usr/include/x86_64-linux-gnu -std=gnu++14 -MMD -MT CMakeFiles/physics_msgs.dir/Wind.pb.cc.o -MF CMakeFiles/physics_msgs.dir/Wind.pb.cc.o.d -o CMakeFiles/physics_msgs.dir/Wind.pb.cc.o -c Wind.pb.cc In file included from Wind.pb.h:32:0, from Wind.pb.cc:5: /usr/include/gazebo-9/gazebo/msgs/vector3d.pb.h:17:2: error: #error This file was generated by an older version of protoc which is #error This file was generated by an older version of protoc which is ^ /usr/include/gazebo-9/gazebo/msgs/vector3d.pb.h:18:2: error: #error incompatible with your Protocol Buffer headers. Please #error incompatible with your Protocol Buffer headers. Please ^ /usr/include/gazebo-9/gazebo/msgs/vector3d.pb.h:19:2: error: #error regenerate this file with a newer version of protoc. #error regenerate this file with a newer version of protoc. ^ In file included from Wind.pb.cc:5:0: Wind.pb.h: In member function ‘const gazebo::msgs::Vector3d& physics_msgs::msgs::Wind::force() const’: Wind.pb.h:318:8: error: ‘_Vector3d_default_instance_’ is not a member of ‘gazebo::msgs’ &::gazebo::msgs::_Vector3d_default_instance_); ^ Wind.pb.cc: In static member function ‘static void physics_msgs::msgs::protobuf_Wind_2eproto::TableStruct::InitDefaultsImpl()’: Wind.pb.cc:98:19: error: ‘gazebo::msgs::protobuf_vector3d_2eproto’ has not been declared ::gazebo::msgs::protobuf_vector3d_2eproto::InitDefaults(); ^ Wind.pb.cc:102:7: error: ‘internal_default_instance’ is not a member of ‘gazebo::msgs::Vector3d’ ::gazebo::msgs::Vector3d::internal_default_instance()); ^ Wind.pb.cc: In function ‘void physics_msgs::msgs::protobuf_Wind_2eproto::{anonymous}::AddDescriptorsImpl()’: Wind.pb.cc:122:19: error: ‘gazebo::msgs::protobuf_vector3d_2eproto’ has not been declared ::gazebo::msgs::protobuf_vector3d_2eproto::AddDescriptors(); ^ FAILED: /usr/bin/c++ -DLIBBULLET_VERSION=2.83 -DLIBBULLET_VERSION_GT_282 -Dsensor_msgs_EXPORTS -isystem /usr/include/gazebo-9 -isystem /usr/include/bullet -isystem /usr/include/simbody -isystem /usr/local/include -isystem /usr/include/sdformat-6.2 -isystem /usr/include/ignition/math4 -isystem /usr/include/OGRE -isystem /usr/include/OGRE/Terrain -isystem /usr/include/OGRE/Paging -isystem /usr/include/ignition/transport4 -isystem /usr/include/ignition/msgs1 -isystem /usr/include/ignition/common1 -isystem /usr/include/ignition/fuel_tools1 -I/home/csgurel/src/Firmware/Tools/sitl_gazebo/include -I. -I/usr/include/eigen3 -I/usr/include/eigen3/eigen3 -I/usr/include/gazebo-9/gazebo/msgs -I/home/csgurel/src/Firmware/mavlink/include -I/usr/include/Paging -isystem /opt/ros/kinetic/include/opencv-3.3.1-dev -isystem /opt/ros/kinetic/include/opencv-3.3.1-dev/opencv -I/home/csgurel/src/Firmware/Tools/sitl_gazebo/external/OpticalFlow/include -isystem /usr/include/uuid -isystem /usr/include/x86_64-linux-gnu -Wno-deprecated-declarations -fPIC -I/usr/include/uuid -I/usr/include/x86_64-linux-gnu -std=gnu++14 -MMD -MT CMakeFiles/sensor_msgs.dir/Imu.pb.cc.o -MF CMakeFiles/sensor_msgs.dir/Imu.pb.cc.o.d -o CMakeFiles/sensor_msgs.dir/Imu.pb.cc.o -c Imu.pb.cc In file included from Imu.pb.h:32:0, from Imu.pb.cc:5: /usr/include/gazebo-9/gazebo/msgs/quaternion.pb.h:17:2: error: #error This file was generated by an older version of protoc which is #error This file was generated by an older version of protoc which is ^ /usr/include/gazebo-9/gazebo/msgs/quaternion.pb.h:18:2: error: #error incompatible with your Protocol Buffer headers. Please #error incompatible with your Protocol Buffer headers. Please ^ /usr/include/gazebo-9/gazebo/msgs/quaternion.pb.h:19:2: error: #error regenerate this file with a newer version of protoc. #error regenerate this file with a newer version of protoc. ^ In file included from Imu.pb.h:33:0, from Imu.pb.cc:5: /usr/include/gazebo-9/gazebo/msgs/vector3d.pb.h:17:2: error: #error This file was generated by an older version of protoc which is #error This file was generated by an older version of protoc which is ^ /usr/include/gazebo-9/gazebo/msgs/vector3d.pb.h:18:2: error: #error incompatible with your Protocol Buffer headers. Please #error incompatible with your Protocol Buffer headers. Please ^ /usr/include/gazebo-9/gazebo/msgs/vector3d.pb.h:19:2: error: #error regenerate this file with a newer version of protoc. #error regenerate this file with a newer version of protoc. ^ In file included from Imu.pb.cc:5:0: Imu.pb.h: In member function ‘const gazebo::msgs::Quaternion& sensor_msgs::msgs::Imu::orientation() const’: Imu.pb.h:290:8: error: ‘_Quaternion_default_instance_’ is not a member of ‘gazebo::msgs’ &::gazebo::msgs::_Quaternion_default_instance_); ^ Imu.pb.h: In member function ‘const gazebo::msgs::Vector3d& sensor_msgs::msgs::Imu::angular_velocity() const’: Imu.pb.h:366:8: error: ‘_Vector3d_default_instance_’ is not a member of ‘gazebo::msgs’ &::gazebo::msgs::_Vector3d_default_instance_); ^ Imu.pb.h: In member function ‘const gazebo::msgs::Vector3d& sensor_msgs::msgs::Imu::linear_acceleration() const’: Imu.pb.h:442:8: error: ‘_Vector3d_default_instance_’ is not a member of ‘gazebo::msgs’ &::gazebo::msgs::_Vector3d_default_instance_); ^ Imu.pb.cc: In static member function ‘static void sensor_msgs::msgs::protobuf_Imu_2eproto::TableStruct::InitDefaultsImpl()’: Imu.pb.cc:108:19: error: ‘gazebo::msgs::protobuf_quaternion_2eproto’ has not been declared ::gazebo::msgs::protobuf_quaternion_2eproto::InitDefaults(); ^ Imu.pb.cc:109:19: error: ‘gazebo::msgs::protobuf_vector3d_2eproto’ has not been declared ::gazebo::msgs::protobuf_vector3d_2eproto::InitDefaults(); ^ Imu.pb.cc:113:7: error: ‘internal_default_instance’ is not a member of ‘gazebo::msgs::Quaternion’ ::gazebo::msgs::Quaternion::internal_default_instance()); ^ Imu.pb.cc:115:7: error: ‘internal_default_instance’ is not a member of ‘gazebo::msgs::Vector3d’ ::gazebo::msgs::Vector3d::internal_default_instance()); ^ Imu.pb.cc:117:7: error: ‘internal_default_instance’ is not a member of ‘gazebo::msgs::Vector3d’ ::gazebo::msgs::Vector3d::internal_default_instance()); ^ Imu.pb.cc: In function ‘void sensor_msgs::msgs::protobuf_Imu_2eproto::{anonymous}::AddDescriptorsImpl()’: Imu.pb.cc:143:19: error: ‘gazebo::msgs::protobuf_quaternion_2eproto’ has not been declared ::gazebo::msgs::protobuf_quaternion_2eproto::AddDescriptors(); ^ Imu.pb.cc:144:19: error: ‘gazebo::msgs::protobuf_vector3d_2eproto’ has not been declared ::gazebo::msgs::protobuf_vector3d_2eproto::AddDescriptors(); ^ FAILED: /usr/bin/c++ -DLIBBULLET_VERSION=2.83 -DLIBBULLET_VERSION_GT_282 -Dnav_msgs_EXPORTS -isystem /usr/include/gazebo-9 -isystem /usr/include/bullet -isystem /usr/include/simbody -isystem /usr/local/include -isystem /usr/include/sdformat-6.2 -isystem /usr/include/ignition/math4 -isystem /usr/include/OGRE -isystem /usr/include/OGRE/Terrain -isystem /usr/include/OGRE/Paging -isystem /usr/include/ignition/transport4 -isystem /usr/include/ignition/msgs1 -isystem /usr/include/ignition/common1 -isystem /usr/include/ignition/fuel_tools1 -I/home/csgurel/src/Firmware/Tools/sitl_gazebo/include -I. -I/usr/include/eigen3 -I/usr/include/eigen3/eigen3 -I/usr/include/gazebo-9/gazebo/msgs -I/home/csgurel/src/Firmware/mavlink/include -I/usr/include/Paging -isystem /opt/ros/kinetic/include/opencv-3.3.1-dev -isystem /opt/ros/kinetic/include/opencv-3.3.1-dev/opencv -I/home/csgurel/src/Firmware/Tools/sitl_gazebo/external/OpticalFlow/include -isystem /usr/include/uuid -isystem /usr/include/x86_64-linux-gnu -Wno-deprecated-declarations -fPIC -I/usr/include/uuid -I/usr/include/x86_64-linux-gnu -std=gnu++14 -MMD -MT CMakeFiles/nav_msgs.dir/Odometry.pb.cc.o -MF CMakeFiles/nav_msgs.dir/Odometry.pb.cc.o.d -o CMakeFiles/nav_msgs.dir/Odometry.pb.cc.o -c Odometry.pb.cc In file included from Odometry.pb.h:32:0, from Odometry.pb.cc:5: /usr/include/gazebo-9/gazebo/msgs/quaternion.pb.h:17:2: error: #error This file was generated by an older version of protoc which is #error This file was generated by an older version of protoc which is ^ /usr/include/gazebo-9/gazebo/msgs/quaternion.pb.h:18:2: error: #error incompatible with your Protocol Buffer headers. Please #error incompatible with your Protocol Buffer headers. Please ^ /usr/include/gazebo-9/gazebo/msgs/quaternion.pb.h:19:2: error: #error regenerate this file with a newer version of protoc. #error regenerate this file with a newer version of protoc. ^ In file included from Odometry.pb.h:33:0, from Odometry.pb.cc:5: /usr/include/gazebo-9/gazebo/msgs/vector3d.pb.h:17:2: error: #error This file was generated by an older version of protoc which is #error This file was generated by an older version of protoc which is ^ /usr/include/gazebo-9/gazebo/msgs/vector3d.pb.h:18:2: error: #error incompatible with your Protocol Buffer headers. Please #error incompatible with your Protocol Buffer headers. Please ^ /usr/include/gazebo-9/gazebo/msgs/vector3d.pb.h:19:2: error: #error regenerate this file with a newer version of protoc. #error regenerate this file with a newer version of protoc. ^ In file included from Odometry.pb.cc:5:0: Odometry.pb.h: In member function ‘const gazebo::msgs::Vector3d& nav_msgs::msgs::Odometry::position() const’: Odometry.pb.h:302:8: error: ‘_Vector3d_default_instance_’ is not a member of ‘gazebo::msgs’ &::gazebo::msgs::_Vector3d_default_instance_); ^ Odometry.pb.h: In member function ‘const gazebo::msgs::Quaternion& nav_msgs::msgs::Odometry::orientation() const’: Odometry.pb.h:348:8: error: ‘_Quaternion_default_instance_’ is not a member of ‘gazebo::msgs’ &::gazebo::msgs::_Quaternion_default_instance_); ^ Odometry.pb.h: In member function ‘const gazebo::msgs::Vector3d& nav_msgs::msgs::Odometry::linear_velocity() const’: Odometry.pb.h:394:8: error: ‘_Vector3d_default_instance_’ is not a member of ‘gazebo::msgs’ &::gazebo::msgs::_Vector3d_default_instance_); ^ Odometry.pb.h: In member function ‘const gazebo::msgs::Vector3d& nav_msgs::msgs::Odometry::angular_velocity() const’: Odometry.pb.h:440:8: error: ‘_Vector3d_default_instance_’ is not a member of ‘gazebo::msgs’ &::gazebo::msgs::_Vector3d_default_instance_); ^ Odometry.pb.cc: In static member function ‘static void nav_msgs::msgs::protobuf_Odometry_2eproto::TableStruct::InitDefaultsImpl()’: Odometry.pb.cc:106:19: error: ‘gazebo::msgs::protobuf_quaternion_2eproto’ has not been declared ::gazebo::msgs::protobuf_quaternion_2eproto::InitDefaults(); ^ Odometry.pb.cc:107:19: error: ‘gazebo::msgs::protobuf_vector3d_2eproto’ has not been declared ::gazebo::msgs::protobuf_vector3d_2eproto::InitDefaults(); ^ Odometry.pb.cc:111:7: error: ‘internal_default_instance’ is not a member of ‘gazebo::msgs::Vector3d’ ::gazebo::msgs::Vector3d::internal_default_instance()); ^ Odometry.pb.cc:113:7: error: ‘internal_default_instance’ is not a member of ‘gazebo::msgs::Quaternion’ ::gazebo::msgs::Quaternion::internal_default_instance()); ^ Odometry.pb.cc:115:7: error: ‘internal_default_instance’ is not a member of ‘gazebo::msgs::Vector3d’ ::gazebo::msgs::Vector3d::internal_default_instance()); ^ Odometry.pb.cc:117:7: error: ‘internal_default_instance’ is not a member of ‘gazebo::msgs::Vector3d’ ::gazebo::msgs::Vector3d::internal_default_instance()); ^ Odometry.pb.cc: In function ‘void nav_msgs::msgs::protobuf_Odometry_2eproto::{anonymous}::AddDescriptorsImpl()’: Odometry.pb.cc:142:19: error: ‘gazebo::msgs::protobuf_quaternion_2eproto’ has not been declared ::gazebo::msgs::protobuf_quaternion_2eproto::AddDescriptors(); ^ Odometry.pb.cc:143:19: error: ‘gazebo::msgs::protobuf_vector3d_2eproto’ has not been declared ::gazebo::msgs::protobuf_vector3d_2eproto::AddDescriptors(); ^ ninja: build stopped: subcommand failed. ninja: build stopped: subcommand failed. Makefile:197: recipe for target 'px4_sitl' failed make: *** [px4_sitl] Error 1

Hello, I have interested in mobile robot, and I have done some projects. But, suddenly, the lidar sendor data comes to wrong in GAZEBO simulator. And I visualized the lidar sensor in GAZEBO, I get a terrible result like below figure.. Who is know about such error? Sorry, why my figure isn't upload(>5 points required to upload files)? I refered to https://www.evernote.com/l/AqNFd1OV2k5E0bkgAyj6UbFtiKOubpMvjcU

New to ros, gazebo, ubuntu. Edited the launch file but gazebo always launches with the initial world that was downloaded.

I've installed Ubuntu 18.04 on a Virtual Machine (using VirtualBox). There I installed ROS Melodic (and Gazebo 9.0.0). I need now to perform a simulation of a simple robot in a simple world using an ad-hoc controller. However, I've noticed that, in general, my Ubuntu 18.04 VM is quite slow. I've also noticed that the FPS values of Gazebo are around 1-4, which I suppose it's quite low. In fact, my simulation is quite laggy and slow. What exactly do these FPS represent? And what are "workable" FPS values for Gazebo?

I'm testing out a two wheeled robot I designed and put in gazebo. I also have a static back wheel with very little friction that is only there for structural support. When I give linear x commands the bot drives forward and backward, however any angular z commands are completely ignored and the robot does nothing. My files are as follows: rover_control.yaml: rover: # Publish all joint states ----------------------------------- joint_state_controller: type: joint_state_controller/JointStateController publish_rate: 50 mobile_base_controller: type: "diff_drive_controller/DiffDriveController" left_wheel: 'motor_wheel_left' right_wheel: 'motor_wheel_right' publish_rate: 50.0 pose_covariance_diagonal : [0.001, .001, 1000000., 1000000., 1000000., 1000.] twist_covariance_diagonal: [0.001, .001, 1000000., 1000000., 1000000., 1000.] wheel_radius : 0.0508 rover_control.launch rover_description.urdf 500.0500.011Gazebo/Black500.0500.011Gazebo/Black505011Gazebo/Blacktrue50.0/rovertransmission_interface/SimpleTransmissionhardware_interface/VelocityJointInterfaceVelocityJointInterface7transmission_interface/SimpleTransmissionhardware_interface/VelocityJointInterfaceVelocityJointInterface7

Hi I want play "thormang" sim in gazebo. I finished to set up below tutorial and run Gazebo simulation. https://github.com/thor-mang/thor_mang_install I can run the sim ,but connot receive Gazboo clock and topic information. $ rostopic echo /clock WARNING: no messages received and simulated time is active. Is /clock being published? So, What am I wrong? I use kinetic in 16.04LTS. thanks. 

am using ubantu 16.04 on windows subsystem for Linux and Ros melodic ,i have tried to open empty world ,also other packages rviz is working fine but in gazebo show black screen when i launch . did any know why and how to fix this problem. i have check similar problem but i don't get clear solutions

Hello all, I am trying for some time now to control (open/close) the two fingered robotiq_85_gripper, as it is described in (https://github.com/DualUR5Husky/robotiq/tree/indigo-devel/robotiq_c2_model_visualization) but augmented with the transmissions and inertial described in (https://github.com/waypointrobotics/robotiq_85_gripper/tree/master/robotiq_85_description/urdf). The problem is that I am not sure how to transmit open - close commands in a Gazebo 7 environment. Do I need an extra plugin to transmit commands to the controllers? I found the following package: (https://github.com/DualUR5Husky/robotiq/tree/indigo-devel/robotiq_c_model_control), but it doesn't seam to do anything. Please let me have your ideas. Thank you.

Hi, I followed this link and able to spawn the sdf model in gazebo. https://github.com/ros-simulation/gazebo_ros_pkgs/wiki/ROS-2-Migration:-Spawn-and-delete But instead of sending sdf model code from command line, can we send just sdf/urdf file ? I tried that but it failed. When i send complete sdf modem from cmnd lien with spawn_entity, it launched in gazebo. I am trying it on crystal. Please let me know if anybody is having any clue. Thanks.

I followed the instructions from http://wiki.ros.org/hector_quadrotor/Tutorials/Quadrotor%20outdoor%20flight%20demo. I wanted to implement a slam navigation scenario. But I don't know how to do this. I can only control the copter manually using the keyboard. Could anyone tell me how to implement the slam navigation scenario shown in the video? Thank you!

So, I have a a robot named Kuka Youbot in Gazebo and with some plugins it works well in ROS Kinetic, I can publish with rostopic pub and the robot executes now I tried to use export ROS_IP and export ROS_MASTER_URI and I can connect to this master from a second PC that are connected in the same network so I export this ROS_IP too, this second PC has also ROS Kinetic, I can try a rostopic list and I see the same things that I have in my Principal PC, now the problem is that from my second PC I can publish but the robot doesn't execute the commands, when I publish from my second PC I can see that the publish is ok because I can check the state in my principal PC through a rostopic info in the node.

Hello, I am trying to build my own robot to make work in gazebo. The model is a .urdf file in which I put a few .xacro files with tag and the model works, I think, quite well. The model can be shown in rviz, but it failed in Gazebo. In the launch file, I use the following line to load the model Error: No link elements found in urdf file at line 180 in /build/buildd/urdfdom-0.2.10+dfsg/urdf_parser/src/model.cpp Error [parser_urdf.cc:2608] Unable to call parseURDF on robot model Error [parser.cc:299] parse as old deprecated model file failed. Error [World.cc:1527] Unable to read sdf string[]

Anytime I run Rviz and use Motionplanning the robot is not shown the way it should be... Right now I am trying to follow this tutorial: https://www.youtube.com/watch?v=j6bBxfD_bYs and as soon as I run the created launch file rviz pops up and shows me a strange representation of my ur5. It looks like every single link is connected to the base link. I had the same issue when I tried the moveit Panda Tutorial. If I only add the robot model it looks fine, but as soon as I add the MotionPlanning it gets weird. Execution from there almost never works... I would upload a Screenshot, but unfortunately I am not yet allowed to upload files :( 2 erros I see in the bash (dunno if they are responsible for the behaviour): [ERROR] [1553171470.019237215, 407.916000000]: Could not find the planner configuration 'None' on the param server [ WARN] [1553171477.355538521, 413.008000000]: Waiting for arm_contoller/follow_joint_trajectory to come up [ INFO] [1553171481.580805297, 416.272000000]: Failed to call service get_planning_scene, have you launched move_group? at /tmp/binarydeb/ros-melodic-moveit-ros-planning-0.10.8/planning_scene_monitor/src/planning_scene_monitor.cpp:495 [ INFO] [1553171482.618004378, 416.826000000]: Constructing new MoveGroup connection for group 'manipulator' in namespace '' [ WARN] [1553171487.914143567, 419.010000000]: Waiting for arm_contoller/follow_joint_trajectory to come up [ERROR] [1553171496.372846748, 425.010000000]: Action client not connected: arm_contoller/follow_joint_trajectory I would be glad if you can explain in the easiest way, since I am new to everything (linux, Ros, C++). Thanks, Joel

when I try to launch gazebo_ros empty_world.launch, the code is here: I always get the error, i want to how to solve, thanks. [gazebo-1] process has died [pid 18905, exit code 255, cmd /opt/ros/kinetic/lib/gazebo_ros/gzserver -e ode worlds/empty.world __name:=gazebo __ log:=/home/robot/.ros/log/7719b5f8-4c52-11e9-a3d6-8cec4b9a7b95/gazebo-1.log]. log file: /home/robot/.ros/log/7719b5f8-4c52-11e9-a3d6-8cec4b9a7b95/gazebo-1*.log

Hi there, i want to create a simulation for a mobile robot (lunar rover) in a specific environment with consideration of dust and rocks and so on. The main focus will be on navigation with LIDAR and/or stereo vision and the handling characteristics in the lunar testbed. The simulation should be as most real as possible. Should i use Gazebo, V-REP or an other simulator to do this? Is there any paper with a comparison of the use of simulators for mobile platforms? Best regards Max

What is the simplest way to publish to a ROS topic whenever a a gazebo collider is in contact with something? I added a contact sensor to the collider in the model description. It publishes to a gazebo topic. How can I forward from gazebo to ROS?

Before this gets marked as a duplicate of http://answers.gazebosim.org/question/4153/gazebo-crashes-immediately-using-roslaunch-after-installing-gazebo-ros-packages/, I tried everything in that question and the comments only allow me to post so much text. I am just trying to make a map and navigate it in the Gazebo. I am running Ubuntu 15.10 and ROS Kinetic. I run these in separate terminal windows: roslaunch turtlebot_gazebo turtlebot_world.launch roslaunch turtlebot_gazebo gmapping_demo.launch roslaunch turtlebot_rviz_launchers view_navigation.launch roslaunch kobuki_keyop keyop.launch But I my kobuki_keyop does not work, giving me: [ WARN] [1550005269.894992827]: KeyOp: could not connect, trying again after 500ms... [ERROR] [1550005270.400225747]: KeyOp: could not connect. [ERROR] [1550005270.400604286]: KeyOp: check remappings for enable/disable topics). I then check the roslaunch turtlebot_gazebo turtlebot_world.launch terminal window, and see the following error: [gazebo-1] process has died [pid 5190, exit code 134, cmd /opt/ros/kinetic/lib/gazebo_ros/gzserver -e ode /opt/ros/kinetic/share/turtlebot_gazebo/worlds/playground.world __name:=gazebo __log:=/home/tony15/.ros/log/534c6c66-2ef1-11e9-854a-080027d85737/gazebo-1.log]. log file: /home/tony15/.ros/log/534c6c66-2ef1-11e9-854a-080027d85737/gazebo-1*.log Upon further inspection, it seems that if I roslaunch turtlebot_gazebo turtlebot_world.launch, then as soon as I roslaunch turtlebot_gazebo gmapping_demo.launch, the turtlebot_world.launch receives the previous error (which then explains why the kobuki_keyop doesn't work). turtlebot_world.launch works completely fine on it's own. turtlebot_world.launch and kobuki_keyop work fine when both running. Does anyone know why my turtlebot_world.launch and gmapping_demo.launch / turtlebot_rviz_launchers can't seem to run at the same time?

Hello All, I am using Husky in Gazebo simulation on ROS Kinetic. And trying to move the it by giving Goals on move_base_action. For around of 10 goals, it moves fine, but after that it cease to move and is in hanging position. I had a look on the `move_base/feedback`, and it continuously gives same feedback, and `move_base/result` stops to publish. Can someone give some clue why it stops moving and how to solve this issue. Regards, Saurabh

It appears that `rclcpp::Rate` uses `std::chrono::system_clock`, which of course doesn't use ROS time, so it doesn't honor `use_sim_time`. Any plans to add a version of `Rate` that uses ROS time?

Hello everyone, I am trying to implement the following simulation. I have been working my way into Ros, Linux and C++ the last few weeks, and want to get going, but still have some difficulties of how to best implement what I want. The szenario is this: I get the pose and orientation of a small object which is detected by an AI (I do not code this part myself). Once I have received this information I want my UR5 to get the object pick it and place it (it will be sticked onto another object). So far I got my UR5 running (used moveit) so I can plan and execute things in Rviz and they will be also executed in Gazebo. I think I need a Gazebo simulation. I still don't quite get the difference between Rviz and Gazebo, but as far as I understood, Gazebo is the proper environment for simulation since it respects e.g. physical restrictions, whereas Rviz doesn't... So right now I can only move the UR5 by using plan and execute in Rviz and then the robot also moves in Gazebo. Do I actually need the Rviz window open or is there a way how I can just do things in gazebo only? I also tried to load my stl object which I want to pick and place into the scene, which worked fine in Rviz by importing file in the motionplanning section, but it didn't appear in the gazebo simulation. Seeing this makes me think even more: I don't really understand the relation between my Rviz and Gazebo simulators, obviously the robot movements are copied, but the environment isn't... I guess I stop writing here and hope you could get a rough idea of what I am trying to do and would appreciate any help on this! Thank You! Best regards Joel