-
Notifications
You must be signed in to change notification settings - Fork 1
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
Joint/IMU/Sensor ordering in datagram is documented and frozen #18
Comments
@francesco-romano But what about the joints? I see the limb ordering but that doesn't help me with the joint ordering. I can assume that the joints will follow the kinematic chain as defined in the SDF and then I just go limb by limb in that order but I just want to make sure that a.) that is a good assumption, and b.) it isn't going to change randomly. |
We are going to document the joint order properly, but as a working pointer the joint order is defined in https://github.com/robotology-playground/ihmc-ors-yarp/blob/master/robots/icubGazeboSim/launch-bridgeihmcors-sim.xml#L37 . |
@francesco-romano @traversaro Are those the only joints that are published/controllable? That list seems to exclude the wrist and neck joints. |
Those are the joints that support torque control. We can add also the wrist/neck joints, but we can't control those one in torque control mode. |
@traversaro We'll definitely at least need them for feedback, at the very least the neck. Control over them would also be nice, maybe just reject the command if the mode is set to TORQUE on the receiving side for those joints? And we'll just try to be extra sure that we only send position commands to those joints. Our control architecture can handle setups where some joints are position controlled no problem. |
Ok, I can easily add those joints to the exposed joints. |
We now have robot feedback working in our software. But we (intentionally) defined an IDL that does not have identifiers for the different sensors because of payload overhead.
We just need to establish what order the joints, IMUs, and F/T sensors are serialized and know that ordering and treat it as convention.
The text was updated successfully, but these errors were encountered: