/ardrone/takeoff topic is missing
Hi, I'm new to ROS and I'm trying to simulate the an AR Parrot drone inside gazebo through tum_simulator. I have ROS kinetic, ardrone_autonomy and tum_simulator installed. The problem is that when I create the ardrone test world it is correctly visualized in gazebo but than I can't control the motion of the drone by the command line. For instance, when I type rostopic pub -1 /ardrone/takeoff std_msgs/Empty, the drone doesn't move. Only sensor monitoring commands are working. The list of my active topics is the following:
/ardrone/bottom/camera_info
/ardrone/bottom/image_raw
/ardrone/bottom/image_raw/compressed
/ardrone/bottom/image_raw/compressed/parameter_descriptions
/ardrone/bottom/image_raw/compressed/parameter_updates
/ardrone/bottom/image_raw/compressedDepth
/ardrone/bottom/image_raw/compressedDepth/parameter_descriptions
/ardrone/bottom/image_raw/compressedDepth/parameter_updates
/ardrone/bottom/image_raw/theora
/ardrone/bottom/image_raw/theora/parameter_descriptions
/ardrone/bottom/image_raw/theora/parameter_updates
/ardrone/bottom/parameter_descriptions
/ardrone/bottom/parameter_updates
/ardrone/front/camera_info
/ardrone/front/image_raw
/ardrone/front/image_raw/compressed
/ardrone/front/image_raw/compressed/parameter_descriptions
/ardrone/front/image_raw/compressed/parameter_updates
/ardrone/front/image_raw/theora
/ardrone/front/image_raw/theora/parameter_descriptions
/ardrone/front/image_raw/theora/parameter_updates
/ardrone/front/parameter_descriptions
/ardrone/front/parameter_updates
/clock
/gazebo/link_states
/gazebo/model_states
/gazebo/parameter_descriptions
/gazebo/parameter_updates
/gazebo/set_link_state
/gazebo/set_model_state
/ground_truth/state
/joint_states
/rosout
/rosout_agg
/tf
/tf_static
The topic /ardrone/takeoff
is not active in that moment but it's existing. Is there anyone who had the same problem?
Edit:
shubham16@shubham16-VirtualBox:~/catkin_ws$ source /opt/ros/kinetic/setup.bash
following is the output of roslaunch ardrone_autonomy ardrone.launch
shubham16@shubham16-VirtualBox:~/catkin_ws$ source devel/setup.bash
shubham16@shubham16-VirtualBox:~/catkin_ws$ roslaunch ardrone_autonomy ardrone.launch
... logging to /home/shubham16/.ros/log/4ee38c18-2db2-11e8-b270-080027a254e1/roslaunch-shubham16-VirtualBox-2077.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://shubham16-VirtualBox:43441/
SUMMARY
========
CLEAR PARAMETERS
* /ardrone_driver/
PARAMETERS
* /ardrone_driver/altitude_max: 4000
* /ardrone_driver/altitude_min: 50
* /ardrone_driver/bitrate: 4000
* /ardrone_driver/control_vz_max: 700
* /ardrone_driver/control_yaw: 1.75
* /ardrone_driver/cov/imu_av: [1.0, 0.0, 0.0, 0...
* /ardrone_driver/cov/imu_la: [0.1, 0.0, 0.0, 0...
* /ardrone_driver/cov/imu_or: [1.0, 0.0, 0.0, 0...
* /ardrone_driver/detect_type: 10
* /ardrone_driver/detections_select_h: 32
* /ardrone_driver/detections_select_v_hsync: 128
* /ardrone_driver/enemy_colors: 3
* /ardrone_driver/enemy_without_shell: 0
* /ardrone_driver/euler_angle_max: 0.21
* /ardrone_driver/flight_without_shell: 0
* /ardrone_driver/max_bitrate: 4000
* /ardrone_driver/navdata_demo: 0
* /ardrone_driver/outdoor: 0
* /ardrone_driver/realtime_navdata: True
* /ardrone_driver/realtime_video: True
* /ardrone_driver/ultrasound_freq: 8
* /rosdistro: kinetic
* /rosversion: 1.12.12
NODES
/
ardrone_driver (ardrone_autonomy/ardrone_driver)
auto-starting new master
process[master]: started with pid [2088]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to 4ee38c18-2db2-11e8-b270-080027a254e1
process[rosout-1]: started with pid [2101]
started core service [/rosout]
process[ardrone_driver-2]: started with pid [2105]
Using custom ip address 192.168.1.1
===================+> 192.168.1.1
Getting AR.Drone version ...
Getting AR.Drone version ...
Getting AR.Drone version ...
Are you able to connect to the drone? I've seen
repeated like you've shown when I wasn't connected to the drone.
I just noticed that you're using
tum_simulator
, you're getting the message from my previous comment because you should use that package's launch files notardrone_autonomy
launch files directly. Otherwise, it tries to connect to a drone that you aren't using.