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
#!/usr/bin/python3fromament_index_python.packagesimportget_package_share_directoryfromlaunchimportLaunchDescriptionfromlaunch_ros.actionsimportLifecycleNodefromlaunch.actionsimportDeclareLaunchArgumentfromlaunch.substitutionsimportLaunchConfigurationfromlaunch.actionsimportEmitEventfromlaunch.actionsimportRegisterEventHandlerfromlaunch_ros.events.lifecycleimportChangeStatefromlaunch_ros.events.lifecycleimportmatches_node_namefromlaunch_ros.event_handlersimportOnStateTransitionfromlaunch.actionsimportLogInfofromlaunch.eventsimportmatches_actionfromlaunch.event_handlers.on_shutdownimportOnShutdownimportlifecycle_msgs.msgimportosdefgenerate_launch_description():
share_dir=get_package_share_directory('robobus_sensor_kit_launch')
parameter_file=LaunchConfiguration('params_file')
node_name='ouster_driver'# Acquire the driver param fileparams_declare=DeclareLaunchArgument('params_file',
default_value=os.path.join(
share_dir, 'config', 'ouster_fl_config.yaml'),
description='FPath to the ROS2 parameters file to use.')
driver_node=LifecycleNode(package='ros2_ouster',
executable='ouster_driver',
name=node_name,
output='screen',
emulate_tty=True,
parameters=[parameter_file],
arguments=['--ros-args', '--log-level', 'INFO'],
namespace='',
)
configure_event=EmitEvent(
event=ChangeState(
lifecycle_node_matcher=matches_action(driver_node),
transition_id=lifecycle_msgs.msg.Transition.TRANSITION_CONFIGURE,
)
)
activate_event=RegisterEventHandler(
OnStateTransition(
target_lifecycle_node=driver_node, goal_state='inactive',
entities=[
LogInfo(
msg="[LifecycleLaunch] Ouster driver node is activating."),
EmitEvent(event=ChangeState(
lifecycle_node_matcher=matches_action(driver_node),
transition_id=lifecycle_msgs.msg.Transition.TRANSITION_ACTIVATE,
)),
],
)
)
# TODO make lifecycle transition to shutdown before SIGINTshutdown_event=RegisterEventHandler(
OnShutdown(
on_shutdown=[
EmitEvent(event=ChangeState(
lifecycle_node_matcher=matches_node_name(node_name=node_name),
transition_id=lifecycle_msgs.msg.Transition.TRANSITION_ACTIVE_SHUTDOWN,
)),
LogInfo(
msg="[LifecycleLaunch] Ouster driver node is exiting."),
],
)
)
returnLaunchDescription([
params_declare,
driver_node,
activate_event,
configure_event,
shutdown_event,
])
behavior
when there was only one LiDAR, The pointcloud topic bandwidth was normal as well as the rate of topic. When I plugged another LiDAR, the bandwidth increased and shown as the pic below.
The text was updated successfully, but these errors were encountered:
What's the ask / action? If there's that much data coming over the network, I'm not sure what you expect the ROS driver to do about it (e.g. we're not the ouster client code getting the packets nor the ROS standards for how pointclouds are published to end users).
I'm not opposed to changes, but you need to propose something actionable in this repository :-)
I am sorry, let me explain.
The bandwidth with was the bandwidth of pointcloud topic. I have multiple LiDARs OS LiDARs in this system, when there was only one LiDAR, the data was normal, but when I plugged another LiDAR, the pointcloud data went crazy. I think it something wrong with the pack parsing process.
Too heavy bandwidth when multiple LiDAR plugged in
System Information
ROS: Humble
LiDAR:
OS1-32
Driver Version: 5425ed0
Description
launch file
behavior
when there was only one LiDAR, The pointcloud topic bandwidth was normal as well as the rate of topic. When I plugged another LiDAR, the bandwidth increased and shown as the pic below.
The text was updated successfully, but these errors were encountered: