firmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
addressed comments

add space in [ ]

add space in [ ]

align comments

align comments

Bamboo Commit: Updated TDCommon.h with build versions from Bamboo.

Should these three alarms be moved after alarm 852? It looks like 999 is currently placed before 852.

Should these three alarms be moved after alarm 852?

It looks like 999 is currently placed before 852.

Bamboo Commit: Updated TDCommon.h with build versions from Bamboo.

Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

LDT-3992: Fix for develop

break this line

break this line

Add @message id MSG_ID_TD_UI_GENERIC_CONFIRMATION_REQUEST

Add @message id MSG_ID_TD_UI_GENERIC_CONFIRMATION_REQUEST

break this line

break this line

break this line

break this line

Update function name: handleRinsebackAdditionalState

Update function name: handleRinsebackAdditionalState

Thank you for clarifying!

Thank you for clarifying!

Thank you for clarifying!

Thank you for clarifying!

Add cumulativeBloodPrimeVolume_mL to ouputs. Optional: While you are updating, can you please also add bloodPrimeRampFlowRate_mL_min and bloodPrimeState to the inputs?

Add cumulativeBloodPrimeVolume_mL to ouputs.

Optional: While you are updating, can you please also add bloodPrimeRampFlowRate_mL_min and bloodPrimeState to the inputs?

Add recircAllowed to outputs.

Add recircAllowed to outputs.

Thank you for clarifying!

Thank you for clarifying!

LDT-4072:Update battery monitoring enum indexing and validate charger data

What if we're in paused state (because your alarm has stop property set)? Should we return TRUE here if in paused state and interrupted state was the await syringe load confirmation state?

What if we're in paused state (because your alarm has stop property set)? Should we return TRUE here if in paused state and interrupted state was the await syringe load confirmation state?

Right now, the load syringe alarm indicates stop so we will go to paused state. Is that what we want to do? Don't we want to stay in this state and wait for confirmation?

Right now, the load syringe alarm indicates stop so we will go to paused state. Is that what we want to do? Don't we want to stay in this state and wait for confirmation?

Should this alarm have stop property set to FALSE?

Should this alarm have stop property set to FALSE?

Merge branch 'staging' of bitbucket.org:diality-cloud/td-firmware into LDT-4149-pinch-valves-fw-implementation

LDT-4029:Updated heparin setup state

Bamboo Commit: Updated TDCommon.h with build versions from Bamboo.

Bamboo Commit: Updated TDCommon.h with build versions from Bamboo.

updated

updated

updated

updated

updated.

updated.