Thread: Help with Gyro
View Single Post
  #7   Spotlight this post!  
Unread 13-01-2015, 15:25
jman4747's Avatar
jman4747 jman4747 is offline
Just building robots
AKA: Josh
FRC #4080 (Team Reboot)
Team Role: CAD
 
Join Date: Apr 2013
Rookie Year: 2011
Location: Atlanta GA
Posts: 418
jman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond reputejman4747 has a reputation beyond repute
Re: Help with Gyro

Quote:
Originally Posted by Caitlinnnnn99 View Post
Thanks Joe,
The new labview 2015 has provided us with an example code for this specific sensor using SPI Vi's. We've put this example program into our robot program and have also tested with just the example program and the results are still the same: an increasing number for the angle.

We need some help on changing this to where we read the actual angle of the gyro's position. Not a constantly increasing number, even when the gyro isn't moving.

Also, in the program it seems to be adding the rate of angular change?
But the thing is when we leave the sensor still it continues to rise in "angle".
Why would it continue to increase even when the gyro is still?

I have attached pictures of the example code we are using.
All a Gyro will ever give you is a roll rate for each axis. The key is that it is a rate not a heading. The thing you need to look for is gyro integration. This is the process of constantly adding in how fast you were turning for the last time period that you were measuring to your current heading. As for the reported movement even when the gyro is still, you need to calibrate to get rid of the false movement. Read http://www.chiefdelphi.com/forums/sh...ight=Best+Gyro it talks about a lot of this. Furthermore I think that if you decide not to use the WPI libraries you will need a co-processor (Arduino) to read the gyro, calculate the heading, and transmit it to the RIO via UART or another coms method.
__________________
---------------------
Alumni, CAD Designer, machinist, and Mentor: FRC Team #4080

Mentor: Rookie FTC Team "EVE" #10458, FRC Team "Drewbotics" #5812

#banthebag
#RIBMEATS
#1620
Reply With Quote