I have been facing problems when using the new pathplanner update, when I create my autochosser all the paths already made on my computer appear, while the ones I declare in my code never appear, in addition to the fact that none of the paths make sense in relation to how they are made in pathplanner, the fact that this could be happening is the factor that I use pathplanner 2025 in WPILib 2024, but I’m not sure about this, has anyone else experienced this?
Is the auto chooser built by AutoBuilder.buildAutoChooser() ?
If so, it will only contain all the autos that you’ve written in the PathPlanner GUI. If you have custom autos declared in the code, you can use addOption() to add that to the auto chooser.
1 Like
I was built by AutoBuilder.buildAutoChooser(), but it contains all the paths that I have already created on my computer, even deleting the old files they still appear in my autonomous selector, could you explain to me how this addoption() works please?
Have you looked in the deploy folder on the Rio? I haven’t checked to see the behavior after delete, but files from the deploy folder are copied onto the Rio (and might not be deleted automatically).
If they’re not auto-deleted, the Rio will still be able to enumerate them from its local filesystem.
Look in /home/lvuser or at the docs for Filesystem.
If you need me to look on my own Rio for more specifics, I can, but not until this evening.
Edit to add: SSH instructions to log into the RoboRio:
If buildAutoChooser doesn’t work, you could also try doing your own autochooser by making a SendableChooser and selecting which autos you want to put in.
I see the files, thanks for the help, I solved the sendableChosser problem with Addoptions, but I’ll look into it.
1 Like