eeros_architecture:control_system:available_blocks:pathplannercubic
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| eeros_architecture:control_system:available_blocks:pathplannercubic [2017/12/12 12:12] – [Parameters] graf | eeros_architecture:control_system:available_blocks:pathplannercubic [2020/09/03 08:58] (current) – ursgraf | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Path Planner Cubic ====== | ====== Path Planner Cubic ====== | ||
| - | A path planner | + | This path planner |
| < | < | ||
| // | // | ||
| Line 8: | Line 8: | ||
| 2.4000000e-01 | 2.4000000e-01 | ||
| </ | </ | ||
| + | The jerk within the second interval is 1e4 while the acceleration, | ||
| + | [{{ : | ||
| + | |||
| + | The trajectory file is loaded with | ||
| + | <code cpp> | ||
| + | init(filename); | ||
| + | </ | ||
| + | where '' | ||
| \\ | \\ | ||
| - | A path planner block has four output signals - jerk, acceleration, | + | When calling |
| - | ===== Parameters ===== | + | <code cpp> |
| - | TODO | + | move(startPos); |
| + | </ | ||
| + | you dispatch a new trajectory. The trajectory is taken from the path file, no scaling is made. The trajectory starts from '' | ||
| + | \\ | ||
| + | You can also call | ||
| + | <code cpp> | ||
| + | move(time, startPos, deltaPos); | ||
| + | </ | ||
| + | This will take the trajectory from the file and scale it so that it starts at '' | ||
| - | ===== Miscellaneous ===== | ||
| - | As soon as a client connects to a socket server a connection is up and running until either one of them stops. It is possible to stop the server or the client and restart it subsequently. In both cases a new connection will be established. \\ | ||
| - | As long as the connection is not yet open the '' | ||
eeros_architecture/control_system/available_blocks/pathplannercubic.1513077161.txt.gz · Last modified: 2017/12/12 12:12 (external edit)