You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm trying to use the picoscan150 on AGV navigation. After launching the sick_lidar_localization.launch, I can see the odometry 0104 and 0105 topics, but there's no message published inside. How can I solve this problem? Thank you.
The text was updated successfully, but these errors were encountered:
whm210806
changed the title
How to get odometry message, grid map and point cloud from picoscan150?
How to get odometry message from picoscan150?
Oct 14, 2024
The ROS driver communicates with LiDAR-LOC to extract the results or additional information from or to LiDAR-LOC. .
This communication happens via ROS topics or ROS services.
Here is the ROS topic list that user gets once the parameters have been correctly set up.
These ROS topics contain different types of variables that the customer can use.
Here is an example from the localization result topic (vehicle's coordinates) "":
Note: The ROS driver needs to be already launched.
To extract the variables from the ROS Driver, the user needs to subscribe to a topic and assign the variables from the messages to a local variable.
Here is an python program that retrieves the localization result output.
The program retrieves the localization result and uses the print function to display it on the terminal.
Please find example python script attached to this post.
Odometry within LiDAR-LOC:
LiDAR-LOC uses the vehicle's wheel odometry or the user's "calculated-external"odometry to uses it as a second source to calculate the vehicle's localization.
This additional input can be sent to LiDAR-LOC via the "/odom" topic in LiDAR-LOC.
Hi, I'm trying to use the picoscan150 on AGV navigation. After launching the sick_lidar_localization.launch, I can see the odometry 0104 and 0105 topics, but there's no message published inside. How can I solve this problem? Thank you.
The text was updated successfully, but these errors were encountered: