Ken

You probably need to decide if you want the flexibility of a bare PIC or a package that is already programmed. I went with the PIC since I can basically make it do anything I want.

There is a price to be paid to get in that game however. Perhaps you already have all the infrastructure, if not you will need a programmer to write to the PIC, and then decide on the language. Since you are on this forum, you may have PICBasic. If not, you can go assembly (free), C (also free from MicroChip without optimization), or some other language (maybe free, maybe not). There are a lot of programmers out there. MicroChip has some, but other vendors too. I use an ICD2 clone from Sparkfun and PICBasic Pro for smaller PICs and the MicroChip C30 C compiler for dsp chips. I also program in asy, but I can get a lot more done with Basic or C.

If you go the PIC route, I would just use a proto board to build up your circuits.

I typically use an 11v LiPo battery to a BEC to get 5 volts for the board. You can actually take the power off the RX on the Red and Black wires of any channel. This is very low power drain compared to the motor and servos.

Just a suggestion, but I would use an RC car or truck that has a very slow speed option. Fast isn't good when you are trying to debug sensors and code.

One way to switch between manual RC and Auto is to use a channel of the RX that the PIC reads. If it is high, then manual, low then auto for instance. but you need a spare channel. I use a Specktrum DX-7 TX/RX with 7 channels for all the goodies I need to control. This approach is useful if the Auto goes nuts, you can switch to manual with the flick of a switch.

This can get a little expensive to start, but if you plan to stick with it and do similar projects, I think the basic building block approach gives you the most fun....but then again I don;t know what the VEX etc are. And I do a lot of this on many different platforms.

Did I understand you were involving students? It's a great learning project.

John