Post Go back to editing


how to calibration adis16365?can you send adis16365 driver to me?

  • Thank you for your interest in the ADIS16365, but I am a bit confused by what you are asking for.  Here are a couple of points to help explain my confusion. 

    1. The ADIS16365 is calibrated in its production process, before it is shipped.

    2. Full IMU calibration is not something that a software driver can address.

    What are you trying to accomplish? I suspect that we can help you get started in this process, but we need to understand what behaviors you are concerned with, along with your requirements for those behaviors.

  • hi,after "Automatic and manual bias correction controls".Will be put on the gyroscope, and then through the integrationto get the degree, every minute of the drift will be generated, there may be 1 degrees, there may be 2 degrees, how to solve?

  • What level of accuracy are you looking for? AN-1041 offers some insights that might be helpful for you.

  • I have been calibrated in accordance with AN-1041, but the offset is still very large, unstable.

  • You didn't answer my question. In others words, I do not understand your problem well enough to think about what solutions might be helpful.  It sounds like you are on the right track for optimizing the performance, but we need a performance goal, which relates to the capability of the devices, as described in the datasheets.  The In-Run Bias Stability provides the resolution, or the "best possible," which means that your goal for stability should be higher than this.  If you need better performance than this device is offering, we have several generations of new products that offer better performance. The ADIS16445, ADIS16460, ADIS16485 and ADIS16490 might worthy of consideration. 

  • Will be placed on the gyroscope, and then collected angular rate, each acquisition time of 15 seconds, and then seek the average value of 15 seconds. I hope that the results of each deviation should not be too large, but the volatility may reach 0.02 degrees per second.

  • It seems like you are taking that number from the Allan Variance Curve in the ADIS16365's datasheet.  Is that correct? 

    So, what type of variation are you seeing when you do this?

    Keep in mind that the units need to be a thermal equilibrium (powered on for >10-15 minutes), they need to be protected from any accidental motion, their power supply needs to be stable and you need to make sure that you are not under sampling the 330Hz gyroscope data (recommend collecting data at maximum sample rate, using no internal filtering, for this test).

  • When I use the 16365, it is found that the zero drift is too large, resulting in the angle of the gyroscope is not accurate. So, I just want to observe the change of angular rate with time. However, it was observed that the rate of change of angular rate was too great. No matter which calibration method I use, the angle is obtained by the angular velocity integral. Although the gyroscope did not move, but soon changed a lot, it may be 1 minutes 1 degrees, there may be 1 minutes 3 degrees. Can help me look for the reason?

    their power supply,i read the  SUPPLY_OUT register,the value is 4.971408v or 4.973826v.

    the allan variance of  ZGYRO_OUT is near 0.01375.

  • I want to help, but I am starting to feel like you don't have a clear objective.  Am I wrong?  I want to help, but I must insist on having clear, quantified answers to the following questions, in order to offer any further response:

    1. You seem to be integrating the gyroscope outputs to track angular displacement.  Is that correct?

    2. Zero bias error is not possible, so when using this technique, angle error will grow with time.  Do you recognize this?

    3. What angle accuracy do you require?

    4. What time period can you bound this to?

    5. Can you offer a specific example, with data and your computation method, in a file that is easy to open in Excel?

    6. Using this as a reference, what improvement do you want to see?

    You might have already found the limitation of the ADIS16365.  In other words, if your needs are much tighter than the ADIS16365 will support, does it make sense to spend lots of time trying to make your existing results a little better?