Activity td-firmware/firmware/App/Modes

We need to look for user request to resume from pause where we would restart BP (at last rate we were at before pause) and re-open art/ven pinch valves and transition back to either ramp or run sta...

We need to look for user request to resume from pause where we would restart BP (at last rate we were at before pause) and re-open art/ven pinch valves and transition back to either ramp or run state (whichever state we were in when we paused).

1:14 pm

Sean Nash

More
Re: LEAHI-TD-FIRMWARE-LDT-3126-1
commented on review

In this state, we still need to signal transition to dialysis when target volume is reached (same as in ramp state). We also need to look for user request to pause (same as in ramp state).

In this state, we still need to signal transition to dialysis when target volume is reached (same as in ramp state).
We also need to look for user request to pause (same as in ramp state).

1:12 pm

Sean Nash

More
Re: LEAHI-TD-FIRMWARE-LDT-3126-1
commented on review

We do need an else if here for when user does change the blood flow rate. In that case, we would want to go to run state where we would run continuously at the requested rate without ramping anymor...

We do need an else if here for when user does change the blood flow rate. In that case, we would want to go to run state where we would run continuously at the requested rate without ramping anymore. Ask Nico which message UI sends when user changes blood flow rate.

And we need another else if for when user asks to pause blood prime and we would stop BP (and maybe close art/ven pinch valves) and go to pause state.

1:10 pm

Sean Nash

More
Re: LEAHI-TD-FIRMWARE-LDT-3126-1
commented on review

Input and Output is cumulativeBloodPrimevolume_mL.

1:07 pm

Sean Nash

More
Re: LEAHI-TD-FIRMWARE-LDT-3126-1
commented on review

signal function will take us out of blood prime, so no reason to change state here. We would not want to go to run state even if we weren't leaving - run state is for when user changes blood flow r...

signal function will take us out of blood prime, so no reason to change state here. We would not want to go to run state even if we weren't leaving - run state is for when user changes blood flow rate which they have not done here.

1:05 pm

Sean Nash

More
Re: LEAHI-TD-FIRMWARE-LDT-3126-1
commented on review

Raghu is fixing this in his Tx Params branch, but you should fix it too. TUBING_BLOOD_PRIME_VOLUME_ML is not a treatment parameter. See Raghu's fix and duplicate it here.

12:49 pm