LEMON Manuals: Even more car manuals for everyone
Home >> Mazda >> 2024 >> 3 Carbon Turbo, 4D Hatchback >> Repair and Diagnosis >> Accessories & Equipment >> Gauges & Instrument Panels >> Symptom Troubleshooting - Telematics Communication System >> Vehicle Information Is Not Sent To Smartphone >> Diagnostic Procedure

Diagnostic Procedure

VEHICLE INFORMATION IS NOT SENT TO SMARTPHONE (TELEMATICS COMMUNICATION SYSTEM) DIAGNOSTIC PROCEDURE

Step Inspection Results Action
1 VERIFY ALL SYSTEM DTCs 
  • Perform the DTC inspection. (See DTC INSPECTION .)
  • Are any DTCs displayed?
Yes Repair or replace the malfunctioning location according to the applicable DTC troubleshooting.
No Go to the next step.
2 INSPECT WIRING HARNESS (INCLUDING CONNECTOR/TERMINAL) BETWEEN TEL ANTENNA No. 1 AND TELEMATICS COMMUNICATION UNIT FOR MALFUNCTION  Yes Go to the next step.
No Repair or replace the malfunctioning location and perform the repair completion verification 1.
3 INSPECT TEL ANTENNA No. 1 FOR MALFUNCTION 
  • Install/connect the part removed/disconnected during the troubleshooting procedure.
  • Has the malfunction symptom been eliminated?
Yes Complete the symptom troubleshooting.
(Explain contents of repair to customer)
No Verify if a similar malfunction on another vehicle with the emergency call system is occurring.
If a similar malfunction can be verified: 
  • A malfunction other than the vehicle, such as a server, the communication environment, Smartphone, or an application can be considered.
  • If the malfunction is not resolved, verify the web content of the official site related to the emergency call system.

If a similar malfunction cannot be verified: 
Repair completion verification 1 VERIFY THAT VEHICLE IS REPAIRED 
  • Install/connect the part removed/disconnected during the troubleshooting procedure.
  • Has the malfunction symptom been eliminated?
Yes Complete the symptom troubleshooting.
(Explain contents of repair to customer)
No Refer to the controller area network (CAN) malfunction diagnosis flow to inspect for a CAN communication error.
(See MALFUNCTION DIAGNOSIS FLOW [CONTROLLER AREA NETWORK (CAN)] .)
If the CAN communication is normal, perform the diagnosis from Step 1.