Controllers

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Update message list with latest data details.

Update message list with latest data details.

Update message list with latest broadcast msg data details.

Update message list with latest broadcast msg data details.

We don't need to calculate digit count - just use strlen(tempCharBuffer) after sprintf creates your string.

We don't need to calculate digit count - just use strlen(tempCharBuffer) after sprintf creates your string.

I would set this to at least 11 because you are using sprintf to create an unsigned integer string (max is 10 digits + 1 zero terminator) and we want to make sure we give sprintf a large enough buf...

I would set this to at least 11 because you are using sprintf to create an unsigned integer string (max is 10 digits + 1 zero terminator) and we want to make sure we give sprintf a large enough buffer to populate - otherwise it will overwrite memory.

.crc?

.crc?

1 and 0 is not clear. Better to say FIFO send and reset.

1 and 0 is not clear. Better to say FIFO send and reset.

Create and trigger new alarm.

Create and trigger new alarm.

.crc?

.crc?

Recommend changing > to >= and then removing the - 1.

Recommend changing > to >= and then removing the - 1.

Please update message list details for this broadcast msg.

Please update message list details for this broadcast msg.

If h/w component is not required to have a calibration, we shouldn't alarm here - right?

If h/w component is not required to have a calibration, we shouldn't alarm here - right?

We should verify bufferLength is >= to cal section byte size before doing this memcpy - otherwise, we will be overwriting memory.

We should verify bufferLength is >= to cal section byte size before doing this memcpy - otherwise, we will be overwriting memory.

Is CRC check on individual cal section done elsewhere or should it be considered here as well?

Is CRC check on individual cal section done elsewhere or should it be considered here as well?

Done.

Done.

Recommend moving this rate to be with the others above.

Recommend moving this rate to be with the others above.

STEADY_VOLUME_COUNT_SEC is a number of seconds of stability indicating volume is steady. This only works because sampling time above is once per second. If somebody changes the sampling time, this ...

STEADY_VOLUME_COUNT_SEC is a number of seconds of stability indicating volume is steady. This only works because sampling time above is once per second. If somebody changes the sampling time, this condition will not be right.

Make 0.5 a #define.

Make 0.5 a #define.

Can we please use available alarm IDs above before adding a new one?

Can we please use available alarm IDs above before adding a new one?

After talking with Hung, This change is currently on his feature branch and should not be changed in here, later which codes are merged it will be resolved in case of conflict.

After talking with Hung,
This change is currently on his feature branch and should not be changed in here,
later which codes are merged it will be resolved in case of conflict.

Late breaking news, the HD_PRE_TREATMENT_PRIME_STATE_T has changed. The correct order of the items in enum type of the pre-treatment states are listed below: HD_PRIME_START_STATE = 0, ///< Prime s...

Late breaking news, the HD_PRE_TREATMENT_PRIME_STATE_T has changed.
The correct order of the items in enum type of the pre-treatment states are listed below:

HD_PRIME_START_STATE = 0, ///< Prime start state
HD_PRIME_WAIT_FOR_USER_START_STATE, ///< Wait for user to start prime state
HD_PRIME_SALINE_SETUP_STATE, ///< Saline setup state
HD_PRIME_SALINE_PURGE_AIR_STATE, ///< Saline purge air state
HD_PRIME_SALINE_CIRC_BLOOD_CIRCUIT_STATE, ///< Circulate blood circuit state
HD_PRIME_RESERVOIR_ONE_FILL_COMPLETE_STATE, ///< Wait for reservoir 1 fill complete
HD_PRIME_DIALYSATE_DIALYZER_STATE, ///< Dialysate dialyzer fluid path state
HD_PRIME_SALINE_DIALYZER_SETUP_STATE, ///< Saline dialyzer setup state
HD_PRIME_SALINE_DIALYZER_STATE, ///< Saline dialyzer fluid path state
HD_PRIME_RESERVOIR_TWO_FILL_COMPLETE_STATE, ///< Wait for reservoir 2 fill complete
HD_PRIME_DIALYSATE_BYPASS_STATE, ///< Dialysate bypass fluid path state
HD_PRIME_WET_SELF_TESTS_STATE, ///< Perform wet self-tests after priming complete
HD_PRIME_PAUSE, ///< Prime pause state, waits to be resumed
HD_PRIME_COMPLETE, ///< Prime complete state
NUM_OF_HD_PRIME_STATES ///< Number of prime sub-mode states

Yes, we could use a single variable as the start time in all the pre-treatment states

Yes, we could use a single variable as the start time in all the pre-treatment states

Replaced "loadcellSteadyVolumeStartTime" with "steadyVolumeSamplingStartTime"

Replaced "loadcellSteadyVolumeStartTime" with "steadyVolumeSamplingStartTime"

Done

Done

Done

Done

No, loadcellSteadyVolumeStartTime was last set when the primeDialysateDialyzerTimeLimit has just expired.

No, loadcellSteadyVolumeStartTime was last set when the primeDialysateDialyzerTimeLimit has just expired.

Done

Done

Done

Done

Done.

Done.

This start time probably needs a new name to better describe what it's doing.

This start time probably needs a new name to better describe what it's doing.

Recommend just setting up pumps and valves in this function rather than calling another function.

Recommend just setting up pumps and valves in this function rather than calling another function.