Team 1675' s AutoFlex automous Program

Team 1675 is making their Autoflex autonomous programming tool available for the first time to any team who is finding they ran out of time to develop an autonomous feature.

It can be added to your existing program.

Basically it records 10 seconds of driver/operator commands that can be replayed during the automonous portion of a competiton. It has been used succesfully for the Triple Play and Aim High games the last two years.

Anyone interested in the code and instructions should contact team 1675 via [email protected].

If you plan to be at the Wi regional look us up.

Brian

I assume you use EEPROM to store the data, but would you still have enough room after camera/tracking data?

You might want to consider posting a white paper on AutoFlex.

During the recording process the data is sent out the programmng port. Use hyperterm to capture the data. paste it into a command table, recompile the program and yoru set to go.

the draw back is that you have to follow the robot around with a laptop and serial cable during the programming process.

This is program is an emergency measure if you run out of time to develop a auto mode. It is not a substitute for real engineering.

Brian - K9WIS

Several years ago I wrote something similar. It’s a really neat idea, but we had to scrap it because of the limited program space (pre-2006 controllers). Recording an autonomous mode is really nice, especially when you’re in a pinch to make your robot go somewhere. I’m thinking we may even use recording as part of our autonomous this year.

What I’d really like to see is a program which can record from the OI’s dashboard port.

The Labview dashboard will record and playback.

Team 360 will soon be putting significant human resources into either:

1 using the EEPROM to record an autonomous routine

2 using another, larger EEPROM connected to the TTL->RS232 (as used in the CMU2 setup) to record an autonomous routine

Because as many of us know, “forever chasing the 'bot around” with a laptop and a serial cable becomes annoying.

This application includes a view that records PWM outputs and converts it to C source code to replay the recording. It requires a compile/download cycle to use it since it generates the code.

http://www.chiefdelphi.com/media/papers/1765

114 has a similar system, although we sample the joystick inputs 10 times a second and store it in EEPROM.

Please think to bring a copy to Buckeye, team 1676 will have jumpdrives ready for a copy…

Don