Mercurial > public > ostc4
changeset 814:26ae9e8f24fd
Dev Bugfix: O2 values of new detected sensors were shown as invalid:
In the previous version sometime O2 values were shown as invalid (red) after a autodetection cycle was run. After sleep/wakeup cycle the status were shown correct. Rootcause was that the out of bounds detection is based on the divesettings while the HW menu were only updating the common settings regarding active / inactive sensors. The problem has been solved by adding an divesettings update within the HW / sensor menu.
| author | Ideenmodellierer |
|---|---|
| date | Sun, 03 Sep 2023 17:58:12 +0200 |
| parents | 1e688b630a6e |
| children | ce8f71217f45 |
| files | Discovery/Src/tMenuEditHardware.c |
| diffstat | 1 files changed, 3 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/Discovery/Src/tMenuEditHardware.c Sun Sep 03 17:53:07 2023 +0200 +++ b/Discovery/Src/tMenuEditHardware.c Sun Sep 03 17:58:12 2023 +0200 @@ -594,6 +594,9 @@ { write_field_on_off(StMHARD3_O2_Sensor3, 30, 95, ME_Y_LINE3, &FontT48, "", sensorActive[2]); } + + stateRealGetPointerWrite()->diveSettings.ppo2sensors_deactivated = pSettings->ppo2sensors_deactivated; + if(settingsGetPointer()->ppo2sensors_deactivated & 1) sensorActive[0] = 0; if(settingsGetPointer()->ppo2sensors_deactivated & 2)