Skip to content

fixed bug torque_controller#45

Open
jorgediosdado wants to merge 1 commit intoarebgun:masterfrom
jorgediosdado:master
Open

fixed bug torque_controller#45
jorgediosdado wants to merge 1 commit intoarebgun:masterfrom
jorgediosdado:master

Conversation

@jorgediosdado
Copy link
Copy Markdown

Torque controller was using the function set_speed, instead of set_goal_torque.

@dbolkensteyn dbolkensteyn mentioned this pull request Jan 13, 2017
def set_torque_enable(self, torque_enable):
mcv = (self.motor_id, torque_enable)
self.dxl_io.set_multi_torque_enabled([mcv])
self.dxl_io.set_multi_torque_enabled([mcv])
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

useless change


def process_command(self, msg):
self.set_speed(msg.data)
self.set_goal_torque(msg.data)
Copy link
Copy Markdown
Contributor

@dbolkensteyn dbolkensteyn Jan 13, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like this is a feature, not a bug.
Step 4 of the torque mode tutorial clearly states To actually move the motor we need to publish a desired velocity to /pan_controller/command (the keyword being velocity).

Moreover this change breaks compatibility for existing users: it is probably safer to change the name of this controller from torque to velocity and add a new one that really controls the torque.

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 this pull request may close these issues.

2 participants