leahi-common

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
This is right, but we don't have a patient connection state implemented yet so we will get stuck here if we do this now. For now, comment out this line with a TODO to restore when patient connectio...

This is right, but we don't have a patient connection state implemented yet so we will get stuck here if we do this now.
For now, comment out this line with a TODO to restore when patient connection state is implemented and add a temporary line of code to request treatment mode here.

pressure is a param

pressure is a param

command is a param

command is a param

Inputs and Outputs should be none

Inputs and Outputs should be none

Inputs and Outputs should be none

Inputs and Outputs should be none

output should be none

output should be none

break this into two lines

break this into two lines

Similarly, we can move this to line 282 and delete handleBPDriverClearCmdAfterAckState()

Similarly, we can move this to line 282 and delete handleBPDriverClearCmdAfterAckState()

We can move this line to 247 and delete handleBPDriverSendCmdState()

We can move this line to 247 and delete handleBPDriverSendCmdState()

Should we be looking at tubing set type instead of modality here?

Should we be looking at tubing set type instead of modality here?

Add an else block and keep the state to idle. In the beginning of the function assign the state to BP_DRIVER_CLEAR_CMD_STATE and remove line 194, 202 and 208.

Add an else block and keep the state to idle.
In the beginning of the function assign the state to BP_DRIVER_CLEAR_CMD_STATE and remove line 194, 202 and 208.

Can we not determine this now? Why TODO?

Can we not determine this now? Why TODO?

Shouldn't we be checking tubing set type instead of modality here?

Shouldn't we be checking tubing set type instead of modality here?

add requestAdultBPMeasurement to outputs

add requestAdultBPMeasurement to outputs

verify given type is valid (< NUM_OF_TUBE_SET_TYPES) and trigger s/w fault if invalid.

verify given type is valid (< NUM_OF_TUBE_SET_TYPES) and trigger s/w fault if invalid.

Initialize to UNKNOWN type. Remove TODO.

Initialize to UNKNOWN type. Remove TODO.

Consider adding TUBE_SET_TYPE_UNKNOWN = 0 as first enum so you can initialize a type variable to something before we install/identify the type.

Consider adding TUBE_SET_TYPE_UNKNOWN = 0 as first enum so you can initialize a type variable to something before we install/identify the type.

Use /// when above, use ///< when to the right. Also remove extra space before Tube

Use /// when above, use ///< when to the right.
Also remove extra space before Tube

Change // to ///<

Change // to ///<

Is this normal UF volume or normal UF volume + Iso UF Volume?

Is this normal UF volume or normal UF volume + Iso UF Volume?

Consider moving this validity check into the setTDRequestedGenDState function. And what should we do if it's not valid?

Consider moving this validity check into the setTDRequestedGenDState function.
And what should we do if it's not valid?

Why only these states are valid?

Why only these states are valid?

Remove list of states from comment. It is not a complete list and we shouldn't even try to list them here anyway.

Remove list of states from comment. It is not a complete list and we shouldn't even try to list them here anyway.

We need to keep D64 opened after supply to maintain the supply to fbicarb flow filter

We need to keep D64 opened after supply to maintain the supply to fbicarb flow filter

in initial fill we are not closing D64, only in supply cycle, just before supply start, we close it and when supply end, we open it again. we need to maintain the pressure balance in chamber F

in initial fill we are not closing D64, only in supply cycle, just before supply start, we close it and when supply end, we open it again.
we need to maintain the pressure balance in chamber F

will address it in new file created for mixing

will address it in new file created for mixing

LEAHI-TD-FIRMWARE-LDT-4013_Fluid Bolus - FW Implementation - 2/4:
LEAHI-TD-FIRMWARE-LDT-4013_Fluid Bolus - FW Implementation - 2/4:
Yes, REmoved

Yes, REmoved

fixed

fixed