dd-firmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Logic update

This was added by Vinay to force the chamber F filling.

This was added by Vinay to force the chamber F filling.

It was changed by Vinay as part of the Conductivity spikes issue.

It was changed by Vinay as part of the Conductivity spikes issue.

This is a problem, when lower cart pressure, D80 closes and if it is not reached upper cart pressure, it won't open D80

This is a problem, when lower cart pressure, D80 closes and if it is not reached upper cart pressure, it won't open D80

Why do we need 1 minutes of D80 opening ? is it not filling withing 10 seconds ?

Why do we need 1 minutes of D80 opening ? is it not filling withing 10 seconds ?

bicarbChamberLevel is a local variable and not an input

bicarbChamberLevel is a local variable and not an input

This is not required , we should design the state machine properly to handle chamber low level

This is not required , we should design the state machine properly to handle chamber low level

This is not the correct order for state machine,

This is not the correct order for state machine,

LDT-5157: Resolved all build errors

    • -151
    • +134
    /firmware/App/Services/NVMessagingDD.c
    • -73
    • +265
    /firmware/App/Services/NVRecordsDD.c
    • -21
    • +3
    /firmware/App/Services/NVRecordsDD.h
LDT-4049:DDstandby review

    • -26
    • +25
    /firmware/App/Modes/ModeStandby.c
LDT-5157: Updated set handlers

    • -819
    • +607
    /firmware/App/Services/NVMessagingDD.c
    • -925
    • +114
    /firmware/App/Services/NVRecordsDD.c
    • -99
    • +24
    /firmware/App/Services/NVRecordsDD.h
At end of transition, do you want to initialize the totalSpentChamberFill reset to zero?

At end of transition, do you want to initialize the totalSpentChamberFill reset to zero?

Could you use SpentChamberLevel here, instead calling the getLevelStatus function again? Same for next conditions check as well ( line:889)

Could you use SpentChamberLevel here, instead calling the getLevelStatus function again? Same for next conditions check as well ( line:889)

Remove extra paranthesis.

Remove extra paranthesis.

Remove empty lines

Remove empty lines

Mention in comment this is equivalent to Qd:600 minus 50ms switching period to stabilize the valve closure.

Mention in comment this is equivalent to Qd:600 minus 50ms switching period to stabilize the valve closure.

Update the comment for Spent chamber fill, max dialysate flow rate (Qd:600) used for fast filling.

Update the comment for Spent chamber fill, max dialysate flow rate (Qd:600) used for fast filling.

LDT-3223-dialysate-flow-rate---dd---mode-7-17-2026 : Added test cases for Messaging.c

Fix 2

    • -9
    • +29
    /firmware/App/Modes/ModeGenDialysate.c
LDT-5157: Added Conductivity Sensor Record

    • -14
    • +32
    /firmware/App/Services/Messaging.c
    • -586
    • +1568
    /firmware/App/Services/NVMessagingDD.c
    • -14
    • +48
    /firmware/App/Services/NVMessagingDD.h
    • -162
    • +449
    /firmware/App/Services/NVRecordsDD.c
    • -100
    • +187
    /firmware/App/Services/NVRecordsDD.h
Bamboo Commit: Updated DDCommon.h with build versions from Bamboo.

LDT-4873 merge into develop

    • -5
    • +13
    /firmware/App/Controllers/Heaters.c
LDT-4873 removed empty line

LDT-4873 latest from staging

    • -4
    • +16
    /firmware/App/Controllers/Heaters.c
LDT-4873 fixing cond level sensor alarm

    • -5
    • +14
    /firmware/App/Controllers/Heaters.c
Same question as above: should we alarm if the retries failed?

Same question as above: should we alarm if the retries failed?

This else is not needed because isFlashAddressValid is set to False at the top of the function (Optional to change).

This else is not needed because isFlashAddressValid is set to False at the top of the function (Optional to change).

This else is not needed because isFlashAddressValid is set to False at the top of the function (Optional to change).

This else is not needed because isFlashAddressValid is set to False at the top of the function (Optional to change).

If a retry goes wrong will you trigger an alarm?

If a retry goes wrong will you trigger an alarm?