We need a GYRO
 

My Team is from Storrs, Connecticut. The team is 3 years old and are still getting the hang of organization. We seemed to have lost the gyroscope from this previous years kit and are attempting to prototype a new drive train with it. We are looking for a local team that may have 1 that we could have. We are willing to pay and if needed pick it up.

We have also been looking on various websites but have had no luck.


You can contact me on AIM at emath88789
or email us at eosrobotics@gmail.com


Thank you
Spontaneous Combustion (Team 1373)

Re: We need a GYRO
 

If you're willing to spend some money on it, I'd have to recommend simply purchasing one of the two primary Evaluation Board Gyros from Analog Devices. The device in the kit has a maximum rotational velocity of approximately 80 degrees/second. Spin it any faster and it just peaks out at 80, and trust me, 80 is very easy to exceed if you get hit moderately roughly on the field. I recommend atleast the ADXRS150EB (150 degrees/second) or the ADXRS300EB (300 degrees/second), the EB on the end of the model numbers notes it's an Evalulation Board. These components come in Ball Grid Array packaging, which is difficult to work with, the EBs come with the package pre-attached with all the support hardware (Capacitors, Resistors and the like) on a small PCB with solder pads to connect your wires to, just like the kit one, but a considerably superior gyro.

The evaluation boards are $50, which I feel is pretty reasonable considering the quality of the sensor, the sensor alone is $30, but I would highly recommend getting the Eval Board as the Ball Grid Array can be very difficult to work with, and the tools required would amount to more than the $20 saved, as well as ease of replacing it if anything happens.

The difference between the 150 and the 300 is merely the maximum rate of turn they can detect. Since both operate over a 5 volt spectrum of output, the 150 has finer resolution, but less range, whereas the 300 has more range, but less resolution. My personal choice has always been the 300, as I never trust the mechanical people to make a robot precise enough to warrant the extra resolution ;) (Just kidding, I love my mechanical guys!)

I'll be posting a whitepaper on gyro programming as well shortly, soon as I finish proofing it for silly mistakes and fully testing all the code examples, expect it in a month at most. (Though I might end up eating those words). However before then feel free to contact me privately with any questions you may have, I'll do my best to answer them in my schedule.

Re: We need a GYRO
 

ok thanks
i'll mention that to my team