leahi-common

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
pushed new code

pushed new code

Fixed

Fixed

fixed it in commit ID 71a6797

fixed it in commit ID 71a6797

Has integrity unit been added to TD project?

Has integrity unit been added to TD project?

Where are these being triggered?

Where are these being triggered?

Is this necessary? If so, why?

Is this necessary? If so, why?

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.

I don't like controller bypassing driver to get to fpga access functions. There should be a get function in the driver that we can call here instead.

I don't like controller bypassing driver to get to fpga access functions. There should be a get function in the driver that we can call here instead.

Add blank line after declarations.

Add blank line after declarations.

Why two leading zeroes?

Why two leading zeroes?

Ya agreed. for the time being keeping it , we can later remove it after feature development complete

Ya agreed. for the time being keeping it , we can later remove it after feature development complete

in other files when they use string and/or math headers they had specified a comment describing which functions are used from the headers.

in other files when they use string and/or math headers they had specified a comment describing which functions are used from the headers.