Late breaking news, the HD_PRE_TREATMENT_PRIME_STATE_T has changed. The correct order of the items in enum type of the pre-treatment states are listed below:
HD_PRIME_START_STATE = 0, ///< Prime start state HD_PRIME_WAIT_FOR_USER_START_STATE, ///< Wait for user to start prime state HD_PRIME_SALINE_SETUP_STATE, ///< Saline setup state HD_PRIME_SALINE_PURGE_AIR_STATE, ///< Saline purge air state HD_PRIME_SALINE_CIRC_BLOOD_CIRCUIT_STATE, ///< Circulate blood circuit state HD_PRIME_RESERVOIR_ONE_FILL_COMPLETE_STATE, ///< Wait for reservoir 1 fill complete HD_PRIME_DIALYSATE_DIALYZER_STATE, ///< Dialysate dialyzer fluid path state HD_PRIME_SALINE_DIALYZER_SETUP_STATE, ///< Saline dialyzer setup state HD_PRIME_SALINE_DIALYZER_STATE, ///< Saline dialyzer fluid path state HD_PRIME_RESERVOIR_TWO_FILL_COMPLETE_STATE, ///< Wait for reservoir 2 fill complete HD_PRIME_DIALYSATE_BYPASS_STATE, ///< Dialysate bypass fluid path state HD_PRIME_WET_SELF_TESTS_STATE, ///< Perform wet self-tests after priming complete HD_PRIME_PAUSE, ///< Prime pause state, waits to be resumed HD_PRIME_COMPLETE, ///< Prime complete state NUM_OF_HD_PRIME_STATES ///< Number of prime sub-mode states
These are no definitions of these class inside alarm_defs.py yet. I think this means PRS definitions rather than pressure. Behrouz NematiPour Should these definitions be moved to another file?
Why there is a endSampleWaterRequest in this state? We should never get here if sample water request is in place. Also, if this an endSampleWaterRequest here, VSP should be closed.
Aren't these alarm enums duplicates of the ones in alarm_defs.py? Also, file name suggests these are pressure related definitions - so why are alarm definitions in here?
Yes that is true. One is specifically looking at the HD software config and the other is checking the DG software config. I can have one function that covers both but it has to have #ifdef for for HD and DG.
