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

Make components more resilient to failure #141

Open
obj-obj opened this issue Mar 24, 2022 · 1 comment
Open

Make components more resilient to failure #141

obj-obj opened this issue Mar 24, 2022 · 1 comment

Comments

@obj-obj
Copy link
Contributor

obj-obj commented Mar 24, 2022

  • Read from two sensors instead of one (to account for misreading or one coming unplugged)
  • Have mid-match manual overrides for all sensors so the robot keeps functioning when they fail (e.g. if the sensors are stuck in the 'ball detected' state, have a way to override so the index & intake motors are stuck in the stopped state).
  • Filter Limelight data to throw out obvious outliers
  • Have mid-match manual override / configuration in case the limelight starts mis-tracking. It's possible to score with the hood, turret & shooter at fixed values. It's nearly impossible to score when they all randomly jump around.
  • Cross-check data from multiple sources (e.g. ignore limelight changes if it says we moved an order of magnitude further than the drivebase encoders say we moved)
  • Read pneumatic pressure and if it's consistently at or near 0, turn off the compressor to save power since we likely disconnected a tube somewhere
@obj-obj
Copy link
Contributor Author

obj-obj commented Mar 24, 2022

  • Limelight connected over laptop during field calibration
  • Codriver controller for presets
  • More auto-modes and naming
  • Reduce CAN
  • Data logging on device
  • Make shuffleboard not scuffed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant