common

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-6402: Added new alarm for no cartridge loaded

When we run blood pump in forward direction, we should see negative on arterial and positive on venous. This limit here is to stop blood pump even if the time to run the blood has not been reached.

When we run blood pump in forward direction, we should see negative on arterial and positive on venous.
This limit here is to stop blood pump even if the time to run the blood has not been reached.

Done. Also moved the function to FPGA module.

Done. Also moved the function to FPGA module.

Done.

Done.

Done.

Done.

Reworded.

Reworded.

Renamed.

Renamed.

If the sensor is bad, we will go to fault. In this case, the calibration does not matter anymore.

If the sensor is bad, we will go to fault. In this case, the calibration does not matter anymore.

Agree. All multi-lines state have been moved to a static function.

Agree. All multi-lines state have been moved to a static function.

Done.

Done.

Done. It is a tolerance on pressure difference after we return back to normal state from pressure self-tests.

Done. It is a tolerance on pressure difference after we return back to normal state from pressure self-tests.

Done. This is not a self-test for blood pump occlusion sensor (OB). This is for PBa and PBo pressure sensors.

Done. This is not a self-test for blood pump occlusion sensor (OB). This is for PBa and PBo pressure sensors.

Done.

Done.

Done.

Done.

Merge branch 'Sprint37' into develop

Fixed comment typo.

Fixed comment alignment.

DG-DEN-5980_Non Volatile Data Management (2 of 2)
DG-DEN-5980_Non Volatile Data Management (2 of 2)
Fair point.

Fair point.

Consider returning a OPN_CLS_STATE_T instead of BOOL for readability.

Consider returning a OPN_CLS_STATE_T instead of BOOL for readability.

What is this state? Where did it get set? Why aren't we going back to recirc state?

What is this state? Where did it get set? Why aren't we going back to recirc state?

Can this wait for door close be a state within the self-test no cartridge sub-mode? Also need to wait for user to open the door at the end of self-test no cartridge sub-mode or beginning of cartrid...

Can this wait for door close be a state within the self-test no cartridge sub-mode? Also need to wait for user to open the door at the end of self-test no cartridge sub-mode or beginning of cartridge install sub-mode and then close the door again at end of cartridge install sub-mode. I see that some of these sub-modes don't have states, but probably should or will eventually. The 3 self-test sub-modes can have their own state machines in SelfTests.c. I think Recirc and Cartridge Install sub-modes may need their own .c files (PreTreatmentRecirc.c and DisposableInstall.c?) with state machines of their own as well.

Move execPrime() to end - only if no door open and no alarm stop signal.

Move execPrime() to end - only if no door open and no alarm stop signal.

Check for door open before running self-tests. Really, self-test execution should go last and only if no door open and no stop signal.

Check for door open before running self-tests. Really, self-test execution should go last and only if no door open and no stop signal.

For no cartridge self-tests, all failures result in a fault because they are essentially POST tests.

For no cartridge self-tests, all failures result in a fault because they are essentially POST tests.

Are these the only two alarms possible in this state? Consider using the alarm stop signal here instead of checking specific alarm status.

Are these the only two alarms possible in this state? Consider using the alarm stop signal here instead of checking specific alarm status.

And if we fail self-tests? Where do we go? Are all failures a fault?

And if we fail self-tests? Where do we go? Are all failures a fault?

Should we check door before we run the self tests?

Should we check door before we run the self tests?

I think there are a few things that need to happen in patient connection sub-mode (e.g. get UF volume, get initial blood pressure reading, ...) before user should be allowed to start treatment. Nee...

I think there are a few things that need to happen in patient connection sub-mode (e.g. get UF volume, get initial blood pressure reading, ...) before user should be allowed to start treatment. Need to check which state in patient connection sub-mode we're in too - should the last state where we've done everything and waiting for user to start.

What is happening in this sub-mode that can be resumed?

What is happening in this sub-mode that can be resumed?