Index: firmware/App/Services/WatchdogMgmt.c =================================================================== diff -u -r48fa4e359dee8dae08067a7642ea3a8a526949d5 -re5e7a37f5f1e2942630f748be23eac9f452af3aa --- firmware/App/Services/WatchdogMgmt.c (.../WatchdogMgmt.c) (revision 48fa4e359dee8dae08067a7642ea3a8a526949d5) +++ firmware/App/Services/WatchdogMgmt.c (.../WatchdogMgmt.c) (revision e5e7a37f5f1e2942630f748be23eac9f452af3aa) @@ -161,7 +161,7 @@ switch ( watchdogSelfTestState ) { case WATCHDOG_SELF_TEST_STATE_START: - watchdogSelfTestState = WATCHDOG_SELF_TEST_STATE_IN_PROGRESS; + watchdogSelfTestState = WATCHDOG_SELF_TEST_STATE_IN_PROGRESS; watchdogSelfTestTimerCount = getMSTimerCount(); // no break here so we pass through directly to in progress processing @@ -176,7 +176,7 @@ F32 isolatedV24 = getMonitoredLineLevel( MONITORED_LINE_24V_POWER_PRIM_HTR_V ); // Verify 24V is down when w.d. expired - if ( ( v24 > MAX_24V_LEVEL_ON_WATCHDOG_EXPIRED ) || ( isolatedV24 > MAX_ISOLATED_24V_LEVEL_ON_WD_EXPIRED ) ) + if ( v24 > MAX_24V_LEVEL_ON_WATCHDOG_EXPIRED ) { SET_ALARM_WITH_2_F32_DATA( ALARM_ID_DG_WATCHDOG_POST_TEST_FAILED, 2.0F, v24 ); watchdogSelfTestStatus = SELF_TEST_STATUS_FAILED; @@ -188,7 +188,7 @@ watchdogSelfTestStatus = SELF_TEST_STATUS_FAILED; } watchdogSelfTestTimerCount = getMSTimerCount(); - watchdogSelfTestState = WATCHDOG_SELF_TEST_STATE_RECOVER; + watchdogSelfTestState = WATCHDOG_SELF_TEST_STATE_RECOVER; break; case WATCHDOG_SELF_TEST_STATE_RECOVER: @@ -201,7 +201,7 @@ // Verify 24V is down when w.d. recovered TODO - If issue persisted // ask EE team why 24V does not quite recover all the way to 22.6V even after 750 ms. How long should it take? - if ( ( v24 < MIN_24V_LEVEL_ON_WATCHDOG_RECOVER ) || ( isolatedV24 < MIN_24V_LEVEL_ON_WATCHDOG_RECOVER ) ) + if ( v24 < MIN_24V_LEVEL_ON_WATCHDOG_RECOVER ) { SET_ALARM_WITH_2_F32_DATA( ALARM_ID_DG_WATCHDOG_POST_TEST_FAILED, 3.0F, v24 ); watchdogSelfTestStatus = SELF_TEST_STATUS_FAILED;