td-firmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
60 should be coming from somewhere. Is there not a treatment parameter for vitals measurement interval? I think we do (TREATMENT_PARAM_BP_MEAS_INTERVAL).

60 should be coming from somewhere. Is there not a treatment parameter for vitals measurement interval? I think we do (TREATMENT_PARAM_BP_MEAS_INTERVAL).

Make a local BOOL variable and assign it TRUE or FALSE with a ternary operator and then return that local BOOl variable.

Make a local BOOL variable and assign it TRUE or FALSE with a ternary operator and then return that local BOOl variable.

These should be moved down to an "else" in the if statement below (payload length check).

These should be moved down to an "else" in the if statement below (payload length check).

It doesn't look like these memsets are necessary. Consider removing them.

It doesn't look like these memsets are necessary. Consider removing them.

Remove blank line.

Remove blank line.

Can you move this down with the other vitals functions?

Can you move this down with the other vitals functions?

LEAHI-TD-FIRMWARE-LDT-4329_Edit Treatment Parameters During Treatment - FW Implementation - 5/4:
LEAHI-TD-FIRMWARE-LDT-4329_Edit Treatment Parameters During Treatment - FW Implementation - 5/4:
Just use 0x0 and 0xFFFFFFFF

Just use 0x0 and 0xFFFFFFFF

NUM_OF_BATTERY_REGISTERS - 1

NUM_OF_BATTERY_REGISTERS - 1

Put 2 items at end of the list here: BATTERY_END_OF_LIST_TIME_TO_PUBLISH NUM_OF_BATTERY_REGISTERS

Put 2 items at end of the list here:
BATTERY_END_OF_LIST_TIME_TO_PUBLISH
NUM_OF_BATTERY_REGISTERS

Put this one back to NUM_OF_BATTERY_DEVICES.

Put this one back to NUM_OF_BATTERY_DEVICES.

Don't need min/max for this. Just use 0x0 and 0xFFFFFFFF where needed.

Don't need min/max for this. Just use 0x0 and 0xFFFFFFFF where needed.

I don't think we need these min/max #defines. Just use 0x0 for minimums and 0xFFFFFFFF for maximums.

I don't think we need these min/max #defines. Just use 0x0 for minimums and 0xFFFFFFFF for maximums.

Please add Alarm ALARM_ID_TD_PRIME_COMPLETED_HIGH and ALARM_ID_TD_SOFTWARE_FAULT

Please add Alarm
ALARM_ID_TD_PRIME_COMPLETED_HIGH and ALARM_ID_TD_SOFTWARE_FAULT

Add alarm ALARM_ID_TD_PRIME_COMPLETED_MEDIUM

Add alarm ALARM_ID_TD_PRIME_COMPLETED_MEDIUM

Please add currentPreTreatmentState to inputs.

Please add currentPreTreatmentState to inputs.

currentPreTxRecircState looks like an input.

currentPreTxRecircState looks like an input.

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

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

    • -2
    • +2
    /firmware/App/Modes/StateTxBloodPrime.c
    • -2
    • +2
    /firmware/App/Modes/StateTxBloodPrime.h
  1. … 7 more files in changeset.
LEAHI-TD-FIRMWARE-LDT-4505_(TD) H4 blood pump does not run in reverse
LEAHI-TD-FIRMWARE-LDT-4505_(TD) H4 blood pump does not run in reverse
Put recirc state after Rx state (both here in switch statement and also in enumeration).

Put recirc state after Rx state (both here in switch statement and also in enumeration).

Put in alphabetical order (before Timers.h).

Put in alphabetical order (before Timers.h).

Where do we trigger high priority prime completed alarm?

Where do we trigger high priority prime completed alarm?

Dialysate rate should be set to the Qd user setting (from Tx params).

Dialysate rate should be set to the Qd user setting (from Tx params).

Add /// doxygen comment for this enumeration and ///< doxygen comments to right of each enum in the list.

Add /// doxygen comment for this enumeration and ///< doxygen comments to right of each enum in the list.

LDT-4013: Merge latest staging into LDT-4013, resolved merge conflicts and addressed CR comments

    • -18
    • +203
    /firmware/App/Modes/ModePreTreat.c
    • -12
    • +23
    /firmware/App/Modes/ModeTreatment.c
    • -18
    • +19
    /firmware/App/Modes/ModeTreatment.h
    • -61
    • +23
    /firmware/App/Services/Messaging.h
    • -0
    • +635
    /firmware/App/Services/StateServices/FluidBolus.c
    • -0
    • +75
    /firmware/App/Services/StateServices/FluidBolus.h
    • -0
    • +437
    /firmware/App/Services/StateServices/TubeSetAutoEject.c
    • -0
    • +335
    /firmware/App/Services/StateServices/TubeSetInstall.c
    • -628
    • +0
    /firmware/App/Services/FluidBolus.c
    • -75
    • +0
    /firmware/App/Services/FluidBolus.h
Should this check be moved to the fluid bolus exec function?

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