firmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-12961 addressed VectorCAST issues raised by PiSquare

DEN-12961 addressed VectorCAST issues raised by PiSquare

DEN-12961 updated the VectorCAST tests

DEN-12847 Zero out the LoadCellBackupReadings. Updated ouput debug message.

Merge branch 'staging' into DEN-12961-sw_dev_sprint_72_dong

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

Merged DEN-12931

DEN-12931 updated the blood leak driver with the latest zero and self test changes

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

Merge branch 'DEN-12931-dg_hd_dev-hd_dg_dvt-update' into develop

DEN-12931 updated the blood leak driver

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

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

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

Merge branch 'DEN-12931-dg_hd_dev-hd_dg_dvt-update' into develop

    • -190
    • +280
    ./App/Controllers/BloodLeak.c
DEN-12931 updated the blood leak embedded mode

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

DEN-12845 addressed the code review comments

    • -24
    • +0
    ./App/Services/SystemCommMessages.c
Removed the message.

Removed the message.

Should probably log ms - so need to multiply by task interval.

Should probably log ms - so need to multiply by task interval.

This appears to be a timer counter (task intervals, not ms).

This appears to be a timer counter (task intervals, not ms).

These are redundant with above. Keep above definitions as they have the 'F' suffix that we want. Remove these.

These are redundant with above. Keep above definitions as they have the 'F' suffix that we want. Remove these.

Add blank line between functions.

Add blank line between functions.

Not sure if this is an issue - but looks like this clear alarm condition check can happen even when occlusion level after install hasn't been set yet.

Not sure if this is an issue - but looks like this clear alarm condition check can happen even when occlusion level after install hasn't been set yet.

Add space after ifs.

Add space after ifs.

We got recommendation to monitor arterial pressure even when not dialyzing if patient is still connected (so all other treatment mode states other than dialysis when not delivering saline bolus), b...

We got recommendation to monitor arterial pressure even when not dialyzing if patient is still connected (so all other treatment mode states other than dialysis when not delivering saline bolus), but didn't want to apply the user provided limits - just want to monitor for max pressure situation.

Im assuming that this if statement covers sub modes like Saline and Blood Prime. How do we know during blood prime, specifically, that we would not be dealing with an edge case in treatment paramet...

Im assuming that this if statement covers sub modes like Saline and Blood Prime. How do we know during blood prime, specifically, that we would not be dealing with an edge case in treatment parameters for the patient (Ex: -300 mmHg to -270 mmHg) and triggering a false positive alarm?

Note: I dont know actual patient bp values but these are currently acceptable treatment parameters for arterial pressure limits.