This connector is used for Subaru Select Monitor.
For detailed connection procedures, refer to “Application help”.
Do not connect any tools other than Subaru Select Monitor or general scan tool because the circuit for Subaru Select Monitor may be damaged.
|
Terminal No. |
Contents |
Measuring condition |
Standard |
|
(i288) No. 1 |
— |
— |
— |
|
(i288) No. 2 |
— |
— |
— |
|
(i288) No. 3 |
— |
— |
— |
|
(i288) No. 4 ←→ Chassis ground |
GND |
Always |
10 Ω or less |
|
(i288) No. 5 ←→ Chassis ground |
GND |
Always |
10 Ω or less |
|
(i288) No. 6 |
CAN-H |
— |
— |
|
(i288) No. 7 |
— |
— |
— |
|
(i288) No. 8 ←→ Chassis ground |
Ignition power supply |
When ignition switch is ON |
Battery voltage |
|
(i288) No. 9 |
— |
— |
— |
|
(i288) No. 10 |
— |
— |
— |
|
(i288) No. 11 |
— |
— |
— |
|
(i288) No. 12 |
— |
— |
— |
|
(i288) No. 13 |
— |
— |
— |
|
(i288) No. 14 |
CAN-L |
— |
— |
|
(i288) No. 15 |
— |
— |
— |
|
(i288) No. 16 ←→ Chassis ground |
Battery power supply |
Always |
Battery voltage |
LHD model
|
(1) |
Data link connector |
RHD model
|
(1) |
Data link connector |
On [Start] screen, select [Diagnosis].
On [Vehicle selection] screen, input the target vehicle information and select [OK].
On [Main Menu] screen, select [Each System].
On [Select System] screen, select the corresponding system and select [Enter].
On [Select Function] screen, select [DTC].
For detailed operation procedures, refer to “Application help”.
Sub screen may appear in the system selection display. In that case, select appropriate items in accordance with the contents of the display.
Current malfunction is a diagnostic code displayed when the system is judging the current malfunction. However, if a DTC is recorded due to poor contact etc., the code remains displayed as current malfunction during the drive cycle even after the poor contact has resolved.
Past malfunction is a diagnostic code recorded when the current malfunction is not occurring but the system has detected a malfunction in the past. When the current malfunction is recorded, it is also recorded to the past malfunction at the same time.
On [Start] screen, select [Diagnosis].
On [Vehicle selection] screen, input the target vehicle information and select [OK].
On [Main Menu] screen, select [Each System].
On [Select System] screen, select the corresponding system and select [Enter].
On [Select Function] screen, select [DTC].
On [DTC] screen, select [Clear memory].
For detailed operation procedures, refer to “Application help”.
Sub screen may appear in the system selection display. In that case, select appropriate items in accordance with the contents of the display.
When the clear memory is performed, diagnostic code (DTC) and freeze frame data (FFD) necessary in diagnosis will also be deleted.
Before performing the clear memory, be sure to save the diagnostic code (DTC) and freeze frame data (FFD) stored in the module.
Initial diagnosis of electronic throttle control is performed after memory clearance. Wait for 10 seconds or more after turning the ignition switch to ON, and then start the engine.
On [Start] screen, select [Diagnosis].
On [Vehicle selection] screen, input the target vehicle information and select [OK].
On [Main Menu] screen, select [Each System].
On [Select System] screen, select the corresponding system and select [Next].
On [Select Function] screen, select [DTC].
On [DTC] screen, select [FFD].
For detailed operation procedures, refer to “Application help”.
Sub screen may appear in the system selection display. In that case, select appropriate items in accordance with the contents of the display.
Freeze frame data is cleared by clearing memory.
On [Start] screen, select [Diagnosis].
On [Vehicle selection] screen, input the target vehicle information and select [OK].
On [Main Menu] screen, select [Each System].
On [Select System] screen, select the corresponding system and select [Next].
On [Select Function] screen, select [Data monitor].
For detailed operation procedures, refer to “Application help”.
Sub screen may appear in the system selection display. In that case, select appropriate items in accordance with the contents of the display.
There are three types of record data for the information of time stamp, and they are stored together with diagnostic codes.
Depending on DTCs, time stamp may not be stored.
Trip Count [count]
This indicates the number of times that the ignition has been turned to ON since the vehicle was manufactured. The ignition ON count of when the diagnostic code is stored is displayed on the diagnostic code check screen.
Subaru Select Monitor 4 screen (A/C system diagnostic code and time stamp)
|
Code |
Description & trouble part |
Trip Count [count] |
Time Count |
Group |
|
B14E1 |
AIR MIX DOOR ACTUATOR STEPPING MOTOR CIRCUIT WIRE BREAK (DRIVER’S SEAT) |
983 |
18000 |
Common |
|
B14E7 |
HEATER CORE REAR SENSOR CIRCUIT WIRE BREAK |
984 |
117800 |
Common |
Furthermore, the current IG ON count (times) can be checked at the data monitor of body control.
By comparing the current Trip Count and the Trip Count of when the diagnostic code was stored, it is possible to determine that it is how many ignition-ON operations ago that DTC was stored.
Time Count
The elapsed time from when the ignition is turned to ON to when the diagnostic code is stored is displayed on the diagnostic code check screen. It is possible to determine the length of time that passed between when the user started driving and when the diagnostic code was stored. Therefore, if Trip Count until the vehicle-received-date is determined by interviewing the user, it is possible to estimate where the user was driving when the diagnostic code was stored, using the information such as Trip Count and Time Count. This estimate is useful information to perform diagnosis including checking of repeatability.
Subaru Select Monitor 4 screen (A/C system diagnostic code and time stamp)
|
Code |
Description & trouble part |
Trip Count [count] |
Time [msec] |
Group |
|
B14E1 |
AIR MIX DOOR ACTUATOR STEPPING MOTOR CIRCUIT WIRE BREAK (DRIVER’S SEAT) |
983 |
18000 |
Common |
|
B14E7 |
HEATER CORE REAR SENSOR CIRCUIT WIRE BREAK |
984 |
117800 |
Common |
When multiple diagnostic codes are recorded for one trouble, it is extremely important to determine the diagnostic code that was stored first. (It is important to perform the diagnosis for the first recorded diagnostic code.) In this case, it is also possible to immediately determine which diagnostic code was recorded first, using the information such as Trip Count and Time Count.
Group
Each unit individually counts the elapsed time
since the ignition is turned to ON. However, these time counts may have
some errors, and therefore, the control modules need to be adjusted to
the time carried by the master-time unit (the body integrated unit).
When the count is set as common, it means that each control module is
already adjusted to the master time, and the display for the master
integrated unit is always indicated as Common. When the count is indicated as Originally,
it means that the time is not synchronized with the master time. In
this case, check the communication between the corresponding control
module and integrated unit. When all controls other than the body
integrated unit is indicated as Originally, perform the basic inspection for the body integrated unit.
BODY CONTROL(DIAGNOSTICS)>Basic Diagnostic Procedure>PROCEDURE
Subaru Select Monitor 4 screen (A/C system diagnostic code and time stamp)
|
Code |
Description & trouble part |
Trip Count [count] |
Time Count [msec] |
Group |
|
B14E1 |
AIR MIX DOOR ACTUATOR STEPPING MOTOR CIRCUIT WIRE BREAK (DRIVER’S SEAT) |
983 |
18000 |
Common |
|
B14E7 |
HEATER CORE REAR SENSOR CIRCUIT WIRE BREAK |
984 |
117800 |
Common |
Even when multiple diagnostic codes are stored in multiple control modules, it is possible to determine the code stored first through the count function.
Troubleshooting for CAN system U-code occurrence
When the first stored diagnostic code is a
U-code for CAN system, perform the troubleshooting as a U code
combination, instead of a U code alone. In addition, when CAN open
circuit occurs, communication of the diagnostic device itself becomes
impossible beyond the particular areas. However, trouble positions can
also be determined by the combination of initial communication
success/failure. Thus, by performing the basic diagnostic procedure in
LAN system, trouble positions can be determined efficiently on the
principle above.
LAN SYSTEM (DIAGNOSTICS)>Basic Diagnostic Procedure>PROCEDURE