Skip to content
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

About the publication of the reflector information. #340

Open
wangyw123456 opened this issue May 31, 2024 · 1 comment
Open

About the publication of the reflector information. #340

wangyw123456 opened this issue May 31, 2024 · 1 comment

Comments

@wangyw123456
Copy link

At present, the reflector information is published through the topic of /cloud_all_fields_fullframe. Can we change it to be published through the topic of /sick_picoscan/scan_fullframe ? Our company is currently testing this aspect and hopes to support it

@wangyw123456 wangyw123456 changed the title about thepublication of reflector information About the publication of the reflector information. May 31, 2024
@rostest
Copy link
Collaborator

rostest commented May 31, 2024

Thanks for your feedback. The messages in topic "/sick_picoscan/scan_fullframe" are standard ROS messages of type sensor_msgs::LaserScan. This data format is defined by the ROS in https://docs.ros.org/en/noetic/api/sensor_msgs/html/msg/LaserScan.html. It allows the transmission of ranges and intensities of a single and planar laser scan, but cannot be extended with additional and lidar specific properties such as reflector bits.
We recommend using the more flexible point cloud data format in the topic "cloud_all_fields_fullframe", which includes all scan properties incl. the reflector bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants