ADXL355 Latch-up condition

Dear ADI support,


We have been using ADXL355BEZ in our condition monitoring (vibration transducer) products for a while, we’ve sold about 1000+ of them now.


We recently discovered that some of them fail strangely – they report a near-zero vibration (the AC part) - after experiencing a period of over-range high-frequency vibration. We initially suspects our firmware might have bugs, but after some research, we are now quite confident that it’s caused by the defects of ADXL355.


We know that ADXL355 has over-range protection mechanism when experiencing excessive accelerations. When activated, the output will be pulled towards midscale in order to protect itself. This is acceptable. But in some rare cases, this condition will persist even after power is re-cycled. The only way to bring the device back to normal is to tap it (or knock it, if you will) with a screwdriver or something.


While in latch-up condition, the ADXL355’s output consist of a fixed DC acceleration (in our two cases, it’s around -5g in x-axis. (we didn’t investigate other axis). On top of that, there’s also a high-frequency (around 1.6Khz) AC content, measured around 3.9g rms.


As I said previously, the condition is only cleared when external shock is applied. We did not try issuing self-test command. We’ll investigate more if you need more information. I’ll keep you up to date.

  • I have same issue (X is 1.5g , Y & Z is 2.048g forever @ stationary's) after disabling the internal LDO and use external 1.8V for pin 8 and pin 10. maybe power up timing issue for the VDDIO, V1P8DIG, V1P8ANA. (use internal LDO, no any issue)

  • I'm seeing this exact issue with an adxl357. x and y axis are locked with an offset (z axis is not affected) which does not go away even if device is reset. For now it resets at random points in time probably due to external vibration.

    Is there any procedure which I can follow to recover the device without physical access?

    the sentence quoted for adxl355 is not present on the datasheet for the adxl357! 

    Are you certain, that this issue is related to the LDO?

    In general, is this a design issue of the MEMS structure which can "lock" or is it some singnal processing error? Also I'd like to highlight, that this error occured in production use "after months" but now appears a few times a week. This looks like a bad condition as even with extensive testing that error would not be deteced but could happen in production use ...

    Is this error in any way related to the race condition of loading data from nvm to the shadow registers mentioned in the docs for the reset register?

    Heres a link to a plot showing the condition:

    The upper plot is from the "locked" adxl357 operating with 10g range at 1kHz. The lower plot is from an adxl375 running at 800Hz only stored when 10g range is exceeded. xyz of adxl375 and adxl 357 do not match. line is the mean value for given time interval, area ploted is min/max for the same time range.

    Desperetly looking for a solution to this issue.

  • Our failures were identical to what you are describing. Production units were out in the field for months when they all of a sudden failed. This happened across numerous units. Your plots indicating failure modes looked identical to ours. The only way to recover the device is to un-stick the internal MEMS structure... i.e by hitting the accelerometer. There was no way to do so electrically as far as we were aware. 

  • Replaced ADXl355 with external 1.8V, still not working (Y & Z is 2.048g); then back to ADXL355 internal LDO with another ADXL355 replacement, now it works. they have POWER SEQUENCING requirement for the 3 powers on datasheet page 22. I do not think my design follows the POWER SEQUENCING.

  •  thank you for your answer.

    "when they all of a sudden failed" did literally "all" fail or just a few? How did you solve the problem, did you switch to another product? Or was this just a faulty batch of ADXL355? Was your sensor exposed to accelerations above the measurment range or not?

    I'm trying to figer out if I am just using the wrong product for my application or if this issu is just related to a faulty adxl357.

    Interesting at my case is, that I have two adxl357 mounted at almost the same location (exposed to the same vibrations). One suffers from the problem the other one does not. AND they are certainly from different production batches of AD.

  • @RCachro851 In an other thread I read that you sent a faulty adxl355 to ad for investigation. What was the result of this investigation?

  • No the sensors were never subjected an acceleration beyond the measurement range; that was confirmed. It is an issue related to the inherent design of the adxl MEMS sensor. We would have sensors fail out in the field randomly and without cause. How many, I don't recall. But enough for us to have to cancel production.

Reply Children
No Data