2018-10-15 02:18 PM
Hello! I am R&D inclinometer based on LIS3DHH. Firstly I started my works with LIS2HH12 as MEMS accelerometer due to his best accuracy and resolution. I wanted to get accuracy about 1-2 angular minutes. All was good when I turned on almost all internal filters and using software moving average. Even with 7 sec response it was ok for my solution. But after few experiments I discovered problem with temperature stability. I decided use internal temperature sensor to compensate temperature coefficient and started temperature experiment (first with termal camera, but after without, because was a lot noise from camera). And I can't find out temperature coefficient for that. Next figure shows angle for one axis (red), temperature from internal sensor (blue) and reference signal from another special inclinometer. So, angle changed unpredictably on different days.
Next figure shows one angle (green) and temperature (blue). Here some unpredictable overshoot.
In this case I cant solve the problem with temperature and discover new LIS3DHH. I made a new PCB layout for it. There only 2 internal filters and with using moving average. The best result I've got only 5 angular minutes accuracy. Then I start temperature experiment for LIS3DHH and it was better than LIS2HH12.
Can you help me, how I can solve temperature stability problem in LIS2HH12 or accuracy in LIS3DHH. Maybe better to chose another accelerometer for inclinometer solution? Is it possible to have stability angle with 1-2 angular minutes accuracy with MEMS technology?
2019-01-06 04:25 AM
I don't understand what exactly is your question.
2019-01-17 09:11 AM
Hi,
my question was relative to the bad behavior that I have on some accelerometers.
Anyway I just wanted to ask you if the internal temperature compensation process can be disabled setting the first bit on the CTRL_REG4 equal to "0".
Can I ?
Basically because I use my temperature compensation process in firmware which is perfectly working with the ADXL203.
Many thanks
Alessio
2019-01-18 02:43 AM
2019-02-11 12:50 AM
Updating......
After several tests on 60 pieces I've observed a different temperature behavior on the same accelerometer.
Basically, if I do a thermal test where I get the temperature coefficient for every device in order to perform the firmware temperature compensation, I can have a different value on a different test.
So it doesn't seems constant for the same component. This aspect makes the accelerometer absolutely unless.
My idea is that either probably the ecopack package has a different thermal behavior or the internal temperature compensation works in some way in order to change the output value.
Further I cannot figure out how the temperature compensation can work because each component has a different temperature behavior which require a test on every device.
Anyway I just wanted to ask you if the internal temperature compensation process can be disabled setting the first bit on the CTRL_REG4 equal to "0" and which kind of calculation it performs internally.
Please try to help me because I will switch over on the MMA8451 immediately.
I cannot waste time and effort on this component anymore.