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

ModelNotFoundError: No Module named xacro #1

Open
Vasanth28897 opened this issue Mar 25, 2022 · 3 comments
Open

ModelNotFoundError: No Module named xacro #1

Vasanth28897 opened this issue Mar 25, 2022 · 3 comments

Comments

@Vasanth28897
Copy link

Hi,
When i try to run the "ros2 launch urdf_example rsp.launch.py" it executes the error like this
"raise InvalidLaunchFileError(extension, likely-errors=exceptions) launch.invalidlaunch_file_error.InvalidLaunchFileError : Caught exception when trying to load file of format [py]: No module named 'xacro'.".
Don't know how to rectify this.

Thanks in Advance.

@joshnewans
Copy link
Owner

Hey, sorry I haven't responded to your other issue yet, it's been on my to do list (have you had any luck with it?)

For this one, you probably need to run sudo apt install ros-foxy-xacro (or if not using foxy, whatever ROS distro you have.
I think this was mentioned in one of the videos somewhere but it's definitely easy to miss :)

@Vasanth28897
Copy link
Author

Vasanth28897 commented Mar 25, 2022 via email

@joshnewans
Copy link
Owner

So regarding the first issue, are you saying that you have it currently working in Gazebo, control works using rqt_robot_steering, but teleop_twist_keyboard is reporting Waiting for subscriber to connect to /cmd_vel? And this is all definitely running under ROS 2 now? That is very odd indeed.

The first thing I would suggest is to open a second terminal and run ros2 topic echo /cmd_vel then start pressing the keys in the teleop window to see whether anything is coming through. Beyond that I'm not sure so maybe report back once you've tried that and we'll see if we can figure it out.

Regarding the second issue (joint_state_publisher_gui not running), that's also a quite strange. Is the error literally No executable command? I've just not seen that as an output before.
I'd try first closing and reopening your terminal, ensuring you've sourced your ROS installation (and only ROS 2, not ROS 1 - maybe check your bashrc?) and if it still isn't working, copy-paste the exact output here.

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

2 participants