Repository navigation
Replies: 1 comment 2 replies
|
Hey @Alan6458 I cannot seem to reproduce your issue on our 2027_alpha7 phoenix6-examples branch with the Please note that there are many changes between 2026 and 2027. We do not recommend manually modifying your existing code, but instead create a new project (you can base it on the example projects), and manually fix-up then and port your subsystems. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
When using the .getState().Pose from Phoenix 6 SwerveDrivetrain, it always stays the same. This can also be seen in the Phoenix 6 SwerveWithPathPlanner example - when running in simulation, the robot moves in the 2026 version, but does not update its position when simulating the code in the 2027 branch. On my team's robot, it's causing problems by throwing off pose estimates.
Is there a solution for this? I'm currently considering using a separate pose estimator based off the cameras, but it'll take a while to code.
Thanks!
All reactions