SystemCommMessages.c

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Why removed?

Why removed?

Why removed? I thought we needed this for VC?

Why removed? I thought we needed this for VC?

F has been added.

F has been added.

No. Code removed.

No. Code removed.

If no actions handled in this mode, add a comment saying so.

If no actions handled in this mode, add a comment saying so.

Yes, at bottom of exec function above.

Yes, at bottom of exec function above.

Remove blank line.

Remove blank line.

Can we remove this now?

Can we remove this now?

Why?

Why?

Why?

Why?

HD-DEN-13141_Miscellaneous HD Issues BB
HD-DEN-13141_Miscellaneous HD Issues BB
Check NEARLY_ZERO #define. Value should be 0.00000001F. I believe previous review commented indicated that all floating point #defines should have "F" at the end.

Check NEARLY_ZERO #define. Value should be 0.00000001F. I believe previous review commented indicated that all floating point #defines should have "F" at the end.

SW_CONFIG_ENABLE_VALUE should be first in the conditional.

SW_CONFIG_ENABLE_VALUE should be first in the conditional.

Need #define for minimum vRef

Need #define for minimum vRef

Is the data being published elsewhere?

Is the data being published elsewhere?

Is this supposed to have been removed.

Is this supposed to have been removed.

indent of cases looks too small.

indent of cases looks too small.

Looks like exit normal request (below) will take precedence over this request. Is that intended?

Looks like exit normal request (below) will take precedence over this request. Is that intended?

Update input/outputs throughout.

Update input/outputs throughout.

Add blank line before return.

Add blank line before return.

Do we want to keep this debug & sprintf?

Do we want to keep this debug & sprintf?

HD-DEN-12931_DG HD Dev HD DG Dvt Update
HD-DEN-12931_DG HD Dev HD DG Dvt Update
RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Removed the message.

Removed the message.

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.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.