[FTC]: Prevent Burnt Motors - Updated RobotC Joystick Driver

[normalmutant]

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.

Advantages:
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 website post.

[l0jec]

First off, thank you for taking the initiative on this. A simple fix was long overdue. I took a quick look at your code and from a glance it looks like it should work, but I would like to compare against the original once I get home to really review the changes.
Regardless, I think you have the right idea and ask if it isn't too much, could you also post this to the ROBOTC forums for additional feedback/visability? If we can test & review this code change as a community, then I think we should be able to follow-up with FIRST to update the official JoystickDriver.c in the next release of ROBOTC.

[emmell]

Originally Posted by l0jec

Regardless, I think you have the right idea and ask if it isn't too much, could you also post this to the ROBOTC forums for additional feedback/visability? If we can test & review this code change as a community, then I think we should be able to follow-up with FIRST to update the official JoystickDriver.c in the next release of ROBOTC.

FIRST doesn't do anything with the ROBOTC code, Carnegie Mellon does. I agree with the poster to give your feedback directly to CMU (on the robotc.net forum is perfect). They would be the ones to address any changes to the software and updates that would come out in future versions.

Thank you, Say Watt, for the research and updates.

[Eric-SayWatt]

I've already contacted the RobotC people with this fix, however, I'll post it to the forums there as well.

Please let us know if you have any other suggestions, or if you see any problems with the code.

[Longrange97]

it looks like the download link on your website is broken. would you mind providing a new link?