-
Notifications
You must be signed in to change notification settings - Fork 89
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
how to add Lidar sensors to settings.json #132
Comments
Hi! Thanks for trying the simulator! A detailed description of how to configure the lidar can be found here. You are right, we should include this in the documentation of this project as well. A full example of the lidar configuration is as follows:
Where I will try to replicate the May I ask out of curiosity, are you part of any formula student team? |
@ctobasti In #138 the lidar documentation is improved. Would you like to check lidar.md and integration-handbook.md and let me know if this satisfies your question? |
@ctobasti About the |
I tried multiple ways to add additional Lidars to the settings.json file, but none of them were successful.
It would be helpful if you could provide a description of how they should be implemented, as well as adding parameters like HorizontalFOV... that aren`t included in the standard settings.json file, that can be found in the repository.
Also, the Lidar data should be published under the topic /fsds/lidar/LIDAR_NAME. By changing the sensor name of a Lidar (sensor type 6) to anything else than "LidarCustom", the ros bridge prints out the following warning: "No lidar with name LidarCustom exist on vehicle".
Shouldnt the topic name adapt to the Lidar name?
Thanks for the work on the simulation
The text was updated successfully, but these errors were encountered: