Index: firmware/App/Monitors/BloodLeak.c =================================================================== diff -u -rb60474498dbccf5022f32b4f5599c5243c2b6ca9 -r655d6046109c3ea0d3edee7bbd7aad6b79765b01 --- firmware/App/Monitors/BloodLeak.c (.../BloodLeak.c) (revision b60474498dbccf5022f32b4f5599c5243c2b6ca9) +++ firmware/App/Monitors/BloodLeak.c (.../BloodLeak.c) (revision 655d6046109c3ea0d3edee7bbd7aad6b79765b01) @@ -103,7 +103,6 @@ static BOOL bloodLeakExitNormalRequested; ///< Blood leak exit normal state requested. static U32 bloodLeakRecoveryStartTimeMS; ///< Blood leak recovery start time in milliseconds. static BLOOD_LEAK_ZEROING_STATUS_T bloodLeakZeroingStatus; ///< Blood leak zeroing status. -static BOOL bloodLeakHasHardwareConfigChanged; ///< Blood leak has hardware configuration chnaged. // Embedded mode variables static BOOL bloodLeakEmbModeHasZeroBeenRqustd; ///< Blood leak embedded mode flag to indicate zero has been requested. @@ -140,7 +139,7 @@ * bloodLeakExitNormalRequested, bloodLeakEmbModeCmdSeqLength, * bloodLeakEmbModeHasRxRqstBeenSent, bloodLeakEmbModeInfoCmdEnqLastTimeStamp, * bloodLeakEmbModeInfoCmdCounter, bloodLeakRecoveryStartTimeMS, - * bloodLeakZeroingStatus, bloodLeakhasHardwareConfigChanged + * bloodLeakZeroingStatus * @return none *************************************************************************/ void initBloodLeak( void ) @@ -159,7 +158,6 @@ bloodLeakEmbModeHasZeroBeenRqustd = FALSE; bloodLeakEmbModeCmdEnqueueCount = 0; bloodLeakRecoveryStartTimeMS = getMSTimerCount(); - bloodLeakHasHardwareConfigChanged = FALSE; bloodLeakZeroingStatus.zeroingDriftIntervalTimeMS.data = BLD_ZERO_MIN_INTERVAL_MS; bloodLeakZeroingStatus.zeroingDriftIntervalTimeMS.ovInitData = BLD_ZERO_MIN_INTERVAL_MS; @@ -191,16 +189,6 @@ processBloodLeakIntensityData(); - if ( ( TRUE == getTestConfigStatus( TEST_CONFIG_DD_FP_ENABLE_BETA_2_0_HW ) ) && ( FALSE == bloodLeakHasHardwareConfigChanged ) ) - { - // If the hardware test configuration has changed, initialize the blood leak driver and start over from the check set point - // because the FPGA registers have changed. - // NOTE: this should be more generic in case other hardware configurations are created. - initBloodLeakDriver(); - bloodLeakState = BLOOD_LEAK_CHECK_SET_POINT_STATE; - bloodLeakHasHardwareConfigChanged = TRUE; - } - switch( bloodLeakState ) { case BLOOD_LEAK_WAIT_FOR_POST_STATE: