Thanks for posting this update. That helps a lot.
- Yes, I can confirm that the data in the GYRO_OUT column is in deg/sec.
- I used a standard deviation on your data and came up with the same number you did for total noise. Assuming you are not using any filtering, the ~0.21 deg/sec is within the typical specification of 0.27 deg/sec-rms.
- When the decimation filter is not in use, the GYRO_OUT2 contents do not matter.
- The GYRO_OUT2 data is not represented in a useful manner, when using scaled data.
- If you need >16-bit resolution of data on the gyroscopes, use the following process:
- Use un-scaled option (check box in Datalog menu)
- Convert decimal numbers in GYRO_OUT and GYRO_OUT2 columns into binary numbers.
- Shift GYRO_OUT result 16-bits to the left
- Add GYRO_OUT and GYRO_OUT2 registers.
- Shift result to the right by the number of bits that are relevant, per Figure 14 in the ADIS16135 datasheet
- Convert that twos complement number to a decimal equivalent
- Multiply it by the scale factor (also from Figure 14)
- Keep in mind, this is an old software package and system, which we are not actively maintaining. The EVAL-ADIS and IMU Evaluation software packages are the preferred tools for the ADIS16135 now. It would appear like you can make your existing tools work, but I wanted to let you know why we have not addressed the weakness in the GYRO_OUT2 representation.
- You cannot calculate sensitivity from this noise data. Just use the nominal value of 0.0125 deg/sec when using unscaled data for GYRO_OUT.
Does that help?
Best,
NevadaMark