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

PlotJuggler in ROS2 Launch file #561

Closed
gurbain opened this issue Nov 8, 2021 · 6 comments
Closed

PlotJuggler in ROS2 Launch file #561

gurbain opened this issue Nov 8, 2021 · 6 comments
Assignees

Comments

@gurbain
Copy link

gurbain commented Nov 8, 2021

Problem description

I am struggling to start plotjuggler in a ROS2 launch file. It seems that starting a Node in a launch file automatically passes the --ros-args argument and plotjuggler does not handle it. Is there a way to circumvent this, while using the Node class of ROS2 launch actions (and not ExecuteProcess)? Thank you!

Steps to reproduce

  • Platform: ROS2 Foxy on Ubuntu 20.04
  • Sample launch file:
from launch import LaunchDescription
from launch_ros.actions import Node

def generate_launch_description():
    node_plot = Node(
        package='plotjuggler',
        executable='plotjuggler')
    return LaunchDescription([node_plot])
  • Behavior:
$ ros2 launch plot plot.launch.py
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [plotjuggler-1]: process started with pid [21577]
[plotjuggler-1] QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
[plotjuggler-1] Unknown option 'ros-args'.
[ERROR] [plotjuggler-1]: process has died [pid 21577, exit code 1, cmd '/opt/ros/foxy/lib/plotjuggler/plotjuggler --ros-args'].
@facontidavide
Copy link
Owner

no, there isn't

@GuihVicentini
Copy link

Hi @facontidavide I know this has been closed, but I am facing the same issue, if there is no solution, what would you advise to do if I would like to launch plotjuggler with a launch file in ROS 2?

@facontidavide facontidavide reopened this Apr 22, 2022
@facontidavide
Copy link
Owner

Will think about this

@facontidavide facontidavide self-assigned this Apr 22, 2022
@frankkusters
Copy link

Might the removeROSArgs() (ROS1) or remove_ros_arguments() (ROS2) functions be of help? As the name says, they remove ROS arguments, allowing the code after it to work without the ROS arguments being in the way.

@facontidavide
Copy link
Owner

I did not know about that. Sound as the right solution

facontidavide added a commit that referenced this issue May 14, 2022
@facontidavide
Copy link
Owner

solution pushed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants