You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm looking for justification for the sleep functions in the sensor reading methods.
There is a commit from May 2020 stating they were added to fix timing issues. But I wonder if they really needed to be added to the sensor reading methods. They significantly reduce the max sample rate on the raspberry pi, and I haven't had any issues since removing them: 516f2dc
I'd like to create a pull request unless I have mistaken their purpose.
The text was updated successfully, but these errors were encountered:
Hello, according to my tests, there could be 3 situations that timing is important:
After, Reset (soft-reset) DEVICE_RESET in the PWR_MGMT_1 register
After Sleep
After reading a different memory bank. But, not sure about this.
Maybe the logic behind removing the sleep from the acc, gyro readings was that probable you could read the 6 values (7 with temp) in one shot, so time was less sensitive there.
Hi, I'm looking for justification for the sleep functions in the sensor reading methods.
There is a commit from May 2020 stating they were added to fix timing issues. But I wonder if they really needed to be added to the sensor reading methods. They significantly reduce the max sample rate on the raspberry pi, and I haven't had any issues since removing them:
516f2dc
I'd like to create a pull request unless I have mistaken their purpose.
The text was updated successfully, but these errors were encountered: