ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

C's profile - activity

2015-06-30 13:39:28 -0500 received badge  Student (source)
2012-10-05 01:59:28 -0500 received badge  Famous Question (source)
2012-10-05 01:59:28 -0500 received badge  Notable Question (source)
2012-08-17 05:37:53 -0500 received badge  Famous Question (source)
2012-06-07 06:40:48 -0500 received badge  Popular Question (source)
2012-03-31 19:52:08 -0500 received badge  Taxonomist
2012-02-25 09:28:48 -0500 received badge  Notable Question (source)
2011-11-16 03:22:11 -0500 received badge  Popular Question (source)
2011-11-03 08:23:17 -0500 marked best answer Turtlebot tutorial - rviz "2D Pose Estimate" button

This problem can be caused by having an incorrect "Fixed Frame" in rviz. For the "2d Nav Goal" and "2d Pose Estimate" buttons to work, the Fixed Frame must be set to "map".

The idea is that you are sending pose information to the navigation system, and it needs to know what coordinate frame the information is relative to. The nav system can only use this data if it is in the "map" coordinate frame.

image description

2011-09-14 06:48:33 -0500 commented question Turtlebot tutorial - rviz "2D Pose Estimate" button
Thanks hersh. Yes, those commands show the message, publisher and subscriber correctly. But it still doesn't move the robot!!!!
2011-09-07 11:25:24 -0500 commented question Turtlebot tutorial - rviz "2D Pose Estimate" button
Um... I don't think they center around the arrow... Drawing an arrow has no effect. (both for "2D Pose estimate" and "2D Nav Goal" button). Though the robot seems to be roughtly at the correct location on the map.
2011-09-07 11:10:17 -0500 commented question Turtlebot tutorial - rviz "2D Pose Estimate" button
I'm not sure if the localization is running. I do see a bunch of red arrows, which get updated when I drive a bit. Are these particles?
2011-09-07 04:57:19 -0500 asked a question Turtlebot tutorial - rviz "2D Pose Estimate" button

Hi,

I am able to complete all steps in the turtlebot tutorial, except the autonomous navigation part. I am stuck on where I am supposed to click on the "2D Pose Estimate" button in rviz and drag an arrow to set the initial location for the robot. I see the map that is loaded, and also the green laser scan dots, as well as the arrow that I drag to set the robots position and orientation. The only problem is that the location of the robot doesn't update after I release the drag.

Any suggestions? Thanks! David

=================
Update Additional questions (9/13)

Thanks for your answer, Hersh. But the fixed frame option was already set to /map and I still can not get the robot to move. In case it helps, here's the output from the terminal that launched rviz. Thanks!


$ rosrun rviz rviz -d `rospack find turtlebot_navigation`/nav_rviz.vcg
[ INFO] [1315931847.897357347]: Loading general config from [/home/user/.rviz/config]
[ INFO] [1315931847.905051080]: Loading display config from [/home/user/.rviz/display_config]
[ WARN] [1315931876.219268690]: Message from [/amcl] has a non-fully-qualified frame_id [map]. Resolved locally to [/map].  This is will likely not work in multi-robot systems.  This message will only print once.
[ INFO] [1315931976.304023293]: Setting pose: 0.360 -0.107 -0.427 [frame=/map]
[ INFO] [1315931996.143238028]: Setting pose: 0.322 -0.112 -0.390 [frame=/map]
[ INFO] [1315932004.627046894]: Setting goal: Frame:/map, Position(-0.084, 0.127, 0.000), Orientation(0.000, 0.000, 0.996, 0.086) = Angle: 2.970

[ INFO] [1315932008.714840910]: Setting goal: Frame:/map, Position(-0.203, 0.249, 0.000), Orientation(0.000, 0.000, 0.987, 0.159) = Angle: 2.822
2011-09-02 10:55:28 -0500 received badge  Supporter (source)
2011-09-02 10:55:21 -0500 marked best answer TurtleBot Calibration -- Still waiting for scan

It sounds like your TurtleBot software on your TurtleBot might not be up to date:

sudo apt-get update

then:

sudo apt-get install ros-diamondback-turtlebot-robot
2011-09-02 10:55:21 -0500 received badge  Scholar (source)
2011-09-02 10:53:57 -0500 commented answer TurtleBot Calibration -- Still waiting for scan
I tried it again after charging for a while and it works now! It may have been the battery. The voltage now is 15.084V. What is a proper operating range? Thanks a lot!!!
2011-09-02 09:15:54 -0500 answered a question TurtleBot Calibration -- Still waiting for scan

Thanks! That updating the software helped a bit. It now gets past the previous error, and the robot starts rotating. However, before completing a full turn, it stops and the wrench icon on the dashboard becomes red. Dashboard says Power System: Error. Further clicking reveals: Level: Error. Message: Error.

Below is how it looks on the terminal.

BTW, you must be Melonee from the Youtube videos. Thanks for the help! I might be asking more questions in the future.

--David


core service [/rosout] found
process[kinect_breaker_enabler-1]: started with pid [7908]
process[openni_manager-2]: started with pid [7909]
process[openni_camera-3]: started with pid [7910]
process[pointcloud_throttle-4]: started with pid [7911]
process[kinect_laser-5]: started with pid [7912]
process[kinect_laser_narrow-6]: started with pid [7923]
process[scan_to_angle-7]: started with pid [7940]
process[turtlebot_calibration-8]: started with pid [7952]
[INFO] [WallTime: 1314997822.154698] Estimating imu drift
[INFO] [WallTime: 1314997822.456846] Still waiting for imu
[INFO] [WallTime: 1314997822.759576] Still waiting for scan
[ INFO] [1314997822.951332371]: [/openni_camera] Number devices connected: 1
[ INFO] [1314997822.952506928]: [/openni_camera] 1. device on bus 001:31 is a Xbox NUI Camera (2ae) from Microsoft (45e) with serial id 'A00364A10656048A'
[ WARN] [1314997822.959441340]: [/openni_camera] device_id is not set! Using first device.
[ INFO] [1314997823.019817499]: [/openni_camera] Opened 'Xbox NUI Camera' on bus 1:31 with serial number 'A00364A10656048A'
[kinect_breaker_enabler-1] process has finished cleanly.
log file: /home/turtlebot/.ros/log/2f26eecc-d5a5-11e0-b536-485d607f5c5a/kinect_breaker_enabler-1*.log
[ INFO] [1314997823.164011946]: rgb_frame_id = 'kinect_rgb_optical_frame' 
[ INFO] [1314997823.181211203]: depth_frame_id = 'kinect_depth_optical_frame' 
[INFO] [WallTime: 1314997833.370081] Still waiting for imu
[INFO] [WallTime: 1314997833.672666] Still waiting for scan
[INFO] [WallTime: 1314997833.974910]  ... imu drift is -0.243444 degrees per second
[INFO] [WallTime: 1314997833.976291] Aligning base with wall
[INFO] [WallTime: 1314997834.279068] Still waiting for imu
[INFO] [WallTime: 1314997834.581917] Still waiting for scan

2011-09-02 09:12:46 -0500 commented answer TurtleBot Calibration -- Still waiting for scan
Thanks! That helped a bit. It now gets past the previous error, and the robot starts rotating. However, before completing a full turn, it stops and the wrench icon on the dashboard becomes red. Its says Power System: Error.
2011-09-02 06:32:36 -0500 received badge  Editor (source)
2011-09-02 06:22:10 -0500 asked a question TurtleBot Calibration -- Still waiting for scan

I've been following the turtlebot tutorial (http://www.ros.org/wiki/Robots/TurtleBot) I am stuck on 5.TurtleBot Odometry and Gyro Calibration

When I run
$ roslaunch turtlebot_calibration calibrate.launch,
I get the following output, and the final message "Still waiting for scan" repeats forever.

Any suggestions?
I am using the full kit that comes with everything (irobot, kinect, eeepc, etc).

Thanks!


turtlebot@turtlepc:~$ roslaunch turtlebot_calibration calibrate.launch
... logging to /home/turtlebot/.ros/log/ff3cc802-d58c-11e0-8856-485d607f5c5a/roslaunch-turtlepc-13025.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://192.168.22.137:60654/

SUMMARY
========

PARAMETERS
 * /rosversion
 * /rosdistro
 * /scan_to_angle/min_angle
 * /scan_to_angle/max_angle

NODES
  /
    scan_to_angle (turtlebot_calibration/scan_to_angle.py)
    turtlebot_calibration (turtlebot_calibration/calibrate.py)

ROS_MASTER_URI=http://192.168.22.137:11311

core service [/rosout] found
process[scan_to_angle-1]: started with pid [13049]
process[turtlebot_calibration-2]: started with pid [13050]
[INFO] [WallTime: 1314988172.573716] Estimating imu drift
[INFO] [WallTime: 1314988172.875424] Still waiting for imu
[INFO] [WallTime: 1314988173.176998] Still waiting for scan
[INFO] [WallTime: 1314988173.478575] Still waiting for scan
[INFO] [WallTime: 1314988173.780582] Still waiting for scan
[INFO] [WallTime: 1314988174.082496] Still waiting for scan
[INFO] [WallTime: 1314988174.384073] Still waiting for scan
[INFO] [WallTime: 1314988174.685638] Still waiting for scan
[INFO] [WallTime: 1314988174.987211] Still waiting for scan
[INFO] [WallTime: 1314988175.289460] Still waiting for scan
[INFO] [WallTime: 1314988175.591138] Still waiting for scan
[INFO] [WallTime: 1314988175.893684] Still waiting for scan
[INFO] [WallTime: 1314988176.195267] Still waiting for scan
[INFO] [WallTime: 1314988176.496867] Still waiting for scan
[INFO] [WallTime: 1314988176.798562] Still waiting for scan