hdfirmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-14763 changed the sizeof of message 0x98 to be able to pick up with the script

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

Fixed merge conflict.

    • -1
    • +1
    /firmware/App/Controllers/DGInterface.c
    • -2
    • +2
    /firmware/App/Controllers/DGInterface.h
    • -2
    • +2
    /firmware/App/Controllers/SyringePump.c
Merge branch 'staging' into DEN-14830-incorrect-dialysate-temperature-alarm-triggered

    • -11
    • +34
    /firmware/App/Controllers/DGInterface.c
    • -4
    • +5
    /firmware/App/Controllers/DGInterface.h
Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

    • -1
    • +1
    /firmware/App/Controllers/DGInterface.c
    • -2
    • +2
    /firmware/App/Controllers/DGInterface.h
    • -1
    • +1
    /firmware/App/Controllers/DialInFlow.c
    • -1
    • +1
    /firmware/App/Controllers/DialInFlow.h
    • -2
    • +2
    /firmware/App/Controllers/SyringePump.c
Merged DEN-13154 into staging.

Fixed merge conflicts from local merge from staging.

    • -22
    • +29
    /firmware/App/Controllers/DGInterface.c
    • -2
    • +2
    /firmware/App/Controllers/DGInterface.h
    • -2
    • +2
    /firmware/App/Controllers/DialInFlow.c
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.

RESOLVED IN CODE WALKTHROUGH.

RESOLVED IN CODE WALKTHROUGH.

RESOLVED IN CODE WALKTHROUGH.

RESOLVED IN CODE WALKTHROUGH.

DEN-13154: Addressed code review comments.

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

FALSE will be determined by our automagic script to be ACK_REQUIRED in the excel sheet. This will cause discrepancies between the readers of that sheet and what the FW does.

FALSE will be determined by our automagic script to be ACK_REQUIRED in the excel sheet. This will cause discrepancies between the readers of that sheet and what the FW does.

Fixed.

Fixed.

Variable is also updated by receipts of DG flow broadcasts. I believe it is overridable on DG side.

Variable is also updated by receipts of DG flow broadcasts. I believe it is overridable on DG side.

Concern was originally just for retract due to highest speed. We ended up reducing retract speed to reduce likelihood of stalls. Still a good idea to check for it though and since retract, preload ...

Concern was originally just for retract due to highest speed. We ended up reducing retract speed to reduce likelihood of stalls. Still a good idea to check for it though and since retract, preload and seek all share same relatively high speed, these are the ops that have the check. For bolus and continuous, should not stall at these speeds and would catch with rate alarm if it did.

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

DEN-14689: updated naming msg_id naming in relation to common changes

Fixed.

Fixed.

Fixed.

Fixed.

Fixed.

Fixed.

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

    • -13
    • +48
    /firmware/App/Modes/ModePreTreat.c
Fixed?

Fixed?

To answer this and comment below: above_high_safety_range = temp > 46 above_low_safety_range = temp > 42 above_target_temp = target + 4 below_target_temp = target - 4 below_low_safety_range = temp...

To answer this and comment below:

above_high_safety_range = temp > 46
above_low_safety_range = temp > 42
above_target_temp = target + 4
below_target_temp = target - 4
below_low_safety_range = temp < 33

I did not see any specification regarding to separate or not to separate. Original functionality had separate triggers. Respective PRS's state OR between the two triggers.
I think it would be clear to for us in terms of debugging to see which alarm is triggered since on the low side, temp - 4 would be lower than 33, (31).

Wording may be unclear. Im up for suggestions to help clarify the alarm differences.

Fixed. Thanks!

Fixed. Thanks!