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

No updates for Pos, Vel, Accel during trajectory execution / motor movement #355

Open
marcomasa opened this issue Apr 25, 2022 · 2 comments

Comments

@marcomasa
Copy link

  1. How to setup:

Use the trajectory callback in the dynamixel_workbench_controllers node.

  1. Which Dynamixel have you used? and how many? (Please describe below format to all connected Dynamixels)

    • Model Name: MX-106

    • ID 1 & 2

    • Baud Rate of Dynamixels: 1Mbps

    • Protocol Version: 1

  2. Write down the commands you used in order:

I am using custom launchfiles,
so i guess they wont be of any use for you.
Most params are the default ones, but i will post some here:

<rosparam>
      publish_period: 0.01             <!--value for periods has to be in the intervall t = [0.1; 0.00032] borders are unstable-->
      dxl_read_period: 0.01
      dxl_write_period: 0.0004
      use_moveit: false
      use_joint_states_topic: true
      use_cmd_vel_topic: false
    </rosparam>
  1. Please, describe detailedly what difficulty you are in

I am getting new messages in the joint_state topic, but they contain the values of the initial position.
This causes pointclouds etc. to be stuck in that reference frame when doing scans with custom built robot arms using dynamixel motors.
How can i enable the motor data update during the movement / trajectory execution?

@marcomasa
Copy link
Author

Updating the motors to FW 2.0 did not help either.

@marcomasa
Copy link
Author

Also, the dynamixel_state topic shows empty messages during motor movement

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

Successfully merging a pull request may close this issue.

1 participant