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

Husky ROS melodic image on a real robot, gmapping.launch stuck at "requesting a map"

asked 2021-07-15 03:08:37 -0500

nurtech gravatar image

Hello, I fresh installed husky melodic ros image from clearpath and installed the husky_navigation package using apt (sudo apt install ros-melodic-husky-navigation). I ran (roslaunch husky_navigation gmapping_demo.launch) but it hangs on:

NODES / move_base (move_base/move_base) slam_gmapping (gmapping/slam_gmapping)

ROS_MASTER_URI=http://localhost:11311

process[slam_gmapping-1]: started with pid [6503] process[move_base-2]: started with pid [6504]
I Also ran (roslaunch husky_viz view_robot.launch) and checked the navigation box but still cant use the (2D nav goal). It seems like the laser is not seeing any obstacles either.

can someone please advise me on how to fix this issue? it is a fresh install and I only installed husky_navigation package using apt.

I added /etc/hosts on both machines and can ping them both ways, I also successfully used (rostopic echo /husky_velocity_controller/odom) from my workstation.

Thank you, Please advise

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2021-07-25 01:31:51 -0500

nurtech gravatar image

updated 2021-07-26 03:44:11 -0500

I realized that the Lidar on our husky is "hokuyo lidar" while the one mentioned in Clearpath installation guide is (Sick LMS1XX Lidar). I managed to turn on my laser by: 1) Install urg_node (sudo apt-get install ros-melodic-urg-node) 2) creating this laser.launch file and adding it to /opt/ros/melodic/share/husky_navigation/launch

laser.launch:

<launch>

<node pkg="urg_node" type="urg_node" name="urg_node">

    <param name="serial_port" value="/dev/ttyACM0" />
    <param name="frame_id" value="laser_link" />
    <param name="calibrate_time" value="true"/>
    <param name="publish_intensity" value="false"/>
    <param name="angle_min" value="-1.5"/>
    <param name="angle_max" value="1.5"/>
</node>

<node pkg="tf" type="static_transform_publisher" name="robot_to_kinect" args="0.393 0 .155 0 0 3.14159 /base_link /laser_link 20"/>

</launch>

I also added this line of code at the top in gmapping_demo.launch:

<launch>

<include file="$(find husky_navigation)/launch/laser.launch"/>

. . .

3) Also make sure when you run rviz to change global_option fixed frame to "map" instead of "odom" It works now :)

edit flag offensive delete link more

Comments

I'm glad you got it working. Thanks for documenting your solution for the community.

You did notice that the argument order for static_transform_publisher is yaw-pitch-roll, not the more common rpy ? I have to double-check I got it right every time I use this node.

Mike Scheutzow gravatar image Mike Scheutzow  ( 2021-07-25 09:38:08 -0500 )edit

Thanks for the heads up. Yes, I got the raw pitch roll values from an older custom launch file that we had on our old husky operating system. (Some other developer was working on this same robot 3 years ago) so I am assuming he got the numbers right but I will double check. I fresh installed to Ubuntu 18.04 and husky melodic so I had to reconfigure many things

nurtech gravatar image nurtech  ( 2021-07-25 12:04:47 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2021-07-15 03:06:37 -0500

Seen: 276 times

Last updated: Jul 26 '21