Fixed.

Fixed.

Fixed.

When Systems gives me Leahi terms, they will be very small fractions.

Fixed.

You're right. Old comment from Denali. Fixed.

Came from Denali, so I believe this is what they wanted. The nearly 5 minutes is the one the user sees.

space needed in sizeof( BOOL ). Follow the same for line no : 526.

Please update I/O.

Add alarm.

Please add param.

just 0.0F would work?

Is it just on/off control or variable speed control?

Alarm descriptions and trigger conditions calls out "more than 4 minutes" and Instructions says, "nearly 5 minutes". is this intended to display this way?

Why?

Restore bulk of this function for now.

I am. Didn't want to wait (up to 50ms) for pump to stop if hard stop is requested. So forcing to off immediately. Not how I would ordinarily want to handle this, but in this case I am.

Why is this necessary? I would think state machine would already handle this.

· /firmware/App/Controllers/BloodFlow.c	(-0, +20)	| History	| Source	| Diff
· /firmware/App/Controllers/BloodFlow.h	(-0, +1)	| History	| Source	| Diff
· /firmware/App/Drivers/PressureSensor.c	(-0, +2)	| History	| Source	| Diff
· /firmware/App/Monitors/Buttons.c	(-2, +4)	| History	| Source	| Diff
· /firmware/App/Monitors/Pressures.c	(-0, +2)	| History	| Source	| Diff
· /firmware/App/Services/Messaging.c	(-1, +2)	| History	| Source	| Diff
· /firmware/App/TDCommon.h	(-0, +2)	| History	| Source	| Diff

]]> Thu, 12 Jun 2025 16:34:14 -0700 Sean Nash https://devapps.diality.us/changelog/td-firmware?cs=079daac611a8eb3a34c0c43392a044a882461d30 https://devapps.diality.us/changelog/td-firmware?cs=079daac611a8eb3a34c0c43392a044a882461d30 Sean Nash committed 079daac on branch LDT-1394-blood-flow-rate-h4-rotor-count, LDT-1415-pressures-monitoring-td and 44 more in td-firmware LDT-736: use off button as a stop button while stop button not implemented in CPLD.

· /firmware/App/Monitors/Buttons.c	(-0, +5)	| History	| Source	| Diff
· /firmware/App/TDCommon.h	(-2, +3)	| History	| Source	| Diff

]]> Thu, 12 Jun 2025 09:24:28 -0700 Dara Navaei https://devapps.diality.us/cru/TD-LDT-736-1 https://devapps.diality.us/cru/TD-LDT-736-1 Dara Navaei started review TD-LDT-736-1 ]]> Tue, 22 Apr 2025 10:51:27 -0700 Sean Nash https://devapps.diality.us/cru/TD-LDT-94-3 https://devapps.diality.us/cru/TD-LDT-94-3 Sean Nash Closed TD-LDT-94-3 ]]> Tue, 22 Apr 2025 10:31:05 -0700 https://devapps.diality.us/cru/TD-LDT-94-3 https://devapps.diality.us/cru/TD-LDT-94-3 Vinayakam Mani and Michael Garthwaite finished reviewing TD-LDT-94-3 TD-LDT-94_Main Treatment Screen Implement ]]> Tue, 22 Apr 2025 09:39:33 -0700 Michael Garthwaite https://devapps.diality.us/cru/TD-LDT-94-3/#c21963 https://devapps.diality.us/cru/TD-LDT-94-3/#c21963 Michael Garthwaite replied to Sean Nash in TD-LDT-94-3

RESOLVED.

RESOLVED.

These get set (lines 485 and 488) before they are used (line 491). No need to initialize before then.

OperationModes.c init function is only at power up. This call to init treatment mode is intended to re-init treatment mode before each treatment starts.

Shouldn't these bools be set to a specific value?