Controllers

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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.

Removed // if ( TRUE == getNoNewTreatmentStatus() ) //{ // rejReason = REQUEST_REJECT_REASON_NO_NEW_TREATMENT_ALARM_TRIGGERED; // }

Removed
// if ( TRUE == getNoNewTreatmentStatus() )
//

Unknown macro: { // rejReason = REQUEST_REJECT_REASON_NO_NEW_TREATMENT_ALARM_TRIGGERED; // }
Removed line // payload.alarmsFlags |= ( almStatus.noNewTreatment ? BIT_BY_POS(ALARM_STATE_FLAG_BIT_POS_NO_NEW_TREATMENT) : 0 );

Removed line // payload.alarmsFlags |= ( almStatus.noNewTreatment ? BIT_BY_POS(ALARM_STATE_FLAG_BIT_POS_NO_NEW_TREATMENT) : 0 );

Removed line //noNewTreatment = ( TRUE == ALARM_TABLE[ a ].alarmNoNewTreatment ? TRUE : noNewTreatment );

Removed line //noNewTreatment = ( TRUE == ALARM_TABLE[ a ].alarmNoNewTreatment ? TRUE : noNewTreatment );

Just delete this line of code.

Just delete this line of code.

Just delete this line of code.

Just delete this line of code.

Just delete this code.

Just delete this code.

It looks like staging branch has things the way it was too.

It looks like staging branch has things the way it was too.

Should be since last service (not last treatment).

Should be since last service (not last treatment).

This was part of the merge from staging branch.

This was part of the merge from staging branch.

What is the reason for these changes? Just reading the code, it makes more sense to me that way it was.

What is the reason for these changes? Just reading the code, it makes more sense to me that way it was.

0xA04E was originally MSG_ID_DG_HD_COMMUNICATION_STATUS_OVERRIDE. It was moved to 0xA008 due to an out of sync error in our lovely excel sheet. MSG_ID_DG_SET_FANS_RPM_ALARM_START_TIME_OFFSET should...

0xA04E was originally MSG_ID_DG_HD_COMMUNICATION_STATUS_OVERRIDE. It was moved to 0xA008 due to an out of sync error in our lovely excel sheet. MSG_ID_DG_SET_FANS_RPM_ALARM_START_TIME_OFFSET should now be 0xA04E.

Note: These values are what is currently reflected on staging.

Where is 0xA04E?

Where is 0xA04E?

Added exception for Stopped sub states and before door should be closed.

Added exception for Stopped sub states and before door should be closed.

Added

Added

Added.

Added.

Added.

Added.

Good catch. Updated.

Good catch. Updated.

Moved and used getSwitchStatus to ensure overrides work.

Moved and used getSwitchStatus to ensure overrides work.

Sean said leave it as is. No harm to be done.

Sean said leave it as is. No harm to be done.

Yes. It writes the entire block for MEMORY and SECTIONS so the entire section must be overridden rather than single items.

Yes. It writes the entire block for MEMORY and SECTIONS so the entire section must be overridden rather than single items.

Similiar to how the check is done in ModePostTreat.c, I think we should check if the heparin parameters are > 0.0 than NEARLY_ZERO.

Similiar to how the check is done in ModePostTreat.c, I think we should check if the heparin parameters are > 0.0 than NEARLY_ZERO.

Out of scope of the changes here but hepRate should be getting TREATMENT_PARAM_HEPARIN_DISPENSE_RATE instead of TREATMENT_PARAM_HEPARIN_BOLUS_VOLUME.

Out of scope of the changes here but hepRate should be getting TREATMENT_PARAM_HEPARIN_DISPENSE_RATE instead of TREATMENT_PARAM_HEPARIN_BOLUS_VOLUME.

Should we check pump track switch too?

Should we check pump track switch too?

Should we check pump track switch too?

Should we check pump track switch too?