common

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
The current design is for each mode to set actuators on entry to a new mode/sub-mode (e.g. this function) per that mode's initial state. Then, while in that mode/sub-mode, the mode's state machine ...

The current design is for each mode to set actuators on entry to a new mode/sub-mode (e.g. this function) per that mode's initial state. Then, while in that mode/sub-mode, the mode's state machine will change actuators as required when moving from one state to another.

This is the reason why at one of my previous companies we used to name variables with f_ or i_ as first characters to know at a glance the variable type definition. Now worth considering though.

This is the reason why at one of my previous companies we used to name variables with f_ or i_ as first characters to know at a glance the variable type definition. Now worth considering though.

Not fully clear what the sub-modes of service mode will be. At this time, I don't know what, if anything, should happen if the user presses the stop/pause button while in service mode. For now, the...

Not fully clear what the sub-modes of service mode will be. At this time, I don't know what, if anything, should happen if the user presses the stop/pause button while in service mode. For now, there is nothing to stop so we are ignoring.

Do we need a #define 0.8?

Do we need a #define 0.8?

Do we need a #define for 1.2?

Do we need a #define for 1.2?

Removed.

Removed.

Delete or add TODO comment.

Delete or add TODO comment.

Is the stop button still part of the design? And why are we ignoring it here?

Is the stop button still part of the design? And why are we ignoring it here?

Replace with function that sets these valves. Settings valves can be its own module for the various modes/sates and sub-modes/sub-states. This same concept can be applied to all actuators where in ...

Replace with function that sets these valves. Settings valves can be its own module for the various modes/sates and sub-modes/sub-states. This same concept can be applied to all actuators where in mode/sate or sub-mode/sub-state, the valves, the pumps, etc. are all set. I would like to avoid setting just the valves manually here and again manually set somewhere else. Let's keep all states centralized per mode/sub-mode or state/sub-state.

In verify state, we change the target pressure with the average pressure over the verify period. That pressure value is in float. For RO pump publish data, the data type for target pressure is floa...

In verify state, we change the target pressure with the average pressure over the verify period. That pressure value is in float.
For RO pump publish data, the data type for target pressure is float as well.

Do both #ifndef need to be satisfied for this portion of the code to execute? Where (at what time) are these two parameters set?

Do both #ifndef need to be satisfied for this portion of the code to execute? Where (at what time) are these two parameters set?

For the time that the RO pump is switching between ramp and stabilize to get to the flow, the drain continues, does that affect the drain process?

For the time that the RO pump is switching between ramp and stabilize to get to the flow, the drain continues, does that affect the drain process?

Calibration factors live in non-volatile memory. Set during calibration via Dialin.

Calibration factors live in non-volatile memory. Set during calibration via Dialin.

Why the RPM has been lowered?

Why the RPM has been lowered?

Where is bloodFlowCalGain defined and what is its value? Is it fixed across machines or does it get set at calibration time?

Where is bloodFlowCalGain defined and what is its value? Is it fixed across machines or does it get set at calibration time?

Do we need any persistent alarm after a couple of trials? How many times are you planning to go back and forth?

Do we need any persistent alarm after a couple of trials? How many times are you planning to go back and forth?

Are we planning to provide pressure in float? Like 30.25 psi?

Are we planning to provide pressure in float? Like 30.25 psi?

Agreed. Moved to DGDefs.h

Agreed. Moved to DGDefs.h

Next cmdSetDGActiveReservoir will put the valves back in a normal state.

Next cmdSetDGActiveReservoir will put the valves back in a normal state.

Should this be moved to common\DG_Defs.h? I see HD has same typedef.

Should this be moved to common\DG_Defs.h? I see HD has same typedef.

Do we need a setting for normal control via active reservoir? Or will the next cmdSetDGActiveReservoir command put the valves back in a normal state?

Do we need a setting for normal control via active reservoir? Or will the next cmdSetDGActiveReservoir command put the valves back in a normal state?

DG-DEN-6402_HD Dev Pretreatment Self Tests
DG-DEN-6402_HD Dev Pretreatment Self Tests
Done.

Done.

Done.

Done.

Done.

Done.

Removed this sub-mode.

Removed this sub-mode.

Removed the sub-mode. Each sub-mode will have their pause/stopped state.

Removed the sub-mode. Each sub-mode will have their pause/stopped state.

Removed. Door close has been converted to sub-mode state for appropriate sub-mode (no cartridge self-test, dry self-test)

Removed. Door close has been converted to sub-mode state for appropriate sub-mode (no cartridge self-test, dry self-test)