firmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-7395: Corrected state machine BLOOD_LEAK_INIT_STATE case

Addressed.

Addressed.

Maybe I do not quite understand the architecture, but is there any reason that your are returning the state of the blood leak detector state machine?

Maybe I do not quite understand the architecture, but is there any reason that your are returning the state of the blood leak detector state machine?

I suppose this is not the monitor function and it is the exec function?

I suppose this is not the monitor function and it is the exec function?

I think it is a good practice to reset all the important variables that are defined as static in the .c file.

I think it is a good practice to reset all the important variables that are defined as static in the .c file.

The states of the state machine should be private. This enum should be transferred to the .c file.

The states of the state machine should be private. This enum should be transferred to the .c file.

A break is needed here.

A break is needed here.

A break is needed here.

A break is needed here.

A break is needed here.

A break is needed here.

I imagine this state should look for self-test to pass (indicate a blood leak) within some time period and then we would tell FPGA to put sensor in normal state and set your state machine to normal...

I imagine this state should look for self-test to pass (indicate a blood leak) within some time period and then we would tell FPGA to put sensor in normal state and set your state machine to normal state. Fault if times out.

I imagine this state would need to look for zero to complete within some time period so we can tell FPGA to put sensor in self-test mode and set your state machine to self-test state. Fault if time...

I imagine this state would need to look for zero to complete within some time period so we can tell FPGA to put sensor in self-test mode and set your state machine to self-test state. Fault if times out.

Where did zeroBloodLeak() and selfTestBloodLeak() functions go? You have prototypes for them in .h and I think you still need at least one of them. zeroBloodLeak would be called by Pre-Treatment Mo...

Where did zeroBloodLeak() and selfTestBloodLeak() functions go? You have prototypes for them in .h and I think you still need at least one of them. zeroBloodLeak would be called by Pre-Treatment Mode and would tell FPGA to put sensor in zero state and would also put your state machine in zero state.

initBloodLeak() was already called from main in sys_main.c. I don't think we need to keep calling it here. How do we get out of INIT state?

initBloodLeak() was already called from main in sys_main.c. I don't think we need to keep calling it here.
How do we get out of INIT state?

Addressed.

Addressed.

DEN-7395: Implemented state machine architecture for Blood Leak Detector driver

DEN-7395: Added execBloodLeak() call to TaskPriority.c

Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

DEN-7395: Reverted lumping of override functions for Blood Leak Detector status and state

    • -5
    • +37
    ./App/Services/SystemCommMessages.c
DEN-7605: Syringe pump driver changes per lab testing w/ Mike.

Minor fixes to syringe pump - will add changes to DEN-7605.

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

DEN-7605: Added no minimize flag to alarm status message to UI.

There is only one state in this override message. It can be status or state (depending on message ID), but not both. Whichever it is, you are passing it to a function twice as if it is two differen...

There is only one state in this override message. It can be status or state (depending on message ID), but not both. Whichever it is, you are passing it to a function twice as if it is two different things. You need to revert back to having two override messages and two message handlers - one for status and one for state.

So you combined the published data into one message in the publish function above which is correct. But these overrides must be separate. You should only override one thing at a time, so overrides ...

So you combined the published data into one message in the publish function above which is correct. But these overrides must be separate. You should only override one thing at a time, so overrides were ok as it was before.

Need to add call to this function from task priority.

Need to add call to this function from task priority.

DEN-7605: Fixes per verification testing.

lab testing fixes - will add to DEN-7605 dev branch.

DEN-7395: Removed Detector from names of functions