Inspection and Verification: Notes
WARNING: This page is about a different car, the 2003 Mercury Mountaineer and 2003 Ford Explorer. However, it is still accessible from the selected car via links, so may be relevant.
- Verify the customer concern by operating the system.
- Visually inspect for obvious signs of mechanical or electrical damage.
- If an obvious cause for an observed or reported concern is found, correct the cause (if possible) before proceeding to the next step.
- If the cause is not visually evident, connect the diagnostic tool to the data link connector and select the vehicle to be tested from the diagnostic tool menu. If the diagnostic tool does not communicate with the vehicle:
- check that the program card is correctly installed.
- check the connections to the vehicle.
- check the key switch position.
- If the diagnostic tool still does not communicate with the vehicle, refer to the Diagnostic tool operating manual.
- Carry out the diagnostic tool data link test. If the diagnostic tool responds with:
- SCP+, SCP-, ISO or UBP circuit fault; all electronic control units no response/not equipped, refer to MODULE COMMUNICATIONS NETWORK .
- No response/not equipped for vehicle security module, refer to MODULE COMMUNICATIONS NETWORK .
- System passed, retrieve and record the continuous diagnostic trouble codes (DTCs), erase the continuous DTCs and carry out self-test diagnostics for the vehicle security module.
- If the DTCs retrieved are related to the concern, go to VEHICLE SECURITY MODULE DIAGNOSTIC TROUBLE CODE (DTC) INDEX to continue diagnostics.
- If no DTCs related to the concern are retrieved, GO to SYMPTOM CHART to continue diagnostics.