Open mattyoung101 opened 4 years ago
@ethanol20924 Procedure for debugging:
ENABLE_VERBOSE_BT
and flash to the non-broken robot. Observe if it will reconnect to BT and if so what it says in the verbose BT logs. Try and see if any variables (eg ball distance or state name) are changingAt this point, if the robot's not working, power cycle the robot and continue.
It appears this issue only occurs when Bluetooth is running (as it didn't happen any time at nationals when BT was disabled).
Bug we found today (Friday) where the robot will stop responding to the ball completely after some time. Seems not to be a crash, but timing related (e.g. a hang somehow). Teensy LED is not blinking, meaning either it's frozen or we on the ESP are failing to give it Protobuf packets (as UART waits until it receives a packet). Maybe time out on the Teensy if waiting for too long for a new packet?