forked from IDSCETHZurich/re_trajectory-generator
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME
40 lines (33 loc) · 1.22 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
General notes
=============
Generate typekit using the following command:
typegen -o kuka_typekit kuka_typekit lwr_fri/include/friComm.h -t mqueue
We assume that you put your friComm.h header file inside lwr_fri/include.
Documentation can be generated using rosdoc in the trajectory_generator directory
rosrun rosdoc rosdoc trajectory_generator
About the use of the TrajectoryGenerator component
==================================================
Solo Mode
---------
Run the TrajectoryGenerator and visualize the robot maneuvers in rviz
ROS package without connecting it to the real robot.
Procedure:
* roscore
* roslaunch trajectory_generator visualize.launch
* cd trajectory_generator/deploy
* ./runSolo.sh
Then you can run
* rosrun poseToOrocos poseSingle (poseLoop. jntPosSingle, jntPosLoop)
to issue commands to the robot from ROS
FRI Mode
--------
Run the TrajectoryGenerator and visualize the robot maneuvers in rviz
ROS package while sending commands to the real robot via FRIComponent.
Procedure:
* roscore
* roslaunch trajectory_generator visualize.launch
* cd trajectory_generator/deploy
* ./runFRI.sh
Then you can run
* rosrun poseToOrocos poseSingle (poseLoop. jntPosSingle, jntPosLoop)
to issue commands to the robot from ROS