All Activity

Yes. The integrity module is in leahi-fwcommon repository, and it serves both TD and DD.

Yes. The integrity module is in leahi-fwcommon repository, and it serves both TD and DD.

These are located in the integrity.c

These are located in the integrity.c

Yes the ECC checks are done in the bootloader stack.

Yes the ECC checks are done in the bootloader stack.

LDT-4516 Treatment Logs - SW - 01 - Treatment Logs - R&I - 05: DEV - Feature Implementation

update vdata from treatment log

    • -0
    • +127
    /sources/gui/qml/dialogs/PatientIdEntry.qml
    • -54
    • +52
    /sources/storage/TreatmentLog.cpp
Merge branch 'DENBUG-337-whitney--inf-values-not-displaying-as-0-on-the-hcp-portal-views' into develop

DENBUG-337 added the cloudsync code from 0.5.6-build_3-052426

    • -0
    • +108
    /cloudsync/handlers/logs_handler.py
CLOUDSYNC-DENBUG-337_Whitney Inf Values Not Displaying AS 0 ON The Hcp Portal Views
CLOUDSYNC-DENBUG-337_Whitney Inf Values Not Displaying AS 0 ON The Hcp Portal Views
SOFTWAREUPDATE-LDT-3239_Software Update - SW - 01 - R&I
SOFTWAREUPDATE-LDT-3239_Software Update - SW - 01 - R&I
LDT-4033-patient-vitals-fw-implementation

The test should verify that the config file content is displayed and should not be hard-coded. So, there should be a function that reads and retrieves the values defined in the conf file, rather th...

The test should verify that the config file content is displayed and should not be hard-coded.
So, there should be a function that reads and retrieves the values defined in the conf file, rather than being hard-coded here, and then compares them with the SW Application dialog content.

LEAHI-DIALIN-LDT-4511_Treatment Logs - SW - 01 - Treatment Logs - R&I
LEAHI-DIALIN-LDT-4511_Treatment Logs - SW - 01 - Treatment Logs - R&I
LEAHI-APPLICATION-LDT-4511_Treatment Logs - SW - 01 - Treatment Logs - R&I
LEAHI-APPLICATION-LDT-4511_Treatment Logs - SW - 01 - Treatment Logs - R&I
Fixed

Fixed

LDT-4519 Treatment Logs - SW - 01 - Treatment Logs - R&I - 08: DEV - Dialin Implementation

add messgae ids

remove camel case for SetPoint, instead use Setpoint Update line 659 too

remove camel case for SetPoint, instead use Setpoint
Update line 659 too

Can we rename this to TREATMENT_DURATION_CONFIRM_REQUEST_PAYLOAD_T

Can we rename this to TREATMENT_DURATION_CONFIRM_REQUEST_PAYLOAD_T

Can we rename this to TREATMENT_DURATION_VALIDATE_REQUEST_PAYLOAD_T?

Can we rename this to TREATMENT_DURATION_VALIDATE_REQUEST_PAYLOAD_T?

What is the difference between the bicarbonateConcentrate and bicarbonate. Please update the comment.

What is the difference between the bicarbonateConcentrate and bicarbonate. Please update the comment.

Looks like comment for 208 and 223 are swapped?

Looks like comment for 208 and 223 are swapped?

Merge branch 'DENBUG-336-whitney-device-logs-stuck-in-the-dcs-backend-upon-device-re-registration' into develop

DENBUG-336: Merged the cloudsync changes of version 0.5.6-build_3-052426

    • -0
    • +108
    /cloudsync/handlers/logs_handler.py
please align the comments

please align the comments

Please update the msg id to MSG_ID_TD_TREATMENT_SET_POINT_DIALYSATE_TEMP_CHANGE_RESPONSE

Please update the msg id to MSG_ID_TD_TREATMENT_SET_POINT_DIALYSATE_TEMP_CHANGE_RESPONSE

Please break it into two lines and check other functions too.

Please break it into two lines and check other functions too.

Fixed

Fixed

Fixed

    • -13
    • +195
    /firmware/App/Modes/ModePreTreat.c
    • -14
    • +253
    /firmware/App/Services/FpgaTD.c
    • -0
    • +1156
    /firmware/App/Services/StateServices/DrySelfTests.c
    • -0
    • +55
    /firmware/App/Services/StateServices/DrySelfTests.h
    • -1156
    • +0
    /firmware/App/Services/DrySelfTests.c
    • -55
    • +0
    /firmware/App/Services/DrySelfTests.h
Please break it into two lines

Please break it into two lines