Skip to content

Conversation

IanTheEngineer
Copy link
Contributor

@IanTheEngineer IanTheEngineer commented Sep 27, 2016

JointCommand associated with JointPlugin interface update. This change moves away from a generic command field and towards individual position, velocity, acceleration, effort fields, to be updated per command mode:

  • position --> (radians) Required for POSITION_MODE and TRAJECTORY_MODE
  • velocity --> (rad/sec) Required for VELOCITY_MODE and TRAJECTORY_MODE
  • acceleration --> (rad/sec^2) Required for TRAJECTORY_MODE
  • effort --> (newton-meters) Required for TORQUE_MODE


int32 mode # Mode in which to command arm

string[] names # Joint names order for command
Copy link
Contributor

Choose a reason for hiding this comment

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

It might be good to specify if only a subset of the joints can be sent.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah, interesting point. The way the interface is written, you can specify any subset of joints and default values will be commanded for every non-specified joint as follows:

Position Mode: default is currently commanded position
Velocity Mode: default is 0.0 velocity
Torque Mode: default is currently commanded torque
Trajectory Mode: default is currently commanded position, 0.0 velocity and 0.0 acceleration

@IanTheEngineer
Copy link
Contributor Author

Merging for now, but I've opened a ticket to better document the Mode / command units.

@IanTheEngineer IanTheEngineer merged commit 26effbf into development Sep 27, 2016
IanTheEngineer added a commit to RethinkRobotics/intera_sdk that referenced this pull request Sep 28, 2016
Updates the Limb interface to utilize the
new TRAJECTORY_MODE in intera_core_msgs. This
new mode is a reworked RAW_POSITION_MODE but
requires Position, Velocity, and Acceleration
commands to execute a Trajectory.

The other modes (Position, Velocity, Torque)
now require commands to be populated in their
respective fields within the JointCommand msg.

Additionally, slight optimization in the JTAS
to execute commands strictly in the mode commanded.

Depends on
RethinkRobotics/intera_common#7
@IanTheEngineer IanTheEngineer deleted the joint_command branch October 3, 2016 19:53
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