- I discovered that when any other update rate is used (non LP & non ULP), an error is returned as expected. However when an update rate of 1 second (and 0.999 too) is used, the BSEC works and returns samples, however it returns samples at a 2 second interval. Is this a bug in that it should report an invalid sample rate when 1.0 is passed in or is there some purpose for a non documented update rate of 1.0 which returns samples at a 2.0 interval?
Your integration of BSEC is not clear to me, but the sensor's settings/profile is provide by BSEC based on the sample rate you provided in bsec_update_subscription(). If the ULP rate was used, then it is expected that each measurement takes about 2 seconds. Having no warning/error when calling BSEC at 1Hz could be a bug.
- The reason I'm asking is because I need a faster update rate with the IAQ data. Maybe twice a second instead of once every 3 seconds. Is there any way to have BSEC return a IAQ faster than every 3 seconds?
Currently the only modes officially supported are LP and ULP modes. As mentioned in a previous thread, we are considering adding a new mode with a faster data rate, but we have no release date planned yet, and don't support such long-term operations until fully qualified.
- Lastly are any other config profiles available (bsec_config_iaq) other than the 3s and 300s profiles?
No. The full list and description of configurations available can be found the Integration Guide in BSEC's package.
... View more
The save rate is only for the next power on, right? The data is not saved and loaded otherwise, correct?
Power cycles is typically when you would expect/want to reload the state. In some applications the state of BSEC's internal variables in RAM cannot be saved when entering deep sleep (e.g. of the MCU). Is such a case it would be mandatory to save/restore BSEC's state for every sample.
What are the advantages and disadvantages of having a more frequent save_data rate? Why wouldn't you choose say every 5 minutes or ever hour or something?
For the sake of BSEC, the impact on the application was described in my previous post. In practice you may need to consider other HW requirements, such as the number of write cycles of your non-volatile memory (e.g. already over 100k times per year if saved every 5 minutes), etc.
... View more