Control API functions description » History » Version 1
Kévin Desormeaux, 2021-06-11 16:29
1 | 1 | Kévin Desormeaux | h1. Control API functions description |
---|---|---|---|
2 | |||
3 | h2. Launching the controllers |
||
4 | |||
5 | This is done by simply using a launch file once the ROS environment is set. |
||
6 | These launch files are located in the launch directory of the CM2C package. |
||
7 | |||
8 | <pre> |
||
9 | So if kukarm is operating panda_1 run: |
||
10 | roslaunch admittance_joint_trajectory_controller panda_1.launch |
||
11 | |||
12 | and this on truyere: |
||
13 | roslaunch admittance_joint_trajectory_controller panda_2.launch |
||
14 | </pre> |
||
15 | |||
16 | * |
||
17 | Important:* These launch files are not identical, and the panda_1.launch must be launched before the panda_2.launch. |
||
18 | Once the controllers are running there is nothing else to do regarding the control side and you can launch the planning stack and refer to the planning API. |
||
19 | |||
20 | h2. Utilities and control API outside of the Cooperative Manipulation scope |