Dashboard

LEAHI-DD-FIRMWARE-LDT-4049_Standby - FW Implementation - 2/2:
LEAHI-DD-FIRMWARE-LDT-4049_Standby - FW Implementation - 2/2:
LEAHI-TD-FIRMWARE-LDT-4049_Standby - FW Implementation - 2/2:
LEAHI-TD-FIRMWARE-LDT-4049_Standby - FW Implementation - 2/2:
LDT-4832:Updated FW/UI Message Id

Being generic is the whole point of it. It was renamed because this is a dialin dedicated to Leahi unit and calling the messages DenaliMessage is misleading. It was renamed to CanMessage for 2 reas...

Being generic is the whole point of it.
It was renamed because this is a dialin dedicated to Leahi unit and calling the messages DenaliMessage is misleading.
It was renamed to CanMessage for 2 reason:
1. This is a Leahi only dialin, so there is no need to differentiate between different type of Can Messages as there would be only 1 type
2. Calling it CanMessage will make it more future compatible when the dialin get copied over for a new unit development (unlikely in the foreseeable future but possible), removing the need to rename it again

There is no Leahi or Denali CANChannels. There are CAN channels and the naming is what that channel is being used for. The collision occurs in the FW and the FW handles it before sending out a mess...

There is no Leahi or Denali CANChannels.
There are CAN channels and the naming is what that channel is being used for.
The collision occurs in the FW and the FW handles it before sending out a message.
When reading a CAN, there are no collisions, so there are no priorities. So I have no clue what you want here.

LDT-4832:Updated FW/UI Message Id

done

done

I have no idea what you are referring to as the link is not working. The need to define the type and the name of the data being read is necessary, so if it's not here it will be somewhere else, tha...

I have no idea what you are referring to as the link is not working.
The need to define the type and the name of the data being read is necessary, so if it's not here it will be somewhere else, that we can't escape.
Exporting that to different files won't serve a purpose and will only increase complexity as when debugging you will need to reference a separate file.
For the defs it made sense as they are used multiple places, but what a message contains is a single use place, so storing it separately is meaningless as it won't have any use outside of this single function.

Merge branch 'staging' into LDT-4484-dry_self_test

    • -10
    • +14
    /leahi_dialin/td/treatment_delivery.py
LEAHI-TD-FIRMWARE-LDT-4875_(TD) H12 is not Actuating during AT Lower and Raise Events
LEAHI-TD-FIRMWARE-LDT-4875_(TD) H12 is not Actuating during AT Lower and Raise Events
Where is testBatteryI2cStatusOverride (from BatteryDriver)?

Where is testBatteryI2cStatusOverride (from BatteryDriver)?

LDT-3735: Updated payload for send cal record

    • -269
    • +284
    /firmware/App/Services/NVMessagingDD.c
    • -14
    • +74
    /firmware/App/Services/NVRecordsDD.c
    • -0
    • +12
    /firmware/App/Services/NVRecordsDD.h
removed some unnecessary entry from calibration records

    • -0
    • +18
    /leahi_dialin/dd/modules/records.py
fixed

fixed

fixed typo

updates

    • -23
    • +39
    /leahi_dialin/dd/modules/records.py
LDT-4857 SW Misc & Enhc - SW - 01 - Remove Old Messaging Logic [PowerOff].sh - R&I - 05: DEV - Feature Implementation

update osbolete onActionTransmit to actionTransmit and removed signal tracing of actionTransmit from GUI -> APp -> MsgDispathcer

    • -78
    • +59
    /sources/canbus/MessageDispatcher.cpp
LEAHI-APPLICATION-LDT-4852_SW Misc & Enhc - SW - 01 - Remove Old Messaging Logic [PowerOff].sh - R&I
LEAHI-APPLICATION-LDT-4852_SW Misc & Enhc - SW - 01 - Remove Old Messaging Logic [PowerOff].sh - R&I
LDT-4815 SW Misc & Enhc - SW - 01 - Device Settings - Screens - R&I - 05: DEV - Feature Implementation

update export logs screen

    • -0
    • +80
    /sources/gui/qml/compounds/ExportLogsHeaderData.qml
    • -1
    • +2
    /sources/gui/qml/globals/Variables.qml
LEAHI-DIALIN-LDT-4410_Dialysate Composition (Mixing) - FW Implementation - 3/1:
LEAHI-DIALIN-LDT-4410_Dialysate Composition (Mixing) - FW Implementation - 3/1:
Add blank line before return statement.

Add blank line before return statement.

LDT-4410 updated broadcast data for bal chamber

    • -12
    • +10
    /leahi_dialin/dd/modules/balancing_chamber.py
LDT-4410 merged latest staging into my branch

    • -80
    • +273
    /firmware/App/Controllers/DryBiCart.c
    • -9
    • +23
    /firmware/App/Controllers/MixingControl.c
fix typo

fix typo

Updated Alarm Priority data type

LDT-4013-1: Add code related to fluid types, tube set types, modality