dgfirmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Bamboo Commit: Updated DGCommon.h with build versions from Bamboo

Merge branch 'DEN-11750-dg_dev-dg-dialysate-temperature-control-tune-up' into develop

DEN-11750 updated the concentrate pumps

Bamboo Commit: Updated DGCommon.h with build versions from Bamboo

Merge branch 'DEN-11928-dg-conductivity-update-den-tbd' into develop

    • -127
    • +254
    /firmware/App/Modes/ModeFill.c
Merge branch 'DEN-11750-dg_dev-dg-dialysate-temperature-control-tune-up' into develop

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

    • -3
    • +12
    /firmware/App/Controllers/UVReactors.c
DEN-11928 Updated conductivity

DEN-11928 Updated conductivity test

DEN-11928 Updated temperature out of range test

DEN-11928 Updated temperature, rejection ratio, CPo with new values

Bamboo Commit: Updated DGCommon.h with build versions from Bamboo

Merge branch 'DEN-11750-dg_dev-dg-dialysate-temperature-control-tune-up' into develop

DEN-12225 updated the UV reactors

    • -1
    • +2
    /firmware/App/Controllers/UVReactors.c
Bamboo Commit: Updated DGCommon.h with build versions from Bamboo

Merge branch 'DEN-11750-dg_dev-dg-dialysate-temperature-control-tune-up' into develop

DEN-11750 updated the code

DEN-11928 Implemented conductivity updates

    • -116
    • +242
    /firmware/App/Modes/ModeFill.c
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;

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: Fixed casting error in ConcentratePumps.c.

Bamboo Commit: Updated DGCommon.h with build versions from Bamboo

Merged DEN-11750 and resolved the coflicts

    • -106
    • +11
    /firmware/App/Controllers/Heaters.c
    • -22
    • +11
    /firmware/App/Controllers/ROPump.c
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

DG-DEN-11750_DG Dev Dialysate Temperature Control Tune Up
DG-DEN-11750_DG Dev Dialysate Temperature Control Tune Up