ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
You should use LaserScan
message, imo, and take care of the spinning logic in your laser scan publisher.
Here are some guidelines and examples:
Keep in mind that you'll need some way of keeping track of your motor's / LiDAR's orientation. Some sort of encoder.
2 | No.2 Revision |
You should use LaserScan
message, messages, imo, and take care of the spinning logic in your laser scan publisher.
Here are some guidelines and examples:
Keep in mind that you'll need some way of keeping track of your motor's / LiDAR's orientation. Some sort of encoder.
3 | No.3 Revision |
You should use LaserScan
messages, imo, and take care of the spinning logic in your laser scan publisher.publisher. Each LaserScan
messsage's ranges
field will be populated with, e.g., 180 degrees worth of LiDAR-Lite measurements.
Here are some guidelines and examples:
Keep in mind that you'll need some way of keeping track of your motor's / LiDAR's orientation. Some sort of encoder.
4 | No.4 Revision |
You should use LaserScan
messages, imo, and take care of the spinning logic in your laser scan publisher. Each LaserScan
messsage's ranges
field will be populated with, e.g., 180 degrees worth of LiDAR-Lite measurements.
Here are some guidelines and examples:
Keep in mind that you'll need some way of keeping track of your motor's / LiDAR's orientation. Some sort of encoder.encoder. (Unless you're using a stepper motor.)