Thingy91: adxl372 accel_polling example not giving proper data.

Hi,

I am trying to test adxl372 on thing91 board using accel_polling example.

I created required alias for adxl372 as mentioned in the example document.

On running the app on thingy91 I am able to get the serial logs printing data on X, Y and Z axis, but the values do not change on respective axis on changing device orientation.

Using same example for adxl362 gives variation in data on respective axis as per orientation.

Is there any specific configuration required for adxl372, or any modification required in the accel_polling example?

Parents
  • Hi  ,

    I have a similar issue.

    At first, it is always 0, I added this configuration

    CONFIG_ADXL372_MEASUREMENT_MODE=y

    then the value began jumpy all the time.

    Look at these measurements I got, it changes a lot even if there is no movement.

           adxl372@1 [m/s^2]:    (  -13.729184,     6.864592,    -4.903280)
    
    
    
    
           adxl372@1 [m/s^2]:    (   -2.941968,    -3.922624,    -7.845248)
    
    
    
    
           adxl372@1 [m/s^2]:    (   -1.961312,    -0.980656,     0.000000)
    
    
    
    
           adxl372@1 [m/s^2]:    (   -1.961312,    19.613120,    -6.864592)
    
    
    
    
           adxl372@1 [m/s^2]:    (  -12.748528,     1.961312,     0.000000)
    
    
    
    
           adxl372@1 [m/s^2]:    (   -3.922624,     0.000000,   -12.748528)
    
    
    
    
           adxl372@1 [m/s^2]:    (   -8.825904,   -15.690496,    -0.980656)
    
    
    
    
           adxl372@1 [m/s^2]:    (   -8.825904,   -10.787216,     3.922624)
    
    
    
    
           adxl372@1 [m/s^2]:    (    9.806560,     1.961312,     2.941968)
Reply
  • Hi  ,

    I have a similar issue.

    At first, it is always 0, I added this configuration

    CONFIG_ADXL372_MEASUREMENT_MODE=y

    then the value began jumpy all the time.

    Look at these measurements I got, it changes a lot even if there is no movement.

           adxl372@1 [m/s^2]:    (  -13.729184,     6.864592,    -4.903280)
    
    
    
    
           adxl372@1 [m/s^2]:    (   -2.941968,    -3.922624,    -7.845248)
    
    
    
    
           adxl372@1 [m/s^2]:    (   -1.961312,    -0.980656,     0.000000)
    
    
    
    
           adxl372@1 [m/s^2]:    (   -1.961312,    19.613120,    -6.864592)
    
    
    
    
           adxl372@1 [m/s^2]:    (  -12.748528,     1.961312,     0.000000)
    
    
    
    
           adxl372@1 [m/s^2]:    (   -3.922624,     0.000000,   -12.748528)
    
    
    
    
           adxl372@1 [m/s^2]:    (   -8.825904,   -15.690496,    -0.980656)
    
    
    
    
           adxl372@1 [m/s^2]:    (   -8.825904,   -10.787216,     3.922624)
    
    
    
    
           adxl372@1 [m/s^2]:    (    9.806560,     1.961312,     2.941968)
Children
  • Hi,

    I'm afraid my problem from the above mentioned ticket is not the same problem.
    For my problem, the most time my values largely meet my requirements.
    There are only sporadically extremely high values that I can not explain.

    But I have also seen that the values of the ADXL372 are very noisy in the lower range. Therefore, I read both sensors and take only the ADXL372 values if the acceleration values are higher than 8G. Otherwise I take the values of the ADXL362.
    May be this could be also usefull for you.

    BR Jürgen

  • Hi Jürgen,

    Thank you for your response!

    Sorry to confuse you, but here is not your ticket. So it would be good if we move to other places to discuss. Sorry!

    Yes, it is noisy, but as the datasheet mentioned, the typical noise is 3LSB, as it is 100mg/LSB, so the typical noise would be 0.1g*3=2.94m/s2 if I am correct.

    So no reason to be that jumpy in my case.

Related