What are we supposed to do!?!?!?!??!?!

[Bomberofdoom]

We already went through the presentation of the C and it didn't give us the real help. It told us where to go but not specifically what to do(yes, write your autonoms code. But what values, varibles, functions etc. are we supposed to use in it?).
What really helped was the the RC reference guide, thx!

[Bomberofdoom]

Originally Posted by Bomberofdoom

Autonomous Mode means that the RC will ignore all data from the Operator Interface and it will not
require a link with the Operator Interface to execute code.

If you wish to run the Robot Controller exclusively in Autonomous Mode, one way to do this is to set
your team number to zero. This is done by setting the team number on your OI to zero, linking your OI
and RC by tether, and then disconnecting from tether. After your RC is reset it will be in Autonomous
Mode.

To exit Autonomous mode if your team number is zero, you must re-tether and change the team number
to anything but zero.

An additional method for getting into Autonomous Mode is described in the Operator Interface
Reference Guide in the “Competition Control LED” section. See the Programming Reference Guide for
details on how to program for Autonomous Mod

Where is the team number value?(which source file?)

[jakk]

Actually, can't you make something that will simulate the master controllers used at FIRST? You can connect some switches to that 'competition' port on the top and run either autonomous or disable the robot. Not really sure what pins but it can be done.

[SuperBK]

Run the default code first. After loading the code into the robot controller, open the terminal, if the statement "printf(..." is not commented out, it will print the values for the joysticks. You can add other variables (like switches) to the printf. Move the sticks and see what values change. Look at Default_Routine() like the other poster said.

Look at ifi_aliases.h for the possible variables you can read and set.

Autonomous mode is in user_routines_fast.c. Look at User_Autonomous_Code(). It runs in a loop so you have to have a state machine. After you get the robot going and a few things figured out, then search around for an example or post back here.

Note: The operator interface will not talk to the robot controller until you set the team number on the IO and tether it first.

Hope this helps,
Brian

[Bomberofdoom]

Thanks for the help guys.
I guess the only problem is right now is just trying to dycript those small macros, functions and other varibles and how they relate to the robot or OI.
But our Programming group all agreed that we've reached the begining point and we can probablly see the next step ahead(with minor help from you guys and Delphi).

Thanks again

[Bomberofdoom]

BTW, I find the previous codes some people sent very usefull. It'll also help me and the team to get some more work to do(I'm head of the programming team{and look how desperate I was}).
Please send any previous codes you can(with comments of course, so we may understand ). We will really appreciate it.

[robbekid]

read kevins code, he has really well documented code, i am learning the programing this year as I am planning on helping with the programming from next year on wards, so i have been working with just decoding kevins FRC code.

[bear24rw]

Originally Posted by robbekid

read kevins code, he has really well documented code, i am learning the programing this year as I am planning on helping with the programming from next year on wards, so i have been working with just decoding kevins FRC code.

www.kevin.org/frc

[bear24rw]

The team number isnt set in the code, its setting in binary using the dipswitches..

Also, just try to get a copy of someones code (i would upload mine but i dont have it with me) and just look through it and try to learn it. Before last year I didnt have a clue what a #define statement was, i just read over the code from previous years over and over again and read all the programming papers on ifirobotics.com... now i knew the controller inside and out...

Good luck