Hey guys, just thought I'd post up a little thread on this.
I'm putting together an autonomous header file for the new controller!
I'm using code samples taken from here (CD) and written by myself.
The PRIMARY core to this is to get a version of CopyCat out for the new controller. For those who don't know what CopyCat is, it's a program that takes driver input and dumps it to EEPROM, and plays it out when auto mode is triggered. Well, I only had a very basic version for the last controller that would record like 25 seconds of input and play it out. The new controller will be able to record almost 10 minutes of driver input (two drive values) and will be able to be splitted into lots of different slots. So, you could have like, 5 prerecorded auto modes at 30 seconds each, and have a digital dipswitch panel or something to switch between them. Great, isnt it? I'm also adding in functions that run an array of movement data, which is tricker to plan out, but still simple for those who like to tinker. And, I'm trying to come up with some sort of sensory-driven-array type of object-like mode. Wow, what a type!
I also suggest that while recording auto modes, don't use interrupts. I've taken the code sample from a previous post (btw, thanks to whoever wrote it, can't jump back to it right now) and it won't write right (aw man...) if you interrupt it.
or at least there's a chance it won't.
But, I guess you could use the CopyCat in collaboration with sensory or something on the interrupts while playing it back. That'd be kinda cool.
So anyway, I'll post it once it's done. Hope it'll help some of those new teams out there get something up and running without too much knowledge of memory handling and so forth. Auto mode should be alot more fun to watch this year
