AlarmMgmt.c

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
I think these remaining 4 else ifs need to have another && condition that your service is in idle state so that we don't change back into one of these 4 states while a bolus is in progress.

I think these remaining 4 else ifs need to have another && condition that your service is in idle state so that we don't change back into one of these 4 states while a bolus is in progress.

Can we restore the real code here yet? Ask Dara.

Can we restore the real code here yet? Ask Dara.

Why comment this out? fault ID should probably be more specific (i.e. which message payload length is invalid?)

Why comment this out? fault ID should probably be more specific (i.e. which message payload length is invalid?)

update total volume too?

update total volume too?

maybe use target rate for both.

maybe use target rate for both.

Use #define for array size.

Use #define for array size.

Make the 6 a #define

Make the 6 a #define

only 1 return statement

only 1 return statement

remove comma

remove comma

signal functions should return BOOL.

signal functions should return BOOL.

Move up with rest

Move up with rest

Move this function to your service.

Move this function to your service.

Not needed.

Not needed.

Should always exec your bolus sm.

Should always exec your bolus sm.

Keep 2 blank lines before banner

Keep 2 blank lines before banner

Add fluid bolus state

Add fluid bolus state

Add fluid bolus state

Add fluid bolus state

FLUID_BOLUS_CMD_EVENT

FLUID_BOLUS_CMD_EVENT

LEAHI-TD-FIRMWARE-LDT-4013_Fluid Bolus - FW Implementation - 2/4:
LEAHI-TD-FIRMWARE-LDT-4013_Fluid Bolus - FW Implementation - 2/4:
Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

  1. … 28 more files in changeset.
Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

  1. … 28 more files in changeset.
LEAHI-TD-FIRMWARE-LDT-2199_Beta 1.0 FW Integration - TD Implementation
LEAHI-TD-FIRMWARE-LDT-2199_Beta 1.0 FW Integration - TD Implementation
LDT-2199: Fixed merge issue.

Done.

Done.

Why the extra leading zeroes? If you want to ensure the literal is treated like a U32, you can do 0x00000001 or simply 1U, but I suspect the compiler will default to 32 bits anyway.

Why the extra leading zeroes? If you want to ensure the literal is treated like a U32, you can do 0x00000001 or simply 1U, but I suspect the compiler will default to 32 bits anyway.

I believe baro is being moved to the TD firmware. DD will have to get baro readings from TD broadcasts.

I believe baro is being moved to the TD firmware. DD will have to get baro readings from TD broadcasts.