Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Space after if.

Space after if.

Can we bring depressurize as well one of the states like fill, supply and drain? And the same way when one of the operations initiated and other should not kick in.

Can we bring depressurize as well one of the states like fill, supply and drain? And the same way when one of the operations initiated and other should not kick in.

remove empty space after d66pressure variable. or match the indent to previous statement.

remove empty space after d66pressure variable. or match the indent to previous statement.

Add a TODO comment (remove later): this should be handled in IO/FP module.

Add a TODO comment (remove later): this should be handled in IO/FP module.

Update comment.

Update comment.

Add comment.

Add comment.

Depressurize?

Depressurize?

Fix the typo.

Fix the typo.

moved to general task

moved to general task

Can we move this exec at task level, independent of Drybicart operations?

Can we move this exec at task level, independent of Drybicart operations?

Comment missing?

Comment missing?

LEAHI-DD-FIRMWARE-LDT-4612_Dialysate Composition (Dry Bicarbonate) - FW Iteration - 4/1:
LEAHI-DD-FIRMWARE-LDT-4612_Dialysate Composition (Dry Bicarbonate) - FW Iteration - 4/1:
On DD f/w side, this should just be a simple pump controller. States should be Off and On (control to commanded Qsub). There is no flow sensor for feedback control, so assuming this is open loop si...

On DD f/w side, this should just be a simple pump controller. States should be Off and On (control to commanded Qsub). There is no flow sensor for feedback control, so assuming this is open loop similar to UF pump.
GenDialysate mode will have an HDF sub-state that signals this controller from Off to On and would also call separate controller for heater and separate (Switches) monitor for door sensors.

With all of that in mind, I think this unit should have a simpler name like SubPump.

I think there should be some state monitoring for potential alarm(s) in here too. Similar to BP door on TD f/w side where the current mode/state can signal this unit that it expects specific switch...

I think there should be some state monitoring for potential alarm(s) in here too. Similar to BP door on TD f/w side where the current mode/state can signal this unit that it expects specific switch state(s) (e.g. while in HDF state, we would expect the cap to be open and stowed and we would want to alarm if that was not the case).

Remove extra blank line.

Remove extra blank line.

LDT-3272 addressed the code review comments

  1. … 3 more files in changeset.
Where is call to HDF controller?

Where is call to HDF controller?

Monitors should come before mode mgmt above.

Monitors should come before mode mgmt above.

What about HemoDiaFiltration.h?

What about HemoDiaFiltration.h?

What about initHDF?

What about initHDF?

Where is HemoDiaFiltration.h?

Where is HemoDiaFiltration.h?

Why does this file name have pound signs pre/post?

Why does this file name have pound signs pre/post?

This macro is already defined in Common.h.

This macro is already defined in Common.h.

Align all "=" or none of them.

Align all "=" or none of them.

DD HDF control data published should just be state and set rate. TD HDF data would have volume, etc...

DD HDF control data published should just be state and set rate. TD HDF data would have volume, etc...

This looks like pump control function. I think TD f/w should be doing this when setting Qsub before sending to DD f/w. Again, I think DD f/w should just be controlling pump to the Qsub rate given b...

This looks like pump control function. I think TD f/w should be doing this when setting Qsub before sending to DD f/w. Again, I think DD f/w should just be controlling pump to the Qsub rate given by TD f/w.
HDF volume should be calculated by TD f/w by integrating commanded Qsub over time.

Remove blank line.

Remove blank line.