Dagu Adventure / Mr.General - Is "turn on all the servos" an error of some sort?
September 26, 2012
So I've gotten my Dagu Adventure Bot running and have successfully been putting code on it. I've turned off the sound, I've played around with the "light chase" mode and edge detection sensors, and so on. So I'm pretty confident that the code I see is the code that's making it down to the bot.
Here's the weird thing. Whenever I run the out of the box code, with nothing commented out? Almost immediately the robot's head whips around until it is tucked down and to the right, and then it tries to go into some sort of spin. I don't know much about the mechanical bit of what's going on but it seems to suddenly go all "Drive all the servos to the max". It is unclear to me whether it's gone to the max position and stopped, or if it is actually attempting to drive past its limits and potentially break itself. When it gets like this it seems to be ignoring the sensors, and no amount of trying to get my hand in front of the head will make it leave this position.
Is there any sort of error condition that might cause this as an expected behavior? I've not yet found anything in the code that would make it do this -- all the movement routines seem wrapped in a combination of "only move X amount at a time", and "make sure you don't go past the defined range for this motor."
I am working my way through the code systematically to determine if this is in fact something the code is telling it to do. If I turn off the wheel motors completely, I can never make it do just the head thing.
Is such an error even a possibility? Where, despite my code saying "Turn the motor off", they are all still powered?