SystemCommTD.c

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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.

pauseBolusResumeState is input

pauseBolusResumeState is input

add alarm

add alarm

Replace // to ///< for line 56 to 60

Replace // to ///< for line 56 to 60

LDT-4103-1: Addressed CR comments

  1. … 2 more files in changeset.
Use // comments for function prototypes.

Use // comments for function prototypes.

Either no comment or // comment for function prototypes since doxygen captures function details from function headers.

Either no comment or // comment for function prototypes since doxygen captures function details from function headers.

These were fine (and preferred) as // because doxygen gets function details from function headers in the .c file.

These were fine (and preferred) as // because doxygen gets function details from function headers in the .c file.

Should we be looking at tubing set type instead of modality here?

Should we be looking at tubing set type instead of modality here?

Can we not determine this now? Why TODO?

Can we not determine this now? Why TODO?

Shouldn't we be checking tubing set type instead of modality here?

Shouldn't we be checking tubing set type instead of modality here?

verify given type is valid (< NUM_OF_TUBE_SET_TYPES) and trigger s/w fault if invalid.

verify given type is valid (< NUM_OF_TUBE_SET_TYPES) and trigger s/w fault if invalid.

Initialize to UNKNOWN type. Remove TODO.

Initialize to UNKNOWN type. Remove TODO.

Consider adding TUBE_SET_TYPE_UNKNOWN = 0 as first enum so you can initialize a type variable to something before we install/identify the type.

Consider adding TUBE_SET_TYPE_UNKNOWN = 0 as first enum so you can initialize a type variable to something before we install/identify the type.

Use /// when above, use ///< when to the right. Also remove extra space before Tube

Use /// when above, use ///< when to the right.
Also remove extra space before Tube

Change // to ///<

Change // to ///<

LEAHI-TD-FIRMWARE-LDT-4013_Fluid Bolus - FW Implementation - 2/4:
LEAHI-TD-FIRMWARE-LDT-4013_Fluid Bolus - FW Implementation - 2/4:
please add blank space between ( (int)postState ), TRUE );

please add blank space between ( (int)postState ), TRUE );

please add blank space between ( (int)postState ), TRUE );

please add blank space between ( (int)postState ), TRUE );

Alarm id should be 196? Description looks same as 194.

Alarm id should be 196?
Description looks same as 194.

Change PRES_OCCL to PRESSURE

Change PRES_OCCL to PRESSURE

Maybe move OperationModes.c?

Maybe move OperationModes.c?

Use generic confirmation functions/messages.

Use generic confirmation functions/messages.

Move this function to OperationModes.c.

Move this function to OperationModes.c.

From here forward, we can just call sendMessage() with appropriate params.

From here forward, we can just call sendMessage() with appropriate params.

Use generic helper function (sendMessage) in MessageSupport.c.

Use generic helper function (sendMessage) in MessageSupport.c.

Use generic confirmation functions/messages for off button.

Use generic confirmation functions/messages for off button.

Remove change.

Remove change.