2021-07-07 06:14:49 -0500 | received badge | ● Famous Question
(source)
|
2021-07-07 06:14:49 -0500 | received badge | ● Notable Question
(source)
|
2019-07-03 16:58:35 -0500 | received badge | ● Famous Question
(source)
|
2019-07-01 09:14:55 -0500 | received badge | ● Famous Question
(source)
|
2019-07-01 09:14:53 -0500 | received badge | ● Famous Question
(source)
|
2019-07-01 09:14:53 -0500 | received badge | ● Notable Question
(source)
|
2019-07-01 09:14:53 -0500 | received badge | ● Popular Question
(source)
|
2018-06-16 10:24:28 -0500 | received badge | ● Popular Question
(source)
|
2018-02-28 20:39:23 -0500 | received badge | ● Famous Question
(source)
|
2018-01-31 06:36:37 -0500 | received badge | ● Notable Question
(source)
|
2017-12-22 15:37:19 -0500 | received badge | ● Famous Question
(source)
|
2017-12-22 15:37:19 -0500 | received badge | ● Notable Question
(source)
|
2017-12-20 07:50:50 -0500 | received badge | ● Famous Question
(source)
|
2017-11-20 06:50:06 -0500 | received badge | ● Notable Question
(source)
|
2017-06-18 11:38:54 -0500 | received badge | ● Notable Question
(source)
|
2017-05-27 21:16:40 -0500 | received badge | ● Famous Question
(source)
|
2017-05-02 15:12:56 -0500 | received badge | ● Famous Question
(source)
|
2017-01-08 17:42:57 -0500 | received badge | ● Notable Question
(source)
|
2016-12-08 16:57:32 -0500 | received badge | ● Popular Question
(source)
|
2016-12-07 15:12:27 -0500 | asked a question | Joystick operation for a gazebo ros youbot Hi everyone, I have created a node just like teleop_joy using ros.org. It publishes a topic /joy and the type of message is sensor_msgs/Joy. My youbot has a topic /cmd_vel and the type of message is geometry_msgs/Twist. I want to move the youbot using joystick by subscribing /cmd_vel to /joy but the type of messages are different. How can I do this? Any ideas please |
2016-11-29 02:54:48 -0500 | received badge | ● Popular Question
(source)
|
2016-11-28 15:58:21 -0500 | received badge | ● Popular Question
(source)
|
2016-11-28 08:19:21 -0500 | asked a question | Subcribing to the Odometry Hi, I have a gazebo model which is moved by teleop_keyboard. My model has a node which publishes Odometry values in X and Y and it has nav msgs.. I want to subscribe the turtlesim(topic turtle1/pose) to my model node and make it move in the same coordinates. How can I do this? |
2016-11-27 15:55:17 -0500 | received badge | ● Scholar
(source)
|
2016-11-27 15:54:43 -0500 | commented answer | Hi, how can I subscribe the node(topic cmd_vel) of turtlesim to the node of my model? Hey, Thank you very much for the help. Its working!! |
2016-11-27 13:59:45 -0500 | asked a question | Hi, how can I subscribe the node(topic cmd_vel) of turtlesim to the node of my model? Hi, I have build a model in gazebo ROS which is moving through teleop keyboard. I want to subscribe cmd_vel of turtlesim to my model and move turtlesim along with my model. Do you have any idea how can I subscribe the node of turtlesim to the node of my model? |
2016-11-23 04:05:04 -0500 | received badge | ● Notable Question
(source)
|
2016-11-19 07:16:24 -0500 | received badge | ● Notable Question
(source)
|
2016-11-07 08:58:17 -0500 | commented question | Hi, I Have the odometry readings from a robot, How can I make the other robot to subscribe to this readings and make it to be in same coordinates and same movement?? First robot is commanded by a joystick. And yes I want to match the movements including coordinates. Help me |
2016-11-07 05:05:17 -0500 | asked a question | Hi, I Have the odometry readings from a robot, How can I make the other robot to subscribe to this readings and make it to be in same coordinates and same movement?? Hi, I Have the odometry readings from a robot, How can I make the other robot to subscribe to this readings and make it to be in same coordinates and same movement? |
2016-11-03 08:45:13 -0500 | received badge | ● Popular Question
(source)
|
2016-11-02 17:10:00 -0500 | commented answer | Hi, How can I path plan a robot in ROS+gazebo using indoor GPS and odometry data? I am using infrared beacons to get the coordinates of the robot. It has got a ROS package and able to show the x,y,z coordinates |
2016-11-02 15:17:37 -0500 | received badge | ● Student
(source)
|
2016-11-02 03:39:51 -0500 | asked a question | Hi, How can I path plan a robot in ROS+gazebo using indoor GPS and odometry data? Hi, How can I path plan a robot in ROS+gazebo using indoor GPS and odometry data? |
2016-10-19 04:56:15 -0500 | received badge | ● Editor
(source)
|
2016-10-19 04:55:35 -0500 | asked a question | Hi, I want to move my robot in a certain path. I have published the data from odometry. How can I use this data to move my robot in a certain path? I use gazebo to simulate Hi, I want to move my robot in a certain path. I have published the data from odometry. How can I use this data to move my robot in a certain path? I use gazebo to simulate |
2016-10-19 00:44:31 -0500 | received badge | ● Enthusiast
|
2016-10-12 03:43:20 -0500 | received badge | ● Popular Question
(source)
|
2016-10-11 16:19:42 -0500 | commented question | Gazebo makes pc freeze try to uninstall and install it again |
2016-10-11 16:10:12 -0500 | asked a question | Catkin_make for publisher - Invoking "make -j4 -l4" failed output of compilation: bharadwaj@bharadwaj-HP-Pavilion-g6-Notebook-PC:~/catkin_ws$ catkin_make
Base path: /home/bharadwaj/catkin_ws
Source space: /home/bharadwaj/catkin_ws/src
Build space: /home/bharadwaj/catkin_ws/build
Devel space: /home/bharadwaj/catkin_ws/devel
Install space: /home/bharadwaj/catkin_ws/install
####
#### Running command: "make cmake_check_build_system" in "/home/bharadwaj/catkin_ws/build"
####
-- Using CATKIN_DEVEL_PREFIX: /home/bharadwaj/catkin_ws/devel
-- Using CMAKE_PREFIX_PATH: /home/bharadwaj/catkin_ws/devel;/opt/ros/indigo
-- This workspace overlays: /home/bharadwaj/catkin_ws/devel;/opt/ros/indigo
-- Using PYTHON_EXECUTABLE: /usr/bin/python
-- Using Debian Python package layout
-- Using empy: /usr/bin/empy
-- Using CATKIN_ENABLE_TESTING: ON
-- Call enable_testing()
-- Using CATKIN_TEST_RESULTS_DIR: /home/bharadwaj/catkin_ws/build/test_results
-- Found gtest sources under '/usr/src/gtest': gtests will be built
-- Using Python nosetests: /usr/bin/nosetests-2.7
-- catkin 0.6.18
-- BUILD_SHARED_LIBS is on
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- ~~ traversing 7 packages in topological order:
-- ~~ - gazebo_ros_pkgs (metapackage)
-- ~~ - gazebo_msgs
-- ~~ - beginner_tutorials
-- ~~ - gazebo_ros
-- ~~ - turtlbot
-- ~~ - gazebo_plugins
-- ~~ - gazebo_ros_control
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- +++ processing catkin metapackage: 'gazebo_ros_pkgs'
-- ==> add_subdirectory(gazebo_ros_pkgs/gazebo_ros_pkgs)
-- +++ processing catkin package: 'gazebo_msgs'
-- ==> add_subdirectory(gazebo_ros_pkgs/gazebo_msgs)
-- Using these message generators: gencpp;genlisp;genpy
-- gazebo_msgs: 9 messages, 20 services
-- +++ processing catkin package: 'beginner_tutorials'
-- ==> add_subdirectory(beginner_tutorials)
-- +++ processing catkin package: 'gazebo_ros'
-- ==> add_subdirectory(gazebo_ros_pkgs/gazebo_ros)
-- Using these message generators: gencpp;genlisp;genpy
-- Boost version: 1.54.0
-- Boost version: 1.54.0
-- Found the following Boost libraries:
-- thread
-- +++ processing catkin package: 'turtlbot'
-- ==> add_subdirectory(turtlbot/srv)
-- +++ processing catkin package: 'gazebo_plugins'
-- ==> add_subdirectory(gazebo_ros_pkgs/gazebo_plugins)
-- Using these message generators: gencpp;genlisp;genpy
-- Boost version: 1.54.0
-- Boost version: 1.54.0
-- Found the following Boost libraries:
-- thread
-- +++ processing catkin package: 'gazebo_ros_control'
-- ==> add_subdirectory(gazebo_ros_pkgs/gazebo_ros_control)
-- Boost version: 1.54.0
-- Configuring done
-- Generating done
-- Build files have been written to: /home/bharadwaj/catkin_ws/build
####
#### Running command: "make -j4 -l4" in "/home/bharadwaj/catkin_ws/build"
####
[ 0%] Built target std_msgs_generate_messages_py
[ 0%] Built target geometry_msgs_generate_messages_py
[ 0%] Built target trajectory_msgs_generate_messages_py
[ 0%] Built target sensor_msgs_generate_messages_py
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_WorldState
[ 0%] [ 0%] Built target _gazebo_msgs_generate_messages_check_deps_DeleteModel
Built target _gazebo_msgs_generate_messages_check_deps_ContactsState
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_LinkStates
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_ApplyJointEffort
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_JointRequest
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_SetModelState
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_ModelStates
[ 0%] [ 0%] Built target _gazebo_msgs_generate_messages_check_deps_GetModelState
Built target _gazebo_msgs_generate_messages_check_deps_SetLinkState
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_ContactState
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_SetLinkProperties
[ 0%] [ 0%] Built target _gazebo_msgs_generate_messages_check_deps_SetJointProperties
Built target _gazebo_msgs_generate_messages_check_deps_SetJointTrajectory
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_BodyRequest
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_SpawnModel
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_GetModelProperties
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_ModelState
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_GetJointProperties
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_ODEPhysics
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_GetWorldProperties
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_SetModelConfiguration
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_ApplyBodyWrench
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_SetPhysicsProperties
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_GetLinkState
[ 0%] Built target _gazebo_msgs_generate_messages_check_deps_GetLinkProperties
[ 0%] [ 0%] Built target _gazebo_msgs_generate_messages_check_deps_LinkState
Built target _gazebo_msgs_generate_messages_check_deps_GetPhysicsProperties
[ 0%] Built target std_msgs_generate_messages_cpp
[ 0%] [ 0%] Built target geometry_msgs_generate_messages_cpp
Built target trajectory_msgs_generate_messages_cpp
[ 0%] [ 0%] Built target sensor_msgs_generate_messages_cpp
Built target _gazebo_msgs_generate_messages_check_deps_ODEJointProperties
[ 0%] [ 0%] Built target sensor_msgs_generate_messages_lisp
Built target std_msgs_generate_messages_lisp
[ 0%] Built target trajectory_msgs_generate_messages_lisp
[ 0%] Built target geometry_msgs_generate_messages_lisp
[ 1%] Building CXX object beginner_tutorials/CMakeFiles/talker.dir/src/talker.cpp.o
[ 1%] Built target std_srvs_generate_messages_cpp
[ 1%] Built target roscpp_generate_messages_lisp
/home/bharadwaj/catkin_ws/src/beginner_tutorials/src/talker.cpp:1:6: error: stray ‘#’ in program
27 #include "ros/ros.h"
^
/home/bharadwaj/catkin_ws/src/beginner_tutorials/src/talker.cpp:2:6: error: stray ‘#’ in program
28 #include "std_msgs/String.h"
^
/home/bharadwaj/catkin_ws/src/beginner_tutorials/src/talker ... (more) |