ADIS16480 gyro issue

I'm trying to read the gyro_x  OUT and LOW registers, but there is an awkward problem. There are continuous variable values unless the ADIS16480 has a fixed position without varying it.

I tried also to read the pitch, roll, and yaw, The values were good but there are some dropped readings.

I'm using the breakout board.

Any help!

Parents
  • Thank you for your post.  It might help to use the EVAL-ADIS and IMU Evaluation Software to validate your observations in parallel with your effort to observe this IMU's behaviors with your embedded interface.  I am not sure I understand the problem associated with this part of your statement.  Since this is an inertial sensor, shouldn't we expect a response when the device is in motion?  Perhaps there are more relevant details that we can use to help you close this gap?

    • ORIGINAL: There are continuous variable values unless the ADIS16480 has a fixed position without varying it.

    With respect to the following, I would address this before doing anything else. 

    • The values were good but there are some dropped readings.

    This typically relates to some sort of timing or signal integrity issue in what the slave (ADIS16480) is receiving. Perhaps this blog may be helpful:

    Connecting to Smart Sensors, it Takes More Than Code 

Reply
  • Thank you for your post.  It might help to use the EVAL-ADIS and IMU Evaluation Software to validate your observations in parallel with your effort to observe this IMU's behaviors with your embedded interface.  I am not sure I understand the problem associated with this part of your statement.  Since this is an inertial sensor, shouldn't we expect a response when the device is in motion?  Perhaps there are more relevant details that we can use to help you close this gap?

    • ORIGINAL: There are continuous variable values unless the ADIS16480 has a fixed position without varying it.

    With respect to the following, I would address this before doing anything else. 

    • The values were good but there are some dropped readings.

    This typically relates to some sort of timing or signal integrity issue in what the slave (ADIS16480) is receiving. Perhaps this blog may be helpful:

    Connecting to Smart Sensors, it Takes More Than Code 

Children
No Data