Services

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-12121: fixed memcpy

Merge branch 'DEN-12121-sw_dev-sprint-65-michael-garthwaite' into develop

DEN-12121: DIAL-147 fixed payload size check.

Merge branch 'DEN-12121-sw_dev-sprint-65-michael-garthwaite' into develop

DEN-12121: switch case for HD communication override. DIAL-147

Merge branch 'DEN-12121-sw_dev-sprint-65-michael-garthwaite' into develop

Does this need to be memset when we can initialize it with 0'd values above? (line 92)

Does this need to be memset when we can initialize it with 0'd values above? (line 92)

Do we need an if for an always true condition? does this branch statement need to be uncommented?

Do we need an if for an always true condition? does this branch statement need to be uncommented?

Shouldn't the override check be its own get function like other overidden properties? Ex: getUVReactorHealth() ?

Shouldn't the override check be its own get function like other overidden properties? Ex: getUVReactorHealth() ?

I think this alarm should be not commented out.

I think this alarm should be not commented out.

DEN-11750 updated the concentrate pumps

  1. … 2 more files in changeset.
DEN-12225, DEN-12221 added code to update the UV reactors health and to calculate the target flow change based on the target drain pump RPM

  1. … 1 more file in changeset.
DEN-11750 updated the code

  1. … 5 more files in changeset.
Could we move these fields outside of the for loop? They dont need to be initialized NUM_OF_FANS_NAMES times.

Could we move these fields outside of the for loop? They dont need to be initialized NUM_OF_FANS_NAMES times.

If the DG is broadcasting these raw values, shouldn't Dialin be sync'd as well to handle these new fields?

If the DG is broadcasting these raw values, shouldn't Dialin be sync'd as well to handle these new fields?

All the new timer counters no longer are initialized to 0. I understand that they get set in their respective init()'s to the timer counter, but was this intentional?

All the new timer counters no longer are initialized to 0. I understand that they get set in their respective init()'s to the timer counter, but was this intentional?

We should probably keep the = 0;

We should probably keep the = 0;

Merged DEN-11750 and resolved the coflicts

  1. … 6 more files in changeset.
Most of the files are VectorCAST that has been brought back from Code Clinic. Look at the files but they are auto generated so they are mostly passing through.

Most of the files are VectorCAST that has been brought back from Code Clinic. Look at the files but they are auto generated so they are mostly passing through.

Notices the 170 files that need to be reviewed https://c.tenor.com/RXMxqsRKEn0AAAAC/this-is-fine.gif

Notices the 170 files that need to be reviewed

https://c.tenor.com/RXMxqsRKEn0AAAAC/this-is-fine.gif

DEN-11750 addressed the bugs that Code Clinic reported

  1. … 5 more files in changeset.
DG-DEN-11750_DG Dev Dialysate Temperature Control Tune Up
DG-DEN-11750_DG Dev Dialysate Temperature Control Tune Up
DEN-12121: Implementation of DIAL-147, HD Communication Status Override.

Merged DEN-11750 and resolved the merge conflicts

  1. … 1 more file in changeset.
Merge branch 'DEN-11750-dg_dev-dg-dialysate-temperature-control-tune-up' of ssh://dvm-linux02:7999/dg/dgfirmware into DEN-11750-dg_dev-dg-dialysate-temperature-control-tune-up

DEN-11750: Renamed msg ack ID for consistency with HD code.

DEN-11750 updated the drain algorithm in reservoirs and updated the fans with the proper RPM out of range check

  1. … 5 more files in changeset.
DEN-11750 updated the publish staggers

  1. … 17 more files in changeset.
Merged DEN-11750 and resolved merge conflict

  1. … 4 more files in changeset.
DEN-11750 updated the drivers with the new calibration data

  1. … 6 more files in changeset.