Free ASE L1 Exam Flashcards

A diagnostic process that explains why the fault occurred, not just which part reacted to it. For L1 work, ask what condition damaged, misled, overheated, contaminated, or disabled the failed component before replacing it.

A symptom is what the driver, scan tool, or emissions test reveals. The cause is the physical, electrical, or control problem creating it. Replacing the component named by a DTC can miss the actual cause.

Use freeze frame, recorded scan data, wiggle tests, heat or vibration checks, and duplicate conditions. A fault that is absent in the bay must be diagnosed from the conditions that made it appear.

Low compression, incorrect cam timing, restricted exhaust, or vacuum leakage can push fuel trims and misfire counters even when sensors and injectors are good. Prove engine breathing and mechanical condition before condemning controls.

A repair is verified when the original symptom is gone under the same operating conditions and the related monitor or data trend behaves normally. Clearing codes alone does not prove the fault is fixed.

Compare what the PCM requests with what the system reports. A gap between commanded and actual position, pressure, flow, or timing points toward actuator limits, mechanical blockage, wiring faults, or feedback sensor errors.

Freeze frame shows the operating conditions present when a fault was stored. Load, speed, temperature, and trim data help decide whether to test at idle, cruise, acceleration, deceleration, cold start, or hot restart.

A rationality check asks whether a sensor reading makes sense compared with other inputs and current conditions. A sensor can stay within its electrical range and still be wrong for the engine state.

The PCM learns corrections for fuel, idle, throttle, and other controls. After correcting a major fault, learned values may need to be reset or relearned so old compensation does not mask the repair.

Enhanced data adds manufacturer-specific PIDs, bidirectional controls, and test results beyond generic OBD II. Use it when generic data does not show the detail needed for an advanced L1-level decision.

Positive trim means the PCM is adding fuel because the feedback system sees a lean result. Common causes include unmetered air, low fuel delivery, incorrect airflow data, exhaust leaks near sensors, or fuel quality problems.

Negative trim means the PCM is subtracting fuel because feedback suggests a rich result. Look for leaking injectors, excessive fuel pressure, saturated EVAP purge, biased airflow data, or contaminated engine oil vapors.

This pattern often points to a vacuum leak or small amount of unmetered air. The leak is a larger percentage of total airflow at idle, so the trim correction is more obvious there.

A lean correction that grows with load suggests the engine cannot receive enough fuel or measured airflow is inaccurate at higher flow. Check pump volume, restrictions, pressure control, injector delivery, and MAF accuracy.

A trim problem on one bank points toward bank-specific causes such as an intake leak, injector issue, exhaust leak, valve sealing problem, or oxygen sensor bias. Similar trims on both banks point toward shared inputs or supply.

If the MAF reports less air than the engine actually ingests, the PCM commands too little fuel and trims go positive. Confirm with airflow plausibility, volumetric efficiency, sensor response, and intake leak inspection.

MAP should agree with engine load, throttle angle, altitude, vacuum, and rpm trends. A biased MAP signal can mislead load calculation and cause incorrect spark, fuel, EGR, and transmission decisions.

Pressure shows resistance in the fuel rail; volume shows delivery capacity. A weak pump or restriction may show acceptable pressure at idle yet fail when flow demand rises.

Injector balance compares how much each injector drops rail pressure when pulsed equally. Uneven drops suggest flow variation, leakage, restriction, or electrical control issues that can create cylinder-specific trims and misfires.

Throttle systems compare pedal sensors, throttle position sensors, motor command, and actual plate movement. Correlation faults require checking signal agreement, power and ground integrity, mechanical binding, and relearn needs.

A misfire can be caused by spark, fuel, compression, air leakage, exhaust dilution, or control timing. Use cylinder contribution, ignition waveform, injector command, and mechanical tests to separate the causes.

Secondary ignition patterns show firing demand, spark duration, and coil behavior. High firing demand can indicate a wide gap, lean mixture, or open secondary path; low demand can suggest fouling or a shorted path.

A current ramp shows coil primary current buildup and control. Abnormal shape, missing dwell, or no current points to power, ground, driver, coil, or command problems rather than guessing from a stored misfire code.

Misfires that appear mainly under load often reveal weak ignition, lean fuel delivery, or cylinder pressure problems. Higher cylinder pressure increases the voltage needed to jump the plug gap.

Some systems need a crankshaft variation relearn after related repairs so the PCM can distinguish normal crank speed changes from actual misfire events. Skipping the relearn can lead to false or missed misfire detection.

Continuous monitors run whenever enabling conditions allow during normal operation. Misfire, fuel system, and comprehensive component monitoring are used to detect faults that can affect emissions quickly.

Non-continuous monitors require specific enable criteria such as temperature, speed, load, fuel level, and time. Catalyst, EVAP, oxygen sensor, EGR, and secondary air tests may not run during every trip.

A pending DTC means the monitor detected a fault but the logic has not fully matured it into a confirmed code. Pending codes can explain why readiness is delayed or why a symptom is intermittent.

Mode 06 reports monitor test data before or after a code sets. Interpret it with the service information for that vehicle because test IDs, units, limits, and pass direction are manufacturer-specific.

Clearing codes resets monitor readiness and adaptive information. The vehicle must meet each monitor's enable criteria and complete the required checks before an OBD-based inspection can pass.

Voltage drop testing checks a circuit while it is operating under load. It finds resistance in powers, grounds, connectors, splices, and switches that an unloaded ohmmeter test can miss.

A circuit can show correct voltage with no load but fail when current is required. Use an appropriate load, current measurement, or commanded actuator test to prove the circuit can do work.

A poor shared ground can bias several sensor readings at once. When unrelated PIDs shift together or a sensor reading changes when another actuator turns on, inspect shared grounds and splice points.

A short on a reference circuit can pull down multiple sensors that share that feed. Unplug sensors one at a time using service information to isolate whether the harness or a sensor is loading the circuit.

A scan tool shows processed data at a limited update rate; a scope shows the electrical waveform. Use the scope when timing, dropout, noise, pulse width, or signal shape matters.

EGR lowers combustion temperature by diluting the intake charge with inert exhaust gas. Too little EGR can raise NOx; too much or flow at idle can cause rough running, stalling, or hesitation.

Flow when the valve is commanded closed suggests the valve is leaking, stuck open, or carbon is holding it off its seat. The result is unwanted exhaust dilution during conditions that need a clean intake charge.

A purge valve stuck open can act like a vacuum leak and add fuel vapor at the wrong time. Symptoms may include hard starting after refueling, rough idle, rich or lean trim swings, and EVAP-related faults.

The vent valve lets filtered air enter or leave the canister during normal operation and closes during leak testing. A stuck vent can prevent monitor completion, cause refueling problems, or create leak-test failures.

Secondary air adds oxygen to the exhaust during selected operating conditions so oxidation can continue in the exhaust stream or catalyst. Diagnosis includes pump operation, valves, plumbing, check valves, and oxygen sensor response.

A working three-way catalyst stores and releases oxygen to help convert HC, CO, and NOx. Loss of oxygen storage causes the downstream oxygen sensor signal to resemble the upstream signal more closely.

The upstream sensor is used mainly for fuel control. The downstream sensor is used mainly to judge catalyst behavior. Do not condemn a catalyst until mixture control, sensor operation, exhaust leaks, and temperature are considered.

Misfire sends unburned fuel and oxygen into the converter, creating excessive heat during oxidation. Replacing the converter without repairing the misfire risks another failure.

A restricted converter limits exhaust flow and can cause low power, poor acceleration, excessive backpressure, and abnormal vacuum behavior. Confirm restriction before replacement and identify what overheated or damaged the substrate.

Before replacing a converter for an efficiency fault, verify fuel control, misfire status, oxygen sensor behavior, exhaust leaks, engine oil or coolant contamination, and applicable service information.

High hydrocarbons indicate unburned fuel or oil leaving the engine. Common causes include misfire, poor combustion, low compression, injector issues, vacuum leaks, oil consumption, or a catalyst unable to finish oxidation.

High carbon monoxide usually points to a rich mixture or incomplete oxidation. Check fuel pressure, injectors, EVAP purge, airflow data, oxygen sensor feedback, thermostat operation, and catalyst activity.

High NOx is associated with excessive combustion temperature or pressure. Check EGR flow, cooling system performance, lean operation, carbon deposits, spark timing control, and catalyst reduction capability.

The vehicle may still fail inspection because readiness proves the self-tests have run. Incomplete monitors after a repair mean the correct drive conditions have not yet completed or another fault is preventing execution.

A permanent DTC is cleared by the vehicle after the related monitor runs and passes. A scan tool clear command alone is not enough, so repair verification must include the correct monitor completion.