Rules regarding sensors/processors

[jacob_dilles]

Originally Posted by KenWittlief

if you are going to design an internal naviagtion system based on a PIC processor, and do it in the off seaon, then there is one hitch - everything on your bot has to be either built (fabricated) after the kickoff for the new season, or it has to be something that is available to all teams

i may be missing the point entierly, but six weeks is a long time to take a working prototype and build a final version. if you plan it out, build a test one, then file the plans away untill january, i see no problem in pre-purchasing parts and just slaping the thing together. if you share it with other teams, all the more power too you, but fabricating extras is a bit excessive.

Originally Posted by phrontist

Sonic Range Finder
"Compass" sensor
Vision tracking with onboard PC!

for a sonic range finder, you can get a $36 polorid transponder. if you wana take it an extra step up, Vernier offers a $69 "canned unit" that is basicly the polorid sensor with a serial interface. ( http://www.vernier.com ). another option is the devantech ranger which retails for $34 ( http://www.acroname.com/robotics/parts/R93-SRF04.html ) and is also a serial interface. what ever you may choose, ultrasonics are easy to code and simple to implement with a servo or just sevral fixed sensors.

for a compas, the best one out there is is by dinsmore ( http://www.dinsmoresensors.com/ ) and is basicly 4 switches in 8 postions that indicate heading. very simple, very reliable. this is oposed to a coil based solid state version... ie a compas on a chip for $50 ( http://www.robot-electronics.co.uk/s...CMPS032004.htm ) and is also very simple to code with a rs232 serial interface.

any other sensors or computers, as long as they fit the budget and are from the sources, are allowd.


the best compas sensor