About chris1seto

See the attached file for the log of timings. ... View more

I tried to reply to this before, but I think the Bosch forum software is having an issue or my post is stuck in moderation.  Regardless, the issue is that in my code, I take the timestamp of the sample when the bme680 is done sampling. This is 2mS off of the next_call time which the bsec wants. After a while, this results in the bsec returning the timing error. My code is doing nothing but attending to the bsec, but obviousl it's impossible form e ot reall have data taken exactly to the nanosecond that the bsec wants. I think the bsec is far too senstive to this, especially if the mcu is going other things in addition to the bsec sampling. If I fake it and just tell the bsec that the sample timestamp is the previous next_call value everything seems to work fine.  ... View more

Turns out I am getting an error: BSEC_W_SC_CALL_TIMING_VIOLATION. So there must be a timing issue somewhere.... everything for the bsec is in nanoseconds, and my ticks are in mS...  So will look for issues in my conversion unless you see one. ... View more

Hi, Unfortunatly, this does not fix the issue. The updates do some in at the lower frequency, but after a smaller number of them, the bsec goes into the same mode of failure seen here where it does not trigger and gives long timeouts. It seems like this might be time related perhaps, where the bsec will only work for a certain amount of time once it is started? Any additional ideas? I'm trying to fast track a demo of this for a production application so I'd really like to get this running quickly. ... View more