Integrating Gyroscope Output for Accurate Angle Measurement

Click For Summary

Discussion Overview

The discussion revolves around integrating gyroscope output for accurate angle measurement using a 6DOF IMU Razor and Arduino. Participants explore numerical integration techniques, sample timing, and the implementation of code for angle calculation based on gyroscope data.

Discussion Character

  • Technical explanation
  • Mathematical reasoning
  • Exploratory

Main Points Raised

  • One participant seeks assistance on how to integrate gyroscope output to update angle measurements.
  • Another participant suggests using rectangular integration, emphasizing the need for current velocity and time between samples to calculate angle.
  • A participant questions how to obtain current and previous time samples and clarifies the representation of "angle" in their calculations.
  • Discussion includes the importance of consistent sampling rates and methods for determining time between samples, with one participant noting potential issues with non-periodic sampling.
  • Corrections are made regarding the calculation method, specifically that angle should be updated by multiplying by time rather than dividing.
  • A proposed code snippet illustrates a basic integration approach using a constant time interval for angle updates.
  • One participant reports that their integration implementation appears correct but expresses concern about the appearance of their graph, suggesting potential issues with their graphing code rather than the integration itself.

Areas of Agreement / Disagreement

Participants generally agree on the method of integrating gyroscope output but express uncertainty regarding specific implementation details, such as sample timing and the accuracy of their results. The discussion remains unresolved regarding the issues with the graph representation.

Contextual Notes

Participants mention various methods for sampling and timing, indicating that the accuracy of angle measurements may depend on these factors. There are unresolved questions about the best practices for handling non-periodic sampling and the implications for angle calculation.

becky91
Messages
3
Reaction score
0
Hey guys,

I recently did a project with combining and accelerometer and gyroscope together using the 6DOF IMU Razor and an Arduino and now i need to try something different but i need some help. How does one integrate a gyroscope output? I tried something like this below but i don't think its complete:

Code:
    xGyro  = analogRead((X_GYRO_APIN) - 403); //removing offset from raw ADC value
    xGyro *= (3.3 / 1023.0) / 0.00333; //now reads deg/sec
    tmpf = xGyro;
    tmpf *= interval / 1000.0f; //now reads deg

How do i update my angle, hence integrating my gyro?

Any help is much appreciated!
Thanks
 
Engineering news on Phys.org
Well, there are a lot of different numerical integration techniques. The simplest follows this pattern and is called "rectangular integration"...

You need two things: your current velocity (degrees/sec in this case) and the time between your current sample and previous sample (in seconds of course). Then your angle is just the running sum of your previous angles and the current velocity divided by the time delta.

angle = angle + velocity/deltat;
 
Ok so, up to now I've found my deg/sec and I've also divided it by time so as to get my value in deg. How do i get my current and previous time sample though? And does "angle" represent the degrees value in this case? Like this:
Code:
    xGyro  = analogRead((X_GYRO_APIN) - 403); //removing offset from raw ADC value
    xGyro *= (3.3 / 1023.0) / 0.00333; //now reads deg/sec
    angle = xGyro*time;
    angle = angle + xGyro)/time
And my time could be any sample time? (eg 100ms)?
 
Last edited:
Your time between samples depends on how your system works. The easiest method is to have a system that sample at a constant rate... for example at 100Hz. In this case your time between samples would always be 0.01 seconds. This can be done in different ways, from using a periodic interrupt for a software based system or implementing the periodic sampling in hardware (where you software would then read out of buffered data).

In other systems you may not be able to periodically sample. In this case you may have to time stamp the data and determine how long it has been between samples. A worse case here would be if you were using a Windows system. Every time you sample you may have to look at the system time and use it versus the system time of your previous sample to determine how long it has been between samples.

In either case, the accuracy of your answer not only depends on the readings but also on your ability to determine the time between them.


And actually I just realized I made a mistake in my earlier post. You actually want to multiply by time and not divide (you would divide if you were using frequency).

So it should be: angle = angle + sample*sample_time

Sorry!


If you think about it this way: velocity = change position / change in time

So if you want to get change in position you need to multiply by change in time -> velocity * change in time = change position

Now, if you sum up all your change in positions, you get your current position relative to where you started.
 
you can try this way:

Code:
double angle = 0.;  ///< your start (initial) angle in degree
double time = 0.01; ///< [seconds] imagine that you get info every 10 milliseconds

while(1) {
    xGyro  = analogRead((X_GYRO_APIN) - 403); //removing offset from raw ADC value
    xGyro *= (3.3 / 1023.0) / 0.00333; //now reads deg/sec
    angle += xGyro*time;
}

this code is OK for one gyro integration. It will be more interesting when you start to integrate all three gyro together.
 
i actually did do my integration like what you both just mentioned so its fine now, the only weird thing is that my graph looks funny now...im starting to think there's something wrong with my graph code and not my actual integral :/
 

Similar threads

  • · Replies 1 ·
Replies
1
Views
3K
Replies
9
Views
7K
  • · Replies 7 ·
Replies
7
Views
7K
  • · Replies 15 ·
Replies
15
Views
7K
  • · Replies 3 ·
Replies
3
Views
2K