The set up is:
Teensy41
Adafruit bmp388 over I2C
openSUSE Leap 15.3
Arduino 1.8.19
teensyduino 1.59
The plan was after powering on some pressure samples (5, 250, ...) are made and from there the gained altitude is measured.
At first the noise of the bmp388 forced me to use the SimpleKalmanFilter library.
I have sampled several times 5000 values (03:20 [mm:ss]) and had a look at the charts.
Sometimes it is a PT1, one had an over shoot and another one a over shoot and slope afterwards:
By only looking on
- a difference
- a gradient (m=dy/dx, from sample to sample with micros=9700)
- >= 0 or <= 0
it will be triggered by the first appearance, which is useless.
(i.e. first: 190 however after 1524 0 is kept)
From my point of view adding a dead band or a hysteresis does not solve it either.
How to identify the steady state, peaks (highest altitude) or slopes?
How to cope with the flickering between a low value and a solid 0, which lasts longer than any other change during the value decay?
Any ideas are very welcome!
Teensy41
Adafruit bmp388 over I2C
openSUSE Leap 15.3
Arduino 1.8.19
teensyduino 1.59
The plan was after powering on some pressure samples (5, 250, ...) are made and from there the gained altitude is measured.
At first the noise of the bmp388 forced me to use the SimpleKalmanFilter library.
I have sampled several times 5000 values (03:20 [mm:ss]) and had a look at the charts.
Sometimes it is a PT1, one had an over shoot and another one a over shoot and slope afterwards:
By only looking on
- a difference
- a gradient (m=dy/dx, from sample to sample with micros=9700)
- >= 0 or <= 0
it will be triggered by the first appearance, which is useless.
(i.e. first: 190 however after 1524 0 is kept)
From my point of view adding a dead band or a hysteresis does not solve it either.
How to identify the steady state, peaks (highest altitude) or slopes?
How to cope with the flickering between a low value and a solid 0, which lasts longer than any other change during the value decay?
Any ideas are very welcome!