View Full Version : Non-Arcade Drive causes problems in Autonomous...
01-31-2009, 07:24 PM
I deployed the default FRC cRIO project correctly and noticed that both drive motors were now controlled by one joystick. When I switched to Autonomous mode, the default program ran as expected EXCEPT...only 1 motor changed directions - the other one ran in the same direction for the duration of the program. I tried switching the connectors, and the OTHER motor experienced the problem while the 1st one corrected itself. Could this be related to the speed controller, or is the autonomous program intended to switch the direction of only 1 motor?
Thanks in advance
02-01-2009, 10:01 AM
The default code is set to Arcade drive. This means that the robot is controlled by one joystick. The y-axis controls velocity, the x controls rotation.
I don't have the autonomous code in front of me, but from what I remember with playing around with it was that your description is correct. The default autonomous code is on a timer, and goes forward then turns (left I believe) for a short amount of time four times.
To me, it sounds like the default code is running perfectly fine. To switch to tank drive (two joysticks, each controlling one side of the robot), you will have to replace the Arcade drive VI with the tank drive VI, and add another joystick. You can also easily change the autonomous code (<A href="http://www.lvmastery.com/tipjar2009-01-02">LV mastery tutorial on autonomous</a>).
If you already modified you code, and it isnt changing anything, make sure your build specifications are correct, and that you are deploying the build to run as startup. If it isnt being run as the startup project, the old code will continue to be run every time you turn the robot on.
02-01-2009, 08:45 PM
alright I shoulda noticed that...was mainly worried about the autonomous mode because I heard it was supposed to run the robot forward and backwards (they probably had already changed it).
vBulletin® v3.6.4, Copyright ©2000-2013, Jelsoft Enterprises Ltd.