The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
I assume by "better estimate height" you mean "provide a 2D pose estimate"? :) Your height estimate has to come from a different source, like ultrasonic, barometric, mirrors mounted to your laser scanner, or a fused combination thereof.
The "syscommand" topic is used by Team Hector´s robots to reset all nodes in a system to a initial state (and some other tasks), but is not required for hector_mapping to work.
The output looks like the scan topic isn´t properly set up. You might also want to have a look at this brand new tutorial on indoor SLAM in simulation using hector_mapping. It should give you an idea on how you can set it up.
| | 2 | No.2 Revision |
I assume by "better estimate height" you mean "provide a 2D pose estimate"? :) Your height estimate has to come from a different source, like ultrasonic, barometric, mirrors mounted to your laser scanner, or a fused combination thereof.
/edit: I just read your other question. So you try to do scanmatching on a vertical 2D slice of the enviroment? That´s not a good idea, as hector_mapping matches scans against the existing map and the "vertical map" will change significantly when the platform travels around.
The "syscommand" topic is used by Team Hector´s robots to reset all nodes in a system to a initial state (and some other tasks), but is not required for hector_mapping to work.
The output looks like the scan topic isn´t properly set up. You might also want to have a look at this brand new tutorial on indoor SLAM in simulation using hector_mapping. It should give you an idea on how you can set it up.
| | 3 | No.3 Revision |
I assume by "better estimate height" you mean "provide a 2D pose estimate"? :) Your height estimate has to come from a different source, like ultrasonic, barometric, mirrors mounted to your laser scanner, or a fused combination thereof.
/edit: I just read your other question. So you try to do scanmatching on a vertical 2D slice of the enviroment? That´s not a good idea, as hector_mapping matches scans against the existing map and the "vertical map" will change significantly when the platform travels around.
The "syscommand" topic is used by Team Hector´s robots to reset all nodes in a system to a initial state (and some other tasks), but is not required for hector_mapping to work.
The output looks like the scan topic isn´t properly set up. You might also want to have a look at this brand new tutorial on quadrotor based indoor SLAM in simulation using hector_mapping. It should give you an idea on how you can set it up.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
