leahi-dialin

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDT-4795 NON-FEATURE: SW Misc & Enhc - SW - 01 - Power Control - Shutdown - R&I - 08: DEV - Dialin Implementation

address cr commetns

Merge branch 'staging' into LDT-3735-non-volatile-memory

    • -30
    • +2
    /leahi_dialin/dd/dialysate_delivery.py
    • -10
    • +14
    /leahi_dialin/td/treatment_delivery.py
Merge branch 'LDT-4878-buildsh' into staging

Merge branch 'LDT-4539-event_on_service_change' into staging

Merge branch 'LDT-4160-alarm_table' into staging

    • -2
    • +2
    /leahi_dialin/utils/abstract_classes.py
Merge branch 'LDT-4539-event_on_service_change' into develop

Merge branch 'LDT-4160-alarm_table' into develop

    • -42
    • +109
    /leahi_dialin/td/modules/alarms.py
    • -2
    • +2
    /leahi_dialin/utils/abstract_classes.py
Merge branch 'LDT-4878-buildsh' into develop

Updated build.sh

LEAHI-DIALIN-LDT-4878_(Dialin) The wheel file generated by the build.sh command failed to install
LEAHI-DIALIN-LDT-4878_(Dialin) The wheel file generated by the build.sh command failed to install
fixed indexing for eventlist enum

docu header

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.

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
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
LEAHI-DIALIN-LDT-4410_Dialysate Composition (Mixing) - FW Implementation - 3/1:
LEAHI-DIALIN-LDT-4410_Dialysate Composition (Mixing) - FW Implementation - 3/1:
LDT-4410 updated broadcast data for bal chamber

    • -12
    • +10
    /leahi_dialin/dd/modules/balancing_chamber.py
fix typo

fix typo

Updated Alarm Priority data type