I thought this was a TEST_CONFIG thing. We aren't doing s/w config status, so maybe we should convert it to a TEST_CONFIG.

Let's hard code for time being with a TODO comment. I don't want alarm to be a problem.

Use OVERRIDE_RESET for .override instead of 0.

align indentation, same for line 338 as well.

Yes.
Otherwise, we will have to hard code the calibration record for the time being.

The function getSoftwareConfigStatus() is also part of NVM module.
Moreover, we are planning to remove this function when NVM will be implemented.
So, we will have to perform a cleanup and remove all similar calls that have been currently commented out in other files as well like AirTrap.c, BloodFlow.c, etc.

Align comment.

Keep 2 blank lines above banner.

Should this line be un-commented?

So we are going to fail this test until calibration record is ready?

In Leahi, we want to do all initialization in the init function instead of here at declaration (see Bubble.c for example).

blank line before return.

Blank line after declarations.

Just a heads up that all message handling functions in Leahi have the same prototype - just different function names (i.e. BOOL funcName( MESSAGE_T *message)) and that includes all Dialin command message handlers like these.

This param has been renamed to HEPARIN_STOP_TIME which is a couple rows below so we don't need to add this.

We will not have this saline bolus state in Leahi.

Fixed.

Fixed.

Fixed.

Fixed.

Fixed.

Added.

Fixed.

DD. Search DG and replace in file.

Fill in outputs.

Current Eject motor set speed?