ligang's profile - activity

https://github.com/DaikiMaekawa/hecto... https://github.com/tu-darmstadt-ros-p...

1,roscore 2,roslaunch hector_slam_example hector_rplidar.launch 3,roslaunch rplidar_ros rplidar.launch

when I move the robot Waiting for tf transform data between frames /map and /base_link to become available [hector_mapping-9] process has died [pid 6941, exit code -11, cmd /opt/ros/hydro/lib/hector_mapping/hector_mapping __name:=hector_mapping __log:=/home/ligang/.ros/log/6f406894-2799-11e6-b330-a088b48fb934/hector_mapping-9.log]. log file: /home/ligang/.ros/log/6f406894-2799-11e6-b330-a088b48fb934/hector_mapping-9*.log

[rospack] Warning: no such package hector_geotiff when i install https://github.com/tu-darmstadt-ros-p... some question is ok. but have another question.

in amcl the Minimum allowed number of particles means what?

Who can give some detail explain ?

I can not know what is particles?

"min_particles", "int", 0, "Minimum allowed number of particles.
"max_particles", "int", 0, "Mamimum allowed number of particles.
"kld_err", "double", 0, "Maximum error between the true distribution and the estimated distribution."
"kld_z", "double", 0, "Upper standard normal quantile for (1 - p), where p is the probability that the error on the estimated distrubition will be less than kld_err."
"update_min_d", "double", 0, "Translational movement required before performing a filter update."
"update_min_a", "double", 0, "Rotational movement required before performing a filter update."

I want to kill all nodes in one command. Now ,we can use rosnode kill 1 step by step to end all the node .

but i want to use one command to kill all node.

We can control the robot to a goal, using base_move and amcl.

but i can not judge that when the robot reached the goal.

I think, we can judge the vel or the tf not change to do it .

but, I think that ,it must have better solution.

I use rqt_graph and rosrun tf view_frames list all. but , I can not find any solution than I do.

anyone can help me to solve it,

thanks!

EDIT1:

when the route is short the status always be 3 , when the robot nav to a long distance the status change to 1 and then change to 3.

I want to know why , the status is not change the status 3 SUCCEEDED->1ACTIVE->3 SUCCEEDED ?

I want to shutdown the robot, and restart the robot ,I want to let the robot remember the status before he shutdown? Any friends can help me?

If I can not save the status, I must move the robot to the start point by hand.

in a project, we use amcl move_base and odom laser . the odom must have error and the amcl can product the pos , through tf to tell the robot pos.

and when we run it some times .

the odom will product 1meter's error.

when we close the robot.

we must save the pose to file. when I restart the program , we can read the pos to rviz.

we use the /map /odom to cal the pos but ,it always product some error. so i use tf /map /base_link and we get some error too.

anyone can help me ? how to cal the pos?

File: actionlib_msgs/GoalStatus.msg Raw Message Definition GoalID goal_id uint8 status uint8 PENDING = 0 # The goal has yet to be processed by the action server uint8 ACTIVE = 1 # The goal is currently being processed by the action server uint8 PREEMPTED = 2 # The goal received a cancel request after it started executing # and has since completed its execution (Terminal State) uint8 SUCCEEDED = 3 # The goal was achieved successfully by the action server (Terminal State) uint8 ABORTED = 4 # The goal was aborted during execution by the action server due # to some failure (Terminal State) uint8 REJECTED = 5 # The goal was rejected by the action server without being processed, # because the goal was unattainable or invalid (Terminal State) uint8 PREEMPTING = 6 # The goal received a cancel request after it started executing # and has not yet completed execution uint8 RECALLING = 7 # The goal received a cancel request before it started executing, # but the action server has not yet confirmed that the goal is canceled uint8 RECALLED = 8 # The goal received a cancel request before it started executing # and was successfully cancelled (Terminal State) uint8 LOST = 9 # An action client can determine that a goal is LOST. This should not be # sent over the wire by an action server

when the route is short the status always be 3 , when the robot nav to a long distance the status change to 1 and then change to 3.

I want to know why , the status is not change the status 3 SUCCEEDED->1ACTIVE->3 SUCCEEDED ?

thank you, It's best!

I want to run a ros node in android, and use usb serial to communication with ubuntu ros.

Can anybody provide some help?

Thank you !

use the action interface, can you provide a simple example, I am a fresh in ROS.