LEMON Manuals: Even more car manuals for everyone
Home >> Subaru >> 2022 >> WRX Premium, Standard Trans >> Repair and Diagnosis (Single Page) >> Accessories & Equipment >> Infotainment >> Telematics System (Diagnostics) >> Diagnostics with Phenomenon >> Inspection >> Remote Horn & Hazard Lights Do Not Operate Upon Request

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

CAUTION:
  1. CHECK THE SUBSCRIPTION STATUS  .
    1. Turn the ignition switch to ON.
    2. Using the Subaru Select Monitor, check the following items in the [Data monitor] of [Telematics]. Ref. to TELEMATICS SYSTEM (DIAGNOSTICS)>DATA MONITOR 
      • Remote Horn & Light Active

    Is the data [TRUE]?

    Yes  : Go to  2.

    No  :

    • The user does not have a service subscription; therefore, it is not a failure.
    • When the user's service subscription is not set to [TRUE], set the provisioning again.

      When the setting does not change to [TRUE] even after setting the provisioning again, replace the DCM. Ref. to ENTERTAINMENT & MONITORING>DATA COMMUNICATION MODULE

  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?

    Yes  : Go to  3.

    No  : 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?

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

    No  : Go to  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]. Ref. to TELEMATICS SYSTEM (DIAGNOSTICS)>DATA MONITOR 

    • Signal Strength

    Is the data 26 [%] or more?

    Yes  : Go to  6.

    No  : Go to  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.)

    Yes  : Go to  6.

    No  : 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?

    Yes  : Go to  8.

    No  : Go to  7.

  7. CHECK HORN OPERATION  .

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

    • [Horn Output]

    Does the horn sound?

    Yes  : Check the keyless transmitter. Ref. to SECURITY AND LOCKS>ACCESS KEY>INSPECTION

    No  : Check the horn circuit. Ref. to WIRING SYSTEM>HORN SYSTEM

  8. CHECK DTCS  .

    Read the following DTCs using Subaru Select Monitor.

    If DTC for body control is displayed and diagnosis is necessary, go to  A.

    If DTC for telematics is displayed and diagnosis is necessary, go to  B.

    If no DTC is displayed, go to  C.

    1. Ref. to BODY CONTROL (DIAGNOSTICS)>DIAGNOSTIC TROUBLE CODE (DTC)>LIST
    2. Ref. to TELEMATICS SYSTEM (DIAGNOSTICS)>DIAGNOSTIC TROUBLE CODE (DTC)>LIST 
    3. 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.