Sometimes the microcontroller on the GPG board gets reset for some unknown reason (for the moment).
While we hunt for the root cause, here are changes that will let the robot behave a bit better when this happens.
The idea is to detect if there was a microcontroller reset that happened while we are in blocking mode, as this is what most of the impacted users are getting as an issue. If a reset has happened, then re-instate the last known values from before the reset and keep going.
While this is a nice way of not leaving the user out to dry, the root cause still needs to be investigated. These changes would then be considered insurance.
Sometimes the microcontroller on the GPG board gets reset for some unknown reason (for the moment).
While we hunt for the root cause, here are changes that will let the robot behave a bit better when this happens.
The idea is to detect if there was a microcontroller reset that happened while we are in blocking mode, as this is what most of the impacted users are getting as an issue. If a reset has happened, then re-instate the last known values from before the reset and keep going.
While this is a nice way of not leaving the user out to dry, the root cause still needs to be investigated. These changes would then be considered insurance.