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.

Sign up for GitHub

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

Jump to bottom

Robots stop responding after some time #3

Open
mattyoung101 opened this issue Oct 5, 2019 · 2 comments
Open

Robots stop responding after some time #3

mattyoung101 opened this issue Oct 5, 2019 · 2 comments
Assignees
@mattyoung101
Labels
Medium Priority Annoyances which will make the robot better if fixed
Milestone
Nationals

Comments

@mattyoung101
Copy link
Owner

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?
@mattyoung101 mattyoung101 added the High Priority Showstopping bugs that must be fixed label Oct 5, 2019
@mattyoung101 mattyoung101 self-assigned this Oct 5, 2019
@mattyoung101 mattyoung101 added this to the Nationals milestone Oct 5, 2019
@mattyoung101
Copy link
Owner Author

@ethanol20924 Procedure for debugging:

  1. Record which robot and which mode it's in. Also useful is rough estimate of time since bug last occurred and a description of what the robot was doing leading up to the bug (e.g. if it switched).
  2. Wait for a minute and observe if it reboots or not.
  3. Turn on 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 changing
  4. Press the reset button on the robot and see what it does. Also see if it changes states in verbose BT log after button is pressed.
  5. See if Teensy light is blinking (usually not, but just interested to see)
  6. Press reset button on ESP and see if it will work again.

At this point, if the robot's not working, power cycle the robot and continue.

@mattyoung101 mattyoung101 added Medium Priority Annoyances which will make the robot better if fixed and removed High Priority Showstopping bugs that must be fixed labels Oct 9, 2019
@mattyoung101
Copy link
Owner Author

It appears this issue only occurs when Bluetooth is running (as it didn't happen any time at nationals when BT was disabled).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mattyoung101 mattyoung101

Labels
Medium Priority Annoyances which will make the robot better if fixed
Projects
None yet
Milestone
Nationals
Development

No branches or pull requests
1 participant
@mattyoung101