MCornelis's profile - activity

Yes, I'm looking for the paper that describes this behaviour in more detail. I can post a link when I find it. It is mor

Yes, I'm looking for the paper that describes this behaviour in more detail. I can post a link when I find it. It is mor

I gave an answer here which explains at a conceptual level how the ROS2 executor works. https://answers.ros.org/questio

The focus for Foxy was to optimize ROS2 and lower CPU overhead. I think the determinism of the Executor is on the roadma

To get an idea of how the ROS2 executor handles callbacks you can have a look at the readme here https://github.com/nobl

The other answer is correct, but I would like to post a more complete global overview of what the executor is doing in t

You can add multiple timers to your node like this (I did it using lambdas, but you can also put the callback somewhere

What is the reason for separating the robots by ROS_DOMAIN_ID? Is it not easier to just name_space the robots and have t

Due to my very limited experience with python+ROS2 I'm not sure if this will help you, or if this will just be a stupid

Due to my very limited experience with python+ROS2 I'm not sure if this will help you, or if this will just be a stupid

Also take into consideration that more nodes -> bigger system. Going from one node to two nodes does not matter much.

If you are in the early stages of development and no hard decisions on ROS versions have been made yet you could also ma

Why is this labeled ROS2 and what is your question?

Jetson TX2 has Quad-Core ARM® Cortex®-A57 MPCore which is an ARMv8-A, so you should be able to install ROS2 binaries dir

I'm not sure I understand your answer. I am aware/heard/read somewhere, that you can write ROS packages in such a way th

I think most of these stderr are quite common when installing ROS2. The ros1_bridge for example will give an error when

The easiest way to get this working however is from 3 terminals. Terminal 1: Source ROS1 environment roslaunch whatever

The easiest way to get this working however is from 3 terminals. Terminal 1: Source ROS1 environment roslaunch whatever

You can simply use ROS1 packages together with ROS2 packages using the ros1_bridge. Make sure to source the ros1 environ

You can simply use ROS1 packages together with ROS2 packages using the ros1_bridge. Make sure to source the ros1 environ

If you want the ros1_bridge to run on the host, then you can only connect to one drone by specifying the ROS master on t

So where do you want to have the ros1_bridge running? What is feasible is to have ROS1 and a minimal ROS2 install with

There was also some talk about work on RCLC, so a C layer sitting on top of RCL, in the RealTime working group on ROS di

You could have a look here https://github.com/micro-ROS/executor_testbench/tree/dashing/rcl_executor . For the implement

Any particular reason to use rcl instead of rclcpp? Could you also clarify what you mean by any message?

Well that depends on the hardware you have. For the most common sensors, drivers will exist that detect the device is co

Simple example to make n nodes that all have 1 subscriber that subscribes to the topic "topic_name": #include <rcl

Nodes also add CPU overhead btw. An explanation can be found here: https://discourse.ros.org/t/reconsidering-1-to-1-mapp

Simple example to make n nodes that all have 1 subscriber that subscribes to the topic "topic_name": #include <rcl

Long answer: Have a look here: https://discourse.ros.org/t/singlethreadedexecutor-creates-a-high-cpu-overhead-in-ros-2/1

Just a heads up, working with CPU utilization is not as straight-forward as some people might think. Especially when dea

Long answer: Have a look here: https://discourse.ros.org/t/singlethreadedexecutor-creates-a-high-cpu-overhead-in-ros-2/1

Currently some work is planned/being discussed to refactor how the executor works in ROS2 for the Foxy release. Discussi

As per request of the questioin poster I'll highlight the answer in the comments that worked for him here: In CMakeList

You can btw also just hit the up-arrow next to a comment. I believe this also gives me karma? You might even be able to

You can btw also make a config folder in one of your packages where you put the .rviz file and then do install(DIRECTOR

A normal colcon build will copy the launch directory to the share directory. So if you then change something in the laun

Are you talking about something like this: Node( package='rosbag2', node_executable=' ', node_