LEMON Manuals: Even more car manuals for everyone
Home >> Ford >> 1996 >> Aerostar Van Window >> Repair and Diagnosis >> Brakes >> Traction Control >> Anti-Lock Brake System - Rear >> Diagnosis >> Intermittent Diagnosis

Intermittent Diagnosis

  1. Reinstall any components previously removed. Reconnect any connectors previously disconnected. Clear all codes. See CLEARING CODES  . Turn ignition on. If Yellow REAR ABS light does not self-check or stays on, go next step. If Yellow REAR ABS light does self-check, go step 3).
  2. Check all component connectors for bent terminals, damaged connector terminal locks or damaged connector wedge. Repair as necessary. If any of these conditions are found, check affected circuit wire length. If length is short, repair as necessary to prevent problem from recurring.
  3. Ensure ignition is on. Observe Yellow ABS light. Starting at one component, wiggle connector by connector until whole circuit has been tested. If Yellow light does not illuminate, go to next step. If Yellow light illuminates, repair wire terminal or connector as necessary. After repairs, go to step 5).
  4. If a trouble code is being serviced, perform step  3 on all circuits affected. If all affected circuits have been tested, go to step  6 .
  5. Retrieve trouble codes. See RETRIEVING TROUBLE CODES  . If code is different than one being serviced, go to appropriate code under TROUBLE CODE DIAGNOSIS  . If code is not different than one being serviced, repair wire, terminal or connector as necessary and go to step 7).
  6. Verify all appropriate diagnostic procedures have been preformed. If system PRELIMINARY CHECK TESTS  have been completed and a code received, and all tests for that code under TROUBLE CODE DIAGNOSIS  have been performed, repeat appropriate code under TROUBLE CODE DIAGNOSIS. If PRELIMINARY CHECK TESTS or test for corresponding code have not been completed, return to procedure not yet performed.
  7. Clear all codes. See CLEARING CODES  . Turn ignition off. Retrieve trouble codes. See RETRIEVING TROUBLE CODES  . If CODE 16 is present, problem has been corrected. If previous code still exists, go to step 4). If a different code is present, go to corresponding test under TROUBLE CODE DIAGNOSIS  .
scientia non olet · About LEMON Manuals