TELEMATICS SYSTEM (DIAGNOSTICS)
TEL(diag)

  1. Basic Diagnostic Procedure
  2. Check List for Interview
  3. General Description
  4. Electrical Component Location
  5. Control Module I/O Signal
  6. Inspection Mode
  7. Diagnostic Procedure for Subaru Select Monitor Communication
  8. Data Monitor
  9. Freeze Frame Data
  10. Active Test
  11. Diagnostic Trouble Code (DTC)
  12. Diagnostic Procedure with Diagnostic Trouble Code (DTC)
  13. Diagnostics with Phenomenon
TELEMATICS SYSTEM (DIAGNOSTICS) > Basic Diagnostic Procedure 
PROCEDURE

1. PERFORM CUSTOMER INTERVIEW.

Ask the customer when and how the trouble occurred using the interview check list. TELEMATICS SYSTEM (DIAGNOSTICS)>Check List for Interview

Did you interview the customer?

2

Perform the interview, and 2

2. PERFORM BASIC INSPECTION.

Is the check result OK?

3

Repair the faulty part found in basic inspection, and 3

3. CHECK SUBARU SELECT MONITOR COMMUNICATION.
1.

Turn the ignition switch to OFF.

2.

Connect the Subaru Select Monitor to data link connector. COMMON(diag)>Data Link Connector

3.

Turn the ignition switch to ON and run the Subaru Select Monitor.

4.

Select [Telematics].

 

For detailed operation procedures, refer to “Help” of application.

Is communication possible?

4. CHECK DTC.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

 

If DTC is detected, only RED LED will illuminate. For details, refer to LED illumination status list. TELEMATICS SYSTEM (DIAGNOSTICS)>Check List for Interview>CHECK > LED ILLUMINATION STATUS LIST

Are any DTCs displayed? (Current malfunction)

Record the DTC, time stamp and freeze frame data, and 5

Perform diagnosis according to the procedures in the diagnostics with phenomenon. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostics with Phenomenon

5. PERFORM DIAGNOSIS.
1.

Perform the diagnosis for the displayed DTCs. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)>LIST

2.

Repair or replace the cause of trouble.

3.

Using the Subaru Select Monitor, perform the clear memory of [Telematics]. COMMON(diag)>Clear memory

4.
5.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Are any DTCs displayed? (Current malfunction)

Repeat step 5 until DTC is not shown. 5

Finish the diagnosis.

TELEMATICS SYSTEM (DIAGNOSTICS) > Check List for Interview 
CHECK
1. CHECK LIST FOR INTERVIEW

Inspect the following items regarding the vehicle’s state.

Telematics Check List for Interview

Received   Year   Month   Date   

Customer’s name

Registration No.

Initial year of registration   Year   Month   Date  

Vehicle model

 

Frame number

 

Interviewer

(     )

Inspector

(     )

Engine type

(     )

Odometer reading

(     )

Customer specified content

Date when problem occurred

    Year   Month   Date   

Frequency of trouble occurrence

Always occurs

Sometimes occurs (   times per day,   times per month)

Conditions at event

Weather  Fine  Cloudy  Rainy  Snowy  Others (      )

Temperature   °C (°F)

How often  Always  Once before  Sometimes (   times a day /   times a week /   times a month)

When and how                                  

 

Situations at event

In what situations did it occur?

 Fast Driving  Rough Roads  Parked  Unknown  Other

In what operations did it occur?

 ACC On

 Press i-button or SOS button (left unattended for 10 seconds or more?)

 Operating door lock function with mobile phone

 Operating door unlock function with mobile phone

 Operating horn & hazard function with mobile phone

 Operating own vehicle positioning function

 Unknown  Other

Situations at restoration

What helped the status return to normal?

 Recover on its own ACC Off and On Does not recover Other

Location at event

 Unknown Any Place

 Driving around open areas like in the country

 Driving around hills or mountains

 Driving around cities with large buildings

 Driving around residential areas or no large buildings

 Driving around areas with power lines

 Driving around rough roads or railway tracks

Attach the map showing the location where the malfunction occurred

Error message

Error message displayed                                    

                           

Mobile phone

Mobile phone carrier (Example: Docomo)

Mobile phone model (Example: Apple Iphone6)

Mobile phone OS version (software version information)

WiFi device

Password

Frequency band

Telematics subscription status

 Subscription (   Year   Month   Date   )  Non-contract

RED LED  OFF  ON  Blink

GREEN LED  OFF  ON  Blink

Check result

Reproducibility

 Reproduced  Always  Sometimes  Cannot be reproduced

Condition

 Cold  Warm  At starting  Immediately after starting  During warm-up

 At idle  When start driving  While driving  At acceleration  At deceleration  When applying brake

MSISDN No. of SIM

Diagnostic trouble code

2. LED ILLUMINATION STATUS LIST

RED LED ON

RED LED Flash

RED LED OFF

GREEN LED ON

Collation with the server failed. It is possible that the server/DCM are malfunctioning.

Communication with the server and DCM are operating normally (communication failure with the STARLINK server. DTCs are not found within the vehicle unit.)

GREEN LED Flash

Collation with the server is in progress.

Connection to the server is being attempted and in progress.

GREEN LED OFF

It is possible that communication with the server/DCM are malfunctioning.

It is possible that communication with the server/DCM are malfunctioning.

Telematics function is not activated.

TELEMATICS SYSTEM (DIAGNOSTICS) > General Description 
CAUTION
1. AIRBAG SYSTEM

Before performing diagnosis, refer to “CAUTION” in “General Description” in AIRBAG SYSTEM. AIRBAG SYSTEM>General Description>CAUTION

2. TELEMATICS

Before performing diagnosis, refer to “CAUTION” in “General Description” in ENTERTAINMENT AND MONITORING. ENTERTAINMENT & MONITORING>General Description>CAUTION

TELEMATICS SYSTEM (DIAGNOSTICS) > General Description 
INSPECTION
1. BASIC INSPECTION

Before performing the diagnosis, check the following items which may affect the problems relating to the telematics system.

2.

Check the relay and fuse condition. ENTERTAINMENT & MONITORING>Relay and Fuse

3.

Check harness and connector. Also check grounding.

TELEMATICS SYSTEM (DIAGNOSTICS) > General Description 
PREPARATION TOOL
1. SPECIAL TOOL

ILLUSTRATION

TOOL NUMBER

DESCRIPTION

REMARKS

SUBARU SELECT MONITOR 4

Used for setting of each function and troubleshooting for electrical system.

 

For detailed operation procedures, refer to “Help” of application.

2. GENERAL TOOL

TOOL NAME

REMARKS

Circuit tester

Used for measuring resistance, voltage and current.

DST-i

Used together with Subaru Select Monitor 4.

TELEMATICS SYSTEM (DIAGNOSTICS) > General Description 
SYSTEM BLOCK DIAGRAM

Main signals used between DCM and relevant CM

EPS CM DCM TPMS CAN USB CAN CAN CAN AHL CAN CAN CAN CAN CAN CAN CAN VDC CAN CAN CAN CAN ET-11286 · TCM ECM · REMOTE DOOR LOCK/UNLOCK INFORMATION · REMOTE HORN/HAZARD INFORMATION BODY INTEGRATED UNIT · REMOTE ENGINE STARTER REQUEST SIGNAL KEYLESS ACCESS CM · AT OIL TEMPERATURE INFORMATION · AWD WARNING LIGHT INFORMATION · DTC INFORMATION · ABS WARNING LIGHT INFORMATION · VDC WARNING LIGHT INFORMATION · EBD WARNING LIGHT INFORMATION · DTC INFORMATION · VEHICLE SPEED INFORMATION · DOOR SWITCH INFORMATION · DTC INFORMATION · LOCK/UNLOCK INFORMATION · ALARM INFORMATION BODY INTEGRATED UNIT · ODOMETER INFORMATION · LOW WASHER FLUID WARNING LIGHT INFORMATION · VEHICLE TYPE INFORMATION · DTC INFORMATION COMBINATION METER · MALFUNCTION INDICATOR LIGHT INFORMATION · OIL LEVEL WARNING INFORMATION · ENGINE SPEED · DTC INFORMATION · VIN INFORMATION · STEERING WARNING LIGHT INFORMATION · EyeSight WARNING LIGHT INFORMATION STEREO CAMERA SOLID LINE · DATA TRANSMISSION FOR EMERGENCY CALL · NUMBER OF COLLISION · AIRBAG DEPLOYMENT INFORMATION · COLLISION SIGNAL · DTC INFORMATION · AIRBAG WARNING LIGHT INFORMATION AIRBAG CM · AUTO HEADLIGHT BEAM LEVELER ABNORMAL · AFS INDICATOR SIGNAL · LED HEADLAMP ERROR · SRVD SYSTEM FAILURE FLAG · BSD CAUTION FLAG · RCTA CAUTION FLAG RADAR SENSOR · REMOTE ENGINE STARTER CONTROL SIGNAL KEYLESS ACCESS CM · TELEMATICS REMOTE ENGINE STARTER REAR DEFOGGER ON/OFF · TELEMATICS REMOTE ENGINE STARTER DRIVER'S SEAT HEATER SETTING · TELEMATICS REMOTE ENGINE STARTER PASSENGER'S SEAT HEATER SETTING · TELEMATICS REMOTE ENGINE STARTER BLOW VENT MODE SETTING · TELEMATICS REMOTE ENGINE STARTER REAR A/C ON/OFF · TELEMATICS REMOTE ENGINE STARTER TEMPERATURE SETTING VALUE · TELEMATICS REMOTE ENGINE STARTER FRESH/RECIRC SETTING · TELEMATICS REMOTE ENGINE STARTER ON SIGNAL A/C CM · TELEMATICS DISPLAY REQUEST · Wi-Fi STATUS INFORMATION · POI INFORMATION · DISPLAY RESPONSE · TELEMATICS VOLUME CHANGE REQUEST · TELEMATICS CALL START REQUEST · Wi-Fi SETTING REQUEST · TPMS WARNING · AIR PRESSURE DISPLAY UNIT · TIRE INFLATION PRESSURE DISPLAY VOICE OUTPUT SPEAKER SPEAKER INPUT MICROPHONE OUTPUT MUTE OUTPUT AUDIO · NAVIGATION UNIT AUDIO · NAVIGATION UNIT TELEMATICS BUTTON INPUT INDICATOR ON OUTPUT OVERHEAD CONSOLE (TELEMATICS BUTTON INDICATOR) MICROPHONE POWER SUPPLY OUTPUT VOICE INPUT MICROPHONE VOICE AND DATA TRANSMITTED VOICE AND DATA RECEIVED SERVER TELEMATICS ANTENNA LTE/3G NETWORK GPS INFORMATION GPS ANTENNA LOCAL CAN
TELEMATICS SYSTEM (DIAGNOSTICS) > Electrical Component Location 
LOCATION

(1)

Data link connector

(4)

GPS antenna

(7)

Front speaker

(2)

Telematics sub antenna

(5)

Data communication module (DCM)

(8)

Airbag CM

(3)

Instrument panel speaker

(6)

Audio or navigation unit

(1)

Telematics antenna

(2)

Audio amplifier

(1)

SOS button

(3)

GREEN LED

(5)

Microphone

(2)

RED LED

(4)

i-button

 

For the LED operation condition, refer to “LED operation condition” in “Check List for Interview”. TELEMATICS SYSTEM (DIAGNOSTICS)>Check List for Interview>CHECK > LED ILLUMINATION STATUS LIST

TELEMATICS SYSTEM (DIAGNOSTICS) > Control Module I/O Signal 
SPECIFICATION
1. DATA COMMUNICATION MODULE (DCM)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 1 2 3 4 5 6 7 8 9 11 10 12 13 14 15 16 i270 i271 USB ET-10833 TO A: TO B: TELEMATICS ANTENNA TELEMATICS SUB ANTENNA GPS ANTENNA

Terminal No.

Contents

Measuring condition

Standard

(i270) No. 1

(i270) No. 2

(i270) No. 3

LED GREEN

(i270) No. 4 ←→ Chassis ground

i-button

i-button OFF → ON

1.6 kΩ or more → Less than 1 Ω

(i270) No. 5 ←→ Chassis ground

SOS button

SOS button OFF → ON

1.6 kΩ or more → Less than 1 Ω

(i270) No. 6

BODY CAN H

(i270) No. 7

MAIN CAN L

(i270) No. 8

Ignition power supply

Ignition switch OFF → ON

Less than 1 V → 9 — 16 V

(i270) No. 9

(i270) No. 10

Battery power supply

Always

9 — 16 V

(i270) No. 11

(i270) No. 12

(i270) No. 13

LED RED

(i270) No. 14 ←→ Chassis ground

GND

Always

Less than 1 Ω

(i270) No. 15

(i270) No. 16

BODY CAN L

(i270) No. 17

MAIN CAN H

(i270) No. 18

Collision detection signal

(i270) No. 19

MUTE

(i270) No. 20 ←→ Chassis ground

ACC

Ignition switch OFF → ACC ON

Less than 1 V → 9 — 16 V

(i271) No. 1

Front speaker input LH −

(i271) No. 2

Front speaker output LH −

(i271) No. 3

Front speaker input RH −

(i271) No. 4

Front speaker output RH −

(i271) No. 5

MIC signal OUT

(i271) No. 6

MIC signal IN

(i271) No. 7

MIC DET

(i271) No. 8

MIC 5 V

(i271) No. 9

Front speaker input LH +

(i271) No. 10

Front speaker output LH +

(i271) No. 11

Front speaker input RH +

(i271) No. 12

Front speaker output RH +

(i271) No. 13 ←→ Chassis ground

MIC GND OUT

Always

Less than 1 Ω

(i271) No. 14

MIC GND IN

(i271) No. 15

(i271) No. 16

TELEMATICS SYSTEM (DIAGNOSTICS) > Inspection Mode 
PROCEDURE

It is possible to diagnose the DTC by performing the indicated inspection mode.

After correcting the DTC, perform a necessary inspection mode and make sure that the function is resumed correctly and the DTC is recorded.

1. INSPECTION MODE 1

DTC

Item

Note

U0073

CONTROL MODULE COMMUNICATION BUS OFF

U0074

Control Module Communication Bus "BODY-CAN" Off

U0100

LOST COMMUNICATION WITH ECM/PCM "A"

U0122

LOST COMMUNICATION WITH VEHICLE DYNAMICS CONTROL MODULE

U0140

LOST COMMUNICATION WITH BODY CONTROL MODULE

U0151

LOST COMMUNICATION WITH RESTRAINTS CONTROL MODULE

U0155

LOST COMMUNICATION WITH INSTRUMENT PANEL CLUSTER (IPC) CONTROL MODULE

U0401

INVALID DATA RECEIVED FROM ECM/PCM "A"

U0416

INVALID DATA RECEIVED FROM VEHICLE DYNAMICS CONTROL MODULE

U0452

INVALID DATA RECEIVED FROM RESTRAINTS CONTROL MODULE

B2A01

LTE1 Antenna Circuit

B2A02

LTE2 Antenna Circuit

B2A03

GPS ANTENNA CIRCUIT

B2A07

BACKUP BATTERY CHARGE SYSTEM PERFORMANCE

B2A08

SOS BUTTON CIRCUIT

B2A09

I-CALL BUTTON CIRCUIT

B2A0C

DCM Internal fault

B2A0D

Airbag Signal

B2A0E

MUTE LINE CIRCUIT

B2A0F

BACKUP BATTERY DEGRADATION

B2A10

Battery Voltage High

Inspection steps:

1.

Using the Subaru Select Monitor, perform the clear memory of [Telematics]. COMMON(diag)>Clear memory

2.

Using the Subaru Select Monitor, read the DTC of [Telematics] to check that there is no DTC displayed. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

 

If the DTC is displayed on the screen, the trouble is still present. Perform the diagnosis according to the DTC. After solving the DTC, repeat from step 1).

3.

Turn the ignition switch to OFF.

4.

Turn the ignition switch to ON, and wait for 5 seconds or more.

5.

Using the Subaru Select Monitor, read the DTC of [Telematics] to check that there is no DTC displayed. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

 

If the DTC is displayed on the screen, the trouble is still present. Perform the diagnosis according to the DTC.

2. INSPECTION MODE 2

Inspection steps:

1.

Using the Subaru Select Monitor, perform the clear memory of [Telematics]. COMMON(diag)>Clear memory

2.

Using the Subaru Select Monitor, read the DTC of [Telematics] to check that there is no DTC displayed. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

 

If the DTC is displayed on the screen, the trouble is still present. Perform the diagnosis according to the DTC. After solving the DTC, repeat from step 1).

3.

Turn the ignition switch to OFF.

4.

Close all doors. (The vehicle enters CAN sleep state.)

5.

Wait for approx. 3 minutes. After the indicator goes off, wait for another 1 minute. (DCM standby mode)

6.

Turn the ignition switch to ON, and wait for 5 seconds or more.

7.

Using the Subaru Select Monitor, read the DTC of [Telematics] to check that there is no DTC displayed. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

 

If the DTC is displayed on the screen, the trouble is still present. Perform the diagnosis according to the DTC. After solving the DTC, repeat from step 1).

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure for Subaru Select Monitor Communication 
INSPECTION

When communication with DCM is impossible

Detecting condition:

  • Defective harness connector

  • Power supply circuit malfunction

  • Defective DCM

  • Defective CAN communication circuit

  • Defective Subaru Select Monitor

Trouble symptom:

Communication is impossible between DCM and Subaru Select Monitor.

i288 i288 1 9 8 16 2 10 7 15 3 11 6 14 4 12 5 13 A14 A10 A8 A7 A17 14 6 8 16 4 5 DCM * 2 * 1 i270 A 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 A: i270 12 11 10 9 8 7 6 5 4 3 2 1 i21 B60 56 57 55 54 60 61 62 13 12 9 8 7 11 10 80 79 76 75 74 78 77 59 58 65 66 64 63 69 70 71 72 73 68 67 36 37 35 34 40 41 42 39 38 45 46 44 43 49 50 51 52 53 48 47 16 17 15 14 20 21 22 6 5 4 3 2 1 86 85 84 83 82 81 19 18 25 26 24 23 29 30 31 32 33 28 27 ET-10990 13 B60 i112 J/C i21 *1 *2 *1 *2 : DATA LINK CONNECTOR REF. TO CAN COMMUNICATION SYSTEM REF. TO ENGINE ELECTRICAL SYSTEM : TERMINAL No. OPTIONAL ARRANGEMENT AMONG 10, 11, 12, 13, 14, 15, 16, 17 AND 18 : TERMINAL No. OPTIONAL ARRANGEMENT AMONG 1, 2, 3, 4, 5, 6, 7, 8 AND 9 FB-47F/B FUSE NO. 19(IG) MB-17M/B FUSE NO. 11(B) FB-44F/B FUSE NO. 8(IG) MB-41M/B FUSE NO. 5(B)
 

After the DCM is replaced, registrations of CommCheck and immobilizer system are required. ENTERTAINMENT & MONITORING>Telematics System>OPERATION > REGISTRATION (COMM CHECK)

1. CHECK FUSE.
1.

Turn the ignition switch to OFF.

2.

Check the fuse of the DCM.

Is the check result OK?

2

Replace the fuse. If the replaced fuse blows out easily, repair the ground short circuit in harness between the fuse — DCM connector.

2. CHECK HARNESS (OPEN CIRCUIT).
1.

Disconnect the DCM connector.

2.

Turn the ignition switch to ON.

3.

Using a tester, measure the voltage between DCM connector (harness side) and the chassis ground.

Connector & terminal

(i270) No. 8 (+) Chassis ground (−):

(i270) No. 10 (+) Chassis ground (−):

Is the voltage 10 V or more?

3

Repair the open circuit in the wiring harness between fuse and DCM connector.

3. CHECK HARNESS (OPEN CIRCUIT).
1.

Turn the ignition switch to OFF.

2.

Using a tester, measure the resistance between DCM connector (harness side) and the chassis ground.

Connector & terminal

(i270) No. 14 — Chassis ground:

Is the resistance 1 Ω or less?

4

Repair the open circuit in the wiring harness between fuse and DCM connector.

4. CHECK LAN SYSTEM.

Is the check result OK?

5

Perform the inspection according to the diagnosis for LAN system.

5. CHECK TELEMATICS.
1.

Turn the ignition switch to ON.

2.

Communicate with [Telematics] using the Subaru Select Monitor.

Is communication possible?

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

TELEMATICS SYSTEM (DIAGNOSTICS) > Data Monitor 
OPERATION
 
TELEMATICS SYSTEM (DIAGNOSTICS) > Data Monitor 
LIST

Display

Contents

Standard/Unit

Unit

Trip Count [count]

time

Count

Time Count [msec]

ms

Signal Strength

Current signal strength

%

MSISDN

Phone number of DCM built-in SIM

TimeStamp at ACN Event

Time stamp information at ACN event occurrence

 

The time stamp is displayed in the Coordinated Universal Time (UTC), which is different from actual time at each location. Therefore, time difference needs to be corrected for use.

Example: [12/22 01:30 in UTC time] is corrected as [12/21 20:30 in New York time].

Call Type at ACN Event

Information of ACN event occurrence

No Attempt

ACN

RSSI at ACN Event

Signal strength at ACN event occurrence

0 — 100%

Call Status at ACN Event

Result of call connection at ACN event occurrence

Call Not Started

Service Not Provisioned

No Network Service

Call Ended by Agero

Call Ended by Driver

Call Ended by Exhausted Retry

Call Started

Call Connected

ACN Active

Subscription information on ACN function

FALSE

TRUE

SOS Active

Subscription information on SOS function

FALSE

TRUE

ICALL Active

Subscription information on I-CALL function

FALSE

TRUE

Security Alarm Active

Subscription information on Security Alarm function

FALSE

TRUE

Diagnostic Alert Active

Subscription information on Diagnostic Alert function

FALSE

TRUE

Power Source Status

Operation power supply information (main battery or DCM built-in BUB)

DCM Currently Running On BUB

DCM Currently Running On VBATT

Subscription Status

DCM mode information

Factory Mode

Comm Check

Unsubscribed

Subscribed

Battery Voltage

Voltage information on main battery

0 — 18.5 V

Stored VIN

VIN information stored in DCM

Timestamp at Time of Button Push(1)

Time stamp information at SOS/I-CALL event occurrence (record 1)

 

The time stamp is displayed in the Coordinated Universal Time (UTC), which is different from actual time at each location. Therefore, time difference needs to be corrected for use.

Example: [12/22 01:30 in UTC time] is corrected as [12/21 20:30 in New York time].

Call Type at SOS/ICALL Event(1)

Information of SOS/I-CALL event occurrence (record 1)

No Call

SOS

I-Call

RSSI at SOS/ICALL(1)

Signal strength at SOS/I-CALL event occurrence (record 1)

0 — 100%

Call status at SOS/ICALL Event(1)

Result of call connection at SOS/I-CALL event occurrence (record 1)

Call Not Started

Service Not Provisioned

No Network Service

Call Ended by Agero

Call Ended by Driver

Call Ended by Exhausted Retry

Call Started

Call Connected

Timestamp at Time of Button Push(2)

Time stamp information at SOS/I-CALL event occurrence (record 2)

 

The time stamp is displayed in the Coordinated Universal Time (UTC), which is different from actual time at each location. Therefore, time difference needs to be corrected for use.

Example: [12/22 01:30 in UTC time] is corrected as [12/21 20:30 in New York time].

Call Type at SOS/ICALL Event(2)

Information of SOS/I-CALL event occurrence (record 2)

No Call

SOS

I-Call

RSSI at SOS/ICALL(2)

Signal strength at SOS/I-CALL event occurrence (record 2)

0 — 100%

Call status at SOS/ICALL Event(2)

Result of call connection at SOS/I-CALL event occurrence (record 2)

Call Not Started

Service Not Provisioned

No Network Service

Call Ended by Agero

Call Ended by Driver

Call Ended by Exhausted Retry

Call Started

Call Connected

Timestamp at Time of Button Push(3)

Time stamp information at SOS/I-CALL event occurrence (record 3)

 

The time stamp is displayed in the Coordinated Universal Time (UTC), which is different from actual time at each location. Therefore, time difference needs to be corrected for use.

Example: [12/22 01:30 in UTC time] is corrected as [12/21 20:30 in New York time].

Call Type at SOS/ICALL Event(3)

Information of SOS/I-CALL event occurrence (record 3)

No Call

SOS

I-Call

RSSI at SOS/ICALL(3)

Signal strength at SOS/I-CALL event occurrence (record 3)

0 — 100%

Call status at SOS/ICALL Event(3)

Result of call connection at SOS/I-CALL event occurrence (record 3)

Call Not Started

Service Not Provisioned

No Network Service

Call Ended by Agero

Call Ended by Driver

Call Ended by Exhausted Retry

Call Started

Call Connected

Speaker Gain Level

Speaker specification information (standard or H/K)

Standard Radio/2 Speakers

Premium Radio/4 Speakers

GREEN LED Voltage

GREEN LED voltage information

0 — 18.5 V

RED LED Voltage

RED LED voltage information

0 — 18.5 V

Left Speaker Status

Left speaker connection status

No Speaker Diagnostic Fault(Default)

Output Short to PVDD

Output Short to Ground

Open Load

Shorted Load

Fault Condition

Load Diagnostics

Speaker Muted

Speaker in Play Mode

Right Speaker Status

Right speaker connection status

No Speaker Diagnostic Fault(Default)

Output Short to PVDD

Output Short to Ground

Open Load

Shorted Load

Fault Condition

Load Diagnostics

Speaker Muted

Speaker in Play Mode

WiFi (Device1) :Device Name

WiFi connection (device ): Device name

WiFi (Device1) :IP Address

WiFi connection (device ): IP address

WiFi (Device1) :Connection Start:Date

WiFi connection (device ): Connection start time

WiFi (Device1) :Connection Start:Time

WiFi (Device1) :Connection Time:Date

WiFi connection (device ): Elapsed time since connection

WiFi (Device1) :Connection Time:Time

WiFi (Device2) :Device Name

WiFi connection (device ): Device name

WiFi (Device2) :IP Address

WiFi connection (device ): IP address

WiFi (Device2) :Connection Start:Date

WiFi connection (device ): Connection start time

WiFi (Device2) :Connection Start:Time

WiFi (Device2) :Connection Time:Date

WiFi connection (device ): Elapsed time since connection

WiFi (Device2) :Connection Time:Time

WiFi (Device3) :Device Name

WiFi connection (device ): Device name

WiFi (Device3) :IP Address

WiFi connection (device ): IP address

WiFi (Device3) :Connection Start:Date

WiFi connection (device ): Connection start time

WiFi (Device3) :Connection Start:Time

WiFi (Device3) :Connection Time:Date

WiFi connection (device ): Elapsed time since connection

WiFi (Device3) :Connection Time:Time

WiFi (Device4) :Device Name

WiFi connection (device ): Device name

WiFi (Device4) :IP Address

WiFi connection (device ): IP address

WiFi (Device4) :Connection Start:Date

WiFi connection (device ): Connection start time

WiFi (Device4) :Connection Start:Time

WiFi (Device4) :Connection Time:Date

WiFi connection (device ): Elapsed time since connection

WiFi (Device4) :Connection Time:Time

WiFi (Device5) :Device Name

WiFi connection (device ): Device name

WiFi (Device5) :IP Address

WiFi connection (device ): IP address

WiFi (Device5) :Connection Start:Date

WiFi connection (device ): Connection start time

WiFi (Device5) :Connection Start:Time

WiFi (Device5) :Connection Time:Date

WiFi connection (device ): Elapsed time since connection

WiFi (Device5) :Connection Time:Time

WiFi (Device6) :Device Name

WiFi connection (device ): Device name

WiFi (Device6) :IP Address

WiFi connection (device ): IP address

WiFi (Device6) :Connection Start:Date

WiFi connection (device ): Connection start time

WiFi (Device6) :Connection Start:Time

WiFi (Device6) :Connection Time:Date

WiFi connection (device ): Elapsed time since connection

WiFi (Device6) :Connection Time:Time

WiFi (Device7) :Device Name

WiFi connection (device ): Device name

WiFi (Device7) :IP Address

WiFi connection (device ): IP address

WiFi (Device7) :Connection Start:Date

WiFi connection (device ): Connection start time

WiFi (Device7) :Connection Start:Time

WiFi (Device7) :Connection Time:Date

WiFi connection (device ): Elapsed time since connection

WiFi (Device7) :Connection Time:Time

WiFi (Device8) :Device Name

WiFi connection (device ): Device name

WiFi (Device8) :IP Address

WiFi connection (device ): IP address

WiFi (Device8) :Connection Start:Date

WiFi connection (device ): Connection start time

WiFi (Device8) :Connection Start:Time

WiFi (Device8) :Connection Time:Date

WiFi connection (device ): Elapsed time since connection

WiFi (Device8) :Connection Time:Time

MAC Address

MAC address

SOC ver

SOC version

VuC ver

VuC version

WiFi ver

WiFi software version

Remote Battery Charging Timer Active

Subscription information on remote battery charging timer function

FALSE

TRUE

Curfew Active

Subscription information on curfew function

FALSE

TRUE

Driving Recorder Active

Subscription information on driving recorder function

FALSE

TRUE

Geo Fencing Active

Subscription information on geo-fencing function

FALSE

TRUE

Remote Horn & Light Active

Subscription information on remote horn & light function

FALSE

TRUE

Over The Air Active

Subscription information on OTA function

FALSE

TRUE

Concierge Active

Subscription information on concierge function

FALSE

TRUE

POI Active

Subscription information on POI function

FALSE

TRUE

Remote Door Lock Active

Subscription information on remote door lock function

FALSE

TRUE

Remote Door Unlock Active

Subscription information on remote door unlock function

FALSE

TRUE

Remote Engine Starter Active

Subscription information on remote engine starter function

FALSE

TRUE

Remote Vehicle Mobilization Active

Subscription information on remote vehicle mobilization function

FALSE

TRUE

Remote Vehicle Immobilization Active

Subscription information on remote vehicle immobilization function

FALSE

TRUE

Service Appointment Scheduler Active

Subscription information on service appointment scheduler function

FALSE

TRUE

Speed Alert Active

Subscription information on speed alert function

FALSE

TRUE

Stolen Vehicle Recovery Plus Active

Subscription information on stolen vehicle recovery plus function

FALSE

TRUE

IGN OFF Data Feed Active

Subscription information on IGN OFF data feed function

FALSE

TRUE

Vehicle Locator Active

Subscription information on vehicle locater function

FALSE

TRUE

TELEMATICS SYSTEM (DIAGNOSTICS) > Freeze Frame Data 
OPERATION
 
TELEMATICS SYSTEM (DIAGNOSTICS) > Freeze Frame Data 
LIST

Display

Content

Standard/Unit

Note

Trip Count

time

Count

Time Count

ms

TELEMATICS SYSTEM (DIAGNOSTICS) > Active Test 
OPERATION
1.

On [Start] screen, select [Diagnosis].

2.

On [Vehicle selection] screen, input the target vehicle information and select [OK].

3.

On [Main Menu] screen, select [Each System].

4.

On [Select System] screen, select [Telematics], and then select [Enter].

5.

On [Select Function] screen, select [Active Test].

 

For detailed operation procedures, refer to “Help” of application.

TELEMATICS SYSTEM (DIAGNOSTICS) > Active Test 
LIST

Active test items

Contents

Execution condition

GREEN LED Lighting

Turn GREEN LED to ON/flashing/OFF.

GREEN LED Flashing

GREEN LED OFF

RED LED Lighting

Turn RED LED to ON/flashing/OFF.

RED LED Flashing

RED LED OFF

Speaker ON

Outputs to speaker.

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Trouble Code (DTC) 
OPERATION
 
TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Trouble Code (DTC) 
LIST

Code

Description & trouble part

Reference

B2A01

LTE1 Antenna Circuit

B2A02

LTE2 Antenna Circuit

B2A03

GPS ANTENNA CIRCUIT

B2A04

MIC CIRCUIT

B2A05

LEFT SPEAKER/AUDIO CIRCUIT

B2A06

RIGHT SPEAKER/AUDIO CIRCUIT

B2A07

BACKUP BATTERY CHARGE SYSTEM PERFORMANCE

B2A08

SOS BUTTON CIRCUIT

B2A09

I-CALL BUTTON CIRCUIT

B2A0A

RED LED CIRCUIT

B2A0B

GREEN LED CIRCUIT

B2A0C

DCM Internal fault

B2A0D

Airbag Signal

B2A0E

MUTE LINE CIRCUIT

B2A0F

BACKUP BATTERY DEGRADATION

B2A10

Battery Voltage High

B2A14

WIFI CHIPSET

B2A15

VIN DATA RESPONSE

B2A16

IMMOBILIZER KEY COLLATION

U0073

CONTROL MODULE COMMUNICATION BUS OFF

U0074

Control Module Communication Bus "BODY-CAN" Off

U0100

LOST COMMUNICATION WITH ECM/PCM "A"

U0122

LOST COMMUNICATION WITH VEHICLE DYNAMICS CONTROL MODULE

U0140

LOST COMMUNICATION WITH BODY CONTROL MODULE

U0151

LOST COMMUNICATION WITH RESTRAINTS CONTROL MODULE

U0155

LOST COMMUNICATION WITH INSTRUMENT PANEL CLUSTER (IPC) CONTROL MODULE

U0401

INVALID DATA RECEIVED FROM ECM/PCM "A"

U0416

INVALID DATA RECEIVED FROM VEHICLE DYNAMICS CONTROL MODULE

U0452

INVALID DATA RECEIVED FROM RESTRAINTS CONTROL MODULE

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A01 LTE1 ANTENNA CIRCUIT

Diagnosis start condition:

When ignition switch is ON.

DTC detecting condition:

Any of the followings continues for 5 seconds or more.

  • LTE1 impedance is more than 1 MΩ. (Detached antenna, etc.)

  • LTE1 impedance is less than 1 kΩ. (Short-circuited antenna, etc.)

Trouble symptom:

  • Telematics function cannot be used.

  • RED LED illuminates.

Wiring diagram:

1 1 AN13 AN4 AN3 2 AN14 1 AN6 AN5 2 AN4 AN5 3 1 2 E1 AN14 DCM AN13 E: E: ET-10991 TELEMATICS ANTENNA
 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A01 displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. CHECK HARNESS (OPEN CIRCUIT).
1.

Turn the ignition switch to OFF.

2.

Disconnect the antenna connector.

3.

Disconnect the DCM connector.

4.

Measure the resistance between antenna connector and DCM connector.

Connector & terminal

(AN13) No. 1 — (AN14) No. 1:

Is the resistance less than 1 Ω?

3

Repair or replace the open circuit of harness.

3. CHECK HARNESS (GROUND SHORT CIRCUIT).

Measure the resistance between DCM connector and chassis ground.

Connector & terminal

(AN13) No. 1 — Chassis ground:

Is the resistance 1 MΩ or more?

4

Repair or replace the short circuit of the harness.

4. CHECK HARNESS (SHORT CIRCUIT TO POWER SUPPLY).
1.

Turn the ignition switch to ON.

2.

Measure the voltage between DCM connector and chassis ground.

Connector & terminal

(AN13) No. 1 (+) — Chassis ground (−):

Is the voltage less than 1 V?

5

Repair or replace the short circuit of the harness.

5. CHECK ANTENNA.
1.

Turn the ignition switch to OFF.

2.

Check the telematics antenna. ENTERTAINMENT & MONITORING>Antenna

Is the check result OK?

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A02 LTE2 ANTENNA CIRCUIT

Diagnosis start condition:

When ignition switch is ON.

DTC detecting condition:

Any of the followings continues for 5 seconds or more.

  • LTE2 impedance is more than 1 MΩ. (Detached antenna, etc.)

  • LTE2 impedance is less than 1 kΩ. (Short-circuited antenna, etc.)

Trouble symptom:

  • Telematics function cannot be used.

  • RED LED illuminates.

 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A02 displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. CHECK ANTENNA.

Visually check the telematics sub antenna. ENTERTAINMENT & MONITORING>Antenna

Is the check result OK?

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A03 GPS ANTENNA CIRCUIT

Diagnosis start condition:

When ignition switch is ON.

DTC detecting condition:

Any of the followings continues for 5 seconds or more.

  • GPS antenna impedance is more than 1 MΩ. (Detached antenna, etc.)

  • GPS antenna impedance is less than 10 Ω. (Short-circuited antenna, etc.)

Trouble symptom:

  • Telematics function cannot be used.

  • RED LED illuminates.

 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A03 displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. CHECK GPS ANTENNA.

Visually check the GPS antenna. ENTERTAINMENT & MONITORING>Antenna

Is the check result OK?

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A04 MIC CIRCUIT

Diagnosis start condition:

When ACC is ON.

DTC detecting condition:

Any of the followings continues for 1 second or more.

  • MIC impedance is more than 10 kΩ. (Detached MIC, etc.)

  • MIC impedance is less than 10 Ω. (Short-circuited MIC, etc.)

Trouble symptom:

  • Call function cannot be used.

  • RED LED illuminates.

Wiring diagram:

16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 B: i271 13 16 15 14 12 11 10 9 8 7 6 5 4 3 2 1 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 R407 R405 7 16 5 R50 i157 6 17 8 R405 R50 B14 B8 B6 DCM i271 B: ET-10992 STEREO CAMERA COVER (MICROPHONE)
 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A04 displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. CHECK HARNESS (OPEN CIRCUIT).
1.

Turn the ignition switch to OFF.

2.

Disconnect the microphone connector.

3.

Disconnect the DCM connector.

4.

Measure the resistance between microphone connector and DCM connector.

Connector & terminal

(R405) No. 5 — (i271) No. 8:

(R405) No. 16 — (i271) No. 14:

(R405) No. 7 — (i271) No. 6:

Is the resistance 1 Ω or less?

3

Repair or replace the open circuit of harness.

3. CHECK HARNESS (GROUND SHORT CIRCUIT).

Measure the resistance between DCM connector and chassis ground.

Connector & terminal

(i271) No. 8 — Chassis ground:

(i271) No. 14 — Chassis ground:

(i271) No. 6 — Chassis ground:

Is the resistance 1 MΩ or more?

4

Repair or replace the short circuit of the harness.

4. CHECK THE CONNECTOR (SHORT CIRCUIT TO POWER SUPPLY).
1.

Turn the ignition switch to ON.

2.

Measure the voltage between DCM connector and chassis ground.

Connector & terminal

(i271) No. 8 (+) — Chassis ground (−):

(i271) No. 14 (+) — Chassis ground (−):

(i271) No. 6 (+) — Chassis ground (−):

Is the voltage less than 1 V?

5

Repair or replace the short circuit of the harness.

5. CHECK MICROPHONE.
1.

Turn the ignition switch to OFF.

2.

Confirm the microphone voice input.

Is the check result OK?

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A05 LEFT SPEAKER/AUDIO CIRCUIT

Diagnosis start condition:

When ACC is ON.

DTC detecting condition:

Speaker impedance is more than 10 kΩ for 100 ms. (Detached speaker connection, etc.)

Trouble symptom:

  • Call function cannot be used.

  • RED LED illuminates.

Wiring diagram:

  • Without audio amplifier

    * 1 * 1 * 1 i166 i167 i168 i169 * 1 * 1 * 1 * 1 * 1 * 1 i169 * 1 * 1 * 1 10 7 12 11 13 14 1 2 3 4 5 6 8 9 41 42 43 44 45 46 35 36 37 38 39 40 28 29 34 33 32 31 30 24 25 27 26 19 20 23 22 21 15 16 18 17 2 4 3 1 i159 i158 2 1 D2 D12 4 3 2 1 D2 i158 i101 D84 i166 i167 i159 D12 J/C i76 D83 i168 D84 D83 1 9 8 16 2 10 7 15 3 11 6 14 4 12 5 13 i271 B: *1 B2 B10 3 1 1 2 B12 B4 i271 B: DCM 6 5 J/C J/C 1 3 2 1 6 5 J/C ET-10993 SIDE TWEETER RH FRONT DOOR SPEAKER RH SIDE TWEETER LH FRONT DOOR SPEAKER LH : TERMINAL No. OPTIONAL ARRANGEMENT
  • With audio amplifier

    i158 i159 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 B: i271 3 4 2 1 i159 B2 B10 4 3 B12 B4 3 4 i158 i271 B: DCM ET-10820 SIDE TWEETER RH SIDE TWEETER LH
 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A05 displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. PERFORM ACTIVE TEST.

Using the Subaru Select Monitor, check the following items in the [Active Test] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Active Test

  • Speaker ON

Does it sound?

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

3

3. CHECK HARNESS (OPEN CIRCUIT).
1.

Turn the ignition switch to OFF.

2.

Disconnect the speaker connector and tweeter connector.

3.

Disconnect the DCM connector.

4.

Measure the resistance between speaker connector and tweeter connector and DCM connector.

Connector & terminal

Without audio amplifier

(i271) No. 2 — (D2) No. 2:

(i271) No. 2 — (i158) No. 1:

(i271) No. 10 — (D2) No. 1:

(i271) No. 10 — (i158) No. 3:

With audio amplifier

(i271) No. 2 — (i158) No. 3:

(i271) No. 10 — (i158) No. 4:

Is the resistance 1 Ω or less?

4

Repair or replace the open circuit of harness.

4. CHECK HARNESS (GROUND SHORT CIRCUIT).

Measure the resistance between DCM connector and chassis ground.

Connector & terminal

(i271) No. 2 — Chassis ground:

(i271) No. 10 — Chassis ground:

Is the resistance 1 MΩ or more?

5

Repair or replace the short circuit of the harness.

5. CHECK THE CONNECTOR (SHORT CIRCUIT TO POWER SUPPLY).
1.

Turn the ignition switch to ON.

2.

Measure the voltage between DCM connector and chassis ground.

Connector & terminal

(i271) No. 2 (+) — Chassis ground (−):

(i271) No. 10 (+) — Chassis ground (−):

Is the voltage less than 1 V?

6

Repair or replace the short circuit of the harness.

6. CHECK THE SPEAKER.
1.

Turn the ignition switch to OFF.

2.

Perform the inspection of speaker unit and tweeter unit. ENTERTAINMENT & MONITORING>Front Speaker

Is the check result OK?

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A06 RIGHT SPEAKER/AUDIO CIRCUIT

Diagnosis start condition:

When ACC is ON.

DTC detecting condition:

Speaker impedance is more than 10 kΩ for 100 ms. (Detached speaker connection, etc.)

Trouble symptom:

  • Call function cannot be used.

  • RED LED illuminates.

Wiring diagram:

  • Without audio amplifier

    * 1 * 1 * 1 i166 i167 i168 i169 * 1 * 1 * 1 * 1 * 1 * 1 i169 * 1 * 1 * 1 10 7 12 11 13 14 1 2 3 4 5 6 8 9 41 42 43 44 45 46 35 36 37 38 39 40 28 29 34 33 32 31 30 24 25 27 26 19 20 23 22 21 15 16 18 17 2 4 3 1 i159 i158 2 1 D2 D12 4 3 2 1 D2 i158 i101 D84 i166 i167 i159 D12 J/C i76 D83 i168 D84 D83 1 9 8 16 2 10 7 15 3 11 6 14 4 12 5 13 i271 B: *1 B2 B10 3 1 1 2 B12 B4 i271 B: DCM 6 5 J/C J/C 1 3 2 1 6 5 J/C ET-10993 SIDE TWEETER RH FRONT DOOR SPEAKER RH SIDE TWEETER LH FRONT DOOR SPEAKER LH : TERMINAL No. OPTIONAL ARRANGEMENT
  • With audio amplifier

    i158 i159 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 B: i271 3 4 2 1 i159 B2 B10 4 3 B12 B4 3 4 i158 i271 B: DCM ET-10820 SIDE TWEETER RH SIDE TWEETER LH
 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A06 displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. PERFORM ACTIVE TEST.

Using the Subaru Select Monitor, check the following items in the [Active Test] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Active Test

  • Speaker ON

Does it sound?

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

3

3. CHECK HARNESS (OPEN CIRCUIT).
1.

Turn the ignition switch to OFF.

2.

Disconnect the speaker connector and tweeter connector.

3.

Disconnect the DCM connector.

4.

Measure the resistance between speaker connector and tweeter connector and DCM connector.

Connector & terminal

Without audio amplifier

(i271) No. 4 — (D12) No. 2:

(i271) No. 4 — (i159) No. 1:

(i271) No. 12 — (D12) No. 1:

(i271) No. 12 — (i159) No. 3:

With audio amplifier

(i271) No. 4 — (i159) No. 3:

(i271) No. 12 — (i159) No. 4:

Is the resistance 1 Ω or less?

4

Repair or replace the open circuit of harness.

4. CHECK HARNESS (GROUND SHORT CIRCUIT).

Measure the resistance between DCM connector and chassis ground.

Connector & terminal

(i271) No. 4 — Chassis ground:

(i271) No. 12 — Chassis ground:

Is the resistance 1 MΩ or more?

5

Repair or replace the short circuit of the harness.

5. CHECK THE CONNECTOR (SHORT CIRCUIT TO POWER SUPPLY).
1.

Turn the ignition switch to ON.

2.

Measure the voltage between DCM connector and chassis ground.

Connector & terminal

(i271) No. 4 (+) — Chassis ground (−):

(i271) No. 12 (+) — Chassis ground (−):

Is the voltage less than 1 V?

6

Repair or replace the short circuit of the harness.

6. CHECK THE SPEAKER.
1.

Turn the ignition switch to OFF.

2.

Perform the inspection of speaker unit and tweeter unit. ENTERTAINMENT & MONITORING>Front Speaker

Is the check result OK?

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A07 BACKUP BATTERY CHARGE SYSTEM PERFORMANCE

Diagnosis start condition:

When ignition switch is ON.

DTC detecting condition:

Backup battery is disconnected for at least 5 seconds when the ignition switch is turned ON. (Detached backup battery connection, etc.)

Trouble symptom:

  • ACN/SOS function cannot be used when the main battery is disconnected.

  • RED LED illuminates.

 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A07 displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. CHECK THE BACKUP BATTERY.
2.

Remove the backup battery cover.

3.

Disconnect the backup battery connector.

4.

Measure the backup battery voltage.

Is the voltage 2.0 V or more?

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A08 SOS BUTTON CIRCUIT

Diagnosis start condition:

When ignition switch is ON.

DTC detecting condition:

The following conditions occur for at least 50 ms.

  • SOS button impedance is more than 10 kΩ.

  • SOS button is stuck for at least 60 seconds.

Trouble symptom:

  • SOS function cannot be used.

  • RED LED illuminates.

Wiring diagram:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 i270 A: 8 7 6 5 4 3 2 1 R463 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 R50 A5 DCM A4 A3 A13 R463 7 4 3 1 6 SOS i i270 A: 12 20 21 1 22 i157 R50 ET-10994 TELEMATICS BUTTON RED LED GREEN LED
 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A08 displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. CHECK HARNESS (OPEN CIRCUIT).
1.

Turn the ignition switch to OFF.

2.

Disconnect the telematics button connector.

3.

Disconnect the DCM connector.

4.

Measure the resistance between telematics button connector and DCM connector.

Connector & terminal

(i270) No. 5 — (R463) No. 6:

(R463) No. 1 — Chassis ground:

Is the resistance 1 Ω or less?

3

Repair or replace the open circuit of harness.

3. CHECK HARNESS (GROUND SHORT CIRCUIT).

Measure the resistance between DCM connector and chassis ground.

Connector & terminal

(i270) No. 5 — Chassis ground:

Is the resistance 1 MΩ or more?

4

Repair or replace the short circuit of the harness.

4. CHECK THE CONNECTOR (SHORT CIRCUIT TO POWER SUPPLY).
1.

Turn the ignition switch to ON.

2.

Measure the voltage between DCM connector and chassis ground.

Connector & terminal

(i270) No. 5 (+) — Chassis ground (−):

(R463) No. 1 (+) — Chassis ground (−):

Is the voltage less than 1 V?

5

Repair or replace the short circuit of the harness.

5. CHECK THE SOS BUTTON UNIT.
1.

Turn the ignition switch to OFF.

2.

Measure the resistance of the SOS button unit.

Terminals

No. 6 — No. 1:

Is the resistance 1 Ω or less when SOS button is ON, and 1.51.7 kΩ when SOS button is OFF?

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A09 I-CALL BUTTON CIRCUIT

Diagnosis start condition:

When ignition switch is ON.

DTC detecting condition:

The following conditions occur for at least 50 ms.

  • i-button impedance is more than 10 kΩ.

  • i-button is stuck for at least 60 seconds.

Trouble symptom:

  • i-Call function cannot be used.

  • RED LED illuminates.

Wiring diagram:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 i270 A: 8 7 6 5 4 3 2 1 R463 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 R50 A5 DCM A4 A3 A13 R463 7 4 3 1 6 SOS i i270 A: 12 20 21 1 22 i157 R50 ET-10994 TELEMATICS BUTTON RED LED GREEN LED
 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A09 displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. CHECK HARNESS (OPEN CIRCUIT).
1.

Turn the ignition switch to OFF.

2.

Disconnect the telematics button connector.

3.

Disconnect the DCM connector.

4.

Measure the resistance between telematics button connector and DCM connector.

Connector & terminal

(i270) No. 4 — (R463) No. 3:

(R463) No. 1 — Chassis ground:

Is the resistance 1 Ω or less?

3

Repair or replace the open circuit of harness.

3. CHECK HARNESS (GROUND SHORT CIRCUIT).

Measure the resistance between DCM connector and chassis ground.

Connector & terminal

(i270) No. 4 — Chassis ground:

Is the resistance 1 MΩ or more?

4

Repair or replace the short circuit of the harness.

4. CHECK THE CONNECTOR (SHORT CIRCUIT TO POWER SUPPLY).
1.

Turn the ignition switch to ON.

2.

Measure the voltage between DCM connector and chassis ground.

Connector & terminal

(i270) No. 4 (+) — Chassis ground (−):

(R463) No. 1 (+) — Chassis ground (−):

Is the voltage less than 1 V?

5

Repair or replace the short circuit of the harness.

5. CHECK THE I-BUTTON.
1.

Turn the ignition switch to OFF.

2.

Measure the resistance of the i-button unit.

Terminals

No. 3 — No. 1:

Is the resistance 1 Ω or less when i-button is ON, and 1.51.7 kΩ when i-button is OFF?

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A0A RED LED CIRCUIT

Diagnosis start condition:

When ACC is ON.

DTC detecting condition:

The following conditions occur for at least 50 ms.

  • Current in RED LED is less than 1 mA. (Improper RED LED connection, etc.)

  • Current in RED LED is more than 200 mA. (Short-circuited RED LED, etc.)

Trouble symptom:

LED does not illuminate.

Wiring diagram:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 i270 A: 8 7 6 5 4 3 2 1 R463 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 R50 A5 DCM A4 A3 A13 R463 7 4 3 1 6 SOS i i270 A: 12 20 21 1 22 i157 R50 ET-10994 TELEMATICS BUTTON RED LED GREEN LED
 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A0A displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. PERFORM ACTIVE TEST.

Using the Subaru Select Monitor, check the following items in the [Active Test] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Active Test

  • RED LED Lighting

Does the LED light illuminate?

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

3

3. CHECK HARNESS (OPEN CIRCUIT).
1.

Turn the ignition switch to OFF.

2.

Disconnect the telematics button connector.

3.

Disconnect the DCM connector.

4.

Measure the resistance between telematics button connector and DCM connector.

Connector & terminal

(i270) No. 13 — (R463) No. 7:

(R463) No. 1 — Chassis ground:

Is the resistance 1 Ω or less?

4

Repair or replace the open circuit of harness.

4. CHECK HARNESS (GROUND SHORT CIRCUIT).

Measure the resistance between DCM connector and chassis ground.

Connector & terminal

(i270) No. 13 — Chassis ground:

Is the resistance 1 MΩ or more?

5

Repair or replace the short circuit of the harness.

5. CHECK THE CONNECTOR (SHORT CIRCUIT TO POWER SUPPLY).
1.

Turn the ignition switch to ON.

2.

Measure the voltage between DCM connector and chassis ground.

Connector & terminal

(i270) No. 13 (+) — Chassis ground (−):

(R463) No. 1 (+) — Chassis ground (−):

Is the voltage less than 1 V?

6

Repair or replace the short circuit of the harness. After the repair, 7

6. CHECK THE TELEMATICS BUTTON (LED) UNIT.
1.

Turn the ignition switch to OFF.

2.

Check that RED LED illuminates when applying the battery voltage to it.

 

Never connect the battery voltage terminals in reverse polarity, because reversed connection damages the telematics button (LED).

Terminals

No. 7 (+) — No. 1 (−):

Does the RED LED illuminate?

7. CHECK THE TELEMATICS BUTTON (LED) UNIT.
1.

Turn the ignition switch to OFF.

2.

Check that RED LED illuminates when applying the battery voltage to it.

 

Never connect the battery voltage terminals in reverse polarity, because reversed connection damages the telematics button (LED).

Terminals

No. 7 (+) — No. 1 (−):

Does the RED LED illuminate?

RED LED is not malfunctioning. Finish the diagnosis.

Replace the telematics button. ENTERTAINMENT & MONITORING>Switches and Harness

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A0B GREEN LED CIRCUIT

Diagnosis start condition:

When ACC is ON.

DTC detecting condition:

The following conditions occur for at least 50 ms.

  • Current in GREEN LED is less than 1 mA. (Improper GREEN LED connection, etc.)

  • Current in GREEN LED is more than 200 mA. (Short-circuited GREEN LED, etc.)

Trouble symptom:

RED LED illuminates.

Wiring diagram:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 i270 A: 8 7 6 5 4 3 2 1 R463 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 R50 A5 DCM A4 A3 A13 R463 7 4 3 1 6 SOS i i270 A: 12 20 21 1 22 i157 R50 ET-10994 TELEMATICS BUTTON RED LED GREEN LED
 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A0B displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. PERFORM ACTIVE TEST.

Using the Subaru Select Monitor, check the following items in the [Active Test] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Active Test

  • GREEN LED Lighting

Does the LED light illuminate?

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

3

3. CHECK HARNESS (OPEN CIRCUIT).
1.

Turn the ignition switch to OFF.

2.

Disconnect the telematics button connector.

3.

Disconnect the DCM connector.

4.

Measure the resistance between telematics button connector and DCM connector.

Connector & terminal

(i270) No. 3 — (R463) No. 4:

(R463) No. 1 — Chassis ground:

Is the resistance 1 Ω or less?

4

Repair or replace the open circuit of harness.

4. CHECK HARNESS (GROUND SHORT CIRCUIT).

Measure the resistance between DCM connector and chassis ground.

Connector & terminal

(i270) No. 3 — Chassis ground:

Is the resistance 1 MΩ or more?

5

Repair or replace the short circuit of the harness.

5. CHECK THE CONNECTOR (SHORT CIRCUIT TO POWER SUPPLY).
1.

Turn the ignition switch to ON.

2.

Measure the voltage between DCM connector and chassis ground.

Connector & terminal

(i270) No. 3 (+) — Chassis ground (−):

(R463) No. 1 (+) — Chassis ground (−):

Is the voltage less than 1 V?

6

Repair or replace the short circuit of the harness. After the repair, 7

6. CHECK THE TELEMATICS BUTTON (LED) UNIT.
1.

Turn the ignition switch to OFF.

2.

Check that GREEN LED illuminates when applying the battery voltage to it.

 

Never connect the battery voltage terminals in reverse polarity, because reversed connection damages the telematics button (LED).

Terminals

No. 4 (+) — No. 1 (−):

Does the GREEN LED illuminate?

7. CHECK THE TELEMATICS BUTTON (LED) UNIT.
1.

Turn the ignition switch to OFF.

2.

Check that GREEN LED illuminates when applying the battery voltage to it.

 

Never connect the battery voltage terminals in reverse polarity, because reversed connection damages the telematics button (LED).

Terminals

No. 4 (+) — No. 1 (−):

Does the GREEN LED illuminate?

GREEN LED is not malfunctioning. Finish the diagnosis.

Replace the telematics button. ENTERTAINMENT & MONITORING>Switches and Harness

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A0C DCM INTERNAL FAULT

Diagnosis start condition:

When ignition switch is ON.

DTC detecting condition:

  • Main microcomputer and communication circuit IC cannot communicate. (Defective IPC)

  • SIM (communication chip) cannot be read. (Defective SIM 1)

Trouble symptom:

  • Telematics function cannot be used.

  • RED LED illuminates.

 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A0C displayed? (Current malfunction)

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A0D AIRBAG SIGNAL

Diagnosis start condition:

When ignition switch is ON.

DTC detecting condition:

Either the regular signal or collision detection signal cannot be detected from the airbag CM for at least 30 seconds.

Trouble symptom:

  • ACN function does not operate.

  • RED LED illuminates.

Wiring diagram:

44 43 42 41 40 45 20 39 19 38 18 37 17 36 16 35 15 34 14 33 13 32 12 31 11 30 10 29 9 28 8 27 7 26 6 25 5 24 4 23 3 22 2 21 1 A: AB6 i270 A: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 i270 A: A18 AB6 DCM A36 A: ET-10822 AIRBAG CM
 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A0D displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. CHECK DTC.

Read the DTC of [Airbag] using the Subaru Select Monitor. AIRBAG(DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Are any DTCs displayed? (Current malfunction)

Perform the diagnosis for the displayed DTCs of airbag. AIRBAG(DIAGNOSTICS)>Diagnostic Trouble Code (DTC)>LIST

3

3. CHECK HARNESS (OPEN CIRCUIT).
1.

Turn the ignition switch to OFF.

2.

Disconnect the airbag CM connector.

3.

Disconnect the DCM connector.

4.

Measure the resistance between airbag CM connector and DCM connector.

 

To measure the voltage and resistance of airbag system component, be sure to use the specified test harness. AIRBAG(DIAGNOSTICS)>General Description

Connector & terminal

(i270) No. 18 — (2BD) No. 9:

Is the resistance 1 Ω or less?

4

Repair or replace the open circuit of harness.

4. CHECK HARNESS (GROUND SHORT CIRCUIT).

Measure the resistance between DCM connector and chassis ground.

Connector & terminal

(i270) No. 18 — Chassis ground:

Is the resistance 1 MΩ or more?

5

Repair or replace the short circuit of the harness.

5. CHECK THE CONNECTOR (SHORT CIRCUIT TO POWER SUPPLY).
1.

Turn the ignition switch to ON.

2.

Measure the voltage between DCM connector and chassis ground.

Connector & terminal

(i270) No. 18 (+) — Chassis ground (−):

Is the voltage less than 1 V?

Repair or replace the short circuit of the harness.

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A0E MUTE LINE CIRCUIT

Diagnosis start condition:

When ignition switch is ON.

DTC detecting condition:

Any of the following conditions occurs continuously for five seconds or more after the ignition switch is turned to ON when DCM does not mute the audio or navigation system.

  • Current in the mute line is less than 1 mA. (Improper line connection, etc.)

  • Current exceeds 50 mA. (Short-circuited line, etc.)

Trouble symptom:

  • The mute function of audio or navigation system does not operate.

  • RED LED illuminates.

Wiring diagram:

i270 A: i87 C: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 i270 A: 24 26 25 28 27 15 17 16 19 18 21 20 23 22 10 12 11 14 13 1 3 2 5 4 7 6 9 8 C: i87 A19 DCM C24 ET-10344 AUDIO OR NAVIGATION
 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A0E displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. CHECK HARNESS (OPEN CIRCUIT).
1.

Turn the ignition switch to OFF.

2.

Disconnect the audio or navigation connector.

3.

Disconnect the DCM connector.

4.

Measure the resistance between audio or navigation connector and DCM connector.

Connector & terminal

(i270) No. 19 — (i87) No. 24:

Is the resistance 1 Ω or less?

3

Repair or replace the open circuit of harness.

3. CHECK HARNESS (GROUND SHORT CIRCUIT).

Measure the resistance between DCM connector and chassis ground.

Connector & terminal

(i270) No. 19 — Chassis ground:

Is the resistance 1 MΩ or more?

4

Repair or replace the short circuit of the harness.

4. CHECK THE CONNECTOR (SHORT CIRCUIT TO POWER SUPPLY).
1.

Turn the ignition switch to ON.

2.

Measure the voltage between DCM connector and chassis ground.

Connector & terminal

(i270) No. 19 (+) — Chassis ground (−):

Is the voltage less than 1 V?

Repair or replace the short circuit of the harness.

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A0F BACKUP BATTERY DEGRADATION

Diagnosis start condition:

When ignition switch is ON.

DTC detecting condition:

The voltage does not reach 4.1 V after the backup battery is charged for 7 hours in total (not continuously).

Trouble symptom:

RED LED illuminates.

 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A0F displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. CHECK THE BACKUP BATTERY.

Is the check result OK?

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A10 BATTERY VOLTAGE HIGH

Diagnosis start condition:

When ignition switch is ON.

DTC detecting condition:

DCM battery power supply input of 16 V or more continues for 5 seconds.

Trouble symptom:

RED LED illuminates.

 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A10 displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. CHECK DATA MONITOR.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Battery voltage

Is the [Battery voltage] OK?

3. CHECK BATTERY.
TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A14 WIFI CHIPSET

Diagnosis start condition:

When ignition switch is ON.

DTC detecting condition:

When SOC reset is performed with WiFi malfunction flag detection, and the malfunction flag does not return after three attempts.

Trouble symptom:

RED LED ON

 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A14 displayed? (Current malfunction)

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A15 VIN DATA RESPONSE

Diagnosis start condition:

When ignition switch is ON.

DTC detecting condition:

When ignition switch is ON, VIN information (CAN) sent from ECM cannot be read.

Trouble symptom:

  • Telematics function cannot be used.

  • RED LED illuminates.

 
 

A DTC may be displayed if non-genuine products such as self-diagnosis tools are connected to the date link connector or accessory connector.

1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A15 displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. CHECK DTC.
  • Telematics

  • Engine Control System

Is DTC U∗∗∗∗ displayed? (Current malfunction)

Perform the diagnosis for LAN system. LAN SYSTEM (DIAGNOSTICS)>Basic Diagnostic Procedure

3

3. CHECK NON-GENUINE PRODUCT CONNECTION.
1.

Remove non-genuine products connected to the date link connector or accessory connector.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A15 displayed? (Current malfunction)

4

  • Effects of non-genuine products.

  •  

    When using Subaru telematics, remove non-genuine products. When not using Subaru telematics, leave them as they are.

4. CHECK DATA MONITOR.
TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC B2A16 IMMOBILIZER KEY COLLATION

Diagnosis start condition:

When ignition switch is ON.

DTC detecting condition:

When DCM received a remote request and couldn’t detect valid cryptographic key within three seconds.

Trouble symptom:

RED LED ON

 
1. CHECK DTC.
1.

Turn the ignition switch to ON.

2.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC B2A16 displayed? (Current malfunction)

2

  • Even if DTC is displayed, the circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

     

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

2. CHECK IGNITION KEY.
1.

Prepare all the pre-registered ignition keys.

2.

Using the Subaru Select Monitor, check the ignition key registration. Refer to the “REGISTRATION MANUAL FOR IMMOBILIZER” provided as a separate volume.

Is an ignition key registered?

3. CHECK BATTERY.
TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC U0073 CONTROL MODULE COMMUNICATION BUS OFF

Detected when CAN line abnormality is detected.

 
TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC U0074 CONTROL MODULE COMMUNICATION BUS "BODY-CAN" OFF

Detected when CAN line abnormality is detected.

 
TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC U0100 LOST COMMUNICATION WITH ECM/PCM "A"

Detected when CAN data from ECM does not arrive.

 
TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC U0122 LOST COMMUNICATION WITH VEHICLE DYNAMICS CONTROL MODULE

Detected when CAN data from VDC CM does not arrive.

 
TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC U0140 LOST COMMUNICATION WITH BODY CONTROL MODULE

Detected when CAN data is not received from body integrated unit.

 
TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC U0151 LOST COMMUNICATION WITH RESTRAINTS CONTROL MODULE

Detected when CAN data is not received from airbag CM.

 
TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC U0155 LOST COMMUNICATION WITH INSTRUMENT PANEL CLUSTER (IPC) CONTROL MODULE

Detected when CAN data from combination meter does not arrive.

 
TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC U0401 INVALID DATA RECEIVED FROM ECM/PCM "A"

Detected when CAN data from ECM is abnormal.

 
TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC U0416 INVALID DATA RECEIVED FROM VEHICLE DYNAMICS CONTROL MODULE

Detected when CAN data from VDC CM is abnormal.

 
TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostic Procedure with Diagnostic Trouble Code (DTC) 
DTC U0452 INVALID DATA RECEIVED FROM RESTRAINTS CONTROL MODULE

Detected when CAN data from airbag CM is abnormal.

 
TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostics with Phenomenon 
LIST

No.

Symptoms

Reference

1

The system does not notify the Telematics Service Provider Center automatically after collision.

2

The system does not notify the center even if the SOS button is pressed.

3

The system places an SOS call unintentionally during driving.

4

The system places an I-CALL unintentionally during driving.

5

The system does not notify the center even if the i-button is pressed upon vehicle malfunction.

6

Remote Vehicle Locator cannot locate the vehicle.

7

Remote Vehicle Locator indicates an incorrect location and therefore the vehicle cannot be located.

8

Remote Door Lock does not lock the doors of the vehicle.

9

The doors lock unintentionally.

10

The doors unlock unintentionally.

11

Remote horn & hazard lights do not operate upon request.

12

When the Vehicle Security Alarm is activated, notification is not sent.

13

When a Malfunction indicator light/warning light is lit, notification is not sent.

14

Maintenance Notifications are not sent.

15

The LED does not display the status. (LED malfunction)

16

Phone conversation is not possible. (The microphone does not respond to a voice. No sound is heard from the speaker.)

17

Telematics remote engine starter/RES air conditioner does not function.

18

Curfew does not operate.

19

Service appointment scheduler does not operate.

20

Geo Fencing does not operate.

21

Remote vehicle condition check does not operate.

22

Speed alert does not operate.

23

Concierge does not operate.

24

Navigation function link does not operate.

25

FOTA does not operate.

26

The device cannot be registered to WiFi HotSpot.

27

WiFi HotSpot does not operate/connection to the Internet fails

28

Engine will not start

TELEMATICS SYSTEM (DIAGNOSTICS) > Diagnostics with Phenomenon 
INSPECTION
1. THE SYSTEM DOES NOT NOTIFY THE TELEMATICS SERVICE PROVIDER CENTER AUTOMATICALLY AFTER COLLISION

Probable cause:

Airbag CM malfunction, no contract agreement, out of service area, DCM malfunction, antenna malfunction, server side malfunction, smartphone malfunction

 
 

Perform the diagnostics for “Phone conversation is not possible. (The microphone does not respond to a voice. No sound is heard from the speaker.)”. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostics with Phenomenon>INSPECTION > PHONE CONVERSATION IS NOT POSSIBLE. (THE MICROPHONE DOES NOT RESPOND TO A VOICE. NO SOUND IS HEARD FROM THE SPEAKER.)

1. CHECK COLLISION TYPE.
no
yes
2. CHECK AIRBAG WARNING LIGHT.
no

Perform the instructed procedures.

yes
3. CHECK DTCS.
yes
no

Perform the instructed procedures.

4. CHECK COLLISION DETECTION SIGNAL RECEPTION STATUS.
yes
no
5. CHECK DTCS.
yes

Perform the instructed procedures.

no
6. CHECK AIRBAG WARNING LIGHT.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

7. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
8. CHECK DTCS.
yes

Perform the instructed procedures.

no
9. CHECK THE RECEIVED SIGNAL STRENGTH AT THE TIME OF THE ACCIDENT (CHECK THE DATA MONITOR).
yes
no
10. CHECK THE AT&T CELLULAR COVERAGE AREA.
no

Perform the instructed procedures.

yes
11. CHECK THE COMMUNICATION STATUS AT THE TIME OF THE ACCIDENT (CHECK THE DATA MONITOR).
choice
choice

Perform the instructed procedures.

choice

Perform the instructed procedures.

choice

Perform the instructed procedures.

12. CHECK THE TIME OF THE ACCIDENT (CHECK THE DATA MONITOR).
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK COLLISION TYPE.

Check the type of collision of the vehicle.

Is it a frontal collision, or a side collision, or a rollover?

2

For rear collision, 4

2. CHECK AIRBAG WARNING LIGHT.

Check the airbag warning light.

Does the airbag warning light illuminate at all times?

3

There is no malfunction in the airbag system. Since the airbag CM does not transmit the collision detection signal in the event of a minor collision, it is normal that the automatic notification function does not work.

3. CHECK DTCS.

Read the DTC of [Airbag] using the Subaru Select Monitor. AIRBAG(DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is any of the DTC [Front Impact Deployment], [Side Impact Deployment], or [Rollover Ignition] displayed?

There is no malfunction in the airbag system. 7

Perform the diagnosis for the airbag system. AIRBAG(DIAGNOSTICS)>Basic Diagnostic Procedure

4. CHECK COLLISION DETECTION SIGNAL RECEPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • TimeStamp at ACN Event:Date

  • TimeStamp at ACN Event:UTC ∗UTC is the basis for local times worldwide.

Is a time stamp recorded?

7 (Rear collision detection was activated)

5

5. CHECK DTCS.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Are any DTCs displayed?

Perform the diagnosis for the displayed DTCs. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)>LIST

6

6. CHECK AIRBAG WARNING LIGHT.

Check the airbag warning light.

Does the airbag warning light illuminate at all times?

Perform the diagnosis for the airbag system. AIRBAG(DIAGNOSTICS)>Basic Diagnostic Procedure

There is no malfunction in the airbag system. Since the airbag CM does not transmit the collision detection signal in the event of a minor collision, it is normal that the automatic notification function does not work.

7. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • ACN Active

Is the data [TRUE]?

8

The user does not have a service subscription; therefore, it is not a failure.

8. CHECK DTCS.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Are any DTCs displayed?

Perform the diagnosis for the displayed DTCs. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)>LIST

9

9. CHECK THE RECEIVED SIGNAL STRENGTH AT THE TIME OF THE ACCIDENT (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • RSSI at ACN Event

Is the data 26% or more?

11

10

10. CHECK THE AT&T CELLULAR COVERAGE AREA.

Check whether the collision occurred within the cellular coverage area.

Is the location where the collision occurred within the cellular coverage area? (For the cellular coverage area, refer to the AT&T website. The system operates only on 3G and 4G technology.)

11

The collision occurred outside the cellular coverage area.

11. CHECK THE COMMUNICATION STATUS AT THE TIME OF THE ACCIDENT (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Call Type at ACN Event

If the data shows [Call Started] or [Call Connected]; Go to A.

If the data shows [Call Not Started]; Go to B.

If the data shows [No Network Service]; Go to C.

If the data shows [Call Ended by Agero]; Go to D.

A

12

C

Replace the antenna. ENTERTAINMENT & MONITORING>Antenna

D

The connection ended due to a server-side reason; therefore, there is no failure on the vehicle.

12. CHECK THE TIME OF THE ACCIDENT (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • TimeStamp at ACN Event:Date

  • TimeStamp at ACN Event:UTC ∗UTC is the basis for local times worldwide.

 

The time stamp is displayed in the Coordinated Universal Time (UTC), which is different from actual time at each location. Therefore, time difference needs to be corrected for use.

Example: [12/22 01:30 in UTC time] is corrected as [12/21 20:30 in New York time].

Does the time of the accident match with the data?

2. THE SYSTEM DOES NOT NOTIFY THE CENTER EVEN IF THE SOS BUTTON IS PRESSED

Probable cause:

No contract agreement, out of service area, DCM malfunction, antenna malfunction, server side malfunction, SOS button malfunction

 
 

Perform the diagnostics for “Phone conversation is not possible. (The microphone does not respond to a voice. No sound is heard from the speaker.)”. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostics with Phenomenon>INSPECTION > PHONE CONVERSATION IS NOT POSSIBLE. (THE MICROPHONE DOES NOT RESPOND TO A VOICE. NO SOUND IS HEARD FROM THE SPEAKER.)

1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK DTCS.
yes

Perform the instructed procedures.

no
3. CHECK THE RECEIVED SIGNAL STRENGTH WHEN THE SOS BUTTON WAS PRESSED (CHECK THE DATA MONITOR).
yes
no
4. CHECK THE AT&T CELLULAR COVERAGE AREA.
no

Perform the instructed procedures.

yes
5. CHECK THE COMMUNICATION STATUS OF WHEN THE SOS BUTTON WAS PRESSED (CHECK THE DATA MONITOR).
choice
choice
choice

Perform the instructed procedures.

choice

Perform the instructed procedures.

6. CHECK THE TIME OF WHEN THE SOS BUTTON WAS PRESSED (CHECK THE DATA MONITOR).
no

Perform the instructed procedures.

yes
7. CHECK THE SOS BUTTON.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • SOS Active

Is the data [TRUE]?

2

The user does not have a service subscription; therefore, it is not a failure.

2. CHECK DTCS.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Are any DTCs displayed?

Perform the diagnosis for the displayed DTCs. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)>LIST

3

3. CHECK THE RECEIVED SIGNAL STRENGTH WHEN THE SOS BUTTON WAS PRESSED (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • RSSI at SOS/ICALL(1)

Is the data 26% or more?

5

4

4. CHECK THE AT&T CELLULAR COVERAGE AREA.

Check whether the SOS button was pressed within the cellular coverage area.

Is the location where the SOS button was pressed within the cellular coverage area? (For the cellular coverage area, refer to the AT&T website. The system operates only on 3G and 4G technology.)

5

The SOS button was pressed outside the cellular coverage area.

5. CHECK THE COMMUNICATION STATUS OF WHEN THE SOS BUTTON WAS PRESSED (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Call status at SOS/ICALL Event(1)

If the data shows [Call Started] or [Call Connected]; Go to A.

If the data shows [Call Not Started]; Go to B.

If the data shows [No Network Service]; Go to C.

If the data shows [Call Ended by Agero]; Go to D.

A

6

B

7

C

Replace the antenna. ENTERTAINMENT & MONITORING>Antenna

D

The connection ended due to a server-side reason; therefore, there is no failure on the vehicle.

6. CHECK THE TIME OF WHEN THE SOS BUTTON WAS PRESSED (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Timestamp at Time of Button Push(1):Date

  • Timestamp at Time of Button Push(1):UTC ∗UTC is the basis for local times worldwide.

 

The time stamp is displayed in the Coordinated Universal Time (UTC), which is different from actual time at each location. Therefore, time difference needs to be corrected for use.

Example: [12/22 01:30 in UTC time] is corrected as [12/21 20:30 in New York time].

Does the time of the SOS button operation match with the data?

3. THE SYSTEM PLACES AN SOS CALL UNINTENTIONALLY DURING DRIVING

Probable cause:

DCM malfunction, SOS button malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK DTCS.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK DTCS.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Are any DTCs displayed?

4. THE SYSTEM PLACES AN I-CALL UNINTENTIONALLY DURING DRIVING

Probable cause:

DCM malfunction, i-button malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK DTCS.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK DTCS.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Are any DTCs displayed?

5. THE SYSTEM DOES NOT NOTIFY THE CENTER EVEN IF THE I-BUTTON IS PRESSED UPON VEHICLE MALFUNCTION

Probable cause:

No contract agreement, out of service area, DCM malfunction, antenna malfunction, server side malfunction, i-button malfunction

 
 

Perform the diagnostics for “Phone conversation is not possible. (The microphone does not respond to a voice. No sound is heard from the speaker.)”. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostics with Phenomenon>INSPECTION > PHONE CONVERSATION IS NOT POSSIBLE. (THE MICROPHONE DOES NOT RESPOND TO A VOICE. NO SOUND IS HEARD FROM THE SPEAKER.)

1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK DTCS.
yes

Perform the instructed procedures.

no
3. CHECK THE RECEIVED SIGNAL STRENGTH WHEN THE I-BUTTON WAS PRESSED (CHECK THE DATA MONITOR).
yes
no
4. CHECK THE AT&T CELLULAR COVERAGE AREA.
no

Perform the instructed procedures.

yes
5. CHECK THE COMMUNICATION STATUS OF WHEN THE I-BUTTON WAS PRESSED (CHECK THE DATA MONITOR).
choice
choice
choice

Perform the instructed procedures.

choice

Perform the instructed procedures.

6. CHECK THE COMMUNICATION STATUS OF WHEN THE I-BUTTON WAS PRESSED (CHECK THE DATA MONITOR).
no

Perform the instructed procedures.

yes
7. CHECK THE I-BUTTON.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • ICALL Active

Is the data [TRUE]?

2

The user does not have a service subscription; therefore, it is not a failure.

2. CHECK DTCS.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC displayed?

Perform the diagnosis for the displayed DTCs. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)>LIST

3

3. CHECK THE RECEIVED SIGNAL STRENGTH WHEN THE I-BUTTON WAS PRESSED (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • RSSI at SOS/ICALL(1)

Is the data 26% or more?

5

4

4. CHECK THE AT&T CELLULAR COVERAGE AREA.

Check whether the i-button was pressed within the cellular coverage area.

Is the location where the i-button was pressed within the cellular coverage area? (For the cellular coverage area, refer to the AT&T website. The system operates only on 3G and 4G technology.)

5

The i-button was pressed outside the cellular coverage area.

5. CHECK THE COMMUNICATION STATUS OF WHEN THE I-BUTTON WAS PRESSED (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Call status at SOS/ICALL Event(1)

If the data shows [Call Started] or [Call Connected]; Go to A.

If the data shows [Call Not Started]; Go to B.

If the data shows [No Network Service]; Go to C.

If the data shows [Call Ended by SXM]; Go to D.

A

A: 6

B

B: 7

C

C: Replace the antenna. ENTERTAINMENT & MONITORING>Antenna

D

D: The connection ended due to a server-side reason; therefore, there is no failure on the vehicle.

6. CHECK THE COMMUNICATION STATUS OF WHEN THE I-BUTTON WAS PRESSED (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Timestamp at Time of Button Push(1):Date

  • Timestamp at Time of Button Push(1):UTC ∗UTC is the basis for local times worldwide.

 

The time stamp is displayed in the Coordinated Universal Time (UTC), which is different from actual time at each location. Therefore, time difference needs to be corrected for use.

Example: [12/22 01:30 in UTC time] is corrected as [12/21 20:30 in New York time].

Does the time of the i-button operation match with the data?

6. REMOTE VEHICLE LOCATOR CANNOT LOCATE THE VEHICLE

Probable cause:

No contract agreement, smartphone malfunction, out of service area, DCM malfunction, server side malfunction, body integrated unit malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK THE CURRENT COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.
no

Perform the instructed procedures.

yes
3. CHECK THE CURRENT COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.
yes

Perform the instructed procedures.

no
4. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).
yes
no
5. CHECK THE AT&T CELLULAR COVERAGE AREA.
no

Perform the instructed procedures.

yes
6. CHECK DTCS.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Vehicle Locator Active

Is the data [TRUE]?

2

The user does not have a service subscription; therefore, it is not a failure.

2. CHECK THE CURRENT COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.

Check that the user’s smartphone can be connected to the Internet.

Can it be connected to the Internet?

3

The user’s smartphone or the Internet environment has a problem.

3. CHECK THE CURRENT COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.

Check that the user’s smartphone can display the current location.

Is the current location displayed?

Currently no failure is found. If the current location is not displayed, the user’s Internet environment (radio waves, etc.) possibly had a problem.

4

4. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Signal Strength

Is the data 26% or more?

6

5

5. CHECK THE AT&T CELLULAR COVERAGE AREA.

Check whether the location where the remote control was operated is within the cellular coverage area.

Is the location where the remote control was operated within the cellular coverage area? (For the cellular coverage area, refer to the AT&T website. The system operates only on 3G and 4G technology.)

6

The location where the remote control was operated was outside the cellular coverage area.

6. CHECK DTCS.
  • Body Control

  • Telematics

Are any DTCs displayed?

Check the Starlink Server report to verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.) If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

7. REMOTE VEHICLE LOCATOR INDICATES AN INCORRECT LOCATION FOR THE VEHICLE

Probable cause:

GPS reception environment failure, DCM malfunction

 
1. CHECK DTCS.
yes

Perform the instructed procedures.

no
2. CHECK THE CURRENT COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.
yes

Perform the instructed procedures.

no
3. CHECK THE CURRENT COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK DTCS.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Are any DTCs displayed?

Perform the diagnosis for the displayed DTCs. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)>LIST

2

2. CHECK THE CURRENT COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.

Check that the user’s smartphone can display the current location.

Is it displayed correctly? (Is a deviation, if any, less than 100 m (328 ft)?)

Currently no failure is found. When the user had a problem, there was a failure with the GPS antenna reception environment, etc.

3

3. CHECK THE CURRENT COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.

Check again that the user’s smartphone can display the current location in a place where the sky is open.

Is it displayed correctly? (Is a deviation, if any, less than 100 m (328 ft)?)

Currently no failure is found. When the user had a problem, there was a failure with the GPS antenna reception environment, etc.

8. REMOTE DOOR LOCK DOES NOT LOCK THE DOORS OF THE VEHICLE

Probable cause:

No contract agreement, smartphone malfunction, out of service area, door lock control system malfunction, server side malfunction, DCM malfunction, body integrated unit malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK THE CURRENT COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.
no

Perform the instructed procedures.

yes
3. CHECK THE DOOR LOCK FUNCTION.
yes

Perform the instructed procedures.

no
4. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).
yes
no
5. CHECK THE AT&T CELLULAR COVERAGE AREA.
no

Perform the instructed procedures.

yes
6. CHECK THE DOOR LOCK FUNCTION.
no

Perform the instructed procedures.

yes
7. CHECK DTCS.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Remote Door Lock Active

Is the data [TRUE]?

2

The user does not have a service subscription; therefore, it is not a failure.

2. CHECK THE CURRENT COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.

Check that the user’s smartphone can be connected to the Internet.

Can it be connected to the Internet?

3

The user’s smartphone or the Internet environment has a problem.

3. CHECK THE DOOR LOCK FUNCTION.

Check that the user’s smartphone can lock the doors in the current situation.

Are the doors locked?

Currently no failure is found. When the user had a problem, there was a failure with the Internet connection environment, etc.

4

4. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Signal Strength

Is the data 26% or more?

6

5

5. CHECK THE AT&T CELLULAR COVERAGE AREA.

Check whether the location where the remote control was operated is within the cellular coverage area.

Is the location where the remote control was operated within the cellular coverage area? (For the cellular coverage area, refer to the AT&T website. The system operates only on 3G and 4G technology.)

6

The location where the remote control was operated was outside the cellular coverage area.

6. CHECK THE DOOR LOCK FUNCTION.

Check that the keyless transmitter can lock the doors of the vehicle.

Are the doors locked?

7

Perform the diagnosis according to the inspection for the door lock control system. SECURITY AND LOCKS>Door Lock Control System>INSPECTION

7. CHECK DTCS.
  • Body Control

  • Telematics

Are any DTCs displayed?

Check the Starlink Server report to verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.) If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

9. THE DOORS LOCK UNINTENTIONALLY

Probable cause:

Server side malfunction, door lock switch malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK DOOR LOCK SWITCH.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK DOOR LOCK SWITCH.

Is the check result OK?

Check the Starlink Server report to verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.) If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

Perform the diagnosis according to the inspection for the door lock switch. SECURITY AND LOCKS>Door Lock Control System>INSPECTION

10. THE DOORS UNLOCK UNINTENTIONALLY

Probable cause:

Server side malfunction, door lock switch malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK DOOR LOCK SWITCH.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK DOOR LOCK SWITCH.

Is the check result OK?

Check the Starlink Server report to verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.) If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

Perform the diagnosis according to the inspection for the door lock switch. SECURITY AND LOCKS>Door Lock Control System>INSPECTION

11. REMOTE HORN & HAZARD LIGHTS DO NOT OPERATE UPON REQUEST

Probable cause:

No contract agreement, smartphone malfunction, out of service area, server side malfunction, keyless transmitter malfunction, horn circuit malfunction, body integrated unit malfunction, DCM malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK THE CURRENT COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.
no

Perform the instructed procedures.

yes
3. CHECK THE HORN AND HAZARD LIGHT FUNCTIONS.
yes

Perform the instructed procedures.

no
4. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).
yes
no
5. CHECK THE AT&T CELLULAR COVERAGE AREA.
no

Perform the instructed procedures.

yes
6. CHECK THE HORN AND HAZARD LIGHT FUNCTIONS.
yes
no
7. CHECK HORN OPERATION.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

8. CHECK DTCS.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Remote Horn & Light Active

Does the data display [TRUE]?

2

The user does not have a service subscription; therefore, it is not a failure.

2. CHECK THE CURRENT COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.

Check that the user’s smartphone can be connected to the Internet.

Can it be connected to the Internet?

3

The user’s smartphone or the Internet environment has a problem.

3. CHECK THE HORN AND HAZARD LIGHT FUNCTIONS.

Check that the horn and hazard light currently operate by the user’s smartphone.

Do the horn and hazard light operate?

Currently no failure is found. When the user had a problem, there was a failure with the Internet connection environment, etc.

4

4. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Signal Strength

Does the data indicate 26% or more?

6

5

5. CHECK THE AT&T CELLULAR COVERAGE AREA.

Check whether the location where the remote control was operated is within the cellular coverage area.

Is the location where the remote control was operated within the cellular coverage area? (For the cellular coverage area, refer to the AT&T website. The system operates only on 3G and 4G technology.)

6

The location where the remote control was operated was outside the cellular coverage area.

6. CHECK THE HORN AND HAZARD LIGHT FUNCTIONS.

Check that the horn and hazard light operate by the keyless transmitter. (Press the lock button three times.)

Do the horn and hazard light operate?

8

7

7. CHECK HORN OPERATION.

Using the Subaru Select Monitor, check the following items in the [Active Test] of [Body Control]. BODY CONTROL(DIAGNOSTICS)>Active Test

  • Horn Output

Does the horn sound?

8. CHECK DTCS.
  • Body Control

  • Telematics

Are any DTCs displayed?

Check the Starlink Server report to verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.) If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

12. WHEN THE VEHICLE SECURITY ALARM IS ACTIVATED, NOTIFICATION IS NOT SENT

Probable cause:

No contract agreement, smartphone malfunction, security alert system malfunction, out of service area, server side malfunction, body integrated unit malfunction, DCM malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK THE CURRENT COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.
no

Perform the instructed procedures.

yes
3. CHECK THE SECURITY ALERT SYSTEM.
no

Perform the instructed procedures.

yes
4. CHECK THE CURRENT COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.
yes

Perform the instructed procedures.

no
5. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).
yes
no
6. CHECK THE AT&T CELLULAR COVERAGE AREA.
no

Perform the instructed procedures.

yes
7. CHECK DTCS.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Security Alarm Active

Does the data display [TRUE]?

2

The user does not have a service subscription; therefore, it is not a failure.

2. CHECK THE CURRENT COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.

Check that the user’s smartphone can be connected to the Internet.

Can it be connected to the Internet?

3

The user’s smartphone or the Internet environment has a problem.

3. CHECK THE SECURITY ALERT SYSTEM.

Operate the security alert system.

Does it operate?

4

Check the security alert system. SECURITY AND LOCKS>Security System>INSPECTION

4. CHECK THE CURRENT COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.

Check that a notification is sent to the user’s smartphone after the security alert is activated.

Does the smartphone receive a notification?

Currently no failure is found.

5

5. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Signal Strength

Does the data indicate 26% or more?

7

6

6. CHECK THE AT&T CELLULAR COVERAGE AREA.

Check whether the location where the remote control was operated is within the cellular coverage area.

Is the location where the remote control was operated within the cellular coverage area? (For the cellular coverage area, refer to the AT&T website. The system operates only on 3G and 4G technology.)

7

The location where the remote control was operated was outside the cellular coverage area.

7. CHECK DTCS.
  • Body Control

  • Telematics

Are any DTCs displayed?

Check the Starlink Server report to verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.) If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

13. WHEN A MALFUNCTION INDICATOR LIGHT/WARNING LIGHT IS LIT, NOTIFICATION IS NOT SENT

Probable cause:

No contract agreement, out of service area, server side malfunction, DCM malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK WARNING LIGHT.
no

Perform the instructed procedures.

yes
3. CHECK DTCS.
yes

Perform the instructed procedures.

no
4. CHECK THE AT&T CELLULAR COVERAGE AREA.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Diagnostic Alert Active

Does the data display [TRUE]?

2

The user does not have a service subscription; therefore, it is not a failure.

2. CHECK WARNING LIGHT.

Check if the warning light illuminates.

Does it Illuminate?

3

Currently no failure is found. Since the warning light is not lit, notification is not sent.

3. CHECK DTCS.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Is DTC displayed?

Perform the diagnosis for the displayed DTCs. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)>LIST

4

4. CHECK THE AT&T CELLULAR COVERAGE AREA.

After the warning light was lit, check whether the location where the ignition switch was turned to OFF is within the cellular coverage area.

Is the location where the ignition switch was turned to OFF after the warning light was lit within the cellular coverage area? (For the cellular coverage area, refer to the AT&T website. The system operates only on 3G and 4G technology.)

Check the Starlink Server report to verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.) If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

The location where the ignition switch was turned to OFF (where warning light illumination information was sent) was outside the cellular coverage area.

14. MAINTENANCE NOTIFICATIONS ARE NOT SENT

Probable cause:

No contract agreement, server side malfunction, DCM malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK DTCS.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Maintenance Alert Active

Does the data display [TRUE]?

2

The user does not have a service subscription; therefore, it is not a failure.

2. CHECK DTCS.

Read the DTC of [Telematics] using the Subaru Select Monitor. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)

Are any DTCs displayed?

Perform the diagnosis for the displayed DTCs. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Trouble Code (DTC)>LIST

Check the Starlink Server report to verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.) If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

15. THE LED DOES NOT DISPLAY THE STATUS. (LED MALFUNCTION)

Probable cause:

No contract agreement, DCM malfunction, telematics button malfunction

 
1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK THE LED.
yes

Perform the instructed procedures.

no
3. CHECK DTCS.
yes

Perform the instructed procedures.

no
4. CHECK THE LED ILLUMINATION CONDITION.
no
yes
5. CHECK THE LED.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

6. CHECK THE LED.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Subscription Status

Is the data Subscribed?

2

The user does not have a service subscription; therefore, it is not a failure. (Both LEDs are turned off.)

2. CHECK THE LED.
1.

Turn the ignition switch to ON.

2.

Check the LED condition.

Does the RED LED go off and the GREEN LED illuminate?

  • The circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

  •  

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

3

4. CHECK THE LED ILLUMINATION CONDITION.

Using the Subaru Select Monitor, check the following items in the [Active Test] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Active Test

  • RED LED Lighting

  • GREEN LED Lighting

Is the LED turned on or off?

5

6

5. CHECK THE LED.
1.

Turn the ignition switch to ON.

2.

Check the LED condition.

Does the RED LED go off and the GREEN LED illuminate?

  • The circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

  •  

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

6. CHECK THE LED.
1.

Turn the ignition switch to OFF.

2.

Check that RED LED or GREEN LED illuminates when applying the battery voltage to it.

 

Never connect the battery voltage terminals in reverse polarity, because reversed connection damages the telematics button (LED).

Terminals

RED side

No. 7 (+) — No. 1 (−):

GREEN side

No. 4 (+) — No. 1 (−):

Does the RED LED or the GREEN LED illuminate?

16. PHONE CONVERSATION IS NOT POSSIBLE. (THE MICROPHONE DOES NOT RESPOND TO A VOICE. NO SOUND IS HEARD FROM THE SPEAKER.)

Probable cause:

Microphone malfunction, speaker malfunction, DCM malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK DTCS.
yes

Perform the instructed procedures.

no
2. CHECK THE SPEAKER OPERATION.
no
yes
3. CHECK MICROPHONE.
no

Perform the instructed procedures.

yes
4. CHECK THE SPEAKER.
no

Perform the instructed procedures.

yes
5. CHECK THE TELEPHONE CALL.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

2. CHECK THE SPEAKER OPERATION.

Using the Subaru Select Monitor, check the following items in the [Active Test] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Active Test

  • Speaker ON

Does it sound?

3

4

3. CHECK MICROPHONE.

Perform the microphone voice input.

Is the voice recognized?

4

Replace the microphone. ENTERTAINMENT & MONITORING>Microphone

4. CHECK THE SPEAKER.

Check the speaker.

Is the check result OK?

5. CHECK THE TELEPHONE CALL.
1.

Place the mobile phone in the vehicle.

2.

Establish a Bluetooth connection between the mobile phone in the vehicle and the vehicle unit.

3.

Make a call from outside to the mobile phone in the vehicle.

4.

Check that a telephone call is available through the in-vehicle microphone with the hands-free function.

Is a telephone call successful?

  • The circuit has returned to a normal condition at this time. Reproduce the failure, and then perform the diagnosis again.

  •  

    In this case, temporary poor contact of connector, temporary open or short circuit of harness may be the cause.

Perform the diagnosis according to inspection for DTC B2A04 MIC CIRCUIT. TELEMATICS SYSTEM (DIAGNOSTICS)>Diagnostic Procedure with Diagnostic Trouble Code (DTC)>DTC B2A04 MIC CIRCUIT

17. TELEMATICS REMOTE ENGINE STARTER/RES AIR CONDITIONER DOES NOT FUNCTION

Probable cause:

No contract agreement, out of service area, server side malfunction, DCM malfunction, antenna malfunction, smartphone malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK DTCS.
yes

Perform the instructed procedures.

no
3. CHECK THE COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.
no

Perform the instructed procedures.

yes
4. CHECK REMOTE ENGINE STARTER FUNCTION.
yes

Perform the instructed procedures.

no
5. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).
no

Perform the instructed procedures.

yes
6. CHECK STARLINK SERVER.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Remote Engine Starter Active

Is the data [TRUE]?

2

The user does not have a service subscription; therefore, it is not a failure.

3. CHECK THE COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.

Check that the user’s smartphone can be connected to the Internet.

Can it be connected to the Internet?

4

The user’s smartphone or the Internet environment has a problem.

4. CHECK REMOTE ENGINE STARTER FUNCTION.

Check that the remote engine starter operates by the smartphone.

Does it operate?

Currently no failure is found. If the remote engine starter did not operate, the user’s Internet environment (radio waves, etc.) possibly had a problem.

5

5. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Signal Strength

Is the data 26% or more?

6

Check the telematics antenna.

6. CHECK STARLINK SERVER.

Verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.)

Was there server outage that coincides with the day/time when the issue occurred?

Currently no failure is found. When the user had a problem, there was a failure with Starlink Server.

If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

18. CURFEW DOES NOT OPERATE

Probable cause:

No contract agreement, out of service area, server side malfunction, DCM malfunction, antenna malfunction, smartphone malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK DTCS.
yes

Perform the instructed procedures.

no
3. CHECK THE COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.
no

Perform the instructed procedures.

yes
4. CHECK CURFEW FUNCTIONS.
yes

Perform the instructed procedures.

no
5. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).
no

Perform the instructed procedures.

yes
6. CHECK THE AT&T CELLULAR COVERAGE AREA.
no

Perform the instructed procedures.

yes
7. CHECK STARLINK SERVER.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Curfew Active

Is the data [TRUE]?

2

The user does not have a service subscription; therefore, it is not a failure.

2. CHECK DTCS.
3. CHECK THE COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.

Check that the user’s smartphone can be connected to the Internet.

Can it be connected to the Internet?

4

The user’s smartphone or the Internet environment has a problem.

4. CHECK CURFEW FUNCTIONS.

Check that the curfew operates.

Does it operate?

Currently no failure is found. The location where the curfew did not operate was outside the cellular coverage area.

5

5. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Signal Strength

Is the data 26% or more?

6

Check the telematics antenna.

6. CHECK THE AT&T CELLULAR COVERAGE AREA.

Check whether the vehicle location where the curfew was set was within the cellular coverage area.

Was the vehicle location where the curfew was set within the cellular coverage area? (For the cellular coverage area, refer to the AT&T website. The system operates only on 3G and 4G technology.)

7

The vehicle location where the curfew was set was outside the cellular coverage area.

7. CHECK STARLINK SERVER.

Verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.)

Was there server outage that coincides with the day/time when the issue occurred?

Currently no failure is found. When the user had a problem, there was a failure with Starlink Server.

If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

19. SERVICE APPOINTMENT SCHEDULER DOES NOT OPERATE

Probable cause:

No contract agreement, out of service area, server side malfunction, DCM malfunction, antenna malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK DTCS.
yes

Perform the instructed procedures.

no
3. CHECK SERVICE APPOINTMENT SCHEDULER FUNCTION.
yes

Perform the instructed procedures.

no
4. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).
no

Perform the instructed procedures.

yes
5. CHECK THE AT&T CELLULAR COVERAGE AREA.
no

Perform the instructed procedures.

yes
6. CHECK STARLINK SERVER.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Service Appointment Scheduler Active

Is the data [TRUE]?

2

The user does not have a service subscription; therefore, it is not a failure.

2. CHECK DTCS.
3. CHECK SERVICE APPOINTMENT SCHEDULER FUNCTION.

Check that the service appointment scheduler operates.

Does it operate?

Currently no failure is found. The location where the service appointment scheduler did not operate was outside the cellular coverage area.

4

4. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Signal Strength

Is the data 26% or more?

5

Check the telematics antenna.

5. CHECK THE AT&T CELLULAR COVERAGE AREA.

Check whether the location where the service appointment scheduler was operated was within the cellular coverage area.

Was the location where the service appointment scheduler was operated within the cellular coverage area? (For the cellular coverage area, refer to the AT&T website. The system operates only on 3G and 4G technology.)

6

The location where the service appointment scheduler was operated was outside the cellular coverage area.

6. CHECK STARLINK SERVER.

Verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.)

Was there server outage that coincides with the day/time when the issue occurred?

Currently no failure is found. When the user had a problem, there was a failure with Starlink Server.

If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

20. GEO FENCING DOES NOT OPERATE

Probable cause:

No contract agreement, out of service area, server side malfunction, DCM malfunction, antenna malfunction, smartphone malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK DTCS.
yes

Perform the instructed procedures.

no
3. CHECK THE COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.
no

Perform the instructed procedures.

yes
4. CHECK GEO FENCING FUNCTIONS.
yes

Perform the instructed procedures.

no
5. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).
no

Perform the instructed procedures.

yes
6. CHECK THE AT&T CELLULAR COVERAGE AREA.
no

Perform the instructed procedures.

yes
7. CHECK STARLINK SERVER.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Geo Fencing Active

Is the data [TRUE]?

2

The user does not have a service subscription; therefore, it is not a failure.

2. CHECK DTCS.
3. CHECK THE COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.

Check that the user’s smartphone can be connected to the Internet.

Can it be connected to the Internet?

4

The user’s smartphone or the Internet environment has a problem.

4. CHECK GEO FENCING FUNCTIONS.

Check that Geo Fencing operates.

Does it operate?

Currently no failure is found. The location where Geo Fencing did not operate was outside the cellular coverage area.

5

5. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Signal Strength

Is the data 26% or more?

6

Check the telematics antenna.

6. CHECK THE AT&T CELLULAR COVERAGE AREA.

Check whether the vehicle location where Geo Fencing was set was within the cellular coverage area.

Was the vehicle location where Geo Fencing was set within the cellular coverage area? (For the cellular coverage area, refer to the AT&T website. The system operates only on 3G and 4G technology.)

7

The vehicle location where Geo Fencing was set was outside the cellular coverage area.

7. CHECK STARLINK SERVER.

Verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.)

Was there server outage that coincides with the day/time when the issue occurred?

No abnormality on the vehicle. After a while, perform the diagnosis from step 3.

If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

21. REMOTE VEHICLE CONDITION CHECK DOES NOT OPERATE

Probable cause:

No contract agreement, out of service area, server side malfunction, DCM malfunction, antenna malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK DTCS.
yes

Perform the instructed procedures.

no
3. CHECK THE COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.
yes

Perform the instructed procedures.

no
4. CHECK REMOTE VEHICLE CONDITION CHECK FUNCTIONS.
yes

Perform the instructed procedures.

no
5. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).
no

Perform the instructed procedures.

yes
6. CHECK THE AT&T CELLULAR COVERAGE AREA.
no

Perform the instructed procedures.

yes
7. CHECK STARLINK SERVER.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Diagnostic Alert Active

Is the data [TRUE]?

2

The user does not have a service subscription; therefore, it is not a failure.

2. CHECK DTCS.
3. CHECK THE COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.

Check that the user’s smartphone can display the remote vehicle condition check.

Is it displayed?

Currently no failure is found. If the remote vehicle condition check could not be displayed, the user’s Internet environment (radio waves, etc.) possibly had a problem.

4

4. CHECK REMOTE VEHICLE CONDITION CHECK FUNCTIONS.

Check that the remote vehicle condition check operates.

Does it operate?

Currently no failure is found. The location where the remote vehicle condition check did not operate was outside the cellular coverage area.

5

5. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Signal Strength

Is the data 26% or more?

6

Check the telematics antenna.

6. CHECK THE AT&T CELLULAR COVERAGE AREA.

Check whether the vehicle location where the remote vehicle condition check was operated was within the cellular coverage area.

Was the vehicle location where the remote vehicle condition check was operated within the cellular coverage area? (For the cellular coverage area, refer to the AT&T website. The system operates only on 3G and 4G technology.)

7

The vehicle location where the remote vehicle condition check was operated was outside the cellular coverage area.

7. CHECK STARLINK SERVER.

Verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.)

Was there server outage that coincides with the day/time when the issue occurred?

No abnormality on the vehicle. After a while, perform the diagnosis from step 3.

If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

22. SPEED ALERT DOES NOT OPERATE

Probable cause:

No contract agreement, out of service area, server side malfunction, DCM malfunction, antenna malfunction, smartphone malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK DTCS.
yes

Perform the instructed procedures.

no
3. CHECK THE COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.
no

Perform the instructed procedures.

yes
4. CHECK THE SPEED ALERT FUNCTIONS.
yes

Perform the instructed procedures.

no
5. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).
no

Perform the instructed procedures.

yes
6. CHECK THE AT&T CELLULAR COVERAGE AREA.
no

Perform the instructed procedures.

yes
7. CHECK STARLINK SERVER.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Speed Alert Active

Is the data [TRUE]?

2

The user does not have a service subscription; therefore, it is not a failure.

2. CHECK DTCS.
3. CHECK THE COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.

Check that the user’s smartphone can be connected to the Internet.

Can it be connected to the Internet?

4

The user’s smartphone or the Internet environment has a problem.

4. CHECK THE SPEED ALERT FUNCTIONS.

Check that the speed alert operates.

Does it operate?

Currently no failure is found. The location where the speed alert did not operate was outside the cellular coverage area.

5

5. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Signal Strength

Is the data 26% or more?

6

Check the telematics antenna.

6. CHECK THE AT&T CELLULAR COVERAGE AREA.

Check whether the vehicle location where the speed alert was set was within the cellular coverage area.

Was the vehicle location where the speed alert was set within the cellular coverage area? (For the cellular coverage area, refer to the AT&T website. The system operates only on 3G and 4G technology.)

7

The vehicle location where the speed alert was set was outside the cellular coverage area.

7. CHECK STARLINK SERVER.

Verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.)

Was there server outage that coincides with the day/time when the issue occurred?

No abnormality on the vehicle. After a while, perform the diagnosis from step 3.

If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

23. CONCIERGE DOES NOT OPERATE

Probable cause:

No contract agreement, out of service area, server side malfunction, DCM malfunction, antenna malfunction, i-button malfunction

 
1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK DTCS.
yes

Perform the instructed procedures.

no
3. CHECK THE RECEIVED SIGNAL STRENGTH WHEN THE I-BUTTON WAS PRESSED (CHECK THE DATA MONITOR).
no

Perform the instructed procedures.

yes
4. CHECK THE AT&T CELLULAR COVERAGE AREA.
no

Perform the instructed procedures.

yes
5. CHECK THE COMMUNICATION STATUS OF WHEN THE CONCIERGE BUTTON WAS PRESSED (CHECK THE DATA MONITOR).
choice

Perform the instructed procedures.

choice
choice

Perform the instructed procedures.

choice
6. CHECK THE I-BUTTON.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

7. CHECK STARLINK SERVER.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Concierge Active

Is the data [TRUE]?

2

The user does not have a service subscription; therefore, it is not a failure.

2. CHECK DTCS.
3. CHECK THE RECEIVED SIGNAL STRENGTH WHEN THE I-BUTTON WAS PRESSED (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • RSSI at SOS/ICALL(1)

Is the data 26% or more?

4

Check the telematics antenna.

4. CHECK THE AT&T CELLULAR COVERAGE AREA.

Check whether the location where the remote control was operated is within the cellular coverage area.

Is the location where the remote control was operated within the cellular coverage area? (For the cellular coverage area, refer to the AT&T website. The system operates only on 3G and 4G technology.)

5

The location where the remote control was operated was outside the cellular coverage area.

5. CHECK THE COMMUNICATION STATUS OF WHEN THE CONCIERGE BUTTON WAS PRESSED (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Call status at SOS/ICALL Event(1)

If the data shows [Call Started] or [Call Connected]; Go to A.

If the data shows [Call Not Started]; Go to B.

If the data shows [No Network Service]; Go to C.

If the data shows [Call Ended by SXM]; Go to D.

B

B: 6

C

C: Replace the antenna. ENTERTAINMENT & MONITORING>Antenna

D

D: The connection ended due to a server-side reason; therefore, there is no failure on the vehicle. 7

7. CHECK STARLINK SERVER.

Verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.)

Was there server outage that coincides with the day/time when the issue occurred?

Currently no failure is found. When the user had a problem, there was a failure with Starlink Server.

If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

24. NAVIGATION FUNCTION LINK DOES NOT OPERATE

Probable cause:

No contract agreement, out of service area, server side malfunction, DCM malfunction, antenna malfunction, smartphone malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
2. CHECK DTCS.
yes

Perform the instructed procedures.

no
3. CHECK THE COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.
no

Perform the instructed procedures.

yes
4. CHECK NAVIGATION FUNCTION LINK.
yes

Perform the instructed procedures.

no
5. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).
no

Perform the instructed procedures.

yes
6. CHECK THE AT&T CELLULAR COVERAGE AREA.
no

Perform the instructed procedures.

yes
7. CHECK STARLINK SERVER.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • POI Active

Is the data [TRUE]?

2

The user does not have a service subscription; therefore, it is not a failure.

2. CHECK DTCS.
3. CHECK THE COMMUNICATION ENVIRONMENT OF THE USER’S SMARTPHONE.

Check that the user’s smartphone can be connected to the Internet.

Can it be connected to the Internet?

4

The user’s smartphone or the Internet environment has a problem.

4. CHECK NAVIGATION FUNCTION LINK.

Perform the navigation function setting using the application.

Is setting possible?

Currently no failure is found. The location where the navigation function link did not operate was outside the cellular coverage area.

5

5. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Signal Strength

Is the data 26% or more?

6

Check the telematics antenna.

6. CHECK THE AT&T CELLULAR COVERAGE AREA.

Check whether the vehicle location where the remote control was operated was within the cellular coverage area.

Was the vehicle location where the remote control was operated within the cellular coverage area? (For the cellular coverage area, refer to the AT&T website. The system operates only on 3G and 4G technology.)

7

The vehicle location where the remote control was operated was outside the cellular coverage area.

7. CHECK STARLINK SERVER.

Verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.)

Was there server outage that coincides with the day/time when the issue occurred?

No abnormality on the vehicle.

If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

25. FOTA DOES NOT OPERATE

Probable cause:

No contract agreement, out of service area, server side malfunction, DCM malfunction, antenna malfunction, navigation unit malfunction

 
1. CHECK NAVIGATION UNIT.
no
yes
2. CHECK THE TELEMATICS BUTTON (LED).
no
yes
3. CHECK DEFECTIVE DCM.
no

Perform the instructed procedures.

yes
4. CHECK THE SUBSCRIPTION STATUS.
no

Perform the instructed procedures.

yes
5. CHECK DTCS.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK NAVIGATION UNIT.
1.

Turn the ignition switch to ON.

2.

Check whether installation-in-progress remains displayed on the screen.

Does it remain displayed?

Check the navigation unit. ENTERTAINMENT & MONITORING>Navigation System If no fault is found, 2

2

2. CHECK THE TELEMATICS BUTTON (LED).

Check that the RED LED or the GREEN LED illuminates.

Does the RED LED or the GREEN LED illuminate?

3

Check the telematics button. ENTERTAINMENT & MONITORING>Switches and Harness If no fault is found, 3

3. CHECK DEFECTIVE DCM.

Connect the Subaru Select Monitor and select [Telematics].

Is there any response?

4. CHECK THE SUBSCRIPTION STATUS.

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Over The Air Active

Is the data [TRUE]?

5

The user does not have a service subscription; therefore, it is not a failure.

5. CHECK DTCS.
  • Telematics

  • Infotainment

Are any DTCs displayed?

26. THE DEVICE CANNOT BE REGISTERED TO WIFI HOTSPOT

Probable cause:

DCM malfunction, navigation unit malfunction, WiFi device malfunction

 
1. CHECK THE WIFI DEVICE.
yes

Perform the instructed procedures.

no
2. CHECK THE WIFI SETTING.
no

Perform the instructed procedures.

yes
3. CHECK THE WIFI DEVICE SETTING (SSID).
no

Perform the instructed procedures.

yes
4. CHECK THE WIFI DEVICE SETTING (PASSWORD).
no

Perform the instructed procedures.

yes
5. CHECK THE WIFI DEVICE SETTING (FREQUENCY BAND).
no

Perform the instructed procedures.

yes
6. CHECK DTCS.
yes

Perform the instructed procedures.

no
7. CHECK CONNECTED DEVICES (DATA MONITOR).
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE WIFI DEVICE.

Check that a properly operating WiFi device can be connected.

Can the WiFi device be registered?

No abnormality on the vehicle. The WiFi device which could not be connected was faulty.

2

2. CHECK THE WIFI SETTING.

Check the WiFi HotSpot setting of DCM by operating the navigation.

Is the WiFi HotSpot setting ON?

3

Set the WiFi HotSpot setting to ON.

3. CHECK THE WIFI DEVICE SETTING (SSID).

Check whether the WiFi device access point is the same access point name as SSID displayed on the navigation display.

Is it the same access point name?

4

No abnormality on the vehicle. The access point is not the same.

4. CHECK THE WIFI DEVICE SETTING (PASSWORD).

Check the password that is input in the WiFi device.

Is the password correct?

5

Input the correct password in the WiFi device to re-register.

5. CHECK THE WIFI DEVICE SETTING (FREQUENCY BAND).

Check the frequency band of the WiFi device and the vehicle side.

Is the frequency band correct?

6

Set the frequency band again.

6. CHECK DTCS.
7. CHECK CONNECTED DEVICES (DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • WiFi (Device1) :Device Name

  • WiFi (Device2) :Device Name

  • WiFi (Device3) :Device Name

  • WiFi (Device4) :Device Name

  • WiFi (Device5) :Device Name

  • WiFi (Device6) :Device Name

  • WiFi (Device7) :Device Name

  • WiFi (Device8) :Device Name

Do all items display a connected device name?

No abnormality on the vehicle. Connection was not able to be established because eight devices were connected.

27. WIFI HOTSPOT DOES NOT OPERATE/CONNECTION TO THE INTERNET FAILS

Probable cause:

Out of service area, server side malfunction, DCM malfunction, antenna malfunction, WiFi device malfunction

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK THE WIFI DEVICE.
yes

Perform the instructed procedures.

no
2. CHECK WIFI COMMUNICATION STATUS.
yes

Perform the instructed procedures.

no
3. CHECK DTCS.
yes

Perform the instructed procedures.

no
4. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).
no

Perform the instructed procedures.

yes
5. CHECK THE AT&T CELLULAR COVERAGE AREA.
no

Perform the instructed procedures.

yes
6. CHECK STARLINK SERVER.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK THE WIFI DEVICE.

Check that the Internet can be viewed with a normal WiFi device.

Can the Internet be viewed?

No abnormality on the vehicle. The WiFi device which could not be connected was faulty.

2

2. CHECK WIFI COMMUNICATION STATUS.

Check that the Internet can be actually viewed with WiFi HotSpot in a good radio wave location.

Can the Internet be viewed?

Currently no failure is found. The location where the Internet could not be connected via WiFi was outside the cellular coverage area. Or, it is possible that it was an interval of re-trying to connect to AT&T.

3

3. CHECK DTCS.
4. CHECK THE CURRENT RECEIVED SIGNAL STRENGTH (CHECK THE DATA MONITOR).

Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. TELEMATICS SYSTEM (DIAGNOSTICS)>Data Monitor

  • Signal Strength

Is the data 26% or more?

5

Check the telematics antenna.

5. CHECK THE AT&T CELLULAR COVERAGE AREA.

Check whether the location where WiFi was used was within the cellular coverage area.

Was the location where WiFi was used within the cellular coverage area? (For the cellular coverage area, refer to the AT&T website. The system operates only on 3G and 4G technology.)

6

The location where WiFi was used was outside the cellular coverage area.

6. CHECK STARLINK SERVER.

Verify that there was no server outage that coincides with the day/time the customer reported that the issue occurred. (Refer to STARLINK Server Maintenance/Down Report under Reports and Starlink section in Subarunet.)

Was there server outage that coincides with the day/time when the issue occurred?

Currently no failure is found. When the user had a problem, there was a failure with Starlink Server.

If no outage exists for that time frame, it is possible that there was environmental interference (radio waves, etc.) when the user performed the operation. No further actions are recommended.

28. ENGINE WILL NOT START

Probable cause:

The vehicle is in the Stolen Vehicle Recovery + state.

 

Before performing diagnosis, refer to “CAUTION” in “General Description”. TELEMATICS SYSTEM (DIAGNOSTICS)>General Description>CAUTION

1. CHECK STOLEN VEHICLE RECOVERY +.
yes

Perform the instructed procedures.

no

Perform the instructed procedures.

1. CHECK STOLEN VEHICLE RECOVERY +.

Using Subaru Select Monitor, check the following items with [Data monitor] of [Body Control] for models without Keyless Access with Push Button Start, and with [Data monitor] of [Keyless Access with Push Button Start] for models with Keyless Access with Push Button Start. BODY CONTROL(DIAGNOSTICS)>Data Monitor KEYLESS ACCESS WITH PUSH BUTTON START(DIAGNOSTICS)>Data Monitor

  • Body Control

    • Immobilizer Set Memory

  • Keyless Access with Push Button Start

    • Immobilizer Set Memory

Is [Set] displayed?

Have the customer contact the call center to release the lock.

Perform inspection according to the diagnosis of engine. ENGINE (DIAGNOSTICS)(H4DO)>Basic Diagnostic Procedure>PROCEDURE