TJump's profile - activity

Since console_bridge is ROS-independent should it go in a ROS workspace or simply in with the debian/Ubuntu somewhere (like with bootstrap dependencies)?

As it is not a catkin package it cannot go in a catkin workspace.

I'm installing on a BeagleBone so Groovy must be installed from source (if this makes any difference in the answer).

I have hector_slam running on the BeagleBone. IMU_UM6 and URG-04X both launch and stream data.

I have not had success getting hokuyo_node functional so I am using the newer urg_node and changed the launch file for hector_slam to launch the urg_node rather than the hokuyo_node.

I do not have rviz running on the BeagleBone as there is no display attached to the BeagleBone.

When I launch hector_slam I get the following error:

[ERROR] [1370640753.966993122]: Trajectory Server: Transform from /map to /base_stabilized failed: Frame id /map does not exist! Frames (4):
Frame /laser exists with parent /base_link.
Frame /base_link exists with parent /base_stabilized.
Frame /base_stabilized exists with parent NO_PARENT.

Is this because rviz is not running and loading the map, or do I have a different issue?

From the tutorial (http://www.ros.org/wiki/hector_slam/Tutorials/SettingUpForYourRobot) which launch file is to be edited?

hector_slam/hector_mapping/launch/mapping_default.launch

or other?

Also, from the tutorial the parameters are listed as value="base_frame", value="odom", etc.; but in the launch file (mapping_default.launch) the parameters are listed as value="$(arg base_frame)" and value="$(arg odom_frame)"...

Am I in the wrong file or is setting arguments and calling them vs. the examples published in the tutorial a change from ROS electric to ROS fuerte?

When running the Hector_slam tutorial (http://www.ros.org/wiki/hector_slam/Tutorials/MappingUsingLoggedData) using the downloaded .bag file I get a map, but I also get the following errors:

ERROR 1343506441.987975020, 1310297991.330406663: Trajectory Server: Transform from /map to scanmatcher_frame failed: Frame id /map does not exist! Frames (1):  
ERROR 1343506441.988524740, 1310297991.330406663: Trajectory Server: Transform from /map to scanmatcher_frame failed: Frame id /map does not exist! Frames (1):  
ERROR 1343506442.239030122, 1310297991.582959932: Trajectory Server: Transform from /map to scanmatcher_frame failed: Frame id /map does not exist! Frames (1):  
ERROR 1343506442.492759217, 1310297991.835439286: Trajectory Server: Transform from /map to scanmatcher_frame failed: Frame id /map does not exist! Frames (1):  
ERROR 1343506442.743658504, 1310297992.087936543: Trajectory Server: Transform from /map to scanmatcher_frame failed: Frame id /map does not exist! Frames (1):  
ERROR 1343506442.987813058, 1310297992.331234214: Trajectory Server: Transform from /map to scanmatcher_frame failed: Frame id /scanmatcher_frame does not exist! Frames (6):
Frame /base_link exists with parent /nav.
Frame /nav exists with parent /map.
Frame /base_stabilized exists with parent /nav.
Frame /base_footprint exists with parent /nav.
Frame /map exists with parent NO_PARENT.

And

SearchDir angle change too large
SearchDir angle change too large

What is needed here to correct this?

Thanks Tony!!

I'm working with different sensors that all require I run things like:

$ sudo chmod a+rw /dev/ttyACM0

$ sudo chmod a+rw /dev/ttyUSB0

to set the port permissions before ROS can see the sensor data. I would like to set these permanently (or somehow in a config or launch file) so I don't need to manually process this step with each attempt to run my app.

Please advise.

Per the following link, the imu tutorial included in the rviz_plugin_tutorials package (apt-get install ros-hydro-visualization-tutorials) only displays the magenta vector.

FYI - I used apt-get install ros-indigo-visualization-tutorials but same result.

http://docs.ros.org/indigo/api/rviz_p...

When I use the rviz_plugin for imu the arrow moves with the movement of the UM6, so it seems the sensor and driver are working fine. There no longer appears to be an imu_pose or imu_pose.py or imu_pose_node.py with the new driver.

I'll need to get back to my lab to get into the different versions and run rostopic list but I'm away maybe until next week. I'm following the procedure from here ( http://wiki.ros.org/um6 ) and

rosrun um6 um6_driver _port:=/dev/ttyUSB0

to run the driver.

I've recently built a new computer with Ubuntu 14.04 and ROS Indigo. In getting all my sensors up and running in the new environment I'm not getting the UM6 to display the same in RVIZ as it did with the older driver (not seeing moving Axes but only moving vertical arrow... which is fine except it is difficult to see rotation with just the arrow). I've noticed the published topics are different as well, so I'm looking for some documentation/information on differences and any direction on what to expect with the new driver and on getting a moving axes or other (maybe a robot profile?).

Thanks. I submitted the issue on the GitHub site.

roslaunch hector_slam_launch tutorial.launch points to an rviz_cfg folder in the hector_slam_launch folder, but no such folder or mapping_demo.rviz file exists after install of hector_slam. I've generated the mapping_demo.rviz file to match the older mapping_demo.cfg file (I just have this on my desktop for now) but I want to verify how to add the rviz_cfg directory to the hector_slam_launch folder along with the .rviz file under the new ROS Indigo format.

OR, is this even the correct protocol under Indigo?

If you want to specify a version of a catkin package to install (--version -new) how do you do this?

wstool set rosconsole_bridge https://github.com/ros/rosconsole_bridge.git --git --version-new -y

or

wstool set rosconsole_bridge https://github.com/ros/rosconsole_bridge.git --git --version-groovy -y

or is there something I'm doing wrong in my syntax?

When reviewing the URGConfig.dox and comparing to the HokuyoConfig.dox there are several differences and I would like to test the urg_node with the values the same as with the hokuyo_node. If I edit the URGConfig.dox will this affect changes to the urg_node or do I need to access a different file to make these changes?

Example:

\b "~angle_min" : \b [double] Controls the angle of the first range measurement in radians. min: -3.14159265359, default: -3.14159265359, max: 3.14159265359

In the HokuyoConfig.dox for the same "~angle_min" it has the default at -1.57079632679; so again, what file do I change in the urg_node to get the settings the same as for the hokuyo_node?