Open alaurenzi opened 4 years ago
Ok, on this I would suggest a first modification from the original urdf.
As was done before you basically need a revolute
joint with qmin = qmax = 0
. This is not convenient... Instead when adding a force torque sensor is possible to specify a pose wrt an existing revolute joint, the following example is for COMAN+.
<gazebo reference="LAnkleRoll">
<sensor type="force_torque" name="l_leg_ft">
<force_torque>
<frame>sensor</frame>
<measure_direction>child_to_parent</measure_direction>
</force_torque>
<always_on>true</always_on>
<visualize>true</visualize>
<update_rate>1000</update_rate>
<pose>0 0 -0.035 0 0 0</pose> <!-- check! -->
</sensor>
</gazebo>
Here LAnkleRoll
is a proper joint of the urdf. I would suggest to follow this more standard way to implement it. What do you think?
I agree. For now, I have put the ft joint fixed to be able to run the framework without errors.
We can keep the ft joint fixed and attach a frame which will be useful to associate ft measurements also in the real robot.
The
centauro.urdf
file (which should be the URDF to use for control) contains revolute jointsj_ft_1
, ..., withqmin = qmax = 0
which are probably used for FT simulation purposes.