PathPlanner: Bézier-based motion profiles for FRC autonomous control
PathPlanner generates motion profiles and field maps using Bézier curve path construction, holonomic drive support, event markers, and a Hot Reload workflow. Created by mjansen4857 and aimed at FIRST Robotics Competition teams, it ties a desktop GUI to a robot-side library for execution. Key capabilities include path smoothing, AD* obstacle pathfinding, and real-time telemetry visualization. The design fits student programmers, mentor engineers, and teams that need precise, testable autonomous routines without rebuilding robot code.
What the tool actually builds and how it outputs runnable commands
PathPlanner constructs trajectories with Bézier curves and exports them to the robot via the PathPlannerLib vendor library, which provides bindings for Java, C++, and Python. The GUI lets you place event markers that map to robot commands, and the modular autonomous routine builder assembles multiple paths and command sequences so the robot runs a composed routine rather than a single static trajectory.
How it affects system resources and runtime behaviour
The tool produces paths that the robot follows; telemetry support shows live robot position and path-following accuracy during operation. PathPlanner handles velocity and acceleration constraints and rotation transitions on export, so the generated profiles embed those limits rather than relying on robot-side computation. Real-time telemetry implies a network link during tests, and Hot Reload updates paths over the network without redeploying code.
Is it safe to run on a competition robot and what safety features exist
PathPlanner uses a desktop-to-robot workflow where the library on the robot executes the precomputed profiles; the presence of event markers and command generation means teams can attach safe stop or rollback behaviours inside their robot code. The tool also includes built-in AD* pathfinding to choose obstacle-avoiding routes, which adjusts trajectories before the robot executes them rather than rewriting robot firmware.
Who should adopt it and a practical tip for deployment
PathPlanner suits FRC teams that need finely shaped autonomous motion and want to iterate routes without redeploying robot code. Use the Hot Reload feature during field testing to tune constraints, and keep command handlers defensive so event markers cannot trigger unsafe actions. Recommended.
