Nissan fault codes are Diagnostic Trouble Codes (DTCs) stored by a vehicle’s control modules when the onboard diagnostic system detects a fault. These codes identify the system or operating condition associated with the problem and provide a starting point for diagnosis. A Nissan DTC can relate to the engine, transmission, emissions system, body electronics, chassis components, or communication between control modules.
Nissan vehicles use four main DTC categories: P (Powertrain), B (Body), C (Chassis), and U (Network Communication). They can include standardized OBD-II codes used across multiple vehicle manufacturers as well as manufacturer-specific codes whose definitions depend on Nissan applications. For this reason, the vehicle model, model year, engine, and control module can be important when interpreting a code.
The Nissan fault code list below explains the meaning and system associated with each DTC. A fault code should be treated as diagnostic information rather than proof that a specific component needs replacement. After identifying a code, the next step is to verify its definition for the vehicle and diagnose the related system before replacing parts or clearing the code.
What Are Nissan Fault Codes?
Nissan fault codes are alphanumeric Diagnostic Trouble Codes (DTCs) that identify faults detected by a vehicle’s onboard control modules. When a monitored value or operating condition falls outside its expected range, the responsible module can store a DTC in memory. A diagnostic scanner can then retrieve the code to identify the system and fault condition that require further testing.
A Nissan vehicle contains multiple electronic control modules responsible for different functions. For example, the Engine Control Module (ECM) monitors engine and emissions functions, while other modules control systems such as the transmission, anti-lock brakes, airbags, body electronics, and vehicle communication network. A fault detected within one of these monitored systems can generate a corresponding DTC.
A stored DTC does not always cause a dashboard warning light immediately. Depending on the fault and monitoring conditions, a code may appear as pending, stored, or permanent where the vehicle and diagnostic system support these statuses. The Check Engine Light primarily relates to faults monitored by the engine and emissions diagnostic system, while faults in other modules may activate different warning indicators.
Most importantly, a Nissan fault code identifies a detected fault condition rather than confirming which component has failed. For example, a DTC associated with a sensor circuit does not automatically mean the sensor itself requires replacement. The fault may originate from the sensor, wiring, electrical connector, power supply, ground circuit, or another condition affecting the sensor reading. The code therefore provides the starting point for diagnosis rather than the final diagnosis.
How Are Nissan DTC Codes Structured?
Nissan DTC codes use a standardized alphanumeric structure in which the first character identifies the vehicle system and the following characters provide additional information about the fault. A typical code contains five characters, such as P0300. Reading this structure helps identify the general fault category before checking the complete code definition.
The first character places a DTC into one of four main categories. P identifies Powertrain faults involving systems such as the engine, transmission, fuel delivery, ignition, and emissions controls. B identifies Body faults involving body-related electrical and electronic systems. C identifies Chassis faults involving systems such as braking, steering, and vehicle dynamics. U identifies Network Communication faults involving communication between electronic control modules.
The second character helps distinguish standardized codes from codes assigned for manufacturer-specific applications. For many commonly encountered OBD-II powertrain codes, a 0 in this position indicates a standardized generic code, while a 1 commonly identifies a manufacturer-controlled code. However, DTC interpretation should be based on the complete code and the applicable diagnostic specification rather than determining its meaning from one digit alone.
The remaining characters narrow the DTC to a particular subsystem and fault condition. For example, P0300 belongs to the Powertrain category and is associated with a random or multiple-cylinder misfire condition. By contrast, a code beginning with U points the diagnostic process toward communication or network operation rather than directly toward an engine mechanical problem.
Nissan vehicles can therefore contain both generic OBD-II codes and Nissan-specific DTCs. Generic codes have standardized definitions across applicable OBD-II vehicles, while manufacturer-specific codes require the Nissan definition for the relevant application. The complete DTC, Nissan model, model year, engine configuration, and control module should be verified before a manufacturer-specific code is diagnosed.
What Do Nissan P Codes Mean?
Nissan P codes identify powertrain faults involving the engine, transmission, fuel system, ignition system, and emissions controls. The letter “P” stands for Powertrain, making this category especially relevant when diagnosing a Check Engine Light, engine performance problem, emissions fault, or transmission-related malfunction.
P codes include both generic OBD-II codes and manufacturer-specific codes. Generic codes use standardized definitions across applicable OBD-II vehicles, while Nissan-specific codes require the definition assigned to the relevant Nissan application. A code should therefore be matched by its complete identifier rather than interpreted only from the component or system mentioned in its description.
The table below lists common Nissan P codes and their meanings.
| DTC | Meaning | System |
|---|---|---|
| P0011 | Intake Valve Timing Control Performance, Bank 1 | Variable Valve Timing |
| P0021 | Intake Valve Timing Control Performance, Bank 2 | Variable Valve Timing |
| P0031 | Heated Oxygen Sensor Heater Control Circuit Low, Bank 1 Sensor 1 | Emissions / O2 Sensor |
| P0051 | Heated Oxygen Sensor Heater Control Circuit Low, Bank 2 Sensor 1 | Emissions / O2 Sensor |
| P0100 | Mass or Volume Air Flow Circuit Malfunction | Air Intake / MAF |
| P0101 | Mass Air Flow Circuit Range/Performance Problem | Air Intake / MAF |
| P0102 | Mass Air Flow Circuit Low Input | Air Intake / MAF |
| P0103 | Mass Air Flow Circuit High Input | Air Intake / MAF |
| P0112 | Intake Air Temperature Circuit Low Input | Air Intake / IAT |
| P0113 | Intake Air Temperature Circuit High Input | Air Intake / IAT |
| P0117 | Engine Coolant Temperature Circuit Low Input | Engine Cooling / ECT |
| P0118 | Engine Coolant Temperature Circuit High Input | Engine Cooling / ECT |
| P0120 | Throttle/Pedal Position Sensor/Switch Circuit Malfunction | Electronic Throttle |
| P0122 | Throttle/Pedal Position Sensor/Switch Circuit Low Input | Electronic Throttle |
| P0123 | Throttle/Pedal Position Sensor/Switch Circuit High Input | Electronic Throttle |
| P0130 | O2 Sensor Circuit Malfunction, Bank 1 Sensor 1 | Emissions / O2 Sensor |
| P0131 | O2 Sensor Circuit Low Voltage, Bank 1 Sensor 1 | Emissions / O2 Sensor |
| P0132 | O2 Sensor Circuit High Voltage, Bank 1 Sensor 1 | Emissions / O2 Sensor |
| P0133 | O2 Sensor Circuit Slow Response, Bank 1 Sensor 1 | Emissions / O2 Sensor |
| P0134 | O2 Sensor Circuit No Activity Detected, Bank 1 Sensor 1 | Emissions / O2 Sensor |
| P0135 | O2 Sensor Heater Circuit Malfunction, Bank 1 Sensor 1 | Emissions / O2 Sensor |
| P0171 | System Too Lean, Bank 1 | Fuel / Air Metering |
| P0172 | System Too Rich, Bank 1 | Fuel / Air Metering |
| P0174 | System Too Lean, Bank 2 | Fuel / Air Metering |
| P0175 | System Too Rich, Bank 2 | Fuel / Air Metering |
| P0300 | Random/Multiple Cylinder Misfire Detected | Ignition / Combustion |
| P0301 | Cylinder 1 Misfire Detected | Ignition / Combustion |
| P0302 | Cylinder 2 Misfire Detected | Ignition / Combustion |
| P0303 | Cylinder 3 Misfire Detected | Ignition / Combustion |
| P0304 | Cylinder 4 Misfire Detected | Ignition / Combustion |
| P0305 | Cylinder 5 Misfire Detected | Ignition / Combustion |
| P0306 | Cylinder 6 Misfire Detected | Ignition / Combustion |
| P0325 | Knock Sensor 1 Circuit Malfunction | Engine / Knock Control |
| P0335 | Crankshaft Position Sensor A Circuit Malfunction | Engine Timing |
| P0340 | Camshaft Position Sensor Circuit Malfunction, Bank 1 | Engine Timing |
| P0400 | Exhaust Gas Recirculation Flow Malfunction | EGR / Emissions |
| P0420 | Catalyst System Efficiency Below Threshold, Bank 1 | Catalytic Converter / Emissions |
| P0430 | Catalyst System Efficiency Below Threshold, Bank 2 | Catalytic Converter / Emissions |
| P0440 | Evaporative Emission Control System Malfunction | EVAP |
| P0442 | Evaporative Emission Control System Leak Detected, Small Leak | EVAP |
| P0446 | Evaporative Emission Control System Vent Control Circuit Malfunction | EVAP |
| P0455 | Evaporative Emission System Leak Detected, Large Leak | EVAP |
| P0500 | Vehicle Speed Sensor Malfunction | Vehicle Speed / Powertrain |
| P0505 | Idle Control System Malfunction | Idle Control |
| P0700 | Transmission Control System Malfunction | Transmission |
| P0715 | Input/Turbine Speed Sensor Circuit Malfunction | Transmission |
| P0720 | Output Speed Sensor Circuit Malfunction | Transmission |
| P0740 | Torque Converter Clutch Circuit Malfunction | Transmission |
| P0744 | Torque Converter Clutch Circuit Intermittent | Transmission |
| P0750 | Shift Solenoid A Malfunction | Transmission |
P codes beginning with P0 commonly belong to the standardized OBD-II powertrain range, while portions of the P1 range contain manufacturer-specific definitions. Additional P2 and P3 codes expand coverage of powertrain faults. The exact definition should still be checked against the applicable Nissan diagnostic information because code implementation can depend on the vehicle and control system.
For example, P0300 identifies a random or multiple-cylinder misfire condition, but it does not identify one failed part. Ignition components, fuel delivery, air intake faults, electrical problems, or mechanical conditions can produce a misfire. Likewise, P0101 indicates a Mass Air Flow circuit range/performance problem rather than proving that the MAF sensor itself has failed. Diagnostic testing is required before parts are replaced.
What Do Nissan B Codes Mean?
Nissan B codes identify faults associated with body-related electronic and electrical systems. The letter “B” stands for Body. Depending on the Nissan model and equipment, these DTCs can relate to systems such as supplemental restraints, occupant detection, climate control, lighting, security functions, doors, seats, and other body electronics.
Unlike the generic powertrain codes commonly retrieved through basic OBD-II scans, many body codes are manufacturer-specific. Their definitions and diagnostic procedures can differ according to the Nissan model, model year, installed equipment, and control module. A scanner must also support the relevant Nissan module to retrieve body DTCs that are not available through a basic engine-only OBD-II scan.
Examples of systems that can store B-series DTCs include the Body Control Module (BCM), airbag or Supplemental Restraint System (SRS) control unit, automatic climate control system, intelligent key system, and other body-related modules. Because these systems vary considerably between Nissan applications, the complete B code must be matched with vehicle-specific Nissan diagnostic information before a repair decision is made.
A B code should not be interpreted as confirmation that the component named in its definition has failed. A body-system fault can also result from damaged wiring, loose or corroded connectors, low system voltage, communication problems, configuration issues, or an open or short circuit. This distinction is particularly important for restraint and safety-related systems, where replacing components based only on a DTC can lead to an incorrect diagnosis.
For this reason, there is no single universal Nissan B-code list that can safely assign the same manufacturer-specific definition to every Nissan vehicle. The correct lookup process is to record the complete B code and identify the model, model year, relevant control module, and applicable Nissan definition before beginning diagnosis.
What Do Nissan C Codes Mean?
Nissan C codes identify Diagnostic Trouble Codes associated with chassis systems, including braking, steering, wheel-speed monitoring, and vehicle stability functions. The letter “C” stands for Chassis and separates these faults from powertrain, body, and network communication DTCs.
Chassis faults are commonly stored by control modules responsible for systems such as the Anti-lock Braking System (ABS), Vehicle Dynamic Control (VDC), traction control, electric or electronic power steering, and other chassis-related functions. For example, an ABS control unit can store a C-series DTC when it detects an abnormal wheel-speed signal, electrical circuit fault, or problem with another input required for braking and stability control.
Many Nissan C codes are manufacturer-specific. This means the same numerical sequence should not be assigned a definition without checking the applicable Nissan model, model year, control module, and diagnostic information. The code retrieved by a scan tool should be recorded in full before determining its meaning.
A chassis DTC also identifies a detected fault condition rather than automatically identifying a failed component. For example, a wheel-speed-related fault can originate from the sensor, wiring, connector, tone or encoder ring, power or ground circuit, or an abnormal signal caused by another physical condition. Testing the associated circuit and system is therefore necessary before replacing the sensor or another chassis component.
Chassis codes require particular attention because some faults can affect safety-related vehicle functions. An illuminated ABS, VDC, traction control, or steering warning indicator can indicate that the corresponding system has detected a malfunction or that a function has been limited or disabled. The meaning and severity of the stored C code should therefore be verified for the specific Nissan before the vehicle is returned to normal operation.
What Do Nissan U Codes Mean?
Nissan U codes identify communication and network faults involving electronic control modules and the data networks that connect them. The letter “U” represents Network Communication, so these codes direct diagnosis toward communication between modules rather than toward one mechanical vehicle system.
Modern Nissan vehicles use electronic networks to exchange information between control modules. Depending on the vehicle architecture, modules such as the ECM, Transmission Control Module (TCM), Body Control Module (BCM), ABS/VDC control unit, combination meter, and other electronic controllers need to send and receive data for vehicle functions to operate correctly. A communication failure can therefore affect several systems at the same time.
| DTC | Meaning | System |
|---|---|---|
| U0001 | High Speed CAN Communication Bus | CAN Network |
| U0073 | Control Module Communication Bus “A” Off | CAN / Module Network |
| U0100 | Lost Communication With ECM/PCM “A” | Engine Control / Network |
| U0101 | Lost Communication With TCM | Transmission Control / Network |
| U0121 | Lost Communication With ABS Control Module | ABS / Network |
| U0140 | Lost Communication With Body Control Module | Body Control / Network |
| U0155 | Lost Communication With Instrument Panel Cluster Control Module | Instrument Cluster / Network |
U codes can result from several electrical and network conditions rather than a failed control module alone. Examples include an open communication circuit, a shorted CAN line, poor electrical connections, low battery voltage, loss of module power or ground, damaged wiring, or a module that is no longer communicating with the network.
For example, U0100 indicates lost communication with the ECM/PCM, but the code alone does not prove that the ECM has failed. The diagnostic process must determine whether the module has adequate power and ground, whether the network circuits are intact, and whether other modules can communicate normally. Replacing the ECM without completing these checks can leave the original communication fault unresolved.
Multiple U codes stored in several modules can also be related to one underlying network or voltage problem. If several control units simultaneously report lost communication with the same module, the shared electrical supply, ground, connectors, network wiring, and communication status should be evaluated before treating every stored code as an independent failure.
As with Nissan B and C codes, manufacturer-specific U-code definitions can depend on vehicle application. The complete DTC, Nissan model, model year, affected module, and applicable diagnostic information should be verified before a network fault is diagnosed or a control module is replaced.
How Do You Read Nissan Fault Codes With an OBD2 Scanner?
To read Nissan fault codes, connect a compatible OBD2 scanner to the vehicle’s diagnostic port, access the appropriate control module, and retrieve the stored DTCs before clearing any diagnostic information. A basic OBD2 scanner can retrieve many powertrain codes, while an enhanced scanner with Nissan-specific coverage may be required to access ABS, airbag, body, transmission, and other control modules.
Start by locating the OBD-II diagnostic connector, which is normally positioned inside the passenger compartment near the driver’s side of the dashboard. Connect the scanner with the vehicle switched off unless the scan tool manufacturer specifies a different procedure. Turn the ignition to the required position and allow the scanner to establish communication with the vehicle.
Select the diagnostic or code-reading function after communication is established. Depending on the scanner and Nissan model, the tool may display stored, pending, or permanent DTCs. Enhanced diagnostic equipment can also identify codes stored in individual modules such as the ECM, TCM, BCM, ABS/VDC control unit, and SRS control unit.
Record every DTC before clearing the vehicle’s memory. For example, if the scanner retrieves P0300 and P0171 together, both codes should be retained because the relationship between a misfire condition and a lean air-fuel condition can provide useful diagnostic context. Diagnosing only one code while ignoring related DTCs can lead the troubleshooting process in the wrong direction.
Freeze-frame and live data should also be reviewed when the vehicle and scanner provide them. Freeze-frame data records operating conditions associated with certain faults, such as engine speed, engine load, coolant temperature, vehicle speed, and fuel-trim values. These values can help establish when the fault occurred and provide more information than the DTC definition alone.
Do not erase Nissan fault codes immediately after reading them. Clearing the codes can remove useful diagnostic information and reset certain monitored conditions. The correct sequence is to retrieve and record the DTCs, identify their definitions, review available diagnostic data, diagnose the underlying fault, complete the required repair, and then clear and retest the system.
Does a Nissan Fault Code Tell You Which Part Needs Replacing?
No. A Nissan fault code identifies the system, circuit, or operating condition in which a problem was detected; it does not automatically identify the component that needs replacement. The component mentioned in a DTC definition is part of the diagnostic context, not proof that the component itself has failed.
For example, P0101 indicates a Mass Air Flow (MAF) circuit range/performance problem. Replacing the MAF sensor solely because P0101 is stored skips the diagnostic process. The abnormal airflow measurement can be related to the sensor, its electrical circuit, connector condition, intake airflow, or another condition that causes the measured value to differ from the value expected by the ECM.
The same principle applies to misfire codes. P0301 identifies a misfire detected on cylinder 1, but it does not specify one defective part. The diagnostic process may need to evaluate ignition, fuel delivery, electrical circuits, air supply, and mechanical condition. Replacing a spark plug or ignition coil without testing can fail to resolve the DTC when the actual cause is elsewhere.
Network codes provide another clear example. U0101 indicates lost communication with the Transmission Control Module, but this does not prove that the TCM itself has failed. Loss of module power, a poor ground, damaged network wiring, connector problems, low system voltage, or another communication fault can prevent the module from communicating.
A reliable repair therefore follows a specific sequence: read the DTC, confirm its definition for the Nissan application, review related codes and diagnostic data, identify possible causes, test the affected system, confirm the failed condition, and repair the verified cause. Parts should be replaced when diagnostic evidence identifies them as faulty rather than because their names appear in a fault-code description.
This distinction is especially important with Nissan manufacturer-specific DTCs because the applicable definition and diagnostic procedure can vary by model, model year, engine, transmission, or control module. Verify the vehicle application before using a Nissan DTC to make a repair decision.
Can the Same Nissan Fault Code Have Different Meanings on Different Models?
Yes. Some Nissan fault codes can require different interpretations depending on the model, model year, engine, transmission, control module, and whether the DTC is generic or manufacturer-specific. For this reason, the complete code should be matched to the specific vehicle before diagnosis begins.
Generic OBD-II codes provide standardized definitions across applicable vehicles. For example, a standardized powertrain DTC retains its basic definition across manufacturers that implement that code. However, the diagnostic procedure and components involved can still differ because Nissan vehicles use different engines, sensors, wiring layouts, control strategies, and powertrain configurations.
Manufacturer-specific DTCs require greater attention to vehicle application. These codes are defined within manufacturer-controlled ranges and can contain diagnostic information specific to Nissan systems. A definition obtained for one Nissan model or control module should not automatically be applied to another vehicle simply because the alphanumeric code is identical.
Model year is also important because vehicle systems change between generations and production periods. Nissan can introduce a different engine, transmission, sensor arrangement, electronic control module, or network architecture while retaining the same model name. Diagnostic information that applies to an earlier vehicle may therefore be inappropriate for a later version.
Engine and transmission configuration can further change the diagnostic context. Two examples of the same Nissan model can use different powertrains, and the systems monitored by their control modules may not be identical. The correct diagnostic information should therefore be selected using the vehicle’s exact application rather than the model name alone.
The safest lookup sequence is DTC → Nissan model → model year → engine or powertrain → control module → applicable code definition. This process is especially important for B, C, and U codes and other manufacturer-specific DTCs, where a generic online code description may not provide enough information for an accurate diagnosis.
Can You Drive a Nissan With a Fault Code?
Whether you can drive a Nissan with a fault code depends on the fault, the warning indicators, the vehicle’s behavior, and the system affected. A stored DTC does not automatically mean the vehicle must be stopped immediately, but a code should not be assumed to be safe simply because the vehicle still drives normally.
Some faults do not immediately prevent normal vehicle operation. For example, an emissions-related DTC may be stored while the engine continues to start, idle, and accelerate normally. The code still requires diagnosis because the underlying problem can affect emissions, fuel control, vehicle performance, or another monitored function even when no obvious drivability symptom is present.
Greater caution is required when the fault is accompanied by symptoms such as severe misfiring, substantial loss of power, abnormal transmission operation, overheating, stalling, unusual mechanical noise, braking problems, or steering problems. These symptoms provide additional information about the severity of the condition and should not be evaluated from the DTC number alone.
Dashboard warning behavior also matters. A warning indicator associated with a safety-critical or potentially damaging condition requires more attention than a stored code with no active symptoms. For example, faults involving braking, steering, engine temperature, or other critical systems can require the vehicle to be stopped rather than driven until the problem is evaluated.
A flashing Check Engine Light should be treated more seriously than a steadily illuminated light because it can accompany an active fault that requires prompt attention. The driver should reduce unnecessary operation and have the cause diagnosed rather than continuing to drive solely because the engine remains running.
The DTC category alone cannot determine whether driving is safe. A P code can represent anything from an emissions-related fault to a serious drivability problem, while C and U codes can affect chassis or communication systems in different ways. Determine whether the vehicle should continue to be driven by evaluating the specific DTC together with warning lights, symptoms, affected systems, and vehicle-specific diagnostic information.
Read more: Nissan Qashqai Not Locking: Causes, Fixes & Diagnosis
Should You Clear a Nissan Fault Code After Reading It?
No. You should not clear a Nissan fault code immediately after reading it because doing so can remove diagnostic information needed to identify the underlying problem. Record the complete DTC and available diagnostic data first, then diagnose and repair the fault before clearing the code and testing the vehicle again.
A stored DTC provides more than a description of the detected problem. Depending on the vehicle, control module, and scanner, diagnostic information can include the code status, related DTCs, freeze-frame data, and live operating values. These details help establish the conditions under which the fault occurred and can be useful when distinguishing between several possible causes.
Clearing a code without diagnosing the fault does not repair the condition that caused it. If the monitored problem remains present, the control module can detect the fault again and store the DTC after the required monitoring conditions are met. The warning light may therefore return even though it temporarily disappeared after the codes were erased.
Code clearing can also reset diagnostic information or monitored conditions that are useful during troubleshooting. For this reason, retrieve and record all relevant codes before using the scanner’s erase function. If several DTCs are present, consider their relationship before treating each code as a separate failure.
The correct sequence is read → record → diagnose → repair → clear → retest. After the verified fault has been repaired, clear the DTC according to the appropriate procedure and operate or test the vehicle under the conditions required to determine whether the fault returns. A code that reappears indicates that the detected condition remains present or that further diagnosis is required.
What Should You Do After Finding Your Nissan DTC?
After finding a Nissan DTC, verify its exact meaning for the vehicle, identify the affected system, review related diagnostic information, test the possible causes, repair the confirmed fault, and retest the system. A fault-code lookup is the beginning of diagnosis rather than the final repair decision.
First, record the complete alphanumeric code exactly as displayed by the scanner. P0300, P0301, and P0302, for example, belong to the same general misfire category but identify different detected conditions. Recording only part of the code can therefore change the diagnostic direction.
Second, verify the DTC against the specific Nissan application. Use the model, model year, engine or powertrain configuration, and control module when required. This step is particularly important for manufacturer-specific B, C, U, and P codes because their applicable definitions can depend on vehicle configuration.
Third, review all related DTCs instead of diagnosing one code in isolation. Several codes can originate from the same underlying condition. For example, one electrical supply, network, or air-fuel problem can cause multiple modules or monitored systems to report faults. The relationship between the codes can therefore provide diagnostic evidence.
Fourth, examine the available diagnostic data and vehicle symptoms. Freeze-frame information, live sensor values, warning indicators, starting behavior, idle quality, acceleration, transmission operation, and other observations can help determine whether the DTC matches an active vehicle problem.
Fifth, test the system associated with the code before replacing components. Depending on the DTC, diagnosis can involve checking wiring, connectors, power and ground circuits, sensor signals, network communication, air or vacuum leaks, fuel delivery, ignition components, or mechanical conditions. The tests should confirm the cause rather than assume that the component named in the DTC definition is defective.
Finally, repair the confirmed fault, clear the stored code when appropriate, and retest the vehicle. A successful repair is confirmed when the relevant system operates correctly and the DTC does not return after the required monitoring conditions have been completed.
Individual Nissan DTC pages can provide the next level of diagnostic detail. For example, dedicated guides for P0300 Nissan, P0101 Nissan, or P0420 Nissan can explain the code definition, symptoms, possible causes, diagnostic procedure, and repair options for that specific fault. This structure allows the main Nissan fault-code list to function as a lookup hub while individual DTC guides handle deeper troubleshooting.