common

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge branch 'staging' into DEN-14763-dg_hd_dev-hd_dg_dvt-update-part-10

DEN-14830: updated alarm table to latest PRS changes regarding dialysate temperature

Merge branch 'staging' into DEN-14830-incorrect-dialysate-temperature-alarm-triggered

Merge branch 'DEN-13154-heparin-syringe-empty-position-incorrect' into develop

DEN-13154: Fixed DEN-14330 re: tilt alarms should allow blood recirculation when treatment paused.

Fixed.

Fixed.

Fixed.

Fixed.

Why alarm if above low temp? I think >42 or > tgt+4 should be two ways to get same non-safety high temp alarm. And I think <33 or < tgt-4 should be two ways to get same non-safety low temp alarm. D...

Why alarm if above low temp? I think >42 or > tgt+4 should be two ways to get same non-safety high temp alarm.
And I think <33 or < tgt-4 should be two ways to get same non-safety low temp alarm.
Did Systems want to separate these? My understanding was not to separate.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Merge branch 'DEN-13154-heparin-syringe-empty-position-incorrect' into develop

DEN-13154: Fixed w.d. post detect.

I believe this MSG_ID is being removed in another branch

I believe this MSG_ID is being removed in another branch

happens in FW common. This branch wasn't created at the start and our automated scripted ended up created its own code review. See: http://devapps.diality.us:8060/cru/DG-DEN-14689-2 Ill reorganize ...

happens in FW common. This branch wasn't created at the start and our automated scripted ended up created its own code review. See: http://devapps.diality.us:8060/cru/DG-DEN-14689-2
Ill reorganize the review naming shortly.

DEN-14830: renamed dialysate temp alarms to be more concise. Added alarm id 322 for below 33degc dialysate temp.

Should REQUEST be moved to end of name? Seems like there are many enum names where REQUEST is not at end of name.

Should REQUEST be moved to end of name? Seems like there are many enum names where REQUEST is not at end of name.

Is this a response to request above or a data broadcast?

Is this a response to request above or a data broadcast?

Should this have _REQUEST added to end?

Should this have _REQUEST added to end?

RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

This will hard fault the HD. Please change to getTreatmentParameterU32()

This will hard fault the HD. Please change to getTreatmentParameterU32()

This will hard fault the HD. Please change to getTreatmentParameterU32()

This will hard fault the HD. Please change to getTreatmentParameterU32()

Merge branch 'staging' into DEN-14689-messaging-bugs

DEN-14689: fixed ui version info request response naming to be more concise

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

Merge branch 'DEN-14689-messaging-bugs' into develop

DEN-14689: fixed compilation error on DG's side.

DEN-14763 added the heat disinfect active cool states