2004 ISUZU TF SERIES engine

6E–80 4JA1/4JH1 ENGINE DRIVEABILITY AND EMISSIONS
Step 3: Simulate the symptom and isolate the
problem
Simulate the symptom and isolate the system by
reproducing all possible conditions suggested in Step 1
while monitoring suspected circuits/components/
systems to isolate the problem symptom. Begin with the
most logical circuit/component.
Isolate the circuit by dividing the suspect system into
simpler circuits. Nex t, confine the problem into a smaller
area of the system. Begin at the most logical point (or
point of easiest access) and thoroughly check the
isolated circuit for the fault, using basic circuit tests.
Hints
You can isolate a circuit by:
Unplugging connectors or removing a fuse to
separate one part of the circuit from another
If only component fails to operate, begin testing the
component
If a number of components do not operate, begin test
at areas of commonality (such as power sources,
ground circuits, switches, main connectors or major
components)
Substitute a known good part from the parts
department or the vehicle system
Try the suspect part in a known good vehicle
See Symptom Simulation Tests on the nex t page for
problem simulation procedures. Refer to service manual
sections 6E and 8A for information about intermittent
diagnosis. Follow procedures for basic circuit testing in
service manual section 8A.
What resources you should use
Whenever appropriate, you should use the following
resources to assist in the diagnostic process:
Service manual
Bulletins
Digital multimeter (with a MIN/MAX feature)
Tech II and Tech II upload function
Circuit testing tools (including connector kits/
harnesses and jumper wires)
Ex perience
Intermittent problem solving simulation methods
Customer complaint check sheet
Symptom Simulation Tests
1. Vibration
This method is useful when the customer complaint
analysis indicates that the problem occurs when the
vehicle/system undergoes some form of vibration.
For connectors and wire harness, slightly shake
vertically and horizontally. Inspect the connector joint
and body for damage. Also, tapping lightly along a
suspected circuit may be helpful.For parts and sensors, apply slight vibration to the part
with a light tap of the finger while monitoring the system
for a malfunction.
2. Heat
This method is important when the complaint suggests
that the problem occurs in a heated environment. Apply
moderate heat to the component with a hair drier or
similar tool while monitoring the system for a
malfunction.
CA UTION: Care must be take to avoid overheating
the component.
3. Water and Moisture
This method may be used when the complaint suggests
that the malfunction occurs on a rainy day or under
conditions of high humidity. In this case, apply water in a
light spray on the vehicle to duplicate the problem.
CA UTION: Care must be take to avoid directly
exposing electrical connections to water.
4. Electrical loads
This method involves turning systems ON (such as the
blower, lights or rear window defogger) to create a load
on the vehicle electrical system at the same time you
are monitoring the suspect circuit/component.
5e. Vehicle Operates as Designed
This condition refers to instances where a system
operating as designed is perceived to be unsatisfactory
or undesirable. In general, this is due to:
A lack of understanding by the customer
A conflict between customer ex pectations and
vehicle design intent
A system performance that is unacceptable to the
customer
What you should do
You can verify that a system is operating as designed
by:
Reviewing service manual functional/diagnostic
checks
Ex amining bulletins and other service information for
supplementary information
Compare system operation to an identical vehicle
If the condition is due to a customer misunderstanding
or a conflict between customer ex pectation and system
operation, you should ex plain the system operation to
the customer.
If the complaint is due to a case of unsatisfactory
system performance, you should contact Technical
Assistance for the latest information.
What resources you should use
Whenever possible, you should use the following
resources to facilitate the diagnostic process:

4JA1/4JH1 ENGINE DRIVEABILITY AND EMISSIONS 6E–81
Vehicle service information (service manual, etc.)
ISUZU field support
Ex perience
Identical vehicle or system for comparison
6. Re-examine the complaint
When you do not successfully find/isolate the problem
after ex ecuting a diagnostic path, you should re-
ex amine the complaint.
What you should do
In this case, you will need to backtrack and review
information accumulated from step 1 through 4 of
Strategy Based Diagnostics. You also should repeat any
procedures that require additional attention.
A previous path may be eliminated from consideration
only if you are certain that all steps were ex ecuted as
directed. You must then select another diagnostic path
(step 5a, 5b, 5c or 5d). If all possible options have been
ex plored, you may call or seek ISUZU field support.
What resources you should use
Whenever possible, you should use the following
resources to facilitate the diagnostic process:
Service manual
Accumulated information form a previous diagnostic
path
Service information and publications
ISUZU field support
7. Repair and Verify Fix
What you should do
After you have located the cause of the problem, you
must ex ecute a repair by following recommended
service manual procedures.
When the repair is completed, you should verify the fix
by performing the system checks under the conditions
listed in the customer complaint.
If applicable, you should carry out preventive measures
to avoid a repeat complaint.
What resources you should use
Whenever possible, you should use the following
resources to facilitate the repair process:
Electrical repair procedures
Service manual information and publications

6E–82 4JA1/4JH1 ENGINE DRIVEABILITY AND EMISSIONS
GENERAL SERVICE INFORMATION
Serviceability Issues
Non-OEM Parts
All of the OBD diagnostics have been calibrated to run
with OEM parts. Accordingly, if commercially sold
sensor or switch is installed, it makes a wrong diagnosis
and turns on the check engine lamp.
Aftermarket electronics, such as cellular phones,
stereos, and anti-theft devices, may radiate EMI into the
control system if they are improperly installed. This may
cause a false sensor reading and turn on the check
engine lamp.
Poor Vehicle Maintenance
The sensitivity of OBD diagnostics will cause the check
engine lamp to turn on if the vehicle is not maintained
properly. Restricted oil filters, fuel filters, and crankcase
deposits due to lack of oil changes or improper oil
viscosity can trigger actual vehicle faults that were not
previously monitored prior to OBD. Poor vehicle
maintenance can not be classified as a “non-vehicle
fault”, but with the sensitivity of OBD diagnostics,
vehicle maintenance schedules must be more closely
followed.
Related System Faults
Many of the OBD system diagnostics will not run if the
ECM detects a fault on a related system or component.
Visual/Physical Engine Compartment
Inspection
Perform a careful visual and physical engine
compartment inspection when performing any
diagnostic procedure or diagnosing the cause of an
emission test failure. This can often lead to repairing a
problem without further steps. Use the following
guidelines when performing a visual/physical
inspection:
Inspect all vacuum hoses for punches, cuts,
disconnects, and correct routing.
Inspect hoses that are difficult to see behind other
components.
Inspect all wires in the engine compartment for
proper connections, burned or chafed spots, pinched
wires, contact with sharp edges or contact with hot
exhaust manifolds or pipes.
Basic Knowledge of Tools Required
NOTE: Lack of basic knowledge of this powertrain
when performing diagnostic procedures could result in
an incorrect diagnosis or damage to powertrain
components. Do not attempt to diagnose a powertrain
problem without this basic knowledge.
A basic understanding of hand tools is necessary to
effectively use this section of the Service Manual.
ON-BOARD DIAGNOSTIC (OBD)
On-Board Diagnostic (Self Diagnosis
System) Tests
A diagnostic test is a series of steps, the result of which
is a pass or fail reported to the diagnostic ex ecutive.
When a diagnostic test reports a pass result, the
diagnostic ex ecutive records the following data:
The diagnostic test has been completed since the
last ignition cycle.
The diagnostic test has passed during the current
ignition cycle.
The fault identified by the diagnostic test is not
currently active.
When a diagnostic test reports a fail result, the
diagnostic ex ecutive records the following data:
The diagnostic test has been completed since the
last ignition cycle.
The fault identified by the diagnostic test is currently
active.
The fault has been active during this ignition cycle.
The operating conditions at the time of the failure.
The Diagnostic Executive
The Diagnostic Executive is a unique segment of
software which is designed to coordinate and prioritize
the diagnostic procedures as well as define the protocol
for recording and displaying their results. The main
responsibilities of the Diagnostic Ex ecutive are listed as
follow s:
Commanding the check engine lamp on and off
DTC logging and clearing
Current status information on each diagnostic
Diagnostic Information
The diagnostic charts and functional checks are
designed to locate a faulty circuit or component through
a process of logical decisions. The charts are prepared
with the requirement that the vehicle functioned
correctly at the time of assembly and that there are not
multiple faults present.
There is a continuous self-diagnosis on certain control
functions. This diagnostic capability is complemented
by the diagnostic procedures contained in this manual.
The language of communicating the source of the
malfunction is a system of diagnostic trouble codes.
When a malfunction is detected by the control module, a
diagnostic trouble code is set and the check engine
lamp is illuminated.
Check Engine Lamp
The check engine lamp looks the same as the check
engine lamp you are already familiar with, the “Check
Engine” lamp.
Basically, the check engine lamp is turned on when the

4JA1/4JH1 ENGINE DRIVEABILITY AND EMISSIONS 6E–83
ECM detects a DTC that will impact the vehicle
emissions.
When the check engine lamp remains “ON” while the
engine is running, or when a malfunction is
suspected due to a driveability or emissions problem,
a Powertrain On-Board Diagnostic (OBD) System
Check must be performed. The procedures for these
checks are given in On-Board Diagnostic (OBD)
System Check. These checks will ex pose faults
which may not be detected if other diagnostics are
performed first.
Data Link Connector (DLC)
The provision for communication with the contorl
module is the Data Link Connector (DLC). It is located
behind the lower front instrument panel. The DLC is
used to connect to a Tech 2. Some common uses of the
Tech 2 are listed below:
Identifying stored Diagnostic Trouble Codes (DTCs).
Clearing DTCs.
Reading serial data.
Verifying Vehicle Repair
Verification of vehicle repair will be more
comprehensive for vehicles with OBD system
diagnostic. Following a repair, the technician should
perform the following steps:
1. Review and record the Fail Records for the DTC
which has been diagnosed.
2. Clear DTC(s).
3. Operate the vehicle within conditions noted in the
Fail Records.
4. Monitor the DTC status information for the specific
DTC which has been diagnosed until the diagnostic
test associated with that DTC runs.
Following these steps is very important in verifying
repairs on OBD systems. Failure to follow these steps
could result in unnecessary repairs.
Reading Flash Diagnostic Trouble Codes
The provision for communicating with the Engine
Control Module (ECM) is the Data Link Connector
(DLC). The DLC is located in the front console box . It is
used in the assembly plant to receive information in
checking that the engine is operating properly before it
leaves the plant.
The diagnostic trouble code(s) (DTCs) stored in the
ECM’s memory can be read either through a hand-held
diagnostic scanner plugged into the DLC or by counting
the number of flashes of the check engine lamp when
the diagnostic test terminal of the DLC is grounded. The
DLC terminal “6” (diagnostic request) is pulled “Low”
(grounded) by jumping to DLC terminal “4 or 5”, which is
a ground wire.
This will signal the ECM that you want to “flash” DTC(s),
if any are present. Once terminals “4 or 5” and “6” have
been connected, the ignition switch must be moved to
the “ON” position, with the engine not running.
The check engine lamp will indicate a DTC three times if
a DTC is present. If more than one DTC has been
stored in the ECM’s memory, the DTC(s) will be output
from the lowest to the highest, with each DTC being
displayed three times.
The DTC display will continue as long as the DLC is
shorted.
Reading Diagnostic Trouble Codes Using a
Tech 2
The procedure for reading diagnostic trouble code(s) is
to used a diagnostic Tech 2. When reading DTC(s),
follow instructions supplied by Tech 2 manufacturer.
For the 1998 model year, Isuzu dealer service
departments will continue to use Tech 2.
Clearing Diagnostic Trouble Codes
To clear Diagnostic Trouble Codes (DTCs), use the
Te c h 2 “clear DTCs” or “clear information” function.
When clearing DTCs follow instructions supplied by the
Tech 2 manufacturer.
History DTC
History DTC can be candeled after 40 cycle driving with
no defect. Or history code can be deleted by Tech 2
“Clear DTCs” function.

6E–84 4JA1/4JH1 ENGINE DRIVEABILITY AND EMISSIONS

4JA1/4JH1 ENGINE DRIVEABILITY AND EMISSIONS 6E–85
DIAGNOSIS WITH Tech 2
If no codes are set:
Refer to F1: Data Display and identify the electrical
faults that are not indicated by trouble code.
Refer to “SYMPTOM DIAGNOSIS”.
If codes are set:
1. Record all trouble codes displayed by Tech 2 and
check id the codes are intermittent.
2. Clear the codes.
3. Drive the vehicle for a test to reproduce the faulty
status.
4. Check trouble codes again using the Tech 2.
5. If no codes is displayed by test driving, the fault is
intermittent. In this case, refer to “DIAGNOSIS
AIDS”.
6. If a code is present, refer to DTC Chart for
diagnosis.
7. Check trouble codes again using the Tech 2.
Tech 2 CONNECTION
Tech 2 scan tool is used to electrically diagnose the
automatic transmission system and to check the
system. The Tech 2 enhances the diagnosis efficiency
though all the troubleshooting can be done without the
Te c h 2 .
1. Configuration of Tech 2
Tech 2 scan tool kit (No. 7000086), Tech 2 scan
tool (No. 7000057) and DLC cable (No.
3000095).
SAE 16/19 adapter (No. 3000098) (3), RS232
loop back connector (No. 3000112) (2) and
PCMCIA card (No. 3000117) (1).
2. Tech 2 Connection
Check the key switch is turn OFF.
Insert the PCMCIA card (1) into the Tech 2 (5).Connect the SAE 16/19 adapter (3) to the DLC
cable (4).
Connect the DLC cable (4) to the Tech 2 (5).
Connect the SAE 16/19 adapter (3) to the data
link connector of the vehicle.
Turn the key switch of the vehicle ON and press
the “PWR” key of the Tech 2.
Check the display of the Tech 2.
NOTE: Be sure to check that the power is not supplied
to the Tech 2 when attaching or removing the PCMCIA
card.

6E–86 4JA1/4JH1 ENGINE DRIVEABILITY AND EMISSIONS
TECH 2 OPERATING FLOW CART (START UP)
Select “4JA1-TC Bosch” or “4JH1-TC Bosch” in Vehicle Identification menu and the following table is shown in the
Tech 2 screen.
Press (ENTER) to Co ntinue
Main Menu
F0: Dia gnostic
F1: Se rvice Programming Syste m (SPS)
F2: View Capture Data
F3: Too l Optio n
F4: Do wnlo a d/ Uploa d He lp
Press “ENTER” key.
Ve hi cl e Ide nt ifi ca ti o n
(3) 2003
(2) 2002
(1) 2001
(Y) 2000
(X) 1999
(W) 1998
Select “F0: Diagnostic”.
Select “(3) 2003”or later.
System Selection Menu
F0: Powe rtra in
F1: Chassis
F3: Body
Select “(TF/UC)”.
Vehicle Identification
4JH1-TC Bosch
4JA1-TC Bosch
4JH1-T Denso
3.5L V6 6VE1 Hita chi
AW30-40LE
A/T JR405E
Select “F0: Powertrain”.
Select “4JA1-TC Bosch” or “4JH1-TC Bosch”.
Vehicle Identification
(UB) Troo pe r, Bigho rn
(UE) Rodeo,/Amigo, Wizard/Mu
(TF/UC) LUV, Fro ntier, LAO-Ro de o
(TBR)
(N*) ELF, NPR, NQR

4JA1/4JH1 ENGINE DRIVEABILITY AND EMISSIONS 6E–87
F0: Diagnostic Trouble Code
The purpose of the “Diagnostic Trouble Codes” mod e i s
to display stored trouble code in the ECM.
When “Clear DTC Information” is selected, a “Clear
DTC Information”, warning screen appears.
This screen informs you that by cleaning DTC's “all
stored DTC information in the ECM will be erased”.
After clearing codes, confirm system operation by test
driving the vehicle.
Symptom Code:
This number or alphabet means identification of the
malfunction. Each DTC includes plural symptoms, such
as DTC P0100 has four kinds of symptom code (7), (9),
(B) and (C). DTC chart (check procedure) is separated
depending on the symptom code.F1: Data Display
The purpose of the “Data Display” mode is to
continuously monitor data parameters.
The current actual values of all important sensors and
signals in the system are display through F1 mode.
See the “Typical Scan Data” section.
F2: Snapshot
“Snapshot” allows you to focus on making the condition
occur, rather than trying to view all of the data in
anticipation of the fault.
The snapshot will collect parameter information around
a trigger point that you select.
F3: Miscellaneous Test:
The purpose of “Miscellaneous Test” mode is to check
for correct operation of electronic system actuators.
F4: Programming (Factory Use Only)
The purpose of “Programming” is to program VIN in the
ECM and lock the programmed data. F0: Diagnostic Trouble Codes
F0: Read DTC Infor As Stored By ECU
F1: Clear DTC Information
F1: Data Display
F2: Snapshot
F3: Miscellaneous Test
F0: Lamps
F0: Glow Time Telltale Test
F1: Relays
F0: Glow Time Relay Test
F2: Solenoids
F0: EGR Solenoid Test
F3: Engine Speed (RPM) Control
F4: Programming
F0: Program VIN
F1: Lock ECU
Read DTC Infor A s Stored By ECU

P0100 Present
(7) Mass Air Flow (MAF) Sensor
Voltage Supply Circuit High Input
DTC No.
Symptom Code