BMI085 frame arrives much earlier

[ysqcn]

Hi

We test gyro+accel together, and  observer a case that a frame may arrive much earlier than expected.

It happens very rarely, and only see it when both gyro  and accel are enabled. Only accel or only gyro doesn't have such issue

We use the official github driver, and would you please comment the possible reason?

E.g. bellow frame 3557, the timer interval with previous frame 3556 is just 310, and expected interval is ~4960

accel loop:0 frame_id:3556 frame_num:3556  x:-8.112 y:3.759 z:3.721 timestamp:1757615540 timeInterVal:4964 
accel loop:0 frame_id:3557 frame_num:3557  x:-8.112 y:3.759 z:3.721 timestamp:1757615850 timeInterVal:310 
accel loop:0 frame_id:3558 frame_num:3558  x:-8.361 y:3.673 z:3.610 timestamp:1757620504 timeInterVal:4654 
accel loop:0 frame_id:3559 frame_num:3559  x:-8.878 y:3.974 z:3.711 timestamp:1757625468 timeInterVal:4964 

[BSTRobin]

Hi ysqcn,

Could we know the following information fron you?

1. Which example code file you used on github?
2. What sensor parameters you configured?

[ysqcn]

Thank you for reply, here is the information

1.  Driver is from https://github.com/BoschSensortec/BMI08x-Sensor-API

2. Use the setting from BMI08x-Sensor-API/examples/interrupt_streaming_pc

[BSTRobin · Accepted solution]

Hi ysqcn,

You could run this example code and test it again.
https://github.com/BoschSensortec/BMI08x-Sensor-API/blob/master/examples/read_sensor_data/read_senso...