hdfirmware

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merged DEN-15250 to staging.

Merge staging to DEN-15250.

DEN-15359: Updated tx params to change art/ven pressure limit params from min/max to window.

    • -27
    • +35
    /firmware/App/Controllers/PresOccl.c
    • -64
    • +17
    /firmware/App/Modes/ModeTreatment.c
    • -44
    • +14
    /firmware/App/Modes/ModeTreatmentParams.c
    • -8
    • +4
    /firmware/App/Modes/ModeTreatmentParams.h
The valves are not returned to their target position until the alarm is cleared. I could make a broader change, but is that what you're suggesting?

The valves are not returned to their target position until the alarm is cleared. I could make a broader change, but is that what you're suggesting?

DEN-13865: Addressed code review comment.

    • -1
    • +1
    /firmware/App/Controllers/SyringePump.c
DEN-15396 Use greater of 10sec or 10 Rotor turn times for minimum persistent error time.

    • -4
    • +8
    /firmware/App/Controllers/DialInFlow.c
Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

Merge branch 'DEN-13865-fw-duplicate-alarms-occur-during-post-treatment-rinseback-and-block-workflow' into develop

DEN-13865: More fixes to alarm re-trigger prevention logic.

Merge branch 'DEN-13865-fw-duplicate-alarms-occur-during-post-treatment-rinseback-and-block-workflow' into develop

DEN-13865: fix re-trigger block logic.

    • -20
    • +23
    /firmware/App/Services/AlarmMgmt.c
Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

Merge branch 'DEN-13865-fw-duplicate-alarms-occur-during-post-treatment-rinseback-and-block-workflow' into develop

DEN-13865: Handle no re-trigger action or end-tx only alarms during rinseback/recirc states of treatment mode.

Merge branch 'DEN-13865-fw-duplicate-alarms-occur-during-post-treatment-rinseback-and-block-workflow' into develop

    • -0
    • +1
    /firmware/App/Controllers/SyringePump.c
DEN-13865: Implemented alarm system feature to prevent alarm re-trigger per new properties. Addressed DEN-15295.

    • -0
    • +1
    /firmware/App/Controllers/SyringePump.c
Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

Merge branch 'DEN-15367-hd_dg_test_configuration_setup' into develop

DEN-15367 updated the use wet cartrdige test configuration

So then can we remove power loss alarm active checks from this condition (just keep the cpld power loss check as before)?

So then can we remove power loss alarm active checks from this condition (just keep the cpld power loss check as before)?

Do we need the alarm active checks? Isn't power loss check sufficient?

Do we need the alarm active checks? Isn't power loss check sufficient?

HD-DEN-13865_FW Duplicate Alarms Occur During Post Treatment Rinseback And Block Workflow
HD-DEN-13865_FW Duplicate Alarms Occur During Post Treatment Rinseback And Block Workflow
Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

Merge branch 'DEN-15250-pre-treatment-does-not-end-successfully' into develop

DEN-15250: cosmetic and coding standard changes.

    • -29
    • +29
    /firmware/App/Modes/OperationModes.c
Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

Merge remote-tracking branch 'origin/DEN-15363-fw-handle-bld-sensor-communication-errors' into develop

    • -5
    • +12
    /firmware/App/Controllers/BloodLeak.c
DEN-15363 Reuse alarm ID 63 for Blood Leak communications errors

The root cause is that abnormal AC power loss on the HD causes abnormal operating conditions and spurious errors. The valves return to position after the alarm is cleared, not when AC returns. The ...

The root cause is that abnormal AC power loss on the HD causes abnormal operating conditions and spurious errors. The valves return to position after the alarm is cleared, not when AC returns. The timer gives a ten-second window following removing the power fail signal and the alarm condition, where the alarm block is active. The original block used the alarms alone, we changed to the CPLD power loss detection - which returns with the return of AC. Clearing the alarms late means removing the block before the valves return to normal operation.

I think there are two approaches. We already have distributed failsafe that is entered on power fail, which we recover from after the alarm is cleared.
1. Create a pervasive state that affects every operating mode, allowing transitions to "safe" states during alarms, then back to the original operating state. The safe state would not register errors until after the transition back to normal operation.
2. Block errors until both AC is returned and the alarm is cleared when normal operation is restored.

The second approach is much simpler and addresses the root problem: odd control configurations resulting from having alarms with conflicting controls. In this case, the secondary alarms are spurious since they result from the valves dropping into a safe position, for instance, on the loss of AC. We also have a handful of other errors that occur under these conditions, fan speed, for instance, as well as valve positions,