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

[Question]: python_ros2_api/joint_trajectory_control.py #152

Open
bestrobotplans opened this issue Jan 8, 2024 · 1 comment
Open

[Question]: python_ros2_api/joint_trajectory_control.py #152

bestrobotplans opened this issue Jan 8, 2024 · 1 comment
Assignees
Labels
manipulators Issues related to manipulators question Further information is requested

Comments

@bestrobotplans
Copy link

Question

Hello!

I am running a copy of the file python_ros2_api/joint_trajectory_control.py in simulation. I start up the simulation by:
ros2 launch interbotix_xsarm_control xsarm_control.launch.py robot_model:=wx250s use_sim:=true
The I run python3 joint_trajectory_control.py in the relevant folder.

I was expecting the output to be a three-part movement trajectory (ignoring the go to home pose and go to sleep parts). Yet I only seem to get a single movement corresponding to {6.0: [-0.5, 0.0, 0.0, 0.0, 0.5, 0.0]}. The robot also only changes behaviour when I change {6.0: [-0.5, 0.0, 0.0, 0.0, 0.5, 0.0]}. Edits to any other component of the trajectory list have no effect.
There is also a weird jumpy jerk in the simulation after the end of go_to_home_pose.

Am I using the program wrong or is this the correct behaviour?
How do I make an n-part trajectory if edits to the trajectory variable have no effect besides at the final entry of the list?

Some further tips would be great, thank you!

Robot Model

wx250s simulation

Operating System

Ubuntu 20.04

ROS Version

ROS 2 Galactic

Additional Info

No response

@bestrobotplans bestrobotplans added manipulators Issues related to manipulators question Further information is requested labels Jan 8, 2024
@lukeschmitt-tr
Copy link
Member

Thanks for reporting this. It does seem like a bug in the XS Simulation. We'll look into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
manipulators Issues related to manipulators question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants