td-firmware / firmware / App / Controllers

BloodFlow.c

Clone Tools

Stats

Commits this week: 0
Total Committers: 5
Last Commit: 12 Mar
Commits this week: 0

Lines of code count not available

Commit Activity

Commits By Day In Week
52 week commits volume
Commits By Day In Week
Commits by day
Commits By Day In Week
Commits by hour
Commits By Hour In Day
Commit calendar
 

Most active committers (90 days)

loading
loading
  • last updated a few seconds ago
All Commits Reviews
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Tuesday 10 Mar
3:21 pm

Sean Nash

If we don't think we need this, let's just delete it. If we think it's coming back, let's keep it and just set the max count to something really high (e.g. 1,000,000).

If we don't think we need this, let's just delete it. If we think it's coming back, let's keep it and just set the max count to something really high (e.g. 1,000,000).

Monday 02 Mar
4:16 pm

Sean Nash

2:13 pm

Vendor - TEL - Jashwant Gantyada

done.

done.

1:58 pm

Sean Nash

Update I/O section here to include rotor revs accumulated and previous.

Update I/O section here to include rotor revs accumulated and previous.

1:32 pm

Vendor - TEL - Jashwant Gantyada

handled accordingly.

handled accordingly.

1:32 pm

Vendor - TEL - Jashwant Gantyada

removed and added.

removed and added.

11:16 am

Sean Nash

Converting U16 to U32. Presumably, U16 will wrap back to zero when it gets to 65535. We don't want our U32 to wrap, so we need to do something to handle this conversion properly.

Converting U16 to U32. Presumably, U16 will wrap back to zero when it gets to 65535. We don't want our U32 to wrap, so we need to do something to handle this conversion properly.

10:42 am

Sean Nash

I think this whole function should be moved to the PeristalticPump.c driver unit. We don't want controller/monitor level units directly accessing fpga registers - the drivers should be doing that.

I think this whole function should be moved to the PeristalticPump.c driver unit. We don't want controller/monitor level units directly accessing fpga registers - the drivers should be doing that.

9:02 am

Dara Navaei

LEAHI-TD-FIRMWARE-LDT-1394_Blood Flow Rate - TD - 04: DEV - Feature Implementation
LEAHI-TD-FIRMWARE-LDT-1394_Blood Flow Rate - TD - 04: DEV - Feature Implementation
Tuesday 03 Feb
1:02 pm

Vendor - TEL - Varshini Nagabooshanam

Wednesday 28 Jan
12:30 pm

Raghu Kallala , Sean Nash and Vendor - TEL - Jashwant Gantyada

10:18 am

Raghu Kallala

LEAHI-TD-FIRMWARE-LDT-473_Treatment Parameters (Create Rx) - TD - 04: DEV - Feature Implementation
LEAHI-TD-FIRMWARE-LDT-473_Treatment Parameters (Create Rx) - TD - 04: DEV - Feature Implementation
Tuesday 16 Dec 2025
2:08 pm

Vendor - TEL - Varshini Nagabooshanam

Updated.

Updated.

2:07 pm

Vendor - TEL - Varshini Nagabooshanam

Yes, we need to

Yes, we need to

2:07 pm

Vendor - TEL - Varshini Nagabooshanam

Deleted.

Deleted.

1:44 pm

Sean Nash

Does OperationModes.c need to include TxParams.h? TxParams is not a mode.

Does OperationModes.c need to include TxParams.h? TxParams is not a mode.

1:43 pm

Sean Nash

I think we should initialize pre-treatment mode here now that we have a pre-treatment mode.

I think we should initialize pre-treatment mode here now that we have a pre-treatment mode.

1:36 pm

Sean Nash

Should we request pre-treatment mode here instead? How do we get to pre-treatment mode?

Should we request pre-treatment mode here instead? How do we get to pre-treatment mode?

1:32 pm

Vendor - TEL - Varshini Nagabooshanam

Yes, I deleted.

Yes, I deleted.

1:31 pm

Vendor - TEL - Varshini Nagabooshanam

Deleted.

Deleted.

1:31 pm

Vendor - TEL - Varshini Nagabooshanam

Removed

Removed

1:31 pm

Vendor - TEL - Varshini Nagabooshanam

Deleted.

Deleted.

10:21 am

Sean Nash

Remove extra blank line.

Remove extra blank line.

10:15 am

Sean Nash

MODE_TPAR should be deleted.

MODE_TPAR should be deleted.

10:14 am

Sean Nash

It should no longer be called from OperationModes.c because we are deleted the TxParams mode (delete from enum and any switch statements in OperationModes.c).

It should no longer be called from OperationModes.c because we are deleted the TxParams mode (delete from enum and any switch statements in OperationModes.c).

10:13 am

Sean Nash

ModeTxParams.c/.h are still not deleted. I want you to delete them and commit/push that change. Then I will see both files in RED here in this CR.

ModeTxParams.c/.h are still not deleted. I want you to delete them and commit/push that change. Then I will see both files in RED here in this CR.

Monday 15 Dec 2025
5:00 pm

Vendor - TEL - Varshini Nagabooshanam

Thanks for the clarification. This handler already follows the single-parameter MESSAGE_T *message pattern, and the message ID is already defined and registered in Messaging.c. I’ll keep using the ...

Thanks for the clarification. This handler already follows the single-parameter MESSAGE_T *message pattern, and the message ID is already defined and registered in Messaging.c. I’ll keep using the existing ID, ensure payload length is validated, and parse the param/value from the payload as expected.

4:59 pm

Vendor - TEL - Varshini Nagabooshanam

Yes, this is called in OperationModes.c

Yes, this is called in OperationModes.c

4:58 pm

Vendor - TEL - Varshini Nagabooshanam

Sure.

Sure.

4:58 pm

Vendor - TEL - Varshini Nagabooshanam

Added.

Added.