Prevent Burnt Motors Upon Disconnect
Ever disconnected from Samantha and burnt out motors? We from Say Watt?, along with other teams in our area, have experienced it multiple times. We saw that it was a big problem, so we set out to find a solution. After some digging, we discovered that the JoystickDriver.c that all teams using RobotC dutifully include in all of their code is the real source of the problem. We created an updated joystick driver that fixes this problem.
1) It is extremely simple for new teams to integrate. It involves changing exactly one line of code.
2) It picks up again the moment the robot is reconnected.
3) It refrains from adding additional tasks and calculations to the code, causing additional lag. It simply increments a variable.
4) It works for every connection type, even Bluetooth.
In essence, this is a very simple solution that can be put to use in less than a minute by teams of any level.
To see our solution explained or download the updated Joystick driver, go to our blog post