Gyros and WPILib

[RyanW]

Our team is using WPILib to program our robot, and we are trying to use a gyroscope to get the heading of the robot. We are using an ADXRS150 gyroscope, and when we try to read off of it, we get continuously incrementing values. Our gyro test code looks somewhat like this:

At the beginning of the autonomous method (only gets called once):

SetGyroType(GYRO_PORT, ADXRS150);
InitGyro(GYRO_PORT);
//The following should create a delay so we don't start doing anything else right after initializing
StartTimer(5);
while(GetTimer(5)<2000);
StopTimer(5);
StartGyro(GYRO_PORT);

We then move into an infinite loop, calling the following over and over:

printf("GyroHeading=%d\r", GetGyroAngle(GYRO_PORT));

The gyroscope has two PWM cables. On both cables, the red and black go to the +5 and ground ends of the gyro respectively. The white signal wire on the first cable (in GYRO_PORT) goes to rate, and the signal wire on the second cable (going to an otherwise unused analog input port) has the 2.5 volt calibration signal. The two self-test pins also go to ground.

Again, whenever we run the test code, the gyro angle continuously increments, regardless of whether or not we turn the gyro. The analog value being returned is varying from about 536-544, staying mostly within +/-2 of the center value.

EDIT: We fixed output from a long to an int, so the values we are getting are reasonable. However, every second or so, it's still incrementing.

EDIT 2: It now changes as we turn it, but the output is not in tenths of a degree (as WPILib specifies), or even in degrees. It is about 1/4 as much as it should be...any ideas what's wrong?

Any ideas as to what's wrong, and what we can do to fix it?

Thank you for your help.

[mluckham]

I guess this is your own circuit, not the gyro in the KOP? Could you publish the circuit so people can comment?

If an AI value is 'continously incrementing' then usually there is nothing connected to the pins. Although from your description, you are actually seeing a fairly fixed value fluctuating in a narrow range. When you connect, and remove, your gyro from the RC is it obvious from the printf output?

If the incrementing is very small, regular, and slow - you say every second or so - you may be seeing gyro drift which you can't do much about ... the usual approach is to reset the gyro to zero when the robot is in a known position. Most advice in these forums states you can pretty well ignore gyro drift for our 2-3 minute matches.

When you specify the type constant in SetGyroType() the second paramater is actually a numeric divisor which scales the gyro value to tenths of a degree. You could experiment with different values for this.

[RyanW]

We're using the ADXRS150 gyro, from SparkFun electronics. The product page is here, and the datasheet is here. After fixing a few things in the code and scaling it properly, the values are much more sensible. We also tested the gyro with Kevin's default gyro code, and got reasonable values with a scale factor of ~3500/1000. I'm just rather surprised that the default scaling factor is off by so much, since I'm using the specified gyroscope, and I was wondering if it meant that something was wrong. However, it now seems to be working okay so far...