SyringePump.h

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
These new functions should be above the test functions. Please align with the Messaging.c file. It looks correct in the Messaging.c file.

These new functions should be above the test functions.

Please align with the Messaging.c file.
It looks correct in the Messaging.c file.

Move this above the test functions.

Move this above the test functions.

What is the use case of this header include?

What is the use case of this header include?

What if we're in paused state (because your alarm has stop property set)? Should we return TRUE here if in paused state and interrupted state was the await syringe load confirmation state?

What if we're in paused state (because your alarm has stop property set)? Should we return TRUE here if in paused state and interrupted state was the await syringe load confirmation state?

Right now, the load syringe alarm indicates stop so we will go to paused state. Is that what we want to do? Don't we want to stay in this state and wait for confirmation?

Right now, the load syringe alarm indicates stop so we will go to paused state. Is that what we want to do? Don't we want to stay in this state and wait for confirmation?

Should this alarm have stop property set to FALSE?

Should this alarm have stop property set to FALSE?

align comment

align comment

When we send any message to UI, usually add the message id in the doxygen header like this. @details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE Please refer to the function s...

When we send any message to UI, usually add the message id in the doxygen header like this.

@details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE

Please refer to the function sendTreatmentParamsResponse()

When we send any message to UI, usually add the message id in the doxygen header like this. *@details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE Please refer to the functi...

When we send any message to UI, usually add the message id in the doxygen header like this.

  • @details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE


Please refer to the function sendTreatmentParamsResponse()

When we send any message to UI, usually add the message id in the doxygen header like this. *@details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE Please refer to the functi...

When we send any message to UI, usually add the message id in the doxygen header like this.

  • @details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE


Please refer to the function sendTreatmentParamsResponse()

It looks like the rows may be misaligned with the alarm ID declarations. For example, ALARM_ID_TD_SAFETY_SHUTDOWN_POST_TEST_FAILED is declared as 207.

It looks like the rows may be misaligned with the alarm ID declarations.
For example, ALARM_ID_TD_SAFETY_SHUTDOWN_POST_TEST_FAILED is declared as 207.

Should Instructions part be this? A problem was detected with the hemodialysis device.

Should Instructions part be this?

A problem was detected with the hemodialysis device.

Please confirm if the source is DD?

Please confirm if the source is DD?

What is the use case of including this header?

What is the use case of including this header?

What is the use case of including this header?

What is the use case of including this header?

Should we move this up before the test functions?

Should we move this up before the test functions?

Add @messages MSG_ID_TD_POST_FINAL_TEST_RESULT

Add @messages MSG_ID_TD_POST_FINAL_TEST_RESULT

Add @messages MSG_ID_TD_POST_SINGLE_TEST_RESULT

Add @messages MSG_ID_TD_POST_SINGLE_TEST_RESULT

is the function description correct? change DG -> DD

is the function description correct?
change DG -> DD

output is none

output is none

add safetyShutdownSelfTestStatus to outputs

add safetyShutdownSelfTestStatus to outputs

why is this line commented out? Should we remove it or add a TODO?

why is this line commented out? Should we remove it or add a TODO?

Remove blank line

Remove blank line

align comment

align comment

break this line

break this line

add @messages MSG_ID_TD_UI_GENERIC_CONFIRMATION_REQUEST

add @messages MSG_ID_TD_UI_GENERIC_CONFIRMATION_REQUEST

add @messages MSG_ID_TD_UI_GENERIC_CONFIRMATION_REQUEST

add @messages MSG_ID_TD_UI_GENERIC_CONFIRMATION_REQUEST

remove blank line

remove blank line