AlarmDefs.h

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
initialized using resetRinsebackFlags()

initialized using resetRinsebackFlags()

those are initialized in resetTreatmentRecircFlags() and that is called in init

those are initialized in resetTreatmentRecircFlags() and that is called in init

align comment

align comment

use FALSE

use FALSE

use FALSE

use FALSE

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

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

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?

Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

  1. … 2 more files in changeset.
LDT-4040: Resolved merge conflicts

  1. … 1 more file in changeset.
LDT-4040: Merge staging into LDT-4040

  1. … 2 more files in changeset.
and break the line

and break the line

assign result to a variable and then return and break the line

assign result to a variable and then return and break the line

break this line

break this line

input is none

input is none

break this line

break this line

assign this to a variable and then return the variable. break this line

assign this to a variable and then return the variable.

break this line

Can we align = from line 270 to 281?

Can we align = from line 270 to 281?

break lines of this function to match our standard of 100 columns.

break lines of this function to match our standard of 100 columns.

break lines of this function to match our standard of 100 columns.

break lines of this function to match our standard of 100 columns.

input is none

input is none

can we define this as NUM_OF_BATTERY_REGISTERS = BATTERY_END_OF_LIST_TIME_TO_PUBLISH, and use NUM_OF_BATTERY_REGISTERS everywhere instead of using [ NUM_OF_BATTERY_REGISTERS - 1 ]

can we define this as NUM_OF_BATTERY_REGISTERS = BATTERY_END_OF_LIST_TIME_TO_PUBLISH,

and use NUM_OF_BATTERY_REGISTERS everywhere instead of using [ NUM_OF_BATTERY_REGISTERS - 1 ]