dgfirmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merged DEN-15199

DEN-15150 increased the inlet water high temperature limit to 45 C

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

DEN-15199 addressed the code review comment

Done

Done

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

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

I said fix throughout. Need fix in function below as well.

I said fix throughout. Need fix in function below as well.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Merge branch 'develop' of ssh://dvm-linux02:7999/dg/dgfirmware into develop

Merged DEN-15199

    • -0
    • +22
    /firmware/App/Services/SystemComm.c
DEN-15199 addressed the code review comments

Done

Done

Done

Done

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Done

Done

Done.

Done.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Brought the code back.

Brought the code back.

Why did we blank title/instructions?

Why did we blank title/instructions?

Acking even if payload length > 0?

Acking even if payload length > 0?

Checking for isTestingActivated should be done in sendTestConfigStatusToDialin function (not here). Fix throughout new handlers.

Checking for isTestingActivated should be done in sendTestConfigStatusToDialin function (not here). Fix throughout new handlers.

This is an output.

This is an output.

Remove "Been" from function name. And add a comment line above explaining what we're doing here.

Remove "Been" from function name. And add a comment line above explaining what we're doing here.

Merge branch 'staging' into DEN-15199-fw_dn_sprint_95

DEN-15199 added to code to check for dialin check in

    • -0
    • +18
    /firmware/App/Services/SystemComm.c
Removed. We'll want to watch for continued pump speed errors occurring on going to zero. There seem to be both RPM resolution and lag errors in the speed measurement, causing problems with the alar...

Removed. We'll want to watch for continued pump speed errors occurring on going to zero. There seem to be both RPM resolution and lag errors in the speed measurement, causing problems with the alarm. If problems continue, we should consider increasing the trigger interval, decreasing the clear interval, and/or resetting the alarm when the target is set to zero (or taking a large step).