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

jdlangs's profile - activity

2023-07-24 11:56:04 -0500 commented question ros2_control: No parameter file provided. Configuration might be wrong. failed to parse input yaml file(s)

Can you include the full terminal output which shows the command you ran and the error?

2023-07-20 15:32:35 -0500 commented answer ROS 2 Variables Substitution Inside YAML

Isn't that key a node namespace? Why not use the namespace argument for launch_ros.actions.Node (which can be substitute

2023-07-20 10:15:29 -0500 answered a question ROS 2 Variables Substitution Inside YAML

I'm not sure if doing a substitution in the yaml parameters file is possible. However, you should be able to load a defa

2023-07-20 10:15:29 -0500 received badge  Rapid Responder (source)
2023-07-19 09:51:38 -0500 answered a question I'm confused with callback_groups and threads

Looking at the additional info posted, I think your second design more-or-less makes sense. You should not use spin thou

2023-07-19 09:51:38 -0500 received badge  Rapid Responder (source)
2023-07-18 13:19:28 -0500 commented question I'm confused with callback_groups and threads

Can you provide the full program context? How is retrieve_value being run?

2023-06-07 11:18:08 -0500 received badge  Nice Answer (source)
2023-06-02 11:54:18 -0500 commented answer Colcon select Python version

Thanks for the log info, that cleared things up quite a bit. It would have been nice to have that pasted from the start.

2023-06-02 11:45:09 -0500 edited answer Colcon select Python version

Based on the log information, it's clear this is unrelated to colcon; it's CMake that's finding the wrong version of pyt

2023-05-31 08:57:33 -0500 commented answer Colcon select Python version

Perhaps you can post more details/logs on how you know a different python version is involved?

2023-05-25 09:55:56 -0500 commented answer Colcon select Python version

That would indicate your python command points to a 3.11 version, which you can double check with python --version. So y

2023-05-19 14:14:55 -0500 received badge  Rapid Responder (source)
2023-05-19 14:14:55 -0500 answered a question Colcon select Python version

Colcon doesn't "select" a python version. Like all python tools, it uses the version of the environment it was installed

2023-03-20 16:54:37 -0500 answered a question Getting error: ‘operator()’ is not a member of ‘void while creating a service

The create_service function expects a pointer to a callback that takes two arguments: request and response. But you're p

2023-03-15 03:07:00 -0500 marked best answer Long compile time for ROS2 interface package

I'm prompted to ask this because I just tried changing a single name in a single service of a *_msgs package and it took colcon over 2 minutes to recompile. I don't have a amazingly fast laptop and it is a relatively large package (~50 interfaces) but this seems like an awfully long time to have to wait for any source change at all.

My understanding of the details of the interface generation process is fairly limited. Would anyone be able to shed some light on what's going on under the hood and where all this time is getting eaten up?

2023-03-13 16:54:36 -0500 commented answer Getting a Node::SharedPtr from "this"

@swiz23 Looks like I phrased it badly. The object does exist from the time the constructor body starts since initializat

2023-01-12 14:19:43 -0500 received badge  Great Answer (source)
2022-12-20 09:04:47 -0500 received badge  Famous Question (source)
2022-08-18 00:08:29 -0500 marked best answer Proper runtime executable install location

I thought I'd ask for official clarification here because I've seen conflicting information from different sources. Until recently, I understood that we should be placing node executables under lib/${PROJECT_NAME} via the RUNTIME category of the CMake install command. This seems like the only place ros2 run and ros2 launch find them.

However, after doing some Windows development, I discovered shared libraries (.dlls) have to go under bin/ in the install space, and they also fall under the RUNTIME category. This is also recommended by the current ament_cmake documentation.

So what is the proper thing to do here? Is everything shifting to being installed under bin/ and the ros2 commands need to be updated to see those files? Or is the expectation now that executable and library targets should always be installed with separate install() commands into the two different places?

2022-08-18 00:07:26 -0500 received badge  Nice Question (source)
2022-07-13 06:27:47 -0500 received badge  Favorite Question (source)
2022-07-09 17:43:33 -0500 received badge  Good Answer (source)
2022-05-25 12:27:11 -0500 commented question rviz2 not loading "Entry Point Not Found"(Windows)

@ncr7 did you resolve this? I'm having similar startup issues with rviz2.

2022-05-23 11:30:16 -0500 answered a question Install ROS2 packages at specified location - source build

colcon provides an --install-base option that will place the installed files anywhere in the filesystem. Be careful with

2022-05-18 23:18:47 -0500 received badge  Good Answer (source)
2022-02-27 02:44:36 -0500 received badge  Famous Question (source)
2022-02-24 11:06:13 -0500 marked best answer No stdout logging output in ROS2 using launch

Hi all,

I am unable to see any logging output from stdout when using ros2 launch, and I need some help figuring out what's going on / if this is expected. For example this cpp file:

int main(int argc, char** argv)
{
  rclcpp::init(argc, argv);
  auto node = std::make_shared<rclcpp::Node>("a_test_node");

  RCLCPP_DEBUG(node->get_logger(), "test log debug");
  RCLCPP_INFO(node->get_logger(), "test log info");
  RCLCPP_WARN(node->get_logger(), "test log warn");
  RCLCPP_ERROR(node->get_logger(), "test log error");

  rclcpp::spin(node);

  return 0;
}

and this launch file:

import launch
import launch_ros.actions

def generate_launch_description():
    return launch.LaunchDescription([
        launch_ros.actions.Node(
            package='test_pkg',
            node_executable='test_node',
            node_name='test_node',
            output={
                'stdout': 'screen',
                'stderr': 'screen',
            }
        ),
    ])

only outputs:

jlangsfeld@swri-jlangsfeld-thinkpad-T560:~/Workspaces/ros2$ ros2 launch test_pkg log_test.launch.py
[INFO] [launch]: All log files can be found below /home/jlangsfeld/.ros/log/2019-09-11-13-45-19-657412-swri-jlangsfeld-thinkpad-T560-18153
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [test_node-1]: process started with pid [18163]
[test_node-1] [WARN] [test_node]: test log warn
[test_node-1] [ERROR] [test_node]: test log error

I've tried other output options too with no luck. For example, using own_log for both stdout and stderr means separate log files are created but the stdout one always is completely empty. Any thoughts / suggestions?

Thanks, Josh

2022-02-08 10:35:26 -0500 edited answer ROS2 Topic Subscription Using Lambda Funtction

You didn't include any error output in your question (please always do this) but I'm guessing you got some very cryptic

2022-02-08 10:34:37 -0500 answered a question ROS2 Topic Subscription Using Lambda Funtction

You didn't include any error output in your question (please always do this) but I'm guessing you got some very cryptic

2022-01-03 10:46:15 -0500 commented question ROS 2 nodes created inside libraries, good practice?

It could vary, so I'm interested in what factors to make the decision on. On one end, it might be something like an obje

2021-12-18 10:28:23 -0500 received badge  Notable Question (source)
2021-12-16 23:30:22 -0500 received badge  Popular Question (source)
2021-12-14 14:38:06 -0500 asked a question ROS 2 nodes created inside libraries, good practice?

ROS 2 nodes created inside libraries, good practice? In porting stuff to ROS2, I'm often faced with the problem of what

2021-11-03 16:40:41 -0500 received badge  Good Answer (source)
2021-10-05 12:03:34 -0500 commented question ros2 launch urdf_tutorial demo.launch.py malformed launch argument 'demo.launch.py', expected format '<name>:=<value>

Can you copy/paste from your terminal the full set of commands you are trying to run along with the full error you see?

2021-09-28 11:35:18 -0500 commented question Problem working with vanilla cmake packages as dependencies in caktin_ws

@Mehdi. It would be best if you can step back from trying to analyze and provide more clear direct information about wha

2021-09-24 13:52:00 -0500 commented question Problem working with vanilla cmake packages as dependencies in caktin_ws

There's a lot of confusing details here, can you edit your question to clarify some things? - What is the workspace layo

2021-07-28 04:43:24 -0500 received badge  Nice Answer (source)
2021-07-27 14:45:57 -0500 answered a question Multiple classes that inherit from rclcpp::Node in one executable

If you make two different classes that derive from rclcpp::Node and create instances of both of them then you will have

2021-07-27 14:45:57 -0500 received badge  Rapid Responder (source)
2021-07-14 22:25:04 -0500 received badge  Famous Question (source)
2021-07-09 15:36:05 -0500 received badge  Notable Question (source)
2021-07-05 02:32:21 -0500 received badge  Nice Question (source)
2021-06-15 11:02:37 -0500 received badge  Nice Answer (source)
2021-05-17 10:11:19 -0500 received badge  Famous Question (source)
2021-04-30 17:35:57 -0500 received badge  Nice Answer (source)
2021-04-22 11:11:06 -0500 commented question Why doesn't ROS2 warn me when my interfaces are incompatible?

I've actually had good past experience getting answers to general ROS2 questions here, usually from @William. And it's n

2021-04-22 05:10:39 -0500 received badge  Popular Question (source)