The measurement time is hardcoded using a delay of 40ms:
|
delay.delay_ms(40).await.map_err(|_| Error::Delay)?; // await measurement |
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 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
Configurationstruct? 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.