-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixing ESDA tf tree #51
Comments
Sensors should be working. Should remind myself that the VLP16 needs 12V NOT 5V. The new piksi does not work. Need a usb to reset to factory settings and see if it'll fix otherwise the old one still works thankfully. |
refactored code as lots of the pkgs we use don't allow for supplying a config so now I use forks imu and vlp16 work. zed shows joint states and robot description but nothing else. I have to launch the perception package instead of just the zed wrapper anyway need to lanch the sim file that plublishes joint states for robot loc and slam to work |
Set publish map tf and urdf to false when launchign zed wrapper but now there is no map from slam tool box and idk why. possible a tf issue. Maybe I need to set some params when launching SLAM or set a TF between map and velodyne link |
Overview
This issue was originally a general sensor integration task but has been repurposed to focus on fixing the tf tree.
For
slam_toolbox
to work, it needs certain transforms to be outputting and iirc, some of these are dependent onrobot_localization
working. Forrobot_localization
to work, it needs adequate GNSS/imu signals and this depends on the following issuesIgnoring the circular dependency between this task and issue 63, the purpose of this task is to fix the tf_tree as much as possible or at least, using static transforms, verify that the issue is indeed the lack of prerequisite transforms for
slam_toolbox
.Relevant resources
Acceptance criteria
slam_toolbox
map is outputting correctlyTodo
The text was updated successfully, but these errors were encountered: