hdfirmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-8103: Removed Heparin concentration in treatment log

Are we adding an alarm here later?

Are we adding an alarm here later?

It looks like you have not added these functions to SystemComm.c. They need to be added there otherwise the commands will not be handled.

It looks like you have not added these functions to SystemComm.c. They need to be added there otherwise the commands will not be handled.

Merge branch 'DEN-8103-dg-hd_dev-alarm-design' into develop

Updated HDCommon.h

Merge branch 'develop' of ssh://dvm-linux02:7999/hd/hdfirmware into develop

Merge branch 'DEN-8030-dg-hd_dev-dg-mode-chemical-disinfect' into develop

DEN-8030 fixed fluid leak detector in systemcommmessages.c

Merge branch 'DEN-7605-hd_dg_dev-self-tests' into develop

DEN-7605: added build switch for flow sensor status check.

    • -0
    • +2
    /firmware/App/Controllers/DialInFlow.c
Fixed merge conflicts.

DEN-7605: Added check for syringe pump stall w/ retries.

    • -11
    • +59
    /firmware/App/Controllers/SyringePump.c
DEN-7860: Addressed part of code review comments

    • -20
    • +23
    /firmware/App/Controllers/Bubble.c
I think this makes sense. We've done the same in other monitors/controllers like valves where there are several similar components handled in same driver.

I think this makes sense. We've done the same in other monitors/controllers like valves where there are several similar components handled in same driver.

Maybe cast the status params as U32 as well so there won't be an issue within the broadcast function (see my comment there for context).

Maybe cast the status params as U32 as well so there won't be an issue within the broadcast function (see my comment there for context).

For blood leak sensor, we didn't want to go to normal state until it was zeroed and self-tested. For bubble detector, do we want to be stuck in init state until self-test is requested? I think if w...

For blood leak sensor, we didn't want to go to normal state until it was zeroed and self-tested. For bubble detector, do we want to be stuck in init state until self-test is requested?
I think if we keep this state machine as is, we will want to request self-test in POST so that we can move on to normal state quickly. Then still request another self-test in each pre-treatment as we are now doing.

Should we broadcast both bubble detectors' data in one message?

Should we broadcast both bubble detectors' data in one message?

Same. Validate bubble param at top of function before using it. Then no need for else below.

Same. Validate bubble param at top of function before using it. Then no need for else below.

Should validate bubble param up top before you use it. S/W fault if invalid. Then don't need the else below.

Should validate bubble param up top before you use it. S/W fault if invalid. Then don't need the else below.

Initialize the other 3 fields of the override structure.

Initialize the other 3 fields of the override structure.

I agree we want to send the two status enums as a U32 over the CAN. I think it's better to assign w/ cast the two status to local U32s before memcpy into payload. That way, memcpy is given 4 bytes ...

I agree we want to send the two status enums as a U32 over the CAN. I think it's better to assign w/ cast the two status to local U32s before memcpy into payload. That way, memcpy is given 4 bytes to copy. As is, I worry compiler will only have 1 or 2 bytes for the enum passed into the function and we're forcing memcpy to copy 4 bytes - could corrupt the upper bytes of the two status fields in the message payload.

Code below looks like this message is expected to have a payload of type OVERRIDE_PUMP_SET_PT_PAYLOAD_T. Not sure why a bubble test request would have a pump type payload, maybe it had what you nee...

Code below looks like this message is expected to have a payload of type OVERRIDE_PUMP_SET_PT_PAYLOAD_T. Not sure why a bubble test request would have a pump type payload, maybe it had what you needed (an index). But this structure will have a length larger than 0. Should be "if ( sizeof( OVERRIDE_PUMP_SET_PT_PAYLOAD_T ) == message->hdr.payloadLen ).

I think it's worth checking that the self-test mode was entered as expected.

I think it's worth checking that the self-test mode was entered as expected.

Same comment as above.

Same comment as above.

No return value for this function.

No return value for this function.

Looks like fpgaActuatorSetPoints is an output and no inputs.

Looks like fpgaActuatorSetPoints is an output and no inputs.

This should be a s/w fault.

This should be a s/w fault.

Agreed. This is for me to add a check for this error. Will remove comment when I'm done.

Agreed. This is for me to add a check for this error. Will remove comment when I'm done.

Is this still an issue?

Is this still an issue?

Agreed. This is for me to add a check for this error. I'll remove comment when I'm done.

Agreed. This is for me to add a check for this error. I'll remove comment when I'm done.