leahi-common

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDT-2004 dialystae dosing control

If you change this line to "if ( ++airPumpStallCounter >= AIR_PUMP_STALL_PERSISTENCE )", you can remove the if statement above.

If you change this line to "if ( ++airPumpStallCounter >= AIR_PUMP_STALL_PERSISTENCE )", you can remove the if statement above.

I was thinking that comment should go above the first if statement.

I was thinking that comment should go above the first if statement.

Updated

Updated

Define what 3 means (#define up top). If 3 means 3 x 50ms general task interval, define it as shown below: #define AIR_PUMP_STALL_PERSISTENCE ( 150 / TASK_GENERAL_INTERVAL ) ///< How long stall con...

Define what 3 means (#define up top). If 3 means 3 x 50ms general task interval, define it as shown below:
#define AIR_PUMP_STALL_PERSISTENCE ( 150 / TASK_GENERAL_INTERVAL ) ///< How long stall condition must persist before alarming.

OR use persistent alarm.

Added

Added

Add a comment explaining what we're looking for here (i.e. we are commanding air pump to run but zero measured pump speed indicates it is not running).

Add a comment explaining what we're looking for here (i.e. we are commanding air pump to run but zero measured pump speed indicates it is not running).

Added

Added

Should probably initialize your new stall counter variable.

Should probably initialize your new stall counter variable.

Sean Nash I need your help for writing this Alarm properties.

Sean Nash I need your help for writing this Alarm properties.

LDT-3215-measured-venous-pressure-decreases

LDT-3126-blood-prime-td-updates

Wrong place.

Wrong place.

I'll drop by and we can set properties together.

I'll drop by and we can set properties together.

LDt-3749 WIP initial draft for DD set sub mode request

LEAHI-DD-FIRMWARE-LDT-3749_Ability to set operation sub mode on DD subsystem
LEAHI-DD-FIRMWARE-LDT-3749_Ability to set operation sub mode on DD subsystem
Added

Added

Updated

Updated

Sorry, Updated

Sorry, Updated

Updated, if this is wrong then I need your help

Updated, if this is wrong then I need your help

LDT-3126-blood-prime-td-updates

Match properties from Denali where you can. The priorities should both be HIGH. The rank for the warning should be a higher number. The alarm should be TRUE for no resume and no rinseback. So, I kn...

Match properties from Denali where you can. The priorities should both be HIGH. The rank for the warning should be a higher number. The alarm should be TRUE for no resume and no rinseback. So, I know these properties aren't correct.
One thing I don't think we should copy from Denali though - I think the warning should not be TRUE for the STOP property so that we stay in blood prime state.

Add a blank line after declaration.

Add a blank line after declaration.

I think we should just have == here so that we only warn them once.

I think we should just have == here so that we only warn them once.

Don't mention alarms in brief. Add a details line for Alarms for the alarm(s) that the function might trigger (look for other functions that do this for example).

Don't mention alarms in brief. Add a details line for Alarms for the alarm(s) that the function might trigger (look for other functions that do this for example).

Name in brief doesn't match function name.

Name in brief doesn't match function name.

I don't understand what you did here. The '*' characters were in the right place before. Do we want to keep the stroke code changes? Do we know where they came from?

I don't understand what you did here. The '*' characters were in the right place before. Do we want to keep the stroke code changes? Do we know where they came from?

LDT-3126-blood-prime-td-updates