Hmmm, as said before, double check all your switch connections. Microcontrollers don't seem to like shorts, even on unused inputs. Also, make sure of two things: Battery voltage and connection. If your voltage is too low, say on a damaged battery, that throws everything awry. A loose battery connection might also be causing some of the problems. I noticed that your battery connections were shrink wrapped and (no offense), occasionally carried around by the anderson connector. A loose wire in one could easily be out without you noticing. That wouldn't account for it ignoring a disable command though. That might be bad.
Just some of Murphy's little tricks, but think it is more likely what was said before; loose electrical connections of some sort.
Quote:
|
Originally Posted by KenWittlief
If you cant isolate the cause, you might have a defective robot controller, or operator interface.
|
You can use your 2004 operator interface to check if it's good, and if you want to go drastically, swap out a 2004 RC with 2005 master code to check the RC. However, that would be a little messy.
__________________
Reading makes a full man, conference a ready man, and writing an exact man.
-Sir Francis Bacon
"Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction."
-Albert Einstein