· /AlarmMgmt.c	(-2, +2)	| History	| Source	| Diff
· /AlarmMgmt.h	(-2, +2)	| History	| Source	| Diff
· /MessagePayloads.h	(-2, +2)	| History	| Source	| Diff

]]> Fri, 05 Jun 2026 10:08:02 -0700 https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4013-1 https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4013-1 Sean Nash finished reviewing LEAHI-TD-FIRMWARE-LDT-4013-1 LEAHI-TD-FIRMWARE-LDT-4013_Fluid Bolus - FW Implementation - 2/4: ]]> Thu, 04 Jun 2026 09:52:42 -0700 https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4013-1 https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4013-1 Vendor - TEL - Jashwant Gantyada finished reviewing LEAHI-TD-FIRMWARE-LDT-4013-1 LEAHI-TD-FIRMWARE-LDT-4013_Fluid Bolus - FW Implementation - 2/4: ]]> Thu, 04 Jun 2026 09:00:19 -0700 Sean Nash https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4013-1/#c29616 https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4013-1/#c29616 Sean Nash commented on LEAHI-TD-FIRMWARE-LDT-4013-1

Should this check be moved to the fluid bolus exec function?

]]> Wed, 03 Jun 2026 12:29:38 -0700 https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4013-1 https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4013-1 Vinayakam Mani resumed reviewing LEAHI-TD-FIRMWARE-LDT-4013-1 LEAHI-TD-FIRMWARE-LDT-4013_Fluid Bolus - FW Implementation - 2/4: ]]> Wed, 03 Jun 2026 09:49:33 -0700 Sean Nash https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-2240-1/#c29613 https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-2240-1/#c29613 Sean Nash commented on LEAHI-TD-FIRMWARE-LDT-2240-1

It looks like you have this as a T/F response from UI. UI should not be determining whether the modality matches - that's our job. UI should be telling us which type of tubing set was installed (HD or HDF type). Then when we get this response msg from UI, we will compare the type to the user selected modality (from TxParams) to see if it matches.

Add doxygen comments to the right of each structure field.

Why is this commented out? We will get stuck in this state if we don't move on to the pressure leak test states.

For now, we need to set authResponseReceived and authResponseValidTubingSet and authResponseModalityAccepted to TRUE until UI is properly responding to authentication request (TODO).

For now, we need to set barcodeScanResponseReceived to TRUE here until barcode scan command is implemented.

Add blank line before return statement.

Keep this blank line above group header.

Something is wrong here. We already had reg 33 at line 192 above. Reconcile with HDD.

· /PIControllers.c	(-2, +2)	| History	| Source	| Diff
· /PIControllers.h	(-1, +1)	| History	| Source	| Diff

]]> Mon, 01 Jun 2026 17:35:01 -0700 Vinayakam Mani https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3958-1 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3958-1 Vinayakam Mani Closed LEAHI-DD-FIRMWARE-LDT-3958-1 ]]> Mon, 01 Jun 2026 17:27:27 -0700 Vinayakam Mani https://devapps.diality.us/changelog/leahi-fwcommon?cs=6718b99feb73a7b947e069de0e0ad3250ede0ea8 https://devapps.diality.us/changelog/leahi-fwcommon?cs=6718b99feb73a7b947e069de0e0ad3250ede0ea8 Vinayakam Mani committed 6718b99 on branch LDT-3223-dialysate-flow-rate---dd---mode-6-5-2026, LDT-4001-hdf-fw-implementation-2-4 and 5 more in leahi-fwcommon LDT-3958 merge into staging

]]> Mon, 01 Jun 2026 17:18:47 -0700 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3958-1 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-3958-1 Sean Nash and Vendor - TEL - Jashwant Gantyada finished reviewing LEAHI-DD-FIRMWARE-LDT-3958-1 LEAHI-DD-FIRMWARE-LDT-3958_Dialysate Temperature - FW Implementation - 2/2: ]]> Mon, 01 Jun 2026 16:34:08 -0700 Vinayakam Mani https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4009-1/#c29592 https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4009-1/#c29592 Vinayakam Mani commented on LEAHI-TD-FIRMWARE-LDT-4009-1

Maintain alphabetical order.

Eliza says we do allow multiple iso UF sessions in a treatment. So do we still need this else if, but looking at <= iso UF elapsed session time?

Done.

Done.

What about HDF?

Once UI software sends the volume and/or duration change request and once we change them, the UI software will send another request to confirm the displayed settings to the user and that is what is being handled in this function.

return result;

Keep local result and set to TRUE or FALSE with a ternary.

Which setting does this message confirm (duration or volume)?

Update alarms and Input/Output sections.

Also, add option individual parameter override for substitutions pump rate as well.

Space after parenthesis. Please add the same in else portion as well (when treatment is in progress, update the rate).