-
Notifications
You must be signed in to change notification settings - Fork 55
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
No calibration files required #89
Comments
The project currently does not have decoders for Innovusion's Lidar. However, if implemented from scratch, it should be possible to create an Innovusion HW connection and Packet Decoder inheriting from NebulaHwInterfaceBase and NebulaDriverBase, respectively. |
Thank you for your reply. Currently, Lidar from innovusion has submitted a PR and will face this issue once merged. |
Thank you for providing additional information, and thank you for your PR. |
Thank you for your solution. We will support it in the next version. |
When we use XML launch files to start Nebula, we found that the hw_interface, monitor, and decoder nodes are running in separate processes, which can lead to performance degradation. On the other hand, using Python launch files allows us to utilize the concept of composite nodes, where all three nodes run in the same process. Based on my research, XML launch files currently do not support composite nodes. To ensure efficiency, would it be possible for us to modify Nebula's nebula_launch.py? Alternatively, could we create a new file called nebula_launch_innovusion.py to address this issue with multiple processes? |
You can create a component container and add the composable nodes. Please look at the link I shared above. It contains an example. Click on the XML tab. https://docs.ros.org/en/humble/How-To-Guides/Launching-composable-nodes.html#launch-file-examples |
I have tried according to the document you provided, but unfortunately, the error message is as follows. It should be a lack of third-party packages or frameworks to support some of the XML tags. Due to time constraints, we have shelved the XML integration combination node solution and continued to use the PY method to start it. We have added a specific startup command line in README (sensor_ip must be configured). Thank you for your continuous attention.
|
Can you please paste the contents of your XML file? |
FYI
|
Thank you |
Of course you can. If you want to test whether the
|
I found two main issues:
I didn't have a sensor, but I could launch successfully with the following file
|
Firstly, thank you for pointing out the error in the XML startup file.
|
FYI. The complete error report is as follows:
|
I see, like I mentioned before this is only for ROS2 Humble. |
I understand that the fundamental issue lies in the version differences of Ros2. If necessary, we will upgrade the Ros2 version. Thanks. |
I have switched to the Ros2 Humble version and verified the XML file you provided, which proves to be feasible. Thank you. |
For Innovusion's LiDAR, data calibration is all done within the LiDAR itself, and no calibration is required on the client side. However, in the existing framework, the system cannot run properly without providing a calibration file. Can the launch script be modified to remove this restriction?
The text was updated successfully, but these errors were encountered: