· /leahi_dialin/dd/modules/records.py

(-7, +0)

| History

| Source

| Diff

]]> 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/dd/modules/records.py

(-6, +282)

| History

| Source

| Diff

]]> Wed, 01 Jul 2026 15:17:25 -0700 Dara Navaei https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4614-1 https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4614-1 Dara Navaei started review LEAHI-DIALIN-LDT-4614-1 ]]> 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

fixed. thanks!

fixed. thanks

Add uncompensated conductivity to the init too

Add uncompensated conductivity to the init too

· /leahi_dialin/common/generic_defs.py	(-1, +1)	| History	| Source	| Diff
· /leahi_dialin/dd/modules/records.py	(-11, +15)	| History	| Source	| Diff

]]> Wed, 01 Jul 2026 12:33:22 -0700 Behrouz NematiPour https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4484-1/#c30308 https://devapps.diality.us/cru/LEAHI-DIALIN-LDT-4484-1/#c30308 Behrouz NematiPour replied to Behrouz NematiPour in LEAHI-DIALIN-LDT-4484-1

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.