firmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge branch 'DEN-13154-heparin-syringe-empty-position-incorrect' into develop

DEN-13154: Removed obsolete pressure data from broadcast. Tightened no cartridge pressure range for PBA and PBo.

DEN-14834 added code to calculate the heating parameters in pre-treatment and send it to DG in the pre-treatment reservoir management

HD-DEN-14834_RO Flow Drops TO Zero And CP Measured Speed 1500 Temporarily During Pre Treatment
HD-DEN-14834_RO Flow Drops TO Zero And CP Measured Speed 1500 Temporarily During Pre Treatment
DEN-14830: reworked dialysate temp timeouts and conditions. Restored previous persistence alarms. added below 33 degC alarm

Merge branch 'staging' into DEN-14830-incorrect-dialysate-temperature-alarm-triggered

HD-DEN-14457-2_Reservoir Drains Before Treatment With Pre Treatment Build Flags Off

Checkpoint. Simplifying AIR_PUMP bug fix.

This will hard fault the HD. Please change to getTreatmentParameterU32()

This will hard fault the HD. Please change to getTreatmentParameterU32()

This will hard fault the HD. Please change to getTreatmentParameterU32()

This will hard fault the HD. Please change to getTreatmentParameterU32()

DEN-14689: synchronized naming from msgdefs.h

HD-DEN-14689_Messaging Bugs_MSG_ID_HD_POST_FINAL_TEST_RESULT_fix
HD-DEN-14689_Messaging Bugs_MSG_ID_HD_POST_FINAL_TEST_RESULT_fix
DEN-14689: DEN-14634: fixed HD_POST_FINAL_TEST_RESULT being sent to be sent 1 time instead of 40 times over 2s.

DEN-14689: further msg id name changing.

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

Merge branch 'DEN-14689-messaging-bugs' into develop

Merge branch 'staging' into DEN-14689-messaging-bugs

DEN-14689: message naming sync

DEN-14689: naming consistency pass.

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

Fixed merge conflicts.

DEN-13154: Update to handling of insufficient Heparin alarm per DEN-14814 and DEN-14287.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

I don't think it's necessary - but I'm ok with either location for declaration. RESOLVED in CODE WALKTHROUGH.

I don't think it's necessary - but I'm ok with either location for declaration.
RESOLVED in CODE WALKTHROUGH.

1. Style, and preference to keep loop control at the top, not buried in the state function. 2. Keep stack size for the state function more predictable. 3. I was considering unwrapping the state mac...

1. Style, and preference to keep loop control at the top, not buried in the state function.
2. Keep stack size for the state function more predictable.
3. I was considering unwrapping the state machine, starting with a separate pause state, that held for priming to advance to the proper state

Ultimately the simplest change may be limited to just this ifndef. No practical reason to move the declaration in that case.

So far as I can tell, this file was included in the code review only. The repository doesn't include these changes, on this branch.

So far as I can tell, this file was included in the code review only. The repository doesn't include these changes, on this branch.

HD-DEN-14860_Recirculation Alarm 68 During High Flow Treatments
HD-DEN-14860_Recirculation Alarm 68 During High Flow Treatments
DEN-14860 Use higher percentage limit of depletion time alarm for faster dialysate flow. Linear interpolation between fast and slow reservoir fill speeds. Heater ON during reservoir transfer.

DEN-14860 Use higher percentage limit of depletion time alarm for faster dialysate flow. Linear interpolation between fast and slow reservoir fill speeds. Heater ON during reservoir transfer.

DEN-14860 Use higher percentage limit of depletion time alarm for faster dialysate flow. Linear interpolation between fast and slow reservoir fill speeds. Heater ON during reservoir transfer.

Let's review PRS req together. Seems like we have conflicting alarm properties in place that don't make sense to me. Let's figure out what behavior Systems team is looking for here and then decide ...

Let's review PRS req together. Seems like we have conflicting alarm properties in place that don't make sense to me. Let's figure out what behavior Systems team is looking for here and then decide what properties/persistence should be set.