Controllers

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-7395: Addressed init state of state machine for Blood Leak Detector

I don't think we should have state as overrideable. Here, you are only looking at non-override version of state, so override would not have any impact anyway. You could have Dialin function force a...

I don't think we should have state as overrideable. Here, you are only looking at non-override version of state, so override would not have any impact anyway.
You could have Dialin function force a transition to a given state - I think that would be useful from testing perspective. But transition would need to be more than just setting state - e.g. we would need to put sensor in zero state via FPGA if we wanted to go to the zero state in your state machine.

But do we want to jump right into zero state or wait for pre-treatment to ask for it? Does zero require fluid (dialysate) to be in the line?

But do we want to jump right into zero state or wait for pre-treatment to ask for it? Does zero require fluid (dialysate) to be in the line?

Yes, Sean and I thought that it would be good for the SWVV, SYSVV, MFR, and SVC Teams to know via Dialin API which state the Blood Leak state machine is in. This detector comes with an independent ...

Yes, Sean and I thought that it would be good for the SWVV, SYSVV, MFR, and SVC Teams to know via Dialin API which state the Blood Leak state machine is in. This detector comes with an independent MCU thqat can be programmed and calibrated via UART and via HD FPGA including self-test mode and zeroing mode to zero the sensor when clear dialysate is run through it. Then a threshold of blood can be set to be detected as soon as blood gets across the dialyzer from the blood circuit to the dialysate circuit.

Good catch, addressed.

Good catch, addressed.

Good catch, addressed.

Good catch, addressed.

Good catch, addressed.

Good catch, addressed.

Addressed.

Addressed.

DEN-7395: Addressed execBloodLeak header clarification needed

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

  1. … 1 more file in changeset.
Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

Addressed.

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

  1. … 3 more files in changeset.
DEN-7605: Syringe pump driver changes per lab testing w/ Mike.

  1. … 1 more file in changeset.
Minor fixes to syringe pump - will add changes to DEN-7605.

  1. … 1 more file in changeset.