2007 NISSAN 350Z LAN System Workshop Manual

TROUBLE DIAGNOSES WORK FLOW
LAN-17
[CAN FUNDAMENTAL]
C
D
E
F
G
H
I
J
L
MA
B
LAN
Revision: 2006 November2007 350Z
Trouble Diagnosis ProcedureNKS004PL
INTERVIEW WITH CUSTOMER
Interview with the customer is important to detect the root cause of CAN communication system errors and to
understand vehicle condition and symptoms for proper trouble diagnosis.
Points in interview

What: Parts name, system name

When: Date, Frequency

Where: Road condition, Place

In what condition: Driving condition/environment

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
from the customer, and it performs CAN communication with many units.
SKIB8717E

LAN-18
[CAN FUNDAMENTAL]
TROUBLE DIAGNOSES WORK FLOW
Revision: 2006 November2007 350Z
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:

Never turn the ignition switch OFF or disconnect the battery cable while the 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 LAN-25,
"DETECT THE ROOT CAUSE" .

TROUBLE DIAGNOSES WORK FLOW
LAN-19
[CAN FUNDAMENTAL]
C
D
E
F
G
H
I
J
L
MA
B
LAN
Revision: 2006 November2007 350Z
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:
CAN system type is easily checked with the vehicle equipment identification information shown in the chart.
SKIB8888E

LAN-20
[CAN FUNDAMENTAL]
TROUBLE DIAGNOSES WORK FLOW
Revision: 2006 November2007 350Z
CAN System Type Specification Chart (Style B)
NOTE:
CAN system type is easily checked with the vehicle equipment identification information shown in the chart.
SKIB8889E

TROUBLE DIAGNOSES WORK FLOW
LAN-21
[CAN FUNDAMENTAL]
C
D
E
F
G
H
I
J
L
MA
B
LAN
Revision: 2006 November2007 350Z
CREATE INTERVIEW SHEET
Fill out the symptom described by the customer, vehicle condition, and CAN system type on the interview
sheet.
Interview Sheet (Example)
PKID1211E

LAN-22
[CAN FUNDAMENTAL]
TROUBLE DIAGNOSES WORK FLOW
Revision: 2006 November2007 350Z
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:
Some items may not be needed depending on CAN system type of vehicle.
PKID1212E

TROUBLE DIAGNOSES WORK FLOW
LAN-23
[CAN FUNDAMENTAL]
C
D
E
F
G
H
I
J
L
MA
B
LAN
Revision: 2006 November2007 350Z
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:
For some models, CAN communication diagnosis result is received from the vehicle monitor. (CONSULT-III is
not available.)
SKIB8722E

LAN-24
[CAN FUNDAMENTAL]
TROUBLE DIAGNOSES WORK FLOW
Revision: 2006 November2007 350Z
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”.

For abbreviations, refer to LAN-41, "Abbreviation List" .
PKID1213E