leahi-fwcommon

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDT-4001: code review comments

same comment as above

same comment as above

This was added as on bootup the registers were looking at beta 1.9 before, so the initialization was failing. Now that it is changed to look at beta 2 registers on bootup can we remove this as this...

This was added as on bootup the registers were looking at beta 1.9 before, so the initialization was failing. Now that it is changed to look at beta 2 registers on bootup can we remove this as this is no longer required?

In develop branch , its substitionrate ? need in sync with develop and staging

In develop branch , its substitionrate ? need in sync with develop and staging

Add Set Substitution pump target speed here.

Add Set Substitution pump target speed here.

leave blank after.

leave blank after.

leave blank after

leave blank after

Align comment please.

Align comment please.

Merge branch 'staging' into LDT-3975-water-treatment-and-degassing--

LDT-4011 initial iso uf implementation

Merge branch 'LDT-4001-hdf-fw-implementation-2-4' into develop

Merge branch 'staging' into LDT-4001-hdf-fw-implementation-2-4

LDT-4009 made changes to the DD payload msg

Merge branch 'staging' into develop

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

LEAHI-TD-FIRMWARE-LDT-4063_Power Control and POST - FW Implementation - 1/6:
LEAHI-TD-FIRMWARE-LDT-4063_Power Control and POST - FW Implementation - 1/6:
Merge branch 'staging' into LDT-4001-hdf-fw-implementation-2-4

Should this check be moved to the fluid bolus exec function?

Should this check be moved to the fluid bolus exec function?

LDT-3735: Converted software configs to test configs

Merge branch 'staging' into LDT-4013-fluid-bolus

It looks like you have this as a T/F response from UI. UI should not be determining whether the modality matches - that's our job. UI should be telling us which type of tubing set was installed (HD...

It looks like you have this as a T/F response from UI. UI should not be determining whether the modality matches - that's our job. UI should be telling us which type of tubing set was installed (HD or HDF type). Then when we get this response msg from UI, we will compare the type to the user selected modality (from TxParams) to see if it matches.

Add doxygen comments to the right of each structure field.

Add doxygen comments to the right of each structure field.

Why is this commented out? We will get stuck in this state if we don't move on to the pressure leak test states.

Why is this commented out? We will get stuck in this state if we don't move on to the pressure leak test states.

For now, we need to set authResponseReceived and authResponseValidTubingSet and authResponseModalityAccepted to TRUE until UI is properly responding to authentication request (TODO).

For now, we need to set authResponseReceived and authResponseValidTubingSet and authResponseModalityAccepted to TRUE until UI is properly responding to authentication request (TODO).

For now, we need to set barcodeScanResponseReceived to TRUE here until barcode scan command is implemented.

For now, we need to set barcodeScanResponseReceived to TRUE here until barcode scan command is implemented.

Add blank line before return statement.

Add blank line before return statement.