MsgDefs.h

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDT-3126-blood-prime-td

Response payload is not U08. I believe UI will be expecting a payload of type UI_RESPONSE_PAYLOAD_T (defined in Messaging.h). Verify with Nico that this is the payload he is expecting in response. ...

Response payload is not U08. I believe UI will be expecting a payload of type UI_RESPONSE_PAYLOAD_T (defined in Messaging.h). Verify with Nico that this is the payload he is expecting in response. See signalPauseResumeUF() function for example of how to respond to a UI request.

Same comment as other message handling function. Use correct payload type. See signalPauseResumeUF() function for example of how to respond to a UI request.

Same comment as other message handling function. Use correct payload type. See signalPauseResumeUF() function for example of how to respond to a UI request.

Why do we need this local variable when we have the static requestedBloodFlowRate_mL_min variable?

Why do we need this local variable when we have the static requestedBloodFlowRate_mL_min variable?

Add a blank line after declarations.

Add a blank line after declarations.

I would say "TRUE if request is accepted, FALSE if rejected."

I would say "TRUE if request is accepted, FALSE if rejected."

I would say "TRUE if request is accepted, FALSE if rejected."

I would say "TRUE if request is accepted, FALSE if rejected."

We do not always want to return to run state. If we were in ramp state prior to pause state, we would want to go back to ramp state here. So you need to remember your previous state in a new variable.

We do not always want to return to run state. If we were in ramp state prior to pause state, we would want to go back to ramp state here.
So you need to remember your previous state in a new variable.

We do not need to set result here since it is already set to run state at top of this function.

We do not need to set result here since it is already set to run state at top of this function.

Remove TODO comment since you have done it.

Remove TODO comment since you have done it.

Still need to close valves.

Still need to close valves.

Use getTargetBloodFlowRate() instead.

Use getTargetBloodFlowRate() instead.

Remove TODO comment since you have done it.

Remove TODO comment since you have done it.

Why assign requested rate to ramp rate? Why not just use requested rate in the set function below?

Why assign requested rate to ramp rate? Why not just use requested rate in the set function below?

I think we actually should be getting commanded blood flow rate here (getTargetBloodFlowRate) instead of measured rate.

I think we actually should be getting commanded blood flow rate here (getTargetBloodFlowRate) instead of measured rate.

Let's go ahead and do this.

Let's go ahead and do this.

Let's add a TODO comment so we don't forget to uncomment this when syringe pump is implemented.

Let's add a TODO comment so we don't forget to uncomment this when syringe pump is implemented.

Should be only one blank line here.

Should be only one blank line here.

I would expect there to be a change to Messaging.c (to add association between msg ID to this new function to the look-up table), but I don't see it.

I would expect there to be a change to Messaging.c (to add association between msg ID to this new function to the look-up table), but I don't see it.

Why NUM_OF_?

Why NUM_OF_?

Variable name suggests it is an action/cmd from UI. Comment suggests it is the number of actions. Which is it? And we should initialize in the init function - not here.

Variable name suggests it is an action/cmd from UI. Comment suggests it is the number of actions. Which is it?
And we should initialize in the init function - not here.

Is this really a timer counter? Looks like a flow rate.

Is this really a timer counter? Looks like a flow rate.

Updated

Updated

Added back

Added back

Updated

Updated

Add spaces inside of ().

Add spaces inside of ().

Stop button is a "hard" pause which would take us to Treatment: Paused state (out of blood prime completely). We want to go to our internal paused state when UI sends us a "soft" blood prime pause ...

Stop button is a "hard" pause which would take us to Treatment: Paused state (out of blood prime completely).
We want to go to our internal paused state when UI sends us a "soft" blood prime pause commands message.

Remove blank line.

Remove blank line.

Should we add this test config? Systems team will likely want it eventually since they wanted it in Denali.

Should we add this test config? Systems team will likely want it eventually since they wanted it in Denali.