Sunday 3 July 2011

WS5 Scan Tool Diagnostics

WS5    Scan Tool Diagnostics

Make   TOYOTA              Model    SPRINTER           Year    1987

(Course: using a Scan Tool that communicates to the engine you want to test.)
Warning: Be careful working around engines and exercise caution to avoid injury.


1. Scan Tool Data


1.1 Find a vehicle which is appropriate for the scan tool. 
1.2 Connect the scanner, power it on, follow the instructions and input the correct vehicle information it asks for so you can view the data.


1.3 Find the data for the information listed on the next page. Turn engine on to idle. Fill in the letters used to label the information and the value of that data. (For example, engine load information may be found under MAP, with a value of 3.6, listed in volts) Note: not all vehicles will support all information, just find as much as you can. If the engine won’t run, input the information with the key on, engine off.
 
<><> <><><> <>
Type of information (PID = Parameter Identification)Letters to describe itValue of dataUnits for data
E.g. TPSE.g. volts
Engine Load (how much air comes in)Intake29kPa
Engine RPMRPM800RPM
Throttle angleTPS0%
Engine coolant temperatureECT85
Intake air temperatureN/AN/AN/A
Fuel Injection opening pulse FIOP2ms
Transmission select positionN/AN/AN/A
Vehicle SpeedN/A0km/h
Oxygen sensor(s)N/ALEANN/A
LEFTRICH
RIGHT
Fuel TrimN/AN/AN/A
Idle controlISC39%
Power steering conditionN/AN/AN/A
Air conditioning conditionA/C signaloffswitch on/off
Exhaust Gas Recirculation (EGR)N/AN/AN/A
Fuel Evap or Purge conditionN/AN/AN/A
Malfunction Indicator Light (MIL)N/AN/AN/A
Barometric PressureN/AN/AN/A 


2 Trouble Codes or Fault Codes


2.1 Find where the Codes are listed


2.2 Record any codes, and what system and condition they describe in the chart below (Example: might be code number 21, for Throttle Position Sensor, signal voltage too low) If there are no codes listed, put “none”.

Code numberSystem affectedCondition described
NO code


3 Lecturer put in Fault


3.1 Find your lecturer and have him create a fault under the hood (don’t look)


4 Record New Codes


4.1 Look up the codes now in the scan tool


4.2 Record the codes in the chart below. Also record what system is affected, and what condition is described.

Code number
System affected
Condition described
31
Air flow meter / VAC sensorengine stop
22
Coolant temperature sensorNo signal, The ECU orders rich mixture all the time therefore, the engine RPM goes up.







5 Find What Data Has Changed
5.1 Look through the scan tool data to see what PIDs (Parameter Identification of system voltages) have changed. Which readings don’t make sense or don’t read what you would expect. Concentrate on the PIDs related to the codes.
5.2 Record the PIDs that have changed below:


Type of information (PID=Parameter Identification)Letters to describe itValue of dataUnits for data
Engine SpeedRPM875RPM
Coolant Temperature SensorCTS90
Intake ManifoldIntake manifold46kPa






6 Visual Inspection to find fault
6.1 Do a visual inspection under the hood to find where the problem is. Use information from the code to know where to look for the problem and what type of problem to look for.


Describe problem you found:
 When the vacuum sensor is disconneted, the engine is not running.
7 Repair fault


7.1 Plug back in the connector, or repair problem found
 
7.2 Describe what you did:


  I have reconnected the vacuum sensor connector and then restarted the engine. The engine runs well with out any problems.

8 Recheck Data PIDs
Type of information (PID=Parameter Identification)Letters to describe itValue of dataUnits for data
Engine SpeedRPM825RPM
Coolant Temperature SensorCTS90
Intake ManifoldIntake manifold27kPa





8.1 Recheck the data with the scan tool

8.2 Record the voltages for the PIDs related to the problem, to confirm they are back to normal
9 Clear Codes

Describe what you did to clear codes:
  I made a disconnection of the negative terminal or the engine main fuse for 30 seconds.  


10 Recheck for codes and record codes in system now:      

 When I recheck the codes from selecting D.T.C, there were no troble codes on the screen.
 
11 Discuss the importance live data when fault finding
 
It shows the state of the sensors from the live data values.
12 Explain the need for parameters when checking live data

when the fault is resolved, the live data will be rechecked with its parameters then the data should be compared to fault datas.

13 Discuss how a scan tool can aid you when fault finding  
   I can find the fault easily and although the vehicle is old or new, I can also check the state of a vehicle with various information.  

No comments:

Post a Comment