Dashboard

But now it's not in right position (in this table only). This table should be sorted by rank.

But now it's not in right position (in this table only). This table should be sorted by rank.

the 2nd if statement for beta 1.0 is an ask from systems team to raise fault alarm if user by mistake enable Beta 2.0 config when Beta1.0 is active

the 2nd if statement for beta 1.0 is an ask from systems team to raise fault alarm if user by mistake enable Beta 2.0 config when Beta1.0 is active

LEAHI-TD-FIRMWARE-LDT-3126_Blood Prime - TD
LEAHI-TD-FIRMWARE-LDT-3126_Blood Prime - TD
Bamboo Commit: Updated Branch develop For Project TD

    • binary
    /TD/BETA/TD_Debug_Beta_v0.0.0-43.out
    • binary
    /TD/BETA/TD_Debug_Beta_v0.0.0-44.out
removed both enums

removed both enums

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

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

LDT-3559 merged into develop

LDT-3559 merged into staging

Updated

Updated

Updated

Updated

LDT-3539-air-infusion-td

LDT-3126-blood-prime-td

    • -0
    • +43
    /firmware/App/Modes/StateTxBloodPrime.c
LDT-3126-blood-prime-td

LDt-473 updated the enum list

LDT-473 updated dd dialysate requst msg and added send pressure limit change response

    • -7
    • +11
    /firmware/App/Modes/ModeTreatment.c
    • -0
    • +11
    /firmware/App/Modes/ModeTreatment.h
    • -0
    • +28
    /firmware/App/Services/SystemCommTD.c
This was correct before (assuming 711 was correct rank).

This was correct before (assuming 711 was correct rank).

Why change rank back to 206? If priority is low, rank was probably correct at 711. I think you had correct properties before - it was just in the wrong row.

Why change rank back to 206? If priority is low, rank was probably correct at 711. I think you had correct properties before - it was just in the wrong row.

LDT-473 updated dialysate delivery request msg payload

In comment, specify units is % duty cycle (0..100%).

In comment, specify units is % duty cycle (0..100%).

Should we specify that power level is now a duty cycle percentage (0..100%)?

Should we specify that power level is now a duty cycle percentage (0..100%)?

Bamboo Commit: Updated Branch develop For Project TD

    • binary
    /TD/BETA/TD_Debug_Beta_v0.0.0-42.out
    • binary
    /TD/BETA/TD_Debug_Beta_v0.0.0-43.out
Updated

Updated

Updated

Updated

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

We have a FRACTION_TO_PERCENT_FACTOR in Common.h that we can use when we need 100.0.

We have a FRACTION_TO_PERCENT_FACTOR in Common.h that we can use when we need 100.0.

Merge branch 'develop' of bitbucket.org:diality-cloud/td-firmware into develop