dd-firmware

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge branch 'staging' into LDT-3972-water-treatment-and-degassing-1

Merge branch 'staging' into LDT-4000-hdf-fw-implementation-1

LDT-3980 addressed review comments

    • -3
    • +10
    /firmware/App/Controllers/DryBiCart.c
Nope. Since we are here after level is LOW (fill request from balancing chamber control state machine) and not filled yet. So level is still LOW

Nope. Since we are here after level is LOW (fill request from balancing chamber control state machine) and not filled yet. So level is still LOW

LDT-3978 firmware implementation for ocean spray

    • -87
    • +77
    /firmware/App/Controllers/DryBiCart.c
First two logics ANDed correct (first cycle and close period). the third one (BC switch only must be ANDed only with close period), not to include first cycle..

First two logics ANDed correct (first cycle and close period). the third one (BC switch only must be ANDed only with close period), not to include first cycle..

LDT-3975 WIP initial draft for boost pump refactor

    • -84
    • +212
    /firmware/App/Controllers/BoostPump.c
    • -3
    • +13
    /firmware/App/Controllers/BoostPump.h
    • -2
    • +2
    /firmware/App/Modes/FPModes/ModeGenPermeate.c
    • -1
    • +1
    /firmware/App/Modes/FPModes/StateFlushFilter.c
LEAHI-DD-FIRMWARE-LDT-4188_SW/FW integration to run a Treatment from UI
LEAHI-DD-FIRMWARE-LDT-4188_SW/FW integration to run a Treatment from UI
Can we check payload.index is equal to D6_LEVL (instead of above comparision)?

Can we check payload.index is equal to D6_LEVL (instead of above comparision)?

Do we need to check if bicarb chamber level is high, ignore opening D80?

Do we need to check if bicarb chamber level is high, ignore opening D80?

This doesn't seem to be correct. Persistence should start once fill complete pressure is achieved, not after D65 opening?

This doesn't seem to be correct. Persistence should start once fill complete pressure is achieved, not after D65 opening?

Align comment

Align comment

Add comment.

Add comment.

Bamboo Commit: Updated DDCommon.h with build versions from Bamboo.

Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

Merge branch LDT-3980-dialysate-composition-dry-bicarb---fw-impl into staging

LEAHI-DD-FIRMWARE-LDT-3975_Water Treatment and Degassing - FW Iteration - 4/4:
LEAHI-DD-FIRMWARE-LDT-3975_Water Treatment and Degassing - FW Iteration - 4/4:
Remove space after 'Supply'.

Remove space after 'Supply'.

Align the value declaration indentation.

Align the value declaration indentation.

looks you are already checking this state in a line above.

looks you are already checking this state in a line above.

Bamboo Commit: Updated DDCommon.h with build versions from Bamboo.

Merge branch LDT-3978-switch-chamber-f-conductive-lev into develop

    • -23
    • +23
    /firmware/App/Controllers/DryBiCart.c
    • -3
    • +3
    /firmware/App/Modes/ModeGenDialysate.c
LDT-3978 fix for conductive level sensor

LDT-872 hetaer control

    • -127
    • +40
    /firmware/App/Controllers/Heaters.c
    • -2
    • +2
    /firmware/App/Modes/ModeGenDialysate.c
Add a blank line before group end marker.

Add a blank line before group end marker.

Are we only doing DD messages? And since these could be coming from UI now, these shouldn't be considered "Dialin" messages anymore and should be moved up to section before 0x8000 IDs where normal ...

Are we only doing DD messages?
And since these could be coming from UI now, these shouldn't be considered "Dialin" messages anymore and should be moved up to section before 0x8000 IDs where normal system messages are defined.

Don't assign BOOL variables implicitly. Always assign a FALSE or TRUE explicitly with ternary operator or inside an if statement.

Don't assign BOOL variables implicitly. Always assign a FALSE or TRUE explicitly with ternary operator or inside an if statement.

Declare local variables at top of scope.

Declare local variables at top of scope.

Add space between ( and ?

Add space between ( and ?