Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PathPlanner sometimes after deploy has paths that do not follow the written path at all. #459

Closed
PGtheVRguy opened this issue Nov 7, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@PGtheVRguy
Copy link

PGtheVRguy commented Nov 7, 2023

Describe the bug
When deploying paths via the Windows PathPlanner on Windows 10 over ethernet on a swerve based robot, the deploy will be successful, but has strange effects where the robot will move in strange ways, and it is entirely unpredictable when the deploy will do this.

To Reproduce
Steps to reproduce the behavior:
Hit deploy via pathplanner 2023 over Ethernet.

Expected behavior
The path will be deployed and run successfully, but what happens is the path moves in a unpredictable way.

image
This is the path that we run, however our drive coach and I believe that this could be the path not flipping towards the red alliance side. In the video you can see the fault where it runs through the path of 2H, but the bot itself moves into the wrong direction. We also saw this problem before a few comps ago. If needed, I can try and find those videos.
https://www.youtube.com/watch?v=SRZZrRkCh_s
(Watch 7211 on Red Alliance, that is our bot!)

Versions: (please complete the following information):

  • OS: [Windows 10]
  • GUI Version: [2023.4.2]
  • PPLib Version: [2023.4.2] (I think)
  • PPLib Language: [Java]
@PGtheVRguy PGtheVRguy added the bug Something isn't working label Nov 7, 2023
@mjansen4857
Copy link
Owner

Based on the video you linked, this looks like a gyro failure. Notice how it continues to drive backwards robot-relative as it rotates when leaving the community. This indicates that the gyro is probably not working here since the path following commands attempt to drive field relative. Driving field relative without a working gyro essentially just ends up being robot relative.

@PGtheVRguy
Copy link
Author

There's a high chance our gyro could be broken. We've slowly seen this problem grow worst and worst as the competitions have gone on. We'll try looking into gyro problems when we can!

@mjansen4857
Copy link
Owner

Closing since its probably a gyro issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants