This file has been updated by HALCoGen automatically.

This file has been updated by HALCoGen automatically.

This file has been updated by HALCoGen automatically.

This file has been updated by HALCoGen automatically.

Done

Done

Done

Non-Dialin messages should be higher in this list than Dialin messages. Move this above all of the "test" handlers.

Remove extra copyright block.

These 2 new channels should be using message boxes before Dialin channel message boxes. Align with buffers enum.

This is auto generated code. How do we keep this code from re-appearing when somebody regenerates this code?

Same.

Same

We shouldn't delete generated code. Add a #if 0 in this user code section and add a #endif in the user section below the coreEnableFlashEcc() call.

· /firmware/App/Services/SystemCommDD.c	(-0, +2)	| History	| Source	| Diff
· /firmware/DD.dil	(-13, +13)	| History	| Source	| Diff
· /firmware/include/can.h	(-1, +1)	| History	| Source	| Diff
· /firmware/source/can.c	(-1, +39)	| History	| Source	| Diff

]]> Mon, 02 Feb 2026 11:37:31 -0800 Michael Garthwaite https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-2004-1 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-2004-1 Michael Garthwaite Closed LEAHI-DD-FIRMWARE-LDT-2004-1 ]]> Mon, 02 Feb 2026 11:01:29 -0800 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-2004-1 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-2004-1 Sean Nash finished reviewing LEAHI-DD-FIRMWARE-LDT-2004-1 LEAHI-DD-FIRMWARE-LDT-2004_Dialysate Composition - DD ]]> Mon, 02 Feb 2026 10:37:42 -0800 Michael Garthwaite https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-2004-1 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-2004-1 Michael Garthwaite started review LEAHI-DD-FIRMWARE-LDT-2004-1 ]]> Tue, 27 Jan 2026 13:02:33 -0800 Michael Garthwaite https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-2004-1/#c26766 https://devapps.diality.us/cru/LEAHI-DD-FIRMWARE-LDT-2004-1/#c26766 Michael Garthwaite replied to Sean Nash in LEAHI-DD-FIRMWARE-LDT-2004-1

fixed. Removed ifdef as well as it is no longer applies here since we are retrieving the data from the monitor which has the #ifdefs for teensy.

I think using filtered values for alarms makes sense.

we need filtered values for various applications in the system. My question is should we be checking dialysate temperature using a filtered value or a sample point? This version showed that we want a sample point.

in Denali, looks like the HD got the filtered temperature value from the DG for checking dialysate temp alarms. Are we upholding that same design of using a filtered value for leahi dialysate temp?

I don't see fix. Did you push fwcommon?

Restore this blank line.

Remove all of these blank lines please.

Removed the ifdef here as these overrides still be used without breaking the teensy driver.
I can add it on request. Unsure if teensy will be tested long enough for them to use those overrides.

In the meantime,

MSG_ID_DD_FILTERED_COND_SENSOR_READINGS_OVERRIDE_REQUEST and MSG_ID_FP_FILTERED_COND_SENSOR_READINGS_OVERRIDE_REQUEST are still available to override the monitor/filtered data.

fixed.

fixed.