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 |
Hector: You pass, thus create, base_link in the hector launchfile, but it should likely be the camera_base_frame.
<arg name="base_frame" default="base_link"/> ----> <arg name="base_frame" default="camera_base_frame"/>
| | 2 | No.2 Revision |
Hector: You pass, thus create, base_link in the hector launchfile, but it should likely be the camera_base_frame.
<arg name="base_frame" default="base_link"/> ----> ---try----> <arg name="base_frame" default="camera_base_frame"/>
| | 3 | No.3 Revision |
Hector: You pass, thus create, base_link in the hector launchfile, but it should likely be the camera_base_frame.
<arg name="base_frame" default="base_link"/> ---try----> <arg name="base_frame" default="camera_base_frame"/>
I would also suggest, looking into changing the camera specific odom and base frame-IDs to more conventional (for the time beeing maybe even dummy ones with Zero static transform publishers) odom and base_link. Because if you develop further you might actually introduce a "real" robot base_link (thats not equal to camera_base) and sensorfusion-odometry. hector gives odometry as well, might make sense to fuse that with the camera odom in future upgrades.
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.
