td-firmware

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

    • -20
    • +20
    /firmware/App/Controllers/Valves.c
    • -46
    • +116
    /firmware/App/Drivers/PinchValve.c
    • -501
    • +0
    /firmware/App/Drivers/RotaryValve.c
    • -70
    • +0
    /firmware/App/Drivers/RotaryValve.h
please add a TODO or remove commented code.

please add a TODO or remove commented code.

please add a TODO or remove commented code.

please add a TODO or remove commented code.

add resumeTreatmentAlarmResponseRequest to output

add resumeTreatmentAlarmResponseRequest to output

Update input - output list.

Update input - output list.

Add presUFRateMlMin to outputs

Add presUFRateMlMin to outputs

recirculateToBloodPrimeRequest is output.

recirculateToBloodPrimeRequest is output.

Add initialization for rinsebackToRecircRequest and recirculateToBloodPrimeRequest

Add initialization for rinsebackToRecircRequest and recirculateToBloodPrimeRequest

So then no need to initialize it here too. Remove " = FALSE".

So then no need to initialize it here too. Remove " = FALSE".

I agree but it is already in the init function.

I agree but it is already in the init function.

LDT-4040: Address CR comments

    • -9
    • +9
    /firmware/App/Modes/StateTxRinseback.c
Swap order of == for these 2 if statements - put constant on left side.

Swap order of == for these 2 if statements - put constant on left side.

Why?

Why?

Why is UF volume being added here? If we add it, we need to change DD f/w too. But it is not clear to me why DD f/w needs to know the UF volume.

Why is UF volume being added here? If we add it, we need to change DD f/w too. But it is not clear to me why DD f/w needs to know the UF volume.

Use ternary operator to explicitly set to TRUE or FALSE.

Use ternary operator to explicitly set to TRUE or FALSE.

LDT:4049- addressed review comments

    • -11
    • +13
    /firmware/App/Modes/ModeStandby.c
Our TODO comments are all CAPs.

Our TODO comments are all CAPs.

I think these if statements should be looking for valve state == VALVE_STATE_IDLE, not <

I think these if statements should be looking for valve state == VALVE_STATE_IDLE, not <

Fix implementation to return a BOOL (TRUE if SW_COMPATIBILITY_REV == ddVersion.compatibilityRev.

Fix implementation to return a BOOL (TRUE if SW_COMPATIBILITY_REV == ddVersion.compatibilityRev.

Should return T/F. Change comment to "TRUE if DD f/w is compatible with TD f/w, FALSE if not.".

Should return T/F. Change comment to "TRUE if DD f/w is compatible with TD f/w, FALSE if not.".

Should return a BOOL (that is what ModeStandby is expecting).

Should return a BOOL (that is what ModeStandby is expecting).

Fix isDDCompatible() function so that it returns a T/F instead of a compatibility revision.

Fix isDDCompatible() function so that it returns a T/F instead of a compatibility revision.

Align comment.

Align comment.

Why are these added? And why commented out. H13 and H20 are not rotary valves - they are 3 way valves. They do not belong here.

Why are these added? And why commented out. H13 and H20 are not rotary valves - they are 3 way valves. They do not belong here.

Messaging ID configuration

LDT:4072-addressed review comments

    • -10
    • +17
    /firmware/App/Monitors/Battery.c
LDT:4049 Addressed review comments

    • -317
    • +11
    /firmware/App/Modes/ModeStandby.c
Should we handle blood sitting timer before publish? Are we publishing anything re: blood sitting?

Should we handle blood sitting timer before publish? Are we publishing anything re: blood sitting?