jcorcoran
commented
2 years ago Test off nominal conditions.
Verify the color sensor and teensy can be unplugged/replugged and not cause problems code execution / ball intaking/firing.
Worst case should be that we don't poop balls.
We don't ever want to be in a scenario where a failed colorsensor/teensy causes:
- problems with normal rio/robot code execution
- inability to collect/fire balls
Before south florida, the pooper was pooping the wrong colored balls.
It also seemed to have significant latency between a ball being present in front of the sensor, and the color being reported on the dashboard (~0.5s). I'm not sure if this time delay was on the teensy or rio side of the interface, but certainly wouldn't be helpful in the scenario where we are trying to automatically eject a ball.