Skip to content

fix: raw_data_stream uses wrong is_ros_subscriber flag#272

Open
ExpectedArgument wants to merge 1 commit intoKumarRobotics:ros2from
ExpectedArgument:fix/raw_data_stream_subscriber_mode
Open

fix: raw_data_stream uses wrong is_ros_subscriber flag#272
ExpectedArgument wants to merge 1 commit intoKumarRobotics:ros2from
ExpectedArgument:fix/raw_data_stream_subscriber_mode

Conversation

@ExpectedArgument
Copy link

When raw_data_stream.enable is true, RawDataStreamPa is constructed with is_ros_subscriber=true, which puts it in subscriber mode. In subscriber mode:

  • getRosParams() reads 'dir' instead of 'raw_data_stream.dir'
  • isEnabled() only returns !file_dir_.empty(), ignoring 'publish' flag
  • setRawDataCallback() is never called → no data flows

Fix: pass false as is_ros_subscriber since the GPS node is a producer, not a subscriber of the raw data stream.

When raw_data_stream.enable is true, RawDataStreamPa is constructed
with is_ros_subscriber=true, which puts it in subscriber mode.
In subscriber mode:
- getRosParams() reads 'dir' instead of 'raw_data_stream.dir'
- isEnabled() only returns !file_dir_.empty(), ignoring 'publish' flag
- setRawDataCallback() is never called → no data flows

Fix: pass false as is_ros_subscriber since the GPS node is a producer,
not a subscriber of the raw data stream.
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

Successfully merging this pull request may close these issues.

1 participant