StateTxDialysis.c

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
We can set bolus volume here now. These functions should be moved to TxParams where all of these settings exist and can be updated.

We can set bolus volume here now. These functions should be moved to TxParams where all of these settings exist and can be updated.

Why does confirm msg have duration again? If UI resends duration, we have to validate it again. If UI just sends confirmation of previously sent duration, we don't have to validate it again.

Why does confirm msg have duration again? If UI resends duration, we have to validate it again. If UI just sends confirmation of previously sent duration, we don't have to validate it again.

These are already in TxParams I believe.

These are already in TxParams I believe.

Should these be moved to Services\TxParams?

Should these be moved to Services\TxParams?

Change 1 to TRUE

Change 1 to TRUE

Agree with name change, but I think BOOL was the correct type. And BOOL is equivalent to U32 anyway so compiler won't care.

Agree with name change, but I think BOOL was the correct type. And BOOL is equivalent to U32 anyway so compiler won't care.

I think these message handlers for editing treatment parameters should be moved to Services\TxParams.

I think these message handlers for editing treatment parameters should be moved to Services\TxParams.

These should probably be moved to Services\TxParams.h because Messaging.c does not use them.

These should probably be moved to Services\TxParams.h because Messaging.c does not use them.

See if we have already defined this stuff in Services\TxParams. TxParams may also have get function(s) for min/max values that you can use.

See if we have already defined this stuff in Services\TxParams. TxParams may also have get function(s) for min/max values that you can use.

Added to be consistent. Once institutional records are implemented will store it in there instead of a macro

Added to be consistent. Once institutional records are implemented will store it in there instead of a macro

LEAHI-TD-FIRMWARE-LDT-3970_Edit Treatment Parameters During Treatment - FW Implementation - 1/4:
LEAHI-TD-FIRMWARE-LDT-3970_Edit Treatment Parameters During Treatment - FW Implementation - 1/4:
DO we need bicarb conversion factor as well?

DO we need bicarb conversion factor as well?

preweight can be non-zero

preweight can be non-zero

Add blank line after declarations.

Add blank line after declarations.

From what I see in UI, it is just a range value not an enum/index

From what I see in UI, it is just a range value not an enum/index

Is it an enum/index like Denali then?

Is it an enum/index like Denali then?

No we are not getting conv factor from UI on it I will have to confirm with Nick to see if we will get the bicarbConvFactor

No we are not getting conv factor from UI on it
I will have to confirm with Nick to see if we will get the bicarbConvFactor

Align comments.

Align comments.

Can we just remove this?

Can we just remove this?

Can we just remove this?

Can we just remove this?

F suffix.

F suffix.

Is bicarbonate also a conversion factor?

Is bicarbonate also a conversion factor?

Can we just remove the old enum now?

Can we just remove the old enum now?

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
Updated

Updated

Updated

Updated