Skip to content
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

ros time source should not use parameter client #580

Closed
wjwwood opened this issue Nov 7, 2018 · 3 comments
Closed

ros time source should not use parameter client #580

wjwwood opened this issue Nov 7, 2018 · 3 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@wjwwood
Copy link
Member

wjwwood commented Nov 7, 2018

Right now the TimeSource class implementation in rclcpp uses a ParameterClient to get notifications of when a parameter changes, which:

  • does not work if parameter service is disabled in the node
  • is not required, the node knows when the parameter changes (with or without ROS services)
@wjwwood wjwwood added enhancement New feature or request help wanted Extra attention is needed labels Nov 7, 2018
@wjwwood
Copy link
Member Author

wjwwood commented Nov 7, 2018

parameter_client_ = std::make_shared<rclcpp::AsyncParametersClient>(
node_base_,
node_topics_,
node_graph_,
node_services_
);
parameter_subscription_ =
parameter_client_->on_parameter_event(std::bind(&TimeSource::on_parameter_event,
this, std::placeholders::_1));

nnmm pushed a commit to ApexAI/rclcpp that referenced this issue Jul 9, 2022
* Improve rcl clock API documentation.

Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>

* Improve rcl clock API error checking.

Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>

* Address peer review comments.

Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>

* Refine rcl_clock_t API thread-safety documentation.

Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>
@CursedRock17
Copy link
Contributor

Since pull request #740 was merged, time_source no longer uses parameter_client_, so this issue should have been solved correct? Otherwise I'd happy to make some changes needed.

@clalancette
Copy link
Contributor

Yeah, I'm going to close this one out for now. We may have to make further changes to the TimeSource (see the conversation in ros2/geometry2#630), but that is not what this PR is talking about.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants