Dashboard

LDT-3860 SW Misc & Enhc - SW - 01 - General Alarm - Temporary Break - R&I - 05: DEV - Feature Implementation

update notification dialog

    • -0
    • +356
    /sources/gui/qml/dialogs/AlarmDialog.qml
    • -13
    • +5
    /sources/gui/qml/dialogs/AlarmListDialog.qml
Merge branch 'LDT-3910-td_test_conf' into develop

    • -9
    • +8
    /leahi_dialin/fp/filtration_purification.py
-Added TD test config - Updated fp get requests based on latest change in FW

    • -1
    • +2
    /leahi_dialin/common/test_config_defs.py
    • -9
    • +8
    /leahi_dialin/fp/filtration_purification.py
LEAHI-DIALIN-LDT-3910_Request: add TD config flag so that alarms originating from other subsystems don't put the TD into fault mode
LEAHI-DIALIN-LDT-3910_Request: add TD config flag so that alarms originating from other subsystems don't put the TD into fault mode
LDT-3259 merged staging and reserved new messages for TD and DD update signals

LDT-3259 merged staging

LDT-3259 added a command in the project to create a .bin file too

LDT-3259 initial commit of the integrity files

LDT-3805 SW Misc & Enhc - SW - 01 - Usability Requests - R&I - 05: DEV - Feature Implementation

fix interactive image pinc h to zoom

LDT-3259 updated the linker file to start at address 0x10000

LDT-2008: code review comments.

LDT-3909 Misc SW Enhancements - SW - 02 - General Aesthetics - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -20
    • +31
    /suite_leahi/shared/scripts/names.py
    • -0
    • +178
    /suite_leahi/tst_general_aesthetics/test.py
LEAHI-TESTSUITES-LDT-3321_Misc SW Enhancements - SW - 02 - General Aesthetics - Q&R
LEAHI-TESTSUITES-LDT-3321_Misc SW Enhancements - SW - 02 - General Aesthetics - Q&R
LDT-3735: Fixed dependency between NVM files.

    • -11
    • +27
    /firmware/App/Services/NVMgmtDD.c
    • -5
    • +21
    /firmware/App/Services/NVRecordsDD.c
    • -90
    • +93
    /firmware/App/Services/NVRecordsDD.h
FALSE?

FALSE?

FALSE?

FALSE?

FALSE?

FALSE?

Should default be TRUE? If we are being asked to validate an jump to an invalid state, shouldn't we return FALSE?

Should default be TRUE? If we are being asked to validate an jump to an invalid state, shouldn't we return FALSE?

Vinayakam Mani, how does that signal happen normally? In your example, when would DD signal FP when starting pre-gen mode? If that signal happened in pre-gen transition function, it would always ha...

Vinayakam Mani, how does that signal happen normally? In your example, when would DD signal FP when starting pre-gen mode? If that signal happened in pre-gen transition function, it would always happen regardless of how we got to pre-gen mode.

Add comment that these modes not (yet?) supported.

Add comment that these modes not (yet?) supported.

LDT-3103 addressed code review comments and merged latest staging

Merge branch 'staging' into LDT-3103-closed-loop-control-pressure-threshold-fix

    • -4
    • +18
    /firmware/App/Modes/ModeGenDialysate.c
Why do some functions take sensor as a U32 and some as a CONDUCTIVITY_SENSORS_T? The latter seems appropriate.

Why do some functions take sensor as a U32 and some as a CONDUCTIVITY_SENSORS_T? The latter seems appropriate.

Remove blank line.

Remove blank line.

Remove blank line.

Remove blank line.

Add blank line before return.

Add blank line before return.