Nissan Pathfinder (2008 year). Manual — part 470
LAN
DIAGNOSIS AND REPAIR WORKFLOW
LAN-15
< BASIC INSPECTION >
[CAN FUNDAMENTAL]
C
D
E
F
G
H
I
J
K
L
B
A
O
P
N
• Result: Symptom
NOTE:
• Check normal units as well as error symptoms.
- Example: Circuit between ECM and the combination meter is judged normal if the customer indicates
tachometer functions normally.
• When a CAN communication system error is present, multiple control units may malfunction or go into fail-
safe mode.
• Indication of the combination meter is important to detect the root cause because it is the most obvious to
the customer, and it performs CAN communication with many units.
INSPECTION OF VEHICLE CONDITION
• Check whether or not “U1000” or “U1001” is indicated on “SELF-DIAG RESULTS” by CONSULT-III.
NOTE:
Root cause cannot be detected using the procedure in this section if “U1000” or “U1001” is not indicated.
• Check whether the symptom is reproduced or not.
NOTE:
• Do not turn the ignition switch OFF or disconnect the battery cable while reproducing the error. The error
may temporarily correct itself, making it difficult to determine the root cause.
• The procedures for present errors differ from the procedures for past errors. Refer to “DETECT THE
ROOT CAUSE”.
CHECK OF CAN SYSTEM TYPE (HOW TO USE CAN SYSTEM TYPE SPECIFICATION CHART)
Determine CAN system type based on vehicle equipment. Then choose the correct diagnosis sheet.
NOTE:
There are two styles for CAN system type specification charts. Depending on the number of available system
types, either style A or style B may be used.
CAN System Type Specification Chart (Style A)
NOTE:
SKIB8717E
LAN-16
< BASIC INSPECTION >
[CAN FUNDAMENTAL]
DIAGNOSIS AND REPAIR WORKFLOW
CAN system type is easily checked with the vehicle equipment identification information shown in the chart.
CAN System Type Specification Chart (Style B)
NOTE:
SKIB8888E
LAN
DIAGNOSIS AND REPAIR WORKFLOW
LAN-17
< BASIC INSPECTION >
[CAN FUNDAMENTAL]
C
D
E
F
G
H
I
J
K
L
B
A
O
P
N
CAN system type is easily checked with the vehicle equipment identification information shown in the chart.
CREATE INTERVIEW SHEET
Fill out the symptom described by the customer, vehicle condition, and CAN system type on the interview
sheet.
SKIB8889E
LAN-18
< BASIC INSPECTION >
[CAN FUNDAMENTAL]
DIAGNOSIS AND REPAIR WORKFLOW
Interview Sheet (Example)
COLLECT DATA
Collect CONSULT-III Data
Print out or save the following CONSULT-III data.
• SELF-DIAG RESULTS
• CAN DIAG SUPPORT MNTR (“ECU list” included)
NOTE:
PKID1211E
LAN
DIAGNOSIS AND REPAIR WORKFLOW
LAN-19
< BASIC INSPECTION >
[CAN FUNDAMENTAL]
C
D
E
F
G
H
I
J
K
L
B
A
O
P
N
Some items may not be needed depending on CAN system type of vehicle.
Create On-board Diagnosis Copy Sheet
Display the trouble diagnosis result of CAN communication with the on-board diagnosis function on the vehicle
monitor, etc. Copy them on the on-board diagnosis copy sheet.
NOTE:
PKID1212E
LAN-20
< BASIC INSPECTION >
[CAN FUNDAMENTAL]
DIAGNOSIS AND REPAIR WORKFLOW
For some models, CAN communication diagnosis result is received from the vehicle monitor. (CONSULT-III is
not available.)
CREATE DIAGNOSIS SHEET
NOTE:
Be sure to use the diagnosis sheet for the correct CAN system type.
Print Diagnosis Sheet
Print the diagnosis sheet for the applicable CAN system type.
Check Collected Data
Make sure that all ECUs are received, referring to “ECU list”.
SKIB8722E
LAN
DIAGNOSIS AND REPAIR WORKFLOW
LAN-21
< BASIC INSPECTION >
[CAN FUNDAMENTAL]
C
D
E
F
G
H
I
J
K
L
B
A
O
P
N
• For abbreviations, refer to
.
DETECT THE ROOT CAUSE
Identify the root cause using the created diagnosis sheet.
Identifying the root cause
• Draw a line on the diagnosis sheet to indicate the possible cause. Narrow the search.
NOTE:
• Color-code when drawing lines.
• Do not draw a line onto a existing line.
• Drawing a line is not necessary if the circuit is shorted. Refer to “Present Error — Short Circuit —”, “Past
Error — Short Circuit —”.
Refer to the following for details of the trouble diagnosis procedure.
• “Present Error — Open Circuit —”
• “Present Error — Short Circuit —”
• “Past Error — Open Circuit —”
• “Past Error — Short Circuit —”
NOTE:
When the root cause appears to be a branch line or short circuit, be sure to check the control unit as well as
the communication line.
Present Error — Open Circuit —
PKID1213E
LAN-22
< BASIC INSPECTION >
[CAN FUNDAMENTAL]
DIAGNOSIS AND REPAIR WORKFLOW
Identify the error circuit using information from the “CAN DIAG SUPPORT MNTR” (“ECU list” included).
1.
ECU list: Check the items indicated in “ECU list”. Draw a line on the diagnosis sheet to indicate the error
circuit.
NOTE:
CAN communication line has no error if units other than Diag on CAN units are not indicated. An error
may be on the power supply of the control unit, DDL1 line or DDL2 line.
a.
“TCM” which is Diag on CAN unit, is not indicated on “ECU list”. This indicates that DLC is not receiving a
signal from TCM. Draw a line to indicate an error between DLC and TCM (line 1-a in the figure below).
NOTE:
• Diag on CAN units are not indicated on the “ECU list” when the CAN line between Diag on CAN unit and
the data link connector is open.
• For a description of Diag on CAN, refer to
2.
CAN DIAG SUPPORT MNTR: Check each item on “CAN DIAG SUPPORT MNTR”. Draw a line on the
diagnosis sheet to indicate the error circuit.
a.
Reception item of “ECM”: On “TCM”, “UNKWN” is indicated. This means ECM cannot receive the signal
from TCM. Draw a line to indicate an error between ECM and TCM (line 2-a in the figure below).
NOTE:
If “UNKWN” is indicated on “TRANSMIT DIAG”, then the control unit cannot transmit CAN communication
signal to each unit. Draw a line between the control unit and the splice.
b.
Reception item of “AFS”: On “TCM”, “UNKWN” is indicated. This means AFS cannot receive the signal
from TCM. Draw a line to indicate an error between AFS and TCM (line 2-b in the figure below).
PKID1214E
Нет комментариевНе стесняйтесь поделиться с нами вашим ценным мнением.
Текст