hdfirmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-8679: Refactor alarm activate functions

Sent events only for changed settings.

Sent events only for changed settings.

Set UF volume initially to 0 and removed this variable and related function.

Set UF volume initially to 0 and removed this variable and related function.

It is part of background task in the battery monitor exec function. The initial value is 0, we will wait here till we get status.

It is part of background task in the battery monitor exec function. The initial value is 0, we will wait here till we get status.

Done. I prefer generally output description, so refactor is easier. Normally, a refactor will often make these variables in the doxygen comment obsolete (variable name change).

Done. I prefer generally output description, so refactor is easier. Normally, a refactor will often make these variables in the doxygen comment obsolete (variable name change).

Dara Navaei Please take a look.

Dara Navaei Please take a look.

This message is requested by UI. UI wants to keep it consistent with other request message, in case there is reject reason in the future.

This message is requested by UI. UI wants to keep it consistent with other request message, in case there is reject reason in the future.

Removed.

Removed.

If fault mode calls the treatment log data collect function, the record can be zeroed also.

If fault mode calls the treatment log data collect function, the record can be zeroed also.

The transition function will call this init function.

The transition function will call this init function.

DEN-8679: Addressed code review

    • -4
    • +21
    /firmware/App/Modes/ModeTreatment.c
    • -16
    • +2
    /firmware/App/Modes/ModeTreatmentParams.c
    • -1
    • +0
    /firmware/App/Modes/ModeTreatmentParams.h
Done.

Done.

Fixed.

Fixed.

Fixed.

Fixed.

Done.

Done.

The else is when AC power detected. Added clear alarm condition.

The else is when AC power detected. Added clear alarm condition.

DEN-9054 changed the build history file form text to log

    • -0
    • +18
    /firmware/hd_build_history.log
DEN-9054 aligned the build history file

DEN-8886: Added UI compatibility POST test. Updated alarm audio per latest HDD. Added handling of UI and DG version messages. Fixed watchdog POST. Added recovery check to watchdog POST.

    • -12
    • +43
    /firmware/App/Modes/ModeInitPOST.c
    • -8
    • +28
    /firmware/App/Services/WatchdogMgmt.c
Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

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

Merge branch 'DEN-8886-hd_dg_dev-self-tests-2-of-2' into develop

    • -21
    • +21
    /firmware/App/Controllers/BloodFlow.c
    • -25
    • +37
    /firmware/App/Controllers/DialInFlow.c
    • -39
    • +44
    /firmware/App/Controllers/DialOutFlow.c
    • -33
    • +169
    /firmware/App/Modes/BloodPrime.c
    • -13
    • +63
    /firmware/App/Modes/ModeInitPOST.c
    • -1
    • +1
    /firmware/App/Modes/ModeTreatmentParams.c
    • -28
    • +68
    /firmware/App/Services/AlarmMgmt.c
    • -26
    • +7
    /firmware/App/Services/Interrupts.c
    • -26
    • +12
    /firmware/App/Services/SystemComm.c
  1. … 4 more files in changeset.
Merge branch 'DEN-7802-dg_dev-dialysate-generation' into develop

    • -5
    • +57
    /firmware/App/Controllers/DGInterface.c
    • -24
    • +26
    /firmware/App/Controllers/DGInterface.h
DEN-7802: Add build flag to disable dialysate temperature

    • -6
    • +4
    /firmware/App/Controllers/DGInterface.c
Remove pack for blood prime data

Merge branch 'DEN-8679-hd_dev-treatment-log' into develop

    • -1
    • +14
    /firmware/App/Controllers/DGInterface.c
    • -13
    • +26
    /firmware/App/Controllers/DGInterface.h
Seems like the two states given as data are not very meaningful. Consider just setting before/after data to zero for this event.

Seems like the two states given as data are not very meaningful. Consider just setting before/after data to zero for this event.

Not sure this variable (and related get function) are needed.

Not sure this variable (and related get function) are needed.

User may not have changed all 4 settings. Should we only send events for those that actually changed?

User may not have changed all 4 settings. Should we only send events for those that actually changed?

I think this will be the time we initiate a treatment. Is that what we want? Or should we move this to transition function to capture time of treatment start?

I think this will be the time we initiate a treatment. Is that what we want? Or should we move this to transition function to capture time of treatment start?