1991 LEXUS SC400 fuse

Back Up Power Source Circuit
CIRCUIT DESCRIPTION
Battery voltage is supplied to terminal BATT of the ECU even when the ignition switch is off for use by
the diagnostic code memory and air±fuel ratio adaptive control value mem\
ory, etc.
DIAGNOSTIC CHARTDIAGNOSTIC CHART
Check for short in all the harness and
components connected to EFI fuse.Check EFI fuse.
Check of terminal BATT.
Proceed to next circuit inspection shown on
matrix chart (See page TR±35).
Check operation for the back up.Check and replace ECU.
Check and repair harness or connector
between battery, EFI fuse and ECU.
WIRING DIAGRAM
TR±130±
ENGINE TROUBLESHOOTING Circuit Inspection
WhereEverybodyKnowsYourName

OKNG
OKNG
YESNO
INSPECTION PROCEDURE
1Check EFI fuse.
C
OK
PRemove EFI fuse from R/B No.2.
Check continuity of EFI fuse.
Continuity
Check for short in all the harness and components con-
nected to EFI fuse (See attached wiring diagram).
2Check voltage between terminal BATT of engine & ECT ECU connector and body ground.
C
OK
PConnect the Check Harness A.
(See page TR±30).
Measure voltage between terminal BATT of engine &
ECT ECU connector and body ground.
Voltage: 10 ± 14 V
Check and repair harness or connector between engine
& ECT ECU and EFI fuse, EFI fuse and battery.
3Are the diagnostic codes still in the memory when the ignition switch is\
turned OFF?
Check and replace engine & ECT ECU.
Proceed to next circuit inspection shown on ma-
trix chart (See page TR±35).
±
ENGINE TROUBLESHOOTING Circuit InspectionTR±131
WhereEverybodyKnowsYourName

DIAGNOSIS SYSTEM
DESCRIPTION
The ECU contains a built±in self±diagnosis system by which
troubles with the engine signal network are detected and a
ºCHECKº engine warning light on the instrument panel lights up.
By analyzing various signals as shown in the later table (See page
TR±14) the Electronic Control Unit (ECU) detects system malfunc-
tions relating to the sensors or actuators.
In the normal mode, the self±diagnosis system monitors 22 (USA
specification vehicles with TRAC control) or 21 (USA (except for
California) and Canadian specification vehicles with TRAC con-
trol) items, indicated by code No. as shown in TR±14. A ºCHECKº
engine warning light informs the driver that a malfunction has been
detected. The light goes off automatically when the malfunction
has been repaired. But the diagnostic code(s) remains stored in
the ECU memory (except for code Nos. 16 and 53). The ECU
stores the code(s) until it is cleared by removing the EFI fuse with
the ignition switch off.
The diagnostic code can be read by the number of blinks of the
ºCHECKº engine warning light when TE1 and E1 terminals on the
TDCL or check connector are connected. When 2 or more codes
are indicated, the lowest number (code) will appear first.
In the test mode, 15 (USA specification vehicles with TRAC con-
trol) or 14 (USA (except for California) and Canadian specification
vehicles with TRAC control) items, indicated by code No. as
shown in TR±14 are monitored. If a malfunction is detected in any
one of the systems indicated by code Nos. 13, 21, 22, 24, 25, 26,
27, 28, 29, 35, 41, 42, 47, 71 and 78 (USA specification vehicles)
or 13, 21, 22, 24, 25, 26, 27, 28, 29, 35, 41, 42, 47 and 78 (USA
(except for California) and Canadian specification vehicles) the
ECU lights the ºCHECKº engine warning light to warn the techni-
cian that malfunction has been detected. In this case, TE2 and E1
terminals on the TDCL should be connected as shown later. (See
page TR±12 ).
In the test mode, even if the malfunction is corrected, the malfunc-
tion code is stored in the ECU memory even when the ignition
switch is off (except code Nos. 43 and 51). This also applies in the
normal mode. The diagnostic mode (normal or test) and the output
of the ºCHECKº engine warning light can be selected by connect-
ing the TE1, TE2 and E1 terminals on the check connector or
TDCL, as shown later.
A test mode function has been added to the functions of the self±
diagnosis system of the normal mode for the purpose of detecting
malfunctions such as poor contact, which are difficult to detect in
the normal mode. This function fills up the selfdiagnosis system.
The test mode can be implemented by the technician following the
appropriate procedures of check terminal connection and opera-
tion described later. (See page TR±12)
TR±10
±
ENGINE TROUBLESHOOTING Diagnosis System
WhereEverybodyKnowsYourName

DIAGNOSTIC CODE CLEARANCE
1. After repair of the trouble areas, the diagnostic code retainedin the ECU memory must be cleared out by removing the EFI
fuse (30A) from R/B No. 2 for 10 seconds or more, with the
ignition switch OFF.
HINT:
wCancellation can also be done by removing the battery
negative (±) terminal, but in this case, other memory
systems (clock, etc.) will also be cancelled out.
w If it is necessary to work on engine components
requiring removal of the battery terminal, a check must
first be made to see if a diagnostic code has been
recorded.
2. After cancellation, road test the vehicle to check that a normal
code is now read on the ºCHECKº engine warning light.
If the same diagnostic code appears, it indicates that the
trouble area has not been repaired thoroughly.
±
ENGINE TROUBLESHOOTING Diagnosis SystemTR±13
WhereEverybodyKnowsYourName

CIRCUIT DESCRIPTION (Cont'd)
DIAGNOSIS CODE DETECTION DRIVING PATTERN
Purpose of the driving pattern.
(a) To simulate diag. code detecting condition after diag. code is recorded.
(b) To check that the malfunction is corrected when the repair is completed co\
nfirming that diag. code isno longer detected.

Disconnect the EFI fuse (15 A) for 10 sec. or more, with IG switch OFF\
.
Initiate test mode (Connect terminal TE2 and E1 of check connector or TDCL with IG
switch OFF).
Start the engine and warm up with all ACC switch OFF.
After the engine is warmed up, let it idle for 3 min.
After performing the idling in , perform gradual acceleration with in th\
e range 1,300
1,700 rpm (centered around 1,500 rpm) with the A/C switch ON and D range fo\
r A/T
(5th for M/T).
(Take care that the engine speed does not fall below 1,200 rpm when shifting.\
Gradu-
ally depress the accelerator pedal and kept it. Steady so that engine br\
aking does not
occur).
Maintain the vehicle speed at 40±50 mph (64±80 km/h).
Keep the vehicle running for 1±2 min. after starting acceleration.
HINT: If a malfunction exists, the ºCHECKº engine warning light will light\
up after approx. 60 sec. from the start of acceleration.
NOTICE: If the conditions in this test are not strictly followed, detection of t\
he malfunction will not be possible.
Malfunction: Main Oxygen Sensor Deterioration
±
ENGINE TROUBLESHOOTING Circuit InspectionTR±61
WhereEverybodyKnowsYourName

CIRCUIT DESCRIPTION (Cont'd)
DIAGNOSIS CODE DETECTION DRIVING PATTERN
Purpose of the driving pattern.
(a) To simulate diag. code detecting condition after diag. code is recorded.
(b) To check that the malfunction is corrected when the repair is completed co\
nfirming that diag. code isno longer detected.

Disconnect the EFI fuse (15 A) for 10 sec. or more. with IG switch OFF\
.
Initiate test mode (Connect terminal TE2 and E1 of check connector or TDCL with IG
switch OFF).
Start engine and warm up with all ACC switch OFF.
After engine is warmed up, let it idle for 5 min.
(After the engine is started, do not depress the accelerator pedal.)
If the malfunction is not detected during idling, perform racing without any load at
approx. 2,000 rpm for 60 sec.
HINT: If a malfunction exists, the ºCHECKº engine warning light will light\
up during the 5 min. idling period or within 60 sec. of starting racing.
NOTICE: If the conditions in this test are not strictly followed, detection of t\
he malfunction will not be possible.
Malfunction: Open or Short in Injector circuit, Injector Leak or Blockag\
e
±
ENGINE TROUBLESHOOTING Circuit InspectionTR±71
WhereEverybodyKnowsYourName

CIRCUIT DESCRIPTION (Cont'd)
DIAGNOSIS CODE DETECTION DRIVING PATTERN
Purpose of the driving pattern.
(a) To simulate diag. code detecting condition after diag. code is recorded.
(b) To check that the malfunction is corrected when the repair is completed co\
nfirming that diag. code isno longer detected.

Disconnect the EFI fuse (15 A) for 10 sec. or more, with IG switch OFF\
.
Initiate test mode (Connect terminal TE2 and E1 of check connector with\
IG switch
OFF).
Start the engine and warm up with all ACC switch OFF.
After the engine is warmed up, let it drive at 50 55 mph (80 88 km/h) for\
10 min. or
more.
After driving, stop at a safe place and perform idling for 2 min. or les\
s.
After performing the idling in , perform acceleration to 60 mph (96 km/h) with the
throttle valve fully open.
HINT: If a malfunction exists, the ºCHECKº engine warning light will lig\
ht up during step
.
NOTICE: If the conditions in this test are not strictly followed, detection of t\
he malfunction will not be possible.
Malfunction: Open or Short in Sub±Oxygen Sensor
±
ENGINE TROUBLESHOOTING Circuit InspectionTR±77
WhereEverybodyKnowsYourName

CIRCUIT DESCRIPTION (Cont'd)
DIAGNOSIS TROUBLE CODE DETECTION DRIVING PATTERN
Purpose of the driving pattern.
(a) To simulate diag. trouble code detecting condition after diag. trouble co\
de is recorded.
(b) To check that the malfunction is corrected when the repair is completed co\
nfirming that diag. trouble codeis no longer detected.
Malfunction: Open in EGR gas temp. sensor circuit
Disconnect the EFI fuse (15 A) for 10 sec. or more, with IG switch OFF\
.
Initiate test mode (Connect terminal TE2 and E1 of check connector or TDCL with\
IG
switch OFF).
Start the engine and warm up.
After the engine is warmed up, let it idle for 3 min.
With the A/C ON and transmission in 5th gear (ECT in 3rd speed) drive at 5\
5 ~ 60 mph
(88 ~ 96 km/h) for 4 min or less.
HINT: If a malfunction exists, the ºCHECKº engine warning light will l\
ight up during step .
NOTICE: If the conditions in this test are not strictly followed, detection of \
the malfunction will not be possible.
±
ENGINE TROUBLESHOOTING Circuit InspectionTR±105
WhereEverybodyKnowsYourName