leahi-common

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge branch 'LDT-4485-dd-conductivity-sensors-d17' into develop

updated msg ids for cal request

Remove the blank line

Remove the blank line

Add headers for all below functions.

Add headers for all below functions.

Rmove extra blank line

Rmove extra blank line

Update Input section: Balancing chamber state

Update Input section: Balancing chamber state

We can keep it as handler instead of exec since this is being invoked from execMixingControl.

We can keep it as handler instead of exec since this is being invoked from execMixingControl.

Merge branch 'staging' into LDT-4485-dd-conductivity-sensors-d17

we should use get balancing chamber fill volume if balancing chamber volume been adjusted by calibration (not an immediate need, but good to have)

we should use get balancing chamber fill volume if balancing chamber volume been adjusted by calibration (not an immediate need, but good to have)

remove min in the comment.

remove min in the comment.

Remove the unused header file.

Remove the unused header file.

Remove the unused header file.

Remove the unused header file.

Update state name matching handler name.

Update state name matching handler name.

Same as above.

Same as above.

The second condition( fill request) should be checked against true?

The second condition( fill request) should be checked against true?

Thank you for the clarification!

Thank you for the clarification!

break into two lines

break into two lines

Add alarm ALARM_ID_TD_EMPTY_SALINE_BAG

Add alarm ALARM_ID_TD_EMPTY_SALINE_BAG

Add newAlarmIndicateStop to output

Add newAlarmIndicateStop to output

Add newAlarmIndicateStop to input and output.

Add newAlarmIndicateStop to input and output.

LEAHI-DD-FIRMWARE-LDT-4539_Provide event on Service state change
LEAHI-DD-FIRMWARE-LDT-4539_Provide event on Service state change
Arpita, we don't want to use doxygen style comments for function prototypes since we cover functions with the function headers. so this is the proper type of comments.

Arpita, we don't want to use doxygen style comments for function prototypes since we cover functions with the function headers. so this is the proper type of comments.

Bubble status, Low and high level level sensors.

Bubble status, Low and high level level sensors.

Input : Blood pump door status?

Input : Blood pump door status?

To be restored?

To be restored?

Are these being initialized in the init function?

Are these being initialized in the init function?

Need to resolve the merge issues?

Need to resolve the merge issues?