Better gyroscope?

[pipsqueaker]

Hey everybody!

We're using a gyroscope on our robot this year (I dont know the model number, but it's the "traditional" one you can see a picture of here). Unfortunately, this gyro tends to drift randomly sometimes (accumulating a few degrees over a few seconds), and at others it will remain almost perfectly stable.

Has anyone come across this problem before? We'd like to use the gyro to aim our robot, so such drift is a problem.

If anyone simply has suggestions for better gyroscopes that would also be welcome

[Alan Anderson]

The random drift you describe sounds like electrical noise. If the wiring from the sensor goes parallel to motor power wires, you might find the integrated value acting like that. Try shielded wire routed well away from high currents and see if it stops misbehaving.

[euhlmann]

We have a NavX-MXP for navigation. The drift is 1 or 2 degrees over match time.

Lower quality gyros do tend to drift a lot, so what you see is probably normal. Make sure your gyro is calibrated correctly though.

[Hjelstrom]

Be extra careful not to move your robot while the gyro is calibrating. Typically that a few seconds is right after you turn the robot on.

[cjl2625]

Not sure if the WPI library was modified recently, but in 2014, when we used a regular gyro, we had similar inconsistent drifting problems. With field-centric swerve, things sometimes got really ugly.
There's a discussion about that on this thread: http://www.chiefdelphi.com/forums/sh...62#post1399062

So I ended up writing my own Gyro code. If you're using LabVIEW, I posted my code here: http://www.chiefdelphi.com/forums/sh...55#post1416955

Those changes definitely improved things.

In 2015, we got the NavX MXP, which offered further improvement, and worked great for our swerve last year. (and since the NavX comes with its own libraries, you don't need the code modifications I mentioned)

[pipsqueaker]

Originally Posted by Hjelstrom

Be extra careful not to move your robot while the gyro is calibrating. Typically that a few seconds is right after you turn the robot on.

Hmm, so the gyro calibrates even before the code starts up? That's good to know.

[Arhowk]

Originally Posted by pipsqueaker

Hmm, so the gyro calibrates even before the code starts up? That's good to know.

If you didn't notice, instantiating a gyro will stall the code for a couple seconds while it calibrates.

[juchong]

If your team used your AndyMark First Choice points, you should have received an FRC Gyro & Accel board with your order free of charge. This sensor should provide much better performance!

[kevin.li.rit]

Also, if you haven't used your FirstChoice points amazingly the ADIS16448 is still available.

[AlexanderTheOK]

I can personally vouch for the navx-mxp and WCP Spartan Board. While in my experience (which involves a sample size of exactly two of each board, and is thus in anecdotal territory) the navx has significantly less drift, neither drifts significantly anyways and thus the difference is meaningless.

[AustinSchuh]

Originally Posted by AlexanderTheOK

I can personally vouch for the navx-mxp and WCP Spartan Board. While in my experience (which involves a sample size of exactly two of each board, and is thus in anecdotal territory) the navx has significantly less drift, neither drifts significantly anyways and thus the difference is meaningless.

The WCP Spartan board has a adxrs453 on it. The adxrs453 is an amazing chip. The drift should be 15 degrees/hour. The spec that the spartan board really wins on is the "Ultrahigh vibration rejection: 0.01°/sec/g". On previous KOP gyros, I saw significant coupling between acceleration and angle. When I had the robot accelerate hard, it would measure that it had turned. On the adxrs453, I've had no issues with that. 254, 1678, 971, 973 and 1323 all ran a previous version of the board last year and will be running it again this year.

The navx has a magnetometer, so it can detect the earth's magnetic field and use that to adjust. That will result in less drift as you noticed, if drift is the metric you want to use for heading quality.

(Full disclosure: I lead the design of the Spartan Sensor board and worked with WCP and others to make it legal this year and make it available for sale. Thanks a ton to RC for helping make this board available to everyone.)

[AustinSchuh]

Originally Posted by kevin.li.rit

Also, if you haven't used your FirstChoice points amazingly the ADIS16448 is still available.

For 50 credits, it's a bargain. Probably one of, if not the best bargain part in the entire catalog. The ADIS16448 dev kit retails for over $800. That's a lot of IMU for your credits.

[juchong]

Originally Posted by AustinSchuh

The WCP Spartan board has a adxrs453 on it. The adxrs453 is an amazing chip. The drift should be 15 degrees/hour. The spec that the spartan board really wins on is the "Ultrahigh vibration rejection: 0.01°/sec/g". On previous KOP gyros, I saw significant coupling between acceleration and angle. When I had the robot accelerate hard, it would measure that it had turned. On the adxrs453, I've had no issues with that. 254, 1678, 971, 973 and 1323 all ran a previous version of the board last year and will be running it again this year.

You're right, the ADXRS450/453 is a nice gyro core on its own! If you're looking for high VRE (Vibration Rectification Error) take a look at the ADIS16448. It has much better VRE and lower drift vs the 450.

Originally Posted by AustinSchuh

For 50 credits, it's a bargain. Probably one of, if not the best bargain part in the entire catalog. The ADIS16448 dev kit retails for over $800. That's a lot of IMU for your credits.

[snekiam]

We had the same problem last year,and switched to the Navx this year. We have no problems with drift at all.

[Joe Johnson]

I went into last year a skeptic and I came out a believer: the NavMXP is going on every FIRST robot from now on until something better comes along (and I suppose that will be a long time, if ever because honestly, 1-2 degrees during a match is pretty much as good as you'll need for almost any algorithm I'm likely to use).

It just works. Very impressive performance.

Dr. Joe J.