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

Chamith's profile - activity

2020-09-16 20:47:27 -0500 received badge  Famous Question (source)
2020-02-14 13:41:42 -0500 received badge  Famous Question (source)
2019-12-31 10:44:04 -0500 received badge  Notable Question (source)
2019-12-27 13:45:48 -0500 received badge  Notable Question (source)
2019-11-25 08:37:29 -0500 received badge  Popular Question (source)
2019-11-14 09:32:10 -0500 received badge  Popular Question (source)
2019-11-09 03:34:55 -0500 asked a question Is it posible to use move_base for an omnidirectional robots?

Is it posible to use move_base for an omnidirectional robots? I am trying to use move_base package to control the omni-d

2019-11-03 06:19:16 -0500 commented answer Why AMCL not update the tf values between map and base_link?

Thank you for the reply. I used rf2o_laser_odometry for create odometry. But there is a small issue. The pose array and

2019-11-01 08:28:57 -0500 commented answer Why AMCL not update the tf values between map and base_link?

Is there any possibility to use laser scan data to create odomerty? Thank you for the reply.

2019-11-01 03:31:10 -0500 marked best answer Why AMCL not update the tf values between map and base_link?

I am developing an Omnidirectional robot's controlling system using ROS kinetic. And I am trying to use AMCL to localize the robot on a saved map. Also I don't use any odom data. I use laser scan data only. So in my AMCL launch file I have used base_link as odom frame. My problem is, tf values between map and base_link does not update when the robot is moving on gazebo. Also the pose array does not converge. This is my AMCL launch file.

<launch>
<node pkg="amcl" type="amcl" name="amcl" respawn="true" output="screen">
<remap from="scan" to="scan" />
<remap from="odom" to="base_link" />
<param name="odom_model_type" value="omni"/>
<param name="odom_alpha5" value="0.1"/>
<param name="transform_tolerance" value="0.2" />
<param name="gui_publish_rate" value="10.0"/>
<param name="laser_max_beams" value="30"/>
<param name="laser_max_range" value="12.0"/>
<param name="min_particles" value="500"/>
<param name="max_particles" value="5000"/>
<param name="kld_err" value="0.05"/>
<param name="kld_z" value="0.99"/>
<param name="odom_alpha1" value="0.2"/>
<param name="odom_alpha2" value="0.2"/>
<!-- translation std dev, m -->
<param name="odom_alpha3" value="0.8"/>
<param name="odom_alpha4" value="0.2"/>
<param name="laser_z_hit" value="0.5"/>
<param name="laser_z_short" value="0.05"/>
<param name="laser_z_max" value="0.05"/>
<param name="laser_z_rand" value="0.5"/>
<param name="laser_sigma_hit" value="0.2"/>
<param name="laser_lambda_short" value="0.1"/>
<param name="laser_lambda_short" value="0.1"/>
<param name="laser_model_type" value="likelihood_field"/>
<param name="laser_likelihood_max_dist" value="2.0"/>
<param name="update_min_d" value="0.2"/>
<param name="update_min_a" value="0.5"/>
<param name="odom_frame_id" value="base_link"/>
<param name="global_frame_id" value="map"/>
<param name="base_frame_id" value="base_link"/>
<param name="resample_interval" value="1"/>
<param name="transform_tolerance" value="0.1"/>
<param name="recovery_alpha_slow" value="0.0"/>
<param name="recovery_alpha_fast" value="0.0"/>
<param name="tf_broadcast" value="true"/>
</node>
</launch>
2019-11-01 03:31:10 -0500 received badge  Scholar (source)
2019-10-31 10:41:49 -0500 asked a question Why AMCL not update the tf values between map and base_link?

Why AMCL not update the tf values between map and base_link? I am developing an Omnidirectional robot's controlling syst