After experiencing electrolysis during an experiment, the DropBot stops responding to actuation requests:
I think this is probably a result of exceeding the current limit. Functionality can sometimes be restored by unplugging/plugging in the DropBot's USB (and power cable?) or by running the "short detection" test; however, I would expect a more useful error to be presented to the user when one of these "faults" occur.
After experiencing electrolysis during an experiment, the DropBot stops responding to actuation requests:
I think this is probably a result of exceeding the current limit. Functionality can sometimes be restored by unplugging/plugging in the DropBot's USB (and power cable?) or by running the "short detection" test; however, I would expect a more useful error to be presented to the user when one of these "faults" occur.