{"id":9681,"date":"2022-03-10T20:30:49","date_gmt":"2022-03-10T20:30:49","guid":{"rendered":"https:\/\/www.hexorcism.com\/19BP\/sm2337313\/"},"modified":"2022-03-10T20:30:49","modified_gmt":"2022-03-10T20:30:49","slug":"sm2337313","status":"publish","type":"page","link":"https:\/\/www.hexorcism.com\/19BP\/sm2337313\/","title":{"rendered":"BASIC KNOWLEDGE"},"content":{"rendered":"
\n

BASIC KNOWLEDGE<\/h3>\n<\/div>\n

SM2337313<\/p>\n

<\/p>\n
\n
\n
\n

id990200000100<\/p>\n



\n<\/a><\/p>\n

Outline<\/p>\n

\u2022 Vehicle has an on-board diagnostic function to facilitate malfunction diagnosis.<\/div>\n



\n<\/a><\/p>\n

Terminology<\/p>\n


<\/p>\n

<\/a><\/p>\n

Mazda Modular Diagnostic System (M-MDS)<\/p>\n

\n
\n
\u2022 The M-MDS is an on-board diagnostic tool developed for the improvement of servicing efficiency, maintenance quality, and convenience, and the reduction of security risk.<\/div>\n
\u2022 The M-MDS consists of a laptop PC for servicing work, the Mazda Diagnostic and Repair Software (MDARS) on-board diagnostic software, the VCM- used as a communication device between the vehicle and the laptop PC for servicing work, and each type of cable.<\/p>\n\n\n\n
\n\n\n\n
<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
am3zzw00024591<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
\u2022 With the MDARS, cloud technology is introduced for the storage of diagnosis history performed using applications (software for controlling on-board diagnosis function) or the MDARS, and data recorded by the PID\/data monitor function.<\/div>\n<\/dd>\n<\/dl>\n


<\/p>\n

<\/a><\/p>\n

Drive cycle<\/p>\n

\n
\n
\u2022 A drive cycle indicates the period of time in which the engine is started to when it is started the next time.<\/div>\n
\u2022 One drive cycle indicates one period of time in which the engine is started to when it is started the next time. If this cycle is repeated two times, it becomes two drive cycles.<\/p>\n\n\n\n
\n\n\n\n
<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
atsvuw00000065<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/dd>\n<\/dl>\n


<\/p>\n

<\/a><\/p>\n

Diagnostic Trouble Code(s) (DTC)<\/p>\n

\n
\n
\u2022 DTC is a code consisting of 9-digit alphanumeric characters which are stored when each module detects a malfunction.<\/div>\n
\u2022 The first 5 digits of the DTC indicate which system or part and what kind of malfunction is occurring. Digits 6 to 7 add more detailed information on the malfunction content (such as open\/short circuit, characteristic malfunction).<\/div>\n
\u2022 The last 2 digits of the DTC are called status byte indicating malfunction conditions such as pending code, past\/current malfunctions, and the warning light illumination condition.<\/p>\n\n\n\n
\n\n\n\n
<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
am3zzw00031576<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
\n
\n
Current malfunction<\/div>\n<\/dd>\n
\n
\u2015 Malfunction being detected by current drive cycle<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
Past malfunction<\/div>\n<\/dd>\n
\n
\u2015 Malfunction detected by past drive cycle, but with current drive cycle, status is determined as normal<\/div>\n<\/dd>\n<\/dl>\n
\u2022 DTCs can be read out by implementing a quick check or an on-demand self-test using the M-MDS. (See DTC INSPECTION<\/a>.)<\/div>\n
\u2022 Status byte can be read out by implementing a quick check using the M-MDS. (See DTC INSPECTION<\/a>.)<\/div>\n
\u2022 For details on the status byte, verify the explanation displayed on the M-MDS screen when reading out DTCs.<\/div>\n<\/dd>\n<\/dl>\n


<\/p>\n

<\/a><\/p>\n

Pending code<\/p>\n

\n
\n
\u2022 The pending code is a temporary malfunction code which differs from the DTC stored when the PCM or TCM detects a system malfunction.<\/div>\n
\u2022 When the PCM or TCM detects a system malfunction, a DTC is stored in the PCM or TCM according to the number of drive cycles. On the other hand, the pending code is stored in the PCM or TCM regardless of the number of drive cycles.<\/div>\n
\u2022 When the PCM or TCM determines that the system is normal, the pending code stored in the PCM or TCM is cleared from the PCM or TCM from the next drive cycle.<\/div>\n
\u2022 Pending codes can be read out by implementing a quick check or an on-demand self-test using the M-MDS. (See DTC INSPECTION<\/a>.)<\/div>\n<\/dd>\n<\/dl>\n


<\/p>\n

<\/a><\/p>\n

Continuous Memory Diagnostic Trouble Code (CMDTC)<\/p>\n

\n
\n
\u2022 CMDTC are the currently stored DTCs which are recorded in a module after clearing the previous DTCs, regardless of past\/current malfunctions.<\/div>\n
\u2022 CMDTC can be read out by implementing a quick check using the M-MDS. (See DTC INSPECTION<\/a>.)<\/div>\n<\/dd>\n<\/dl>\n


<\/p>\n

<\/a><\/p>\n

On Demand Diagnostic Trouble Code (ODDTC)<\/p>\n

\n
\n
\u2022 ODDTC are DTCs which have been read out by implementing the diagnostic procedure programmed in the module beforehand.<\/div>\n
\u2022 ODDTC can be read out by implementing an on-demand self-test using the M-MDS. (See DTC INSPECTION<\/a>.)<\/div>\n<\/dd>\n<\/dl>\n


<\/p>\n

<\/a><\/p>\n

Data logger<\/p>\n

\n
\n
\u2022 The data logger is data in which the voltage values input by each module from parts such as switches and actuators is converted to signals for use in on-board diagnostics.<\/div>\n
\u2022 The data logger can be used to implement the PID\/data monitor function which reads input\/output signals, and the simulation function which drives output parts. (See PID\/data monitor function<\/a>.) (See Simulation function<\/a>.)<\/div>\n<\/dd>\n<\/dl>\n


<\/p>\n

<\/a><\/p>\n

Freeze frame data, Snapshot data<\/p>\n

\n
\n
\u2022 The freeze frame data and snapshot data consist of vehicle condition data when a malfunction is detected.<\/div>\n
\u2022 The freeze frame data and snapshot data are displayed automatically when displaying CMDTC.<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
Freeze frame data<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
\u2022 For the freeze frame data, only a part of the DTC data is stored.<\/div>\n
\u2022 If there are several malfunctions in the engine control system, the data for the malfunction which occurred initially is stored. After that, if a misfire or malfunction in the fuel injection control occurs, the misfire or malfunction data in the fuel injection control overwrites the previously stored data. However, if the previously stored freeze frame data is due to a misfire or malfunction in the fuel injection control, the data is not overwritten.<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
Snapshot data<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
\u2022 For the snapshot data, the data for all DTCs currently detected is stored.<\/div>\n
\u2022 For DTCs with one drive cycle, the data is stored when a malfunction is determined.<\/div>\n
\u2022 For DTCs with two drive cycles, the data is stored when a malfunction is not determined (first diagnosis) and a malfunction is determined (second diagnosis).<\/div>\n<\/dd>\n<\/dl>\n



\n<\/a><\/p>\n

Functions<\/p>\n

\u2022 The on-board diagnostic function has the following functions.<\/div>\n
\n
\n
\u2015 Malfunction detection function<\/div>\n
\u2015 External on-board diagnostic tester communication function<\/div>\n
\u2015 Memory function<\/div>\n
\u2015 Malfunction indication function<\/div>\n
\u2015 PID\/data monitor function<\/div>\n
\u2015 Simulation function<\/div>\n
\u2015 Self-test function<\/div>\n
\u2015 OBD test mode<\/div>\n<\/dd>\n<\/dl>\n


<\/p>\n

<\/a><\/p>\n

Malfunction detection function<\/p>\n

\n
\n
\u2022 The malfunction detection function is a function which detects malfunctions by monitoring the operation status of each system from input\/output signals.<\/div>\n<\/dd>\n<\/dl>\n


<\/p>\n

<\/a><\/p>\n

External on-board diagnostic tester communication function<\/p>\n

\n
\n
\u2022 The external on-board diagnostic tester communication function is for sending\/receiving data to and from each module and the external on-board diagnostic tester mutually.<\/div>\n
\u2022 The M-MDS has been adopted as an external on-board diagnostic tester, and DLC-2 has been adopted as a communication media.<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
Data Link Connector (DLC) -2<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
\u2022 A DLC-2 compliant with the International Standardization Organization (ISO) standard has been adopted.<\/div>\n
\u2022 Connector shapes and terminal layouts as specified by ISO 15031-3 (SAE J1962) have been adopted, and the terminals are 16-pin.<\/p>\n\n\n\n
<\/td>\n\n\n\n\n
<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
am3zzw00024593<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/dd>\n<\/dl>\n

\n

\u2014: Not applicable<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n

Terminal<\/p>\n<\/th>\n

\n

Function<\/p>\n<\/th>\n<\/tr>\n<\/thead>\n

\n
A<\/div>\n<\/td>\n
\n
Terminal for battery power supply<\/div>\n<\/td>\n<\/tr>\n
\n
B<\/div>\n<\/td>\n
\n
Terminal for headlight auto leveling system initial setting<\/div>\n<\/td>\n<\/tr>\n
\n
C<\/div>\n<\/td>\n
\n
SAS control module<\/div>\n<\/td>\n<\/tr>\n
\n
D<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
E<\/div>\n<\/td>\n
\n
Terminal LO for HS-CAN<\/div>\n<\/td>\n<\/tr>\n
\n
F<\/div>\n<\/td>\n
\n
Terminal HI for HS-CAN<\/div>\n<\/td>\n<\/tr>\n
\n
G<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
H<\/div>\n<\/td>\n
\n
Ground terminal for serial communication<\/div>\n<\/td>\n<\/tr>\n
\n
I<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
J<\/div>\n<\/td>\n
\n
Body ground terminal<\/div>\n<\/td>\n<\/tr>\n
\n
K<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
L<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
M<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
N<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
O<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
P<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n


<\/p>\n

<\/a><\/p>\n

Memory function<\/p>\n

\n
\n
\u2022 The memory function stores malfunctions detected by the malfunction detection function in the volatile memory or non-volatile memory in each module as a DTC.<\/div>\n
\u2022 The stored DTC can be read by the M-MDS. (See DTC INSPECTION<\/a>.)<\/div>\n
\u2022 The DTCs stored in the non-volatile memory are not cleared even if the ignition is switched off or the negative battery terminal is disconnected. Therefore, it is necessary to clear the memory from each module after repairing the malfunctions. (See CLEARING DTC<\/a>.)<\/div>\n<\/dd>\n<\/dl>\n


<\/p>\n

<\/a><\/p>\n

Malfunction indication function<\/p>\n

\n
\n
\u2022 The malfunction indication function turns on\/flashes the warning lights in the instrument cluster when a malfunction is detected and displays warnings on the center display and the multi-information display to notify the driver of a malfunction.<\/div>\n
\u2022 If a malfunction occurs in the engine control system, the check engine light turns on.<\/div>\n
\u2022 When the PCM determines that a system is continuously normal for 3 drive cycles, it turns off the check engine light, and when it determines that the system is continuously normal for 41 warm-up cycles, it clears the DTC.<\/p>\n
\n
\n
Note<\/div>\n<\/dd>\n
\n
\u2022 A warm-up cycle is a drive cycle including the period until the engine is completely warmed up after a cold-engine starts. This cycle repeated 41 times is a 41 warm-up cycle.<\/div>\n<\/dd>\n<\/dl>\n<\/div>\n<\/dd>\n<\/dl>\n


<\/p>\n

<\/a><\/p>\n

PID\/data monitor function<\/p>\n

\n
\n
\u2022 The PID\/data monitor function can select the input\/output signal monitor items set in each module and read out in real-time.<\/div>\n
\u2022 The PID\/data monitor function can be used by the M-MDS. (See PID\/DATA MONITOR INSPECTION<\/a>.)<\/div>\n<\/dd>\n<\/dl>\n


<\/p>\n

<\/a><\/p>\n

Simulation function<\/p>\n

\n
\n
\u2022 The simulation function can drive the output parts set in each module regardless of the control condition.<\/div>\n
\u2022 The simulation function can be used by the M-MDS. (See SIMULATION INSPECTION<\/a>.)<\/div>\n<\/dd>\n<\/dl>\n


<\/p>\n

<\/a><\/p>\n

How to make use of PID\/data monitor function and simulation function (Ex. Wipers do not operate correctly)<\/p>\n

\n
\n
\u2022 A system (such as input\/output side) where a malfunction is occurring can be specified by using the PID\/data monitor function or simulation function.<\/p>\n\n\n\n
\n\n\n\n
<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
am3zzw00024594<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
Input system examination (windshield wiper switch to body control module (BCM))<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
1. Operate the windshield wiper switch and verify that the windshield wiper operation condition is in conjunction with the body control module (BCM) PID “F_WIP” (windshield wiper operation condition table) value.<\/div>\n<\/dd>\n<\/dl>\n

\n

\u2014: Not applicable<\/p>\n\n\n\n\n\n\n\n\n
\n

Windshield wiper switch condition<\/p>\n<\/th>\n

\n

PID\/data monitor item “F_WIP” value<\/p>\n<\/th>\n

\n

Diagnostic result<\/p>\n<\/th>\n

\n

Malfunctioning system<\/p>\n<\/th>\n

\n

Inspection item<\/p>\n<\/th>\n<\/tr>\n<\/thead>\n

\n
OFF<\/div>\n<\/td>\n
\n
OFF<\/div>\n<\/td>\n
\n
Normal<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
LO<\/div>\n<\/td>\n
\n
OFF<\/div>\n<\/td>\n
\n
Malfunction<\/div>\n<\/td>\n
\n
Input system (Windshield wiper switch\u2014Body control module (BCM))<\/div>\n<\/td>\n
\n
\u2022 Windshield wiper switch<\/div>\n
\u2022 Instrument cluster<\/div>\n
\u2022 Body control module (BCM)<\/div>\n
\u2022 Related connectors<\/div>\n
\u2022 Related wiring harness<\/div>\n<\/td>\n<\/tr>\n
\n
HI<\/div>\n<\/td>\n
\n
FrontWiper On Hi<\/div>\n<\/td>\n
\n
Normal<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
INT\/AUTO<\/div>\n<\/td>\n
\n
FrontWiperINT Auto On<\/div>\n<\/td>\n
\n
Normal<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n
\n
Output system examination (body control module (BCM) to wiper motor)<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
1. Verify that the wipers are operating correctly using the body control module (BCM) simulation PID item “F_WIP_REQ” (windshield wiper drive) and “R_WIP_REQ” (rear wiper drive).<\/div>\n<\/dd>\n<\/dl>\n

\n

\u2014: Not applicable<\/p>\n\n\n\n\n\n\n\n\n\n
\n

Simulation item “F_WIP_REQ” value<\/p>\n<\/th>\n

\n

Simulation item “R_WIP_REQ” value<\/p>\n<\/th>\n

\n

Windshield wiper operation condition<\/p>\n<\/th>\n

\n

Rear wiper operation condition<\/p>\n<\/th>\n

\n

Diagnostic result<\/p>\n<\/th>\n

\n

Malfunctioning system<\/p>\n<\/th>\n

\n

Inspection item<\/p>\n<\/th>\n<\/tr>\n<\/thead>\n

\n
Off<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
OFF<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
Normal<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
F.WiperLo<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
LO<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
Normal<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
F.WiperHi<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
HI<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
Normal<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
\u2014<\/div>\n<\/td>\n
\n
Off<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
OFF<\/div>\n<\/td>\n
\n
Normal<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
\u2014<\/div>\n<\/td>\n
\n
Rear Wiper Low On<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
OFF<\/div>\n<\/td>\n
\n
Malfunction<\/div>\n<\/td>\n
\n
Output system (Body control module (BCM)\u2014Rear wiper motor)<\/div>\n<\/td>\n
\n
\u2022 Body control module (BCM)<\/div>\n
\u2022 Electrical supply unit (ESU)<\/div>\n
\u2022 Rear wiper motor<\/div>\n
\u2022 Related connectors<\/div>\n
\u2022 Related wiring harness<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n


<\/p>\n

<\/a><\/p>\n

Self-test function<\/p>\n

\n
\n
\u2022 If the self-test function is performed, each module diagnoses the system. If a malfunction is detected, the applicable DTC is stored.<\/div>\n
\u2022 Current malfunction verification and verification after repair can be facilitated by performing the self-test function.<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
Quick check<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
\u2022 When the quick check is implemented, the CMDTCs recorded in all the modules can be read out at once regardless of past\/current malfunctions. (See DTC INSPECTION<\/a>.)<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
On-demand self-test<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
\u2022 When the on-demand self test is implemented, the current malfunctions of the selected module can be read out. (See DTC INSPECTION<\/a>.)<\/div>\n
\u2022 There are two types of the ODDTC self-tests; KOEO (key ON, ignition off) self-test while the ignition is switched ON and engine is stopped, and KOER (key ON, ignition running) self-test while idling and the vehicle is stopped.<\/div>\n
\u2022 The DTCs which can be read out by the on-demand self test are not stored in the module, but with the M-MDS, the CMDTCs are read out automatically after the ODDTCs read out, and both of the results are displayed.<\/div>\n<\/dd>\n<\/dl>\n


<\/p>\n

<\/a><\/p>\n

On-Board Diagnostic (OBD) test mode<\/p>\n

\n
\n
\u2022 The OBD system detects malfunction in the exhaust gas purification system and evaporative gas leakage of the vehicle itself, and it records that malfunction content.<\/div>\n
\u2022 Diagnosis related to the OBD system can be facilitated using the OBD test mode.<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
Mode 1: On-Board system readiness test<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
\u2022 In Mode 1, the completion status of the PID\/data monitor related to the exhaust gas purification system and related system monitors can be verified.<\/div>\n
\u2022 The system monitor verifies whether the operation condition such as for misfire, fuel, CCM, catalyst, evaporative gas, HO2S, and HO2S heater is operating normally.<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
Mode 2: Freeze frame data<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
\u2022 Mode 2 reads out the freeze frame data.<\/div>\n
\u2022 The M-MDS displays the freeze frame data automatically when the CMDTCs are displayed.<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
Mode 3: Exhaust gas purification system related CMDTC<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
\u2022 Mode 3 reads out the CMDTCs related to the exhaust gas purification system.<\/div>\n
\u2022 When a quick check is performed, the M-MDS automatically reads out the CMDTCs related to the exhaust gas purification system.<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
Mode 4: Exhaust gas purification system-related malfunction information deletion\/reset<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
\u2022 Mode 4 deletes\/resets information (such as CMDTC, pending code, and freeze frame data) related to the exhaust gas purification system.<\/div>\n
\u2022 When the DTCs are cleared, the M-MDS automatically deletes\/resets the information related to the exhaust gas purification system.<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
Mode 5: HO2S monitor test<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
\u2022 Mode 5 reads out the results of HO2S monitor test.<\/div>\n
\u2022 The M-MDS does not support because it substitutes for Mode 6.<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
Mode 6: Diagnostic monitoring test<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
\u2022 Mode 6 reads out the results (number of misfires of each cylinder) of each system monitor test.<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
Mode 7: Pending code<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
\u2022 Mode 7 reads out the pending codes.<\/div>\n
\u2022 When a self-test is performed, the M-MDS automatically reads out the pending codes.<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
Mode 8: Force drive<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
\u2022 Mode 8 performs force drive.<\/div>\n
\u2022 The M-MDS is used only for forcibly driving the valve for the outlet opening to atmosphere of the charcoal canister to check for fuel evaporative gas leakage.<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
Mode 9: Vehicle information read out<\/div>\n<\/dd>\n<\/dl>\n
\n
\n
\u2022 Mode 9 reads out information such as the vehicle identification number and calibration ID number.<\/div>\n<\/dd>\n<\/dl>\n



\n<\/a><\/p>\n

Topological figure<\/p>\n

\u2022 A Controller Area Network (CAN) system has been adopted which performs transmission\/reception of multiple module signals.<\/div>\n
\u2022 There are multiple CAN buses in the vehicle and they are relayed by the body control module (BCM).<\/p>\n\n\n\n
\n\n\n\n
<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
am3zzw00034894<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
* :Differs depending on availability of each module, based on the specification.<\/div>\n


<\/p>\n

<\/a><\/p>\n

Parent\/child module diagnosis<\/p>\n

\n
\n
\u2022 Each CAN bus consists of a parent module which integrates multiple modules, and other child modules.<\/div>\n
\u2022 When a child module detects a malfunction, it sends the malfunction information to the parent module via CAN communication, and the parent module outputs a DTC according to the malfunction content.<\/p>\n
\n
\n
Note<\/div>\n<\/dd>\n
\n
\u2022 DTCs are not supported, but because the data logger also has child modules which it supports, verify DTCs even with the child modules if the PID\/data monitor function or simulation function is used.<\/div>\n<\/dd>\n<\/dl>\n<\/div>\n
\u2022 The parent\/child module relationship for each CAN bus is as follows.<\/div>\n<\/dd>\n<\/dl>\n

\n

\u2014: Not applicable<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n
\n

Parent module<\/p>\n<\/th>\n

\n

Body control module (BCM)<\/p>\n<\/th>\n

\n

Vehicle control module<\/p>\n<\/th>\n

\n

PCM<\/p>\n<\/th>\n

\n

TCM<\/p>\n<\/th>\n<\/tr>\n<\/thead>\n

\n
Child module<\/span><\/div>\n<\/td>\n
\n
Electrical supply unit (ESU)<\/div>\n<\/td>\n
\n
Rear side radar sensor<\/div>\n<\/td>\n
\n
NOx sensor<\/div>\n<\/td>\n
\n
Shift panel (indicator)<\/div>\n<\/td>\n<\/tr>\n
\n
Door-electrical supply unit<\/div>\n<\/td>\n
\n
Front radar sensor<\/div>\n<\/td>\n
\n
PM sensor<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
LF control unit<\/div>\n<\/td>\n
\n
Parking assist unit (ultrasonic)<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
Light control module<\/div>\n<\/td>\n
\n
Driver monitoring camera unit<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
Instrument cluster<\/div>\n<\/td>\n
\n
360\u00b0 view monitor control module<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
Active driving display<\/div>\n<\/td>\n
\n
Parking assist unit (optical)<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
Steering angle sensor<\/div>\n<\/td>\n
\n
Forward sensing camera (FSC)<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n
\n
\u2014<\/div>\n<\/td>\n
\n
Front side radar sensor<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n
\n
\u2014<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
* :Differs depending on availability of each module, based on the specification.<\/div>\n



\n<\/a><\/p>\n

Block Diagram<\/p>\n\n\n\n
\n\n\n\n
<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
am3zzw00024595<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n

<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

BASIC KNOWLEDGE SM2337313 id990200000100 Outline \u2022 Vehicle has an on-board diagnostic function to facilitate malfunction diagnosis. Terminology Mazda Modular Diagnostic System (M-MDS) \u2022 The M-MDS is an on-board diagnostic tool developed for the improvement of servicing efficiency, maintenance quality, and convenience, and the reduction of security risk. \u2022 The M-MDS consists of a laptop PC for servicing work, the Mazda Diagnostic and Repair Software (MDARS) on-board diagnostic software, the VCM- used as a communication device […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"class_list":["post-9681","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.hexorcism.com\/19BP\/wp-json\/wp\/v2\/pages\/9681","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.hexorcism.com\/19BP\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.hexorcism.com\/19BP\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.hexorcism.com\/19BP\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.hexorcism.com\/19BP\/wp-json\/wp\/v2\/comments?post=9681"}],"version-history":[{"count":0,"href":"https:\/\/www.hexorcism.com\/19BP\/wp-json\/wp\/v2\/pages\/9681\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.hexorcism.com\/19BP\/wp-json\/wp\/v2\/media?parent=9681"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}