hdfirmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-7091: Addressed code reviews

    • -6
    • +6
    /firmware/App/Modes/ConsumableSelfTest.c
    • -16
    • +15
    /firmware/App/Modes/SampleWater.c
If DG somehow gets ahead of HD here, I worry we will get stuck. Consider second condition with "getDGSubMode() >= DG_FILL_MODE_STATE_BICARB_PUMP_CHECK". Same for states below.

If DG somehow gets ahead of HD here, I worry we will get stuck. Consider second condition with "getDGSubMode() >= DG_FILL_MODE_STATE_BICARB_PUMP_CHECK". Same for states below.

When using build switches, convention is to put the normal code first. So use #ifndef and swap the statements below.

When using build switches, convention is to put the normal code first. So use #ifndef and swap the statements below.

When the sample water result entered by the user, HD will command DG to end water sampling mode and go back to standby idle state.

When the sample water result entered by the user, HD will command DG to end water sampling mode and go back to standby idle state.

Why is bad sample result handled here and good sample result handled in pre-treatment mode?

Why is bad sample result handled here and good sample result handled in pre-treatment mode?

How will DG standby get back to idle state from flush idle state? Where does that happen?

How will DG standby get back to idle state from flush idle state? Where does that happen?

Use set dialysate temp from treatment parameters for trimmer heater target temp. Add 2 degrees for primary heater target temp.

Use set dialysate temp from treatment parameters for trimmer heater target temp. Add 2 degrees for primary heater target temp.

Add fault.

Add fault.

Consider renaming this to sampleWaterResultEntered to clarify its purpose.

Consider renaming this to sampleWaterResultEntered to clarify its purpose.

Should we check here if calibration data is valid?

Should we check here if calibration data is valid?

Where is this getHDFlowSensorsCalibrationRecord function located? Is it part of fwcommon changes? If yes, please add to code review.

Where is this getHDFlowSensorsCalibrationRecord function located? Is it part of fwcommon changes? If yes, please add to code review.

Remove this typedef. It is defined in common repo.

Remove this typedef. It is defined in common repo.

Remove this case. Its obsolete.

Remove this case. Its obsolete.

Comment's first letter needs to be capitalized.

Comment's first letter needs to be capitalized.

DEN-7091: Added timeout to i2c receive

DEN-7117: Fixed volume safety check for rinseback and blood prime. Added more interface functions to syringe pump driver.

    • -1
    • +37
    /firmware/App/Controllers/SyringePump.c
    • -0
    • +2
    /firmware/App/Controllers/SyringePump.h
Fixed merge conflicts.

DEN-7117: Fix saline bolus safety check.

Merge branch 'develop' of ssh://dvm-linux02:7999/hd/hdfirmware into develop

Fixed saline bolus safety check. Will add changes to dev branch.

Merge branch 'DEN-7091-pre-treatment-mode' into develop

    • -2
    • +6
    /firmware/App/Controllers/DGInterface.c
    • -2
    • +0
    /firmware/App/Controllers/DGInterface.h
DEN-7091: Added build switch to disable battery comm

Merge branch 'DEN-7117-hd_dev-hd-heparin-delivery' into develop

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Make it private function to this module and call from DG monitor function.

Make it private function to this module and call from DG monitor function.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.