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 it E.g. TPS	Value of data	Units for data E.g. volts
Engine Load (how much air comes in)	Intake	29	kpa
Engine RPM	RPM	800	RPM
Throttle angle	TPS	0	%
Engine coolant temperature	ECT	85	degree
Intake air temperature	N/A	N/A	N/A
Fuel Injection opening pulse	FIOP	2	ms
Transmission select position	N/A	N/A	N/A
Vehicle Speed	N/A	0	km/h
Oxygen sensor(s)	N/A	LEAN RICH	N/A
Fuel Trim	N/A	N/A	N/A
Idle control	ISC	39	%
Power steering condition	N/A	N/A	N/A
Air conditioning condition	A/C Signal	off	switch on/off
Exhaust Gas Recirculation (EGR)	N/A	N/A	N/A
Fuel Evap or Purge condition	N/A	N/A	N/A
Malfunction Indicator Light (MIL)	N/A	N/A	N/A
Barometric Pressure	N/A	N/A	N/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 number	System affected	Condition 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 sensor	Engine stop
22	Coolant Temperature Sensor	No signal, the ECU orders a 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 it	Value of data	Units for data
Engine speed	RPM	875	RPM
Coolant Temperature Sensor	CTS	90	degree c
Intake Manifold	Intake Manfold	46	kPa

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 Engine Vacuum sensor is disconnected, 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 re-connected the vacuum sensor and restarted the engine. The engine ran good without any problems.


8              Recheck Data PIDs

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

Type of information (PID = Parameter Identification)	Letters to describe it	Value of data	Units for data
Engine Speed	RPM	825	RPM
Engine Coolant Temperature Sensor	CTS	90	°C
Intake Manifold	Intake Manifold	27	KPa

9              Clear Codes 

Describe what you did to clear codes:


I disconnected the battery negative cable for 30 seconds then reconnected it. 

           

                       
10          Recheck for codes and record codes in system now:
         There were no trouble codes detected when I selected the D.T.C button on the tool. 

11          Discuss the importance live data when fault finding:
        Live data allows me to see the values of all the sensors on the vehicle on one screen. 

                 

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

          A scan tool can display all the values of the different types of sensors on a variety of different vehicles. This makes it easier to locate faults.