View Single Post
  #10   Spotlight this post!  
Unread 14-09-2012, 12:54
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,112
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Communication lost

Quote:
Originally Posted by Skehtb View Post
We found out that the robot doesn't stop functioning when we drive it forward. It happens only when try to turn it (and I'm pretty sure it happens only when it truns to the left), drive it backwards, or stop it after driving forward. I'm not sure about how long the robot stops functioning, but its definetly more than 20 seconds. I'll check it.
Look for a shorted wire between one of the left side drive motors and its speed controller. You might be getting voltage on the frame when a motor drives backwards, and another shorted frame connection somewhere (likely a power return or "ground" wire) could be causing your D-Link or cRIO to reset. Or you might have cross-wired motor leads, with one motor connecting to two different speed controllers. That results in very weird symptoms that can sometimes match what you're describing.

You can start troubleshooting electrical issues by removing the circuit breaker from the power branch to one speed controller at a time and seeing if the problem can be narrowed down to one motor's circuitry.

Last edited by Alan Anderson : 14-09-2012 at 13:41.