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
Is your feature request related to a problem? Please describe.
At the moment I am switching back and forth between the different XML and Python launch files. As far as I understand the preferred approach in the future would be to use driver.launch.py. The problem for me is that it does not publish raw lidar_packets which I like to record.
Describe the solution you'd like
Would it be possible to add another key to proc_mask like RAW to publish raw lidar_packets?
Describe alternatives you've considered
At the moment I simply use sensor.independent.launch.py. (sensor.independent.launch.xml gave me recently some errors as described in this issue #159.)
Targeted Platform (please complete the following information only if applicable, otherwise dot N/A):
ROS version/distro? ROS2 humble
Operating System? Jammy
Machine Architecture? ARM
The text was updated successfully, but these errors were encountered:
@Samahu: Thanks, but this does not really answer my question.
To rephrase, is it possible to provide a RAW option to proc_mask so we can record lidar_packets with driver.launch.py launch file, or will sensor.independent.launch.py be the way to go also in future?
Is your feature request related to a problem? Please describe.
At the moment I am switching back and forth between the different XML and Python launch files. As far as I understand the preferred approach in the future would be to use
driver.launch.py
. The problem for me is that it does not publish raw lidar_packets which I like to record.Describe the solution you'd like
Would it be possible to add another key to proc_mask like
RAW
to publish raw lidar_packets?Describe alternatives you've considered
At the moment I simply use
sensor.independent.launch.py
. (sensor.independent.launch.xml
gave me recently some errors as described in this issue #159.)Targeted Platform (please complete the following information only if applicable, otherwise dot N/A):
The text was updated successfully, but these errors were encountered: