Skip to content
Snippets Groups Projects
README.md 2.71 KiB
Newer Older
Olivier Stasse's avatar
Olivier Stasse committed
Talos_data
==========

## Introduction

Olivier Stasse's avatar
Olivier Stasse committed
This repository is dedicated to use the TALOS robot with the stack-of-tasks.

Specific data were generated to account to some specific problems when generating/planning motion
with the SoT.

For instance in order to avoid using xacro (with ROS) plain URDF were recorded.

Some dummy data were added (rotor inertia) to help the dynamic regularization.

For initial and data validated by PAL-Robotics please see the http://github.com/pal-robotics/talos_robot
repository.
Olivier Stasse's avatar
Olivier Stasse committed

## Fixed joint
To start the robot in the air you can use:
```
roslaunch talos_data talos_gazebo.launch enable_fixed_robot:=true
```

## Straight robot
To start the robot straight (i.e. not in half-sitting) you can use:
```
roslaunch talos_data talos_gazebo.launch starting_half_sitting:=false
```

Olivier Stasse's avatar
Olivier Stasse committed
## Flexibilities

To start the flexibilities:
```
roslaunch talos_data talos_gazebo.launch enable_leg_passive:=true
```

Olivier Stasse's avatar
Olivier Stasse committed
You should see in the robot model two new links:
Olivier Stasse's avatar
Olivier Stasse committed
```
leg_left_1_link_passive
leg_right_1_link_passive
```
and two new joints
```
leg_left_1_joint_passive
leg_right_1_joint_passive
```

They are updated by the plugin in the src directory:
```
src/SpringPlugin.cc
```

This plugin is specified in the file:
```
urdf/leg/leg.urdf.xacro
```
by the following lines
```
    <gazebo>
      <plugin filename="libSpringPlugin.so" name="spring_leg_${prefix}_1_joint_passive">
        <joint_spring>leg_${prefix}_1_joint_passive</joint_spring>
        <kp>970.0</kp>
        <kd>0.0</kd>
      </plugin>
    </gazebo>
```

You can create new joints by expanding the robot kinematic tree
and adding the same lines in the xacro files.

The spring constants are modified by the associated fields
Olivier Stasse's avatar
Olivier Stasse committed
*kp* and *kd*.
Olivier Stasse's avatar
Olivier Stasse committed
The name of the joint to which this apply is specified by the field
Olivier Stasse's avatar
Olivier Stasse committed
*joint_spring*.
Olivier Stasse's avatar
Olivier Stasse committed

The plugin is generating a torque based on the actuator state using:
$$\tau = - kp q - kd \dot{q}$$ where $q$ is the actuator position and $\dot{q}$
is the actuator velocity.

This might be changed in the future to cope with a different equilibrium point.

Olivier Stasse's avatar
Olivier Stasse committed
Finally to have the state of the joint in the topic */joint_states* you need to add the following lines:
Olivier Stasse's avatar
Olivier Stasse committed
```
    <transmission name="leg_${prefix}_1_passive_trans">
      <type>transmission_interface/SimpleTransmission</type>
      <actuator name="leg_${prefix}_1_motor" >
        <mechanicalReduction>1.0</mechanicalReduction>
      </actuator>
      <joint name="leg_${prefix}_1_joint_passive">
        <hardwareInterface>hardware_interface/PositionJointInterface</hardwareInterface>
        <hardwareInterface>hardware_interface/EffortJointInterface</hardwareInterface>
      </joint>
    </transmission>
```

This is telling to ros_control that the passive joint has Position and Effort interfaces.