Dashboard

right now pre and post are same. make a TODO to update post later

right now pre and post are same. make a TODO to update post later

its mixing control interval

its mixing control interval

LEAHI-DRYDEMO-LDT-4899_SW Misc & Enhc - SW - 01 - Dry-Demo Software - Main-Tx - R&I
LEAHI-DRYDEMO-LDT-4899_SW Misc & Enhc - SW - 01 - Dry-Demo Software - Main-Tx - R&I
LDT-4899 worked on the treatment pause and treatment rinseback

    • -10
    • +85
    /sources/drydemo/DryDemoDefines.h
    • -77
    • +167
    /sources/drydemo/StateController.cpp
    • -11
    • +33
    /sources/drydemo/StateController.h
    • -0
    • +128
    /sources/drydemo/StateControllerRinseback.cpp
    • -0
    • +152
    /sources/drydemo/StateControllerStandby.cpp
    • -252
    • +5
    /sources/drydemo/StateControllerTreatment.cpp
    • -0
    • +256
    /sources/drydemo/StateControllerTreatmentBroadcasts.cpp
could you document th math behind the calculation also

could you document th math behind the calculation also

LEAHI-APPLICATION-LDT-4959_SW Misc & Enhc - SW - 01 - SW Integration - Calibration - R&I
LEAHI-APPLICATION-LDT-4959_SW Misc & Enhc - SW - 01 - SW Integration - Calibration - R&I
LDT-4772 NON-FEATURE: SW Misc & Enhc - SW - 01 - Isolated UF - R&I - 05: DEV - Feature Implementation

updated edit iso uf edit

it will be adjusted when I merge latest staging

it will be adjusted when I merge latest staging

not required anymore, forgot to remove

not required anymore, forgot to remove

I think a comment here is needed. Keep it and maybe mention rinseback alarm responses too.

I think a comment here is needed. Keep it and maybe mention rinseback alarm responses too.

Maybe this should be handled in OperationModes exec since it applies to all confirmations (not just alarm related ones).

Maybe this should be handled in OperationModes exec since it applies to all confirmations (not just alarm related ones).

There will be confirmations that are not handled here (e.g. power off). So we shouldn't fault in default - we should do nothing.

There will be confirmations that are not handled here (e.g. power off). So we shouldn't fault in default - we should do nothing.

Shutdown would be handled somewhere else (buttons.c probably). It's not related to alarms.

Shutdown would be handled somewhere else (buttons.c probably). It's not related to alarms.

Is this still possible since we're not returning to TxPaused from rinseback anymore?

Is this still possible since we're not returning to TxPaused from rinseback anymore?

added

added

updatead

updatead

removed

removed

LDT-5079 SW Misc & Enhc - SW - 01 - Miscellaneous - Feature Complete - R&I - 05: DEV - Feature Implementation

aaddress cr comments

New Driver Add ons

LDT-4614 addressed review comments

LDT-4614 addressed review comments

    • -25
    • +22
    /firmware/App/Controllers/MixingControl.c
    • -8
    • +3
    /firmware/App/Modes/ModePreGenDialysate.c
    • -18
    • +16
    /firmware/App/Services/TDInterface.c
New Driver Add ons

    • -420
    • +600
    /firmware/App/Drivers/PinchValve.c
    • -30
    • +49
    /firmware/App/Drivers/PinchValve.h
LDT-4987 SW Misc & Enhc - SW - 01 - SW Integration - Pre-Tx - R&I - 08: DEV - Dialin Implementation

update modality option list

    • -0
    • +1
    /configurations/Parameters/DataList.conf
LDT-4987 SW Misc & Enhc - SW - 01 - SW Integration - Pre-Tx - R&I - 08: DEV - Dialin Implementation

update initate tx request

LDT-4984 SW Misc & Enhc - SW - 01 - SW Integration - Pre-Tx - R&I - 05: DEV - Feature Implementation

update initiate tx message to include modality

    • -2
    • +3
    /sources/gui/qml/components/HeaderBar.qml
    • -0
    • +17
    /sources/gui/qml/pages/MainHome.qml