Original post>>
In the documentation you cannot find information that accelerometer has 12 bit ADC and is converted to 16 bit. Only information you can find is that sensitivity is ~61 μg/LSB on page 9 (http://www.analog.com/static/imported-files/data_sheets/ADIS16210.pdf) .
NevadaMark>>
The scale factor in the part of the datasheet you reference describes the format of the register. I don't presently believe that the register coding explicitly commits to 16-bit, 512SPS data, like one might see in an ADC datasheet. In light of your feedback and experience, I will review this position. In general, we produce datasheets with specific users in mind, but try to make them as useful as possible for the general market. I suspect that this has not been an issue for most because they typically leverage the averaging/decimating filter to minimize noise on the tilt angle measurements. I suspect that this is not how you are using the data, so I hope that you will support further disclosure so we can better understand how this limits you. Despite our best effort, we aren't perfect and are very open to customer feedback on these matters. We are certainly open to updating product datasheets, when we can understand how a particular information gap impacts a specific situation.
Original post>> There is only written, that temperature is coded as 12 bit value (page 11). Dominance of ADIS16210 is in the added CPU which calculate average value from the programmed set of samples, but it is only statistical trick.
.
NevadaMark>> I understand that you are a bit frustrated. I am sorry about that do want to help but I am struggling to understand what you mean by "statistical trick." Capturing bit growth associated with a accumulation stage is a very common technique that has been leveraged and proven in many different applications. Again, we look forward to better understanding how this limits you.
Original Post>> The cost of ADIS16210 is 20x higher then ADXL362, but quality is less... I expected very good device according to the price, and I loosed a time and money...
NevadaMark>> I think that I already provided some feedback on this but in this context (very general), this assessment is not correct. Is there any chance you can describe how you are using this data, along with its impact on your application?
Best,
NevadaMark