bergercookie's profile - activity

Please provide more info about your setup. What are the contents of the CMakeLists.txt file? What's the directory struct

I don't think there's a global variable concept in ROS1 for this purpose. Could you perhaps limit the publishing rate of

ros2 launch: Forward keystrokes to child node I want to create a launchfile, which launches a keyboard teleop node. When

ros2 launch: Forward keystrokes to child node I want to create a launchfile, which launches a keyboard teleop node. When

This is about the package's CMakeLists.txt

What's your OS version? What's the output of uname -a? If you have Ubuntu20.04 you shouldn't be installing melodic since

What's your OS version? What's the output of uname -a? If you have Ubuntu20.04 you shouldn't be installing melodic since

ROS2 Launch - Detect error on process startup I understand that in ROS2 you can use on_exit=actions.Shutdown() to detect

It's now possible to do that with, at least, the ROS2 Foxy version. --ros-args -p scenario_id:="check_scenario" I also

I'm looking at the ros2 lifecycles demo here: https://github.com/ros2/demos/blob/fo...

According to the Lifecycles page of ROS2 if an exception occurs in any of the primary states then the on_error method should be called, which in turn, on SUCCESS reverts to the Unconfigured state, and on FAILUREit goes to Finalized and eventually the node gets shutdown.

For the sake of the example I'll throw an exception from within one of the transition callbacks, e.g., on_activate.

on_activate(const rclcpp_lifecycle::State &)
{
  throw std::runtime_error("some_error");
  ...

With this change in place I see the following transitions happening (see roslaunch output of command ros2 launch lifecycle lifecycle_demo.launch.py)

[lifecycle_listener-2] [INFO] [1627469418.643524277] [lc_listener]: notify callback: Transition from state activating to errorprocessing
[lifecycle_listener-2] [INFO] [1627469418.643625385] [lc_listener]: notify callback: Transition from state errorprocessing to unconfigured
[lifecycle_service_client-3] [WARN] [1627469418.643600791] [lc_client]: Failed to trigger transition 3

I understand why it transitions to errorprocessing and then to unconfigured. However it then tries to transition to "3" which is the TRANSITION_ACTIVATE transition and it fails to do so since that is not a valid transition (Unconfigured -> Active)

I don't understand though, why is it trying transition to activate since I or any other node didn't explicitly trigger this transition? What can I do to solve this?

Here's also the full list of transitions the node goes through, in case it's helpful

ros2 topic echo /lc_talker/transition_event
timestamp: 0
transition:
  id: 0
  label: ''
start_state:
  id: 1
  label: unconfigured
goal_state:
  id: 10
  label: configuring
---
timestamp: 0
transition:
  id: 0
  label: ''
start_state:
  id: 10
  label: configuring
goal_state:
  id: 2
  label: inactive
---
timestamp: 0
transition:
  id: 0
  label: ''
start_state:
  id: 2
  label: inactive
goal_state:
  id: 13
  label: activating
---
timestamp: 0
transition:
  id: 0
  label: ''
start_state:
  id: 13
  label: activating
goal_state:
  id: 15
  label: errorprocessing
---
timestamp: 0
transition:
  id: 0
  label: ''
start_state:
  id: 15
  label: errorprocessing
goal_state:
  id: 1
  label: unconfigured
---

System Information

I'm using:

• Ubuntu 20.04
• Latest version of the PPA packages of ROS Foxy.

Any pointers?

Ah, yoiu're right! Nice catch! Do you want to form it into an answer? I'd be happy to approve it

No transition matching 3 found for current state I'm looking at the ros2 lifecycles demo here: https://github.com/ros2/d

No transition matching 3 found for current state I'm looking at the ros2 lifecycles demo here: https://github.com/ros2/d

I’m interested in using the ROS 2 variant of the navigation stack for a simple navigation task, namely, follow a given nav_msgs::Path without caring about obstacle avoidance or anything else.

The repository I'm looking at is: https://github.com/ros-planning/navig...

Are the tools needed for this task already ported to ROS 2? After going through bits of the ROS 1 documentation, it seems that move_base would be the component to use, but AFAIK, that is not ported to ROS 2. Anything I’m missing? What would you suggest for the application at hand?

Generating roslaunch documentation Since indigo, roslaunch args have a doc attribute for adding documentation to each on

I don't really understand what this parameter represents or how does the algorithm use it? Any more insight? Why would t

What's the parameter/setting that specifies how far backwards though?

I'm in the middle of migrating a ROS1 app of mine to ROS2 and I'm currently trying to convert a .launch file to a python script.

I want to be able to pass a command line argument to the script and then get its value in the generate_launch_description call.

This is how I currently pass extra arguments to the LaunchDescription:

run_rqt_arg = DeclareLaunchArgument(name="run_rqt",
                                    default_value="True",
                                    description="Launch RQT?")
run_rviz_arg = DeclareLaunchArgument(name="run_rviz",
                                     default_value="True",
                                     description="Launch RVIZ?")

if run_rqt:
    rqt = Node(...)
    l.append(rqt)
if run_rviz:
    rviz = Node(...)
    l.append(rviz)

return LaunchDescription(l, run_rqt, run_rviz)

I'm running the launch script via ros2 launch ...

Is the passing of extra arguments handled correctly? How do I fetch the values of these cli args at runtime?