ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

sbrills's profile - activity

2024-02-19 14:12:39 -0500 received badge  Famous Question (source)
2023-08-29 04:52:07 -0500 received badge  Famous Question (source)
2023-06-20 17:04:45 -0500 received badge  Notable Question (source)
2023-06-20 17:04:45 -0500 received badge  Popular Question (source)
2023-02-15 05:58:46 -0500 received badge  Famous Question (source)
2023-02-15 05:58:46 -0500 received badge  Notable Question (source)
2023-02-15 05:58:46 -0500 received badge  Popular Question (source)
2022-07-22 13:59:58 -0500 asked a question Probing Blackboard Variables from CLI in Nav2

Probing Blackboard Variables from CLI in Nav2 Is it possible to probe the values of behavior tree blackboard variables i

2022-07-11 13:45:09 -0500 marked best answer Suggestion for Custom Behaviour and Clarification of FollowPath Action Node in Behaviour Tree

This is a question regarding the behaviour of the FollowPath action node in the nav2 behaviour tree.

In the default implementation of the navigate to pose behaviour, the FollowPath action node has a goal checker that calls the ComputeVelocity method of the plugin controller as long as the robot is outside the goal tolerance region. Now, as soon as the robot is inside the tolerance region, the goal checker registers a success and publishes a zero twist to stop the robot. Each subsequent tick then results in the goalchecker returning a success and publishing a zero twist.

In my particular use case, I'd like to perform a final orientation behaviour once the robot is within the goal region. I have made separate plugins for this behaviour that are attached to the parent pipeline sequence control node. Once the controller returns a success, this behaviour gets ticked but the controller also gets ticked since it is attached to a pipeline sequence node. This causes the zero twist to get published repeatedly.

Is there a suggested way to work around this or modify this behaviour so that subsequent actions on the robot can be implemented while a previously ticked node is halted after completion? I'm not sure if the single trigger would work here since my understanding dictates that it would tick the controller only once and never tick it again thus not permitting it to track the path.

2022-07-11 09:39:27 -0500 commented answer Suggestion for Custom Behaviour and Clarification of FollowPath Action Node in Behaviour Tree

Thank you for the input. What I needed were some of the other sequence control nodes from the default Behavior Tree pac

2022-07-11 09:37:19 -0500 received badge  Notable Question (source)
2022-07-06 12:57:04 -0500 received badge  Enthusiast
2022-07-05 08:40:56 -0500 received badge  Supporter (source)
2022-07-05 08:03:26 -0500 received badge  Popular Question (source)
2022-07-01 13:52:49 -0500 asked a question Suggestion for Custom Behaviour and Clarification of FollowPath Action Node in Behaviour Tree

Suggestion for Custom Behaviour and Clarification of FollowPath Action Node in Behaviour Tree This is a question regardi

2022-06-28 13:42:30 -0500 commented question ROS 2 Custom Action Build: Action type is registered and shows with ROS 2 CLI "interface" command but does not work with CLI "send_goal" command

I think the problem is related to this answer (Related Answer) in that the executable depends on the generated action me

2022-06-27 17:28:32 -0500 asked a question ROS 2 Custom Action Build: Action type is registered and shows with ROS 2 CLI "interface" command but does not work with CLI "send_goal" command

ROS 2 Custom Action Build: Action type is registered and shows with ROS 2 CLI "interface" command but does not work wit