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
This limits the measurement rate to 25Hz, while both the BMP280 and BME280 datasheets say faster updates rates are supported when using lower oversampling and IIR values. Would it make sense to add a measurement delay field to the Configuration struct? The datasheets don't provide the correct values for all combinations of oversampling and IRR filter settings so I think setting the delay is best left to the user.
The text was updated successfully, but these errors were encountered:
The datasheets don't provide the correct values for all combinations of oversampling and IRR filter settings so I think setting the delay is best left to the user.
What do you mean exactly? The measurement delay seems to be defined precisely in chapter 9 of the datasheet. And the IIR Filter doesn't add any delay to measurements. I think the 40ms should just be replaced by the correct value for the specific device settings. Unfortunately the owner of this crate hasn't responded or updated the crate for 11 months, so in the meantime I implemented my own driver which respects this. If you want to fork this one and replace the 40ms by the precise calculation, you can view the code here.
The measurement time is hardcoded using a delay of 40ms:
bme280-rs/src/lib.rs
Line 691 in 051071f
This limits the measurement rate to 25Hz, while both the BMP280 and BME280 datasheets say faster updates rates are supported when using lower oversampling and IIR values. Would it make sense to add a measurement delay field to the
Configuration
struct? The datasheets don't provide the correct values for all combinations of oversampling and IRR filter settings so I think setting the delay is best left to the user.The text was updated successfully, but these errors were encountered: