hdfirmware

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fixed. Thanks!

Fixed. Thanks!

Fixed. Thanks!

Fixed. Thanks!

Fixed. Thanks!

Fixed. Thanks!

Fixed. Thanks!

Fixed. Thanks!

Fixed. Thanks!

Fixed. Thanks!

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Please remove the extra blank line.

Please remove the extra blank line.

State removed.

State removed.

Add blank line after function scope.

Add blank line after function scope.

I think we should be checking alarm condition instead of alarm active. Temperature may have come back into range (condition cleared) but user hasn't resumed to clear alarm (maybe stepped away for a...

I think we should be checking alarm condition instead of alarm active. Temperature may have come back into range (condition cleared) but user hasn't resumed to clear alarm (maybe stepped away for a minute).

Why is this a separate condition when it's doing the exact same thing as above?

Why is this a separate condition when it's doing the exact same thing as above?

Add space between if and (.

Add space between if and (.

If you search for where execReservoirs() is called, you will see that it's already called by ModeTreatment.c right before this function is called.

If you search for where execReservoirs() is called, you will see that it's already called by ModeTreatment.c right before this function is called.

The next state - which should now be the first drain state - also checks DG modes. I don't see an issue with removing this state except that next state needs to check for DG in fault mode so that i...

The next state - which should now be the first drain state - also checks DG modes. I don't see an issue with removing this state except that next state needs to check for DG in fault mode so that it will skip past drain state.

CLOSED in CODE WALKTHROUGH.

CLOSED in CODE WALKTHROUGH.

Not required. checkPostTreatmentPatientDisconnect() releases the door closed requirements when user confirms patient disconnect. Removed.

Not required. checkPostTreatmentPatientDisconnect() releases the door closed requirements when user confirms patient disconnect. Removed.

I left it because DG modes are checked and thought it must be waiting for DG mode to sync before moving on. If not an issue, I can remove it.

I left it because DG modes are checked and thought it must be waiting for DG mode to sync before moving on. If not an issue, I can remove it.

Updated.

Updated.

HD-DEN-15330_Dialysate Temp Alarm Recovery Takes A Long Time NO Reservoir Switching
HD-DEN-15330_Dialysate Temp Alarm Recovery Takes A Long Time NO Reservoir Switching
I feel like this whole state should be removed. We are no longer doing de-prime. Removing state will mean Dialin must be updated to reflect new state list.

I feel like this whole state should be removed. We are no longer doing de-prime. Removing state will mean Dialin must be updated to reflect new state list.

Do we still need this condition? Door closed requirement may have been released in prior state. Doesn't seem like this is truly needed to move on from here.

Do we still need this condition? Door closed requirement may have been released in prior state. Doesn't seem like this is truly needed to move on from here.

Add patientDisconnectHandled to header

Add patientDisconnectHandled to header

HD-DEN-15436_Dpi Tubing Comes Out OF Pump Track During Dpi Reversal IN Post Treatment
HD-DEN-15436_Dpi Tubing Comes Out OF Pump Track During Dpi Reversal IN Post Treatment
HD-DEN-15489_FW DG Disinfect Has Expired Check Does Not Clear With Valid Dates
HD-DEN-15489_FW DG Disinfect Has Expired Check Does Not Clear With Valid Dates
HD Staging Unreviewed Commits
HD Staging Unreviewed Commits