Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/stack-of-tasks/talos-data
TALOS robot data for the Stack-Of-Tasks
https://github.com/stack-of-tasks/talos-data
Last synced: 3 days ago
JSON representation
TALOS robot data for the Stack-Of-Tasks
- Host: GitHub
- URL: https://github.com/stack-of-tasks/talos-data
- Owner: stack-of-tasks
- License: lgpl-3.0
- Created: 2019-01-30T13:49:37.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2024-10-21T21:13:06.000Z (21 days ago)
- Last Synced: 2024-10-22T16:29:37.150Z (20 days ago)
- Language: CMake
- Size: 7.17 MB
- Stars: 1
- Watchers: 12
- Forks: 8
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- Changelog: NEWS
- License: LICENSE
Awesome Lists containing this project
- awesome-legged-locomotion-learning - URDF - 3.0 | ✔️ | ✔️ | ✔️ | (Robot models / Humanoids)
- awesome-robot-descriptions - URDF - robotics/talos_robot/tree/kinetic-devel/talos_description), [MJCF](https://github.com/google-deepmind/mujoco_menagerie/tree/main/pal_talos) | LGPL-3.0, Apache-2.0 | ✔️ | ✔️ | ✔️ | (Robot Descriptions / Humanoids)
README
# Talos_data
[](https://gitlab.laas.fr/stack-of-tasks/talos_data/commits/master)
[](https://gepettoweb.laas.fr/doc/stack-of-tasks/talos_data/master/coverage/)
[](https://github.com/psf/black)
[](https://results.pre-commit.ci/latest/github/stack-of-tasks/talos_data)
## Introduction
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.
If you have problem in starting the robot in a specific position you should look at the
[python section](#python)
## 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
```
## Flexibilities
To start the flexibilities:
```
roslaunch talos_data talos_gazebo.launch enable_leg_passive:=true
```
You should see in the robot model two new links:
```
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
```
leg_${prefix}_1_joint_passive
970.0
0.0
```
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
*kp* and *kd*.
The name of the joint to which this apply is specified by the field
*joint_spring*.
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.
Finally to have the state of the joint in the topic */joint_states* you need to add the following lines:
```
transmission_interface/SimpleTransmission
1.0
hardware_interface/PositionJointInterface
hardware_interface/EffortJointInterface
```
This is telling to ros_control that the passive joint has Position and Effort interfaces.
## Python for launching nodes
In the directory scripts you can start a complete simulation by doing:
```
./start_talos_gazebo.py
```
In this specific case it will start the robot with a wide base.