firmware

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

measuredDialInFlow is (and was) local to this function, but measuredDialInFlowRate is not - it is accessed via getMeasuredDialInFlowRate().

measuredDialInFlow is (and was) local to this function, but measuredDialInFlowRate is not - it is accessed via getMeasuredDialInFlowRate().

measuredDialInFlowRate is now local to the function.

measuredDialInFlowRate is now local to the function.

If this condition (timeout) occurs in middle of pressure build up, will we release on transition to next state?

If this condition (timeout) occurs in middle of pressure build up, will we release on transition to next state?

Magic # 5 - use #define. What happens if prior bubble clear is still active when this times out? Seems like condition should check that bubbleClearActive is FALSE too.

Magic # 5 - use #define.
What happens if prior bubble clear is still active when this times out? Seems like condition should check that bubbleClearActive is FALSE too.

HD-DEN-14197_SW S83 MG PI Optimization
HD-DEN-14197_SW S83 MG PI Optimization
HD-DEN-14099_Bubbles IN Dialysate Out Line From DG TO Cartridge
HD-DEN-14099_Bubbles IN Dialysate Out Line From DG TO Cartridge
HD-DEN-14307_DG HD Dev HD DG Dvt Update Part 6
HD-DEN-14307_DG HD Dev HD DG Dvt Update Part 6
RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Done

Done

Need to make sure these only get called once before pre-treatment.

Need to make sure these only get called once before pre-treatment.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Done.

Done.

Done

Done

Done.

Done.

Done.

Done.

Still doesn't belong here. We can either have a new shared FPGA header file or we can have two of these - one for each sub-system (similar to how we have two FPGA.c/.h files).

Still doesn't belong here. We can either have a new shared FPGA header file or we can have two of these - one for each sub-system (similar to how we have two FPGA.c/.h files).

Doesn't this command take a pointer to a structure now?

Doesn't this command take a pointer to a structure now?