Quote:
|
Originally Posted by Eldarion
I got to thinking about this. Is this the reason IFI has the second "initialization" section directly before the autonomous while loop? Would it be a good idea just to bypass IFI's initialization calls altogether and make your own initialized / not initialized flag that, when zero, calls the init routine and sets the flag to 1?
|
The only initialization I see is giving all outputs a default value. Not only is there a comment explaining why, but the user code gets called once on startup even when in autonomous mode. So forcing outputs to off is a good idea.
Quote:
|
Originally Posted by Eldarion
I distinctly recall a similar problem in our custom code last year, with the robot acting completely bezerk on the field, yet in the pit with the dongle, it worked perfectly. I had heard a rumor about the Arena Controller forcing some king of sync with the OI and RC; is there anything to justify this rumor? It might explain a lot of the "it worked perfectly until I put it on the field" problems.
Would this issue be reproducable on a 2004/2005 RC, since it seems to be a problem with IFI's default code?
Just some ideas...  |
Thanks for the ideas.
In the rush at the Regional we never had the time to sit down, develop a test plan, and methodically track down the problem. But we did find a sequence of events where we could reproduce the problem in the pits. Our code was just not instrumented to diagnose the problem.
Today I developed a test plan involving: using the default frc_camera_2 code, adding camera tracking to autonomous, and instrumenting the camera and tracking initialization variables to show their state on OI lights. My team contact is on the other coast for 2 weeks so I may not be able to arrange test time for a while.
Unfortunately our regional is over and we are done for the year.
Our strategy was heavily weighted towards scoring during autonomous. All the pieces were in place but the camera never worked during autonomous.