|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
autonomous hates our motors
The problem is that all of our motors work on teleop, but when we try to run a very simple "go forward" autonomous program one motor stops working. It is not the motor and it is not the wiring of the motor. We only have two motors and our programing for the motors is all correct. We just don't know what to do. Anything will be helpful.
|
|
#2
|
||||||
|
||||||
|
Re: autonomous hates our motors
You might get more focused answers if you posted in the FTC forum. This general forum is very FRC centric, so you'll need to clearly identify your problem as FTC specific.
You might get better answers if you gave more details about your autonomous code. Last edited by Joe Ross : 30-10-2010 at 14:43. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| [FTC]: Our motors are too slow :( | aybose | FIRST Tech Challenge | 2 | 30-11-2009 10:53 |
| control 4 motors in autonomous? | pinballwizard96 | NI LabVIEW | 4 | 10-02-2009 12:03 |
| The Team Update #3 killed our autonomous | Trav-O | Programming | 1 | 19-01-2008 12:11 |
| Connecting our cam motors | Max Brin | Technical Discussion | 4 | 07-02-2006 12:14 |
| where do we connect our motors for navigate.c | thelastride | Programming | 5 | 15-02-2004 15:45 |