Raghu Kallala

LEAHI-DD-FIRMWARE-LDT-4188_SW/FW integration to run a Treatment from UI
LEAHI-DD-FIRMWARE-LDT-4188_SW/FW integration to run a Treatment from UI
Updated to ml/min, except for broadcast in treatment mode

Updated to ml/min, except for broadcast in treatment mode

Changed to U32

Changed to U32

we are sending a message ack as response in the handler of this message request

we are sending a message ack as response in the handler of this message request

Other existing set functions in TD is using UF in liter and rate in L/hr Shall I change all of them? Which might impact how systems is sending this info(L/hr or ml/min) in their scripts

Other existing set functions in TD is using UF in liter and rate in L/hr

Shall I change all of them? Which might impact how systems is sending this info(L/hr or ml/min) in their scripts

To resolve the build failure with DD, haven't added all the features, instead added TODO comment

To resolve the build failure with DD, haven't added all the features, instead added TODO comment

Idea is to have this in institutional records we implement it

Idea is to have this in institutional records we implement it

This should be LAST_DD_LEVL not NUM_OF_LEVELS if DD and FP levels are in same enum

This should be LAST_DD_LEVL not NUM_OF_LEVELS if DD and FP levels are in same enum

LEVEL_OFFSET?

LEVEL_OFFSET?

Updated

Updated

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

COMM_BUFFER_OUT_CAN_FP_BROADCAST sendEvent check the event ID. if it is an FP event, FP event will be sent on COMM_BUFFER_OUT_CAN_FP_BROADCAST

COMM_BUFFER_OUT_CAN_FP_BROADCAST

sendEvent check the event ID. if it is an FP event, FP event will be sent on COMM_BUFFER_OUT_CAN_FP_BROADCAST

You are right, modified in all places

You are right, modified in all places