Modes

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Done.

Done.

Done.

Done.

Done

Done

Done

Done

Done

Done

default should come last.

default should come last.

Blank line between break and next case.

Blank line between break and next case.

Not really all pumps are being stopped here. Just DPi and syringe (do we need to stop syringe pump?). We are also bypassing dialyzer here.

Not really all pumps are being stopped here. Just DPi and syringe (do we need to stop syringe pump?). We are also bypassing dialyzer here.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Removed the reset function.

Removed the reset function.

Added another state to check the extra volume.

Added another state to check the extra volume.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

If a zero is requested, it is checked first and then this flag is reset. I also want this flag to be reset all the time so we do not zero on old reservoir.

If a zero is requested, it is checked first and then this flag is reset. I also want this flag to be reset all the time so we do not zero on old reservoir.

This requests the blood zeroing and then the zeroing state machine does the flush prior to zeroing.

This requests the blood zeroing and then the zeroing state machine does the flush prior to zeroing.

Once reservoir switch occurs, do we have to wait until the "fresh" dialysate from new reservoir reaches the BLD?

Once reservoir switch occurs, do we have to wait until the "fresh" dialysate from new reservoir reaches the BLD?

This looks like it would reset the flag way too soon. Shouldn't flag reset be done in the resetBloodLeakZeroing() function?

This looks like it would reset the flag way too soon. Shouldn't flag reset be done in the resetBloodLeakZeroing() function?

No it is not custom please look at systemcommmessages.

No it is not custom please look at systemcommmessages.

I thought this was going to be an indexed override like when you have an array of temp sensors and the index gives you the enum of the temp sensor you want to override. You have a BOOL flag instead...

I thought this was going to be an indexed override like when you have an array of temp sensors and the index gives you the enum of the temp sensor you want to override. You have a BOOL flag instead. Does that mean you're using a custom payload instead of the array override payload?

Done

Done

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Should be 2 blank lines above test support banner.

Should be 2 blank lines above test support banner.

Add comment explaining what we are checking here.

Add comment explaining what we are checking here.

Done

Done

Move this too if you didn't already.

Move this too if you didn't already.