· /leahi_dialin/common/dd_defs.py	(-1, +2)	| History	| Source	| Diff
· /leahi_dialin/common/generic_defs.py	(-13, +361)	| History	| Source	| Diff
· /leahi_dialin/common/msg_ids.py	(-69, +92)	| History	| Source	| Diff
· /leahi_dialin/common/td_defs_proxy.py	(-0, +15)	| History	| Source	| Diff
· /leahi_dialin/td/treatment_delivery.py	(-0, +2)	| History	| Source	| Diff

]]> Tue, 21 Jul 2026 07:29:20 -0700 https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-3735-1 https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-3735-1 Raghu Kallala finished reviewing LEAHI-DIALIN-LDT-3735-1 LEAHI-DIALIN-LDT-3735_System Data and Logs - DD - Non-Volatile Memory - 04: DEV - Feature Implementation ]]> Mon, 20 Jul 2026 12:34:32 -0700 Dara Navaei https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-5152-1 https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-5152-1 Dara Navaei started review LEAHI-DIALIN-LDT-5152-1 ]]> Wed, 15 Jul 2026 15:04:04 -0700 Dara Navaei https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4611-5 https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4611-5 Dara Navaei started review LEAHI-DIALIN-LDT-4611-5 ]]> Mon, 13 Jul 2026 14:46:50 -0700 https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-3735-1 https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-3735-1 Tiffany Mejia and Michael Garthwaite finished reviewing LEAHI-DIALIN-LDT-3735-1 LEAHI-DIALIN-LDT-3735_System Data and Logs - DD - Non-Volatile Memory - 04: DEV - Feature Implementation ]]> Mon, 13 Jul 2026 11:51:27 -0700 Zoltan Miskolci https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4872-1 https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4872-1 Zoltan Miskolci Closed LEAHI-DIALIN-LDT-4872-1 ]]> Sun, 12 Jul 2026 23:43:02 -0700 Behrouz NematiPour https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4484-1/#c30436 https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4484-1/#c30436 Behrouz NematiPour replied to Zoltan Miskolci in LEAHI-DIALIN-LDT-4484-1

Zoltan and I had a meeting, and the counter solution he provided works better than mine.
He explained to me that my proposed solution has flaws.
RESOLVED.

· /leahi_dialin/common/msg_ids.py	(-2, +2)	| History	| Source	| Diff
· /leahi_dialin/td/modules/blood_pressure.py	(-0, +102)	| History	| Source
· /leahi_dialin/td/proxies/ui_proxy.py	(-0, +16)	| History	| Source	| Diff
· /leahi_dialin/td/treatment_delivery.py	(-0, +2)	| History	| Source	| Diff

]]> Mon, 06 Jul 2026 12:55:22 -0700 https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4072-1 https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4072-1 Sean Nash finished reviewing LEAHI-DIALIN-LDT-4072-1 LEAHI-DIALIN-LDT-4072_Power Loss - FW Implementation - 2/3: ]]> Wed, 01 Jul 2026 14:28:52 -0700 Zoltan Miskolci https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4484-1/#c30320 https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4484-1/#c30320 Zoltan Miskolci replied to Behrouz NematiPour in LEAHI-DIALIN-LDT-4484-1

The approach of what this code does and the conversion module are similar in function but a differ on maintenance and flexibility.
1. The conversion module's bytearray to value methods work, but they require manual logistic around the indexing. It's the user's responsibility to handle where the reading starts and you need to code the handler for that (previous approach with MsgFieldPositions), It's inflating the method. I worked hard to remove the need for indexing where the value starts. Instead of the previous struct.unpack approach, where you needed to maintain the type, you will be needing to maintain the conversion methods that are being called, so it would be the same as before, you still need to mind the indexing, which was the main reason of changing from this approach.

2. In the current approach, you declare the type and pass it to a processor that dynamically handling the unpack type (based on the set datatype) and the indexing for that. This works much better and easier to maintain, as you can just insert a new value when it's added to the FW, and don't need to adjust all your indexes for the reading.

Example #1, changing build type from U16 to U08:

• with the conversion approach, you need to change the function used, and update the starting index for all the following methods.
• with the current approach you change the Datatype.U16 to Datatype.U08 and that's all you need to do.

Example #2: adding a new variable fpga_micro after fpga_minor, with U08 type:

• with the conversion approach, you add the bytearray_to_byte, update the indexes for all the following reads.
• with the current approach you insert an element after the fpga_minor with a value ('fpga_micro', Datatype.U08), and nothing more needed

RESOLVED for now.

I would not do that because the function names and messages for each project should be different to avoid confusion.
I think that is fine for now.

RESOLVED.

So the same channels are used for both the Leahi and Denali?
I am not talking about how collisions are handled; that is handled by the CAN driver, not the FW or SW.
My point is that the CAN Channels by themselves do not have the meaning we want; they are only a priority.
As we defined them, we gave them a meaning as a category; therefore, it is better to name them the Denali/Leahi Channels rather than the CAN Channels.

RESOLVED.

· /leahi_dialin/common/dd_defs.py	(-2, +27)	| History	| Source	| Diff
· /leahi_dialin/common/dd_defs_proxy.py	(-0, +1)	| History	| Source	| Diff
· /leahi_dialin/common/msg_ids.py	(-8, +35)	| History	| Source	| Diff
· /leahi_dialin/dd/dialysate_delivery.py	(-30, +2)	| History	| Source	| Diff
· /leahi_dialin/td/treatment_delivery.py	(-10, +14)	| History	| Source	| Diff

]]> Mon, 29 Jun 2026 10:50:32 -0700 https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4072-1 https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4072-1 Michael Garthwaite finished reviewing LEAHI-DIALIN-LDT-4072-1 LEAHI-DIALIN-LDT-4072_Power Loss - FW Implementation - 2/3: ]]> Mon, 29 Jun 2026 09:28:46 -0700 Zoltan Miskolci https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4484-1/#c30193 https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4484-1/#c30193 Zoltan Miskolci replied to Behrouz NematiPour in LEAHI-DIALIN-LDT-4484-1

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 message.
When reading a CAN, there are no collisions, so there are no priorities. So I have no clue what you want here.

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, 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.

fixed

fix typo