Note: This also applies to any other Dexter 'bot with motors and wheels. (except maybe the GiggleBot).
For the sake of argument, assume I want to play with the Remote Camera Robot code to make it easier to use and less “quirky”. (I’ve noticed some sensitivity quirks - especially after having traveled backwards.)
I would like to investigate this by modifying code and printing out variables, etc., to debug/troubleshoot this issue.
Obviously, I don’t want Charlie running amok while I do this. Also, placing Charlie upside down makes him dizzy and he has a tendency to vomit all over my desk. (just kidding!)
What I would like to be able to do is (somehow) disable the motors from running without disabling the API’s or functionality. IOW, if I command the motors to go “forward”, they would get the command to go “forward”, but just wouldn’t do it.
SparkFun’s micro:bot has a master ON-OFF switch to disable the motors while coding and debugging - which is a stroke of genius, IMHO. Of course, I don’t believe they have encoder feedback either. . . .
Is it possible to include a “motor_enable(bool)” feature that would inhibit all motor activity without having to pull out those pesky six-pin connectors?
Thanks - and a hug for all of you!