Hi, Seems like you were right, the timestamp output is set to 2657000 and stays there after 33.5s of system time. Added the logs with the get_timestamp_us call to it. what I am seeing is this (bsec_integration line 637): time_stamp_interval_ms = (sensor_settings.next_call - get_timestamp_us() * 1000) / 1000000; return time_stamp_interval_ms; after a few times get_timestamp_us is returning the time_stamp_interval_ms value of 2.7s instead of the system time which is why it keeps outputting the 33.5s runtime. 33.5s seems to be the maximum value of the clock before it is resetting which seems to be causing the problem. Any advice on how to handle the clock timer exceeding max value for BSEC scheduling? NOTE: my max value is 33.5s because my system clock seems to be of type uint32_t and CLOCK_SECOND is 128 (4,294,967,295/128 = 335....)
... View more