Differences

This shows you the differences between two versions of the page.

--- getting_started:tutorials:pathplanner [2026/05/12 10:26] – ursgraf
+++ getting_started:tutorials:pathplanner [2026/05/12 10:43] (current) – [Rate Limiter] ursgraf
@@ Line 21: / Line 21: @@
 </code>
-The example shows the output of the path planner in the log, with the actual acceleration, velocity and position. The path starts from position (0/0) and later reaches its endpoint at (10/20). After 15s it starts from (15/30) and goes to (-5/20).
+The example shows the output of the path planner in the log, with the actual jerk, acceleration, velocity and position. The path starts from position (0/0) and later reaches its endpoint at (10/20). After 15s it starts from (15/30) and goes to (-5/20).
 ===== Cubic =====
@@ Line 31: / Line 31: @@
 </code>
-The example shows the output of the path planner in the log, with the actual acceleration, velocity and position. The path starts from position (0/0) and later reaches its endpoint at (10/20). After 15s it starts from (15/30) and goes to (-5/20).
+The example shows the output of the path planner in the log, with the actual timestamp, jerk, acceleration, velocity and position. The path is given by //path.txt//.
+===== Rate Limiter =====
+The last example shows the use of a simple [[eeros_architecture:control_system:available_blocks:ratelimiter|]] to generate a rising or falling slope from a step. This can be used as a simple method for path planning, see [[https://github.com/eeros-project/eeros-framework/blob/master/examples/block/RateLimiterTest.cpp|RateLimiterTest.cpp]].
+Open a shell in the build directory of your EEROS library and run
+<code>
+$ ./examples/block/rateLimiterTest1
+</code>
+The example shows the output of the path planner in the log, with the actual position of the step together with the output of the rate limiter. After 1s the path starts from position (0/0) and later reaches its endpoint at (2/3). After 8s it ramps down to (-1/-2).