P015B Code: O2 Sensor Delayed Response Lean to Rich B1S1
Prove the Mixture Change Before Replacing the Sensor
P015B targets the lean-to-rich delay of Bank 1 Sensor 1. Save the event, confirm the mixture actually changed, then test leaks, fueling, wiring and calibration before replacing parts.
P015B means the PCM measured too much delay before the Bank 1 upstream oxygen or air/fuel sensor responded to a lean-to-rich change. It does not prove the sensor is bad. First establish that the commanded mixture changed on time; then separate air or exhaust leakage, fueling and purge errors, wiring, sensor response and VIN-specific calibration.
What P015B Means — Direction, Bank, and Sensor
The standard description is O2 Sensor Delayed Response — Lean to Rich (Bank 1, Sensor 1). Bank 1 is the side containing cylinder 1; an inline engine has only Bank 1. Sensor 1 is the upstream or pre-catalyst control sensor, not the downstream catalyst-monitor sensor.
The direction matters. P015B measures an initial delay before B1S1 follows a lean-to-rich exhaust change. P015A covers the opposite rich-to-lean delay on the same sensor. P0133 is a broader Bank 1 Sensor 1 slow-response code, while P0130/P0135 point toward circuit or heater faults.
The ECM creates or observes a calibrated lean-to-rich transition under defined conditions.
B1S1 does not begin responding within the time expected by that exact calibration.
Fuel trim, command, load, companion codes and sensor type decide what the graph means.
P015B Symptoms, Severity, and Driving Safety
P015B often turns on the MIL without a noticeable change in how the vehicle drives. Other symptoms depend on the underlying air, fuel, purge, wiring or sensor problem rather than the code name alone.
A steady MIL may be the only symptom. Several OEM bulletins describe P015B appearing without an obvious drivability complaint.
A history or pending event may be stored even when the engine idles and accelerates normally. Preserve its status before clearing it.
If a genuine air, fuel, purge or exhaust problem caused the delayed transition, the engine may idle unevenly or hesitate during load changes.
Abnormal correction may accompany the code, but P015B alone does not prove that fuel economy changed or identify the direction of the underlying mixture fault.
An active emissions DTC can prevent monitor readiness or an inspection pass until the cause is repaired and the monitor completes.
P0130-series circuit faults, P0171/P0172 mixture codes, misfires, MAF/MAP, fuel-pressure or EVAP codes can supply the missing diagnostic direction.
Six P015B Causes in Test Order
This order avoids a common mistake: replacing the B1S1 sensor before proving that the exhaust mixture reached it when expected. The cause list is a testing sequence, not a claimed failure-rate ranking.
Intake or Upstream Exhaust Leak
Unmetered intake air or fresh air entering the exhaust before B1S1 can change the mixture evidence and delay the expected lean-to-rich response.
How to prove it: Inspect the complete intake path and sensor sealing, then use the OEM-approved smoke or exhaust-leak method. Do not condemn the sensor because fuel trim moved.
Check firstFuel Delivery, Injector, or EVAP Purge Problem
Low or unstable pressure, a restricted or leaking injector, incorrect fuel, or uncontrolled purge flow can prevent the commanded mixture from changing as expected.
How to prove it: Use companion codes, pressure evidence, injector balance and purge control tests appropriate to the VIN. A scan PID is not an independent physical pressure measurement.
Check firstConnector, Harness, Heater, or Ground Fault
Water intrusion, heat damage, poor terminal tension, chafing or a related heater fault can slow or corrupt the B1S1 signal.
How to prove it: Inspect the connector and hot-zone routing, then test supply, ground and signal paths with the exact OEM diagram and specified equipment.
Test directlyContaminated or Aged B1S1 Sensor
Oil, coolant, silicone or fuel contamination and normal aging can reduce the response of a narrowband O2 sensor or wideband A/F/UEGO sensor.
How to prove it: First identify the sensor technology and correct PID. Prove that the mixture changed promptly while the sensor response remained delayed.
Test directlyVIN-Specific Software or Monitor Calibration
Some OEM bulletins document an overly sensitive monitor or a calibration anomaly that can set P015B under limited operating conditions.
How to prove it: Check VIN, engine, calibration ID and bulletin applicability. A software example for one vehicle is not permission to reprogram every P015B vehicle.
Test directlyRare ECM/PCM Hardware Fault
A controller input fault is possible only after the sensor, mixture, wiring, powers, grounds and applicable software path have passed.
How to prove it: Follow the final OEM pinpoint-test branch. Do not replace or program a controller based only on P015B or a slow graph.
Final branchSoftware is vehicle-specific. Toyota has published a limited P015B calibration correction for named vehicles and conditions. Its existence proves that software can matter; it does not make reprogramming the universal first step.
Using UR1000 for P015B Scan Evidence
The iCARZONE UR1000 can save supported ECM codes, freeze frame, live data and diagnostic reports. On compatible vehicles, graph the available B1S1 lambda, equivalence-ratio, A/F-current or O2 PID beside commanded lambda, short- and long-term fuel trim, RPM and load. A two-bank comparison can help identify shared versus Bank 1 behavior when the architectures match.
Coverage and PID names vary by make, model, year, VIN, ECU and software. A scanner cannot physically measure sensor resistance, heater current, voltage drop or waveform, and it cannot prove an intake or exhaust leak. Use a meter, scope, smoke equipment, pressure gauge and OEM diagram where the diagnostic chart requires them.
iCARZONE UR1000 Bidirectional Scan Tool with ECU Coding
Preserve the original P015B event, review companion systems and compare the supported command, fuel-trim and B1S1 response. Confirm exact coverage by VIN.
Price checked August 17, 2026. Recheck price, availability and VIN/function coverage before purchase. ECU coding does not mean universal ECM firmware programming.
How to Diagnose P015B in 6 Steps
Work with the exhaust cool during inspection and keep the vehicle outdoors or on approved extraction equipment during running tests. Reproduce only the OEM-specified monitor conditions; a throttle snap at idle is not a universal P015B test.
Compact P015B Test Path
-
1
Save the Complete Event
- Record all-module DTCs, current/pending/permanent status, freeze frame, readiness and any available Mode $06 monitor result before clearing anything.
- Note recent battery work, refueling, engine repairs, oil or coolant use and the exact conditions when the MIL appeared.
-
2
Confirm Bank 1 Sensor 1 and Sensor Type
- Use VIN-specific cylinder numbering to identify Bank 1; on an inline engine there is only Bank 1. Sensor 1 is the upstream/pre-catalyst control sensor.
- Identify narrowband O2, wideband A/F or UEGO technology and the OEM PID names. Do not apply a universal 0.1–0.9 V pattern or resistance value.
-
3
Resolve Companion Codes and Visible Faults
- Diagnose relevant heater/circuit, misfire, MAF/MAP, fuel-pressure, EVAP and rich/lean codes in the order specified by the manufacturer.
- With the exhaust cool, inspect B1S1 sealing, connector, harness, intake ducts, vacuum lines and the upstream exhaust for damage or leakage.
-
4
Compare Command, Fuel Trim, and B1S1 Response
- Use UR1000 to save and graph supported commanded lambda, equivalence ratio, A/F current or O2 data, STFT/LTFT, RPM and load. On two-bank engines, Bank 2 can provide context—not a universal pass/fail reference.
- Reproduce only the OEM monitor conditions. The controller may judge delay during a deceleration fuel-shutoff event or another calibrated transition, not during a generic idle snap.
-
5
Prove the Delayed Branch With Physical Tests
- If the data shows a real delay, use the specified smoke, exhaust-leak, fuel-pressure, injector, purge, meter or scope test to isolate the air, fuel, wiring or sensor branch.
- Do not spray propane or cleaner to force a rich event, back-probe without the proper method, or use universal timing, voltage, current or resistance thresholds.
-
6
Repair, Reset, and Re-run the Monitor
- Repair only the proven leak, connector, harness, fuel, purge, sensor or applicable calibration issue. Use correct sensor handling, sealing, torque and programming voltage support.
- After evidence is saved, clear eligible codes, complete the OEM enable conditions and rescan current, pending and permanent status plus readiness. A temporarily dark MIL is not proof of repair.
How to Fix, Clear, and Budget for P015B
Seal Air or Exhaust Leaks
Repair the proven intake, vacuum, sensor-seat, flange or upstream exhaust leak before judging sensor speed.
Restore Fuel and Purge Control
Correct verified pressure, injector, fuel-quality or EVAP purge behavior that delayed the real mixture transition.
Repair Wiring or Replace B1S1
Restore failed terminals or conductors, or replace a sensor only after its response remains slow during a proven mixture event.
Apply Applicable Calibration
Program the ECM only when VIN, engine, calibration ID and current OEM service information support that branch.
After repair, complete required learns, clear eligible codes and run the exact enable conditions. Confirm the live and pending code remains absent and readiness returns. A permanent code is not manually erased; the vehicle clears it after its own successful OBD criteria are met.
Scan and Response Testing
VIN-specific quoteMonitor reproduction, data capture and time required to separate mixture delay from sensor delay.
Leak, Fuel, or Purge Repair
VIN-specific quoteLeak location, pressure diagnosis, injector access and EVAP-system design.
Connector, Harness, or B1S1
VIN-specific quoteSensor technology, hot-zone access, terminal serviceability and exhaust corrosion.
Calibration or Controller Work
VIN-specific quoteBulletin applicability, programming access, stable power support and post-update verification.
P015B does not identify a part or a universal repair price. Request a written estimate based on the VIN, proven cause, access, local labor and any related air, fuel, exhaust or contamination issue.
Vehicle Differences and DIY Limits
A narrowband gasoline sensor, wideband A/F sensor and UEGO system can report the same generic code through very different PIDs and electrical behavior. Monitor entry conditions, response thresholds and the number of qualifying events are calibration-specific.
May use a switching-voltage display, but only the OEM test defines the correct threshold and timing.
Use supported lambda, equivalence ratio or pump-current information; do not apply narrowband rules.
A bulletin may prescribe software for a limited VIN and condition after all applicability checks pass.
- Save codes, freeze frame and readiness.
- Confirm Bank 1, Sensor 1 and sensor type.
- Inspect cool, accessible ducts, wiring and connectors.
- Graph supported lambda and fuel-trim data.
- Exhaust-leak, pressure and injector testing.
- Wideband current and waveform diagnosis.
- Seized sensor or exhaust-thread repair.
- ECM programming or controller diagnosis.
Frequently Asked Questions About P015B
What does P015B mean?
Which sensor is Bank 1 Sensor 1?
Is P015B a Bank 2 code?
Does P015B prove the oxygen sensor is bad?
Can UR1000 diagnose P015B?
Can I drive with P015B?
Can I use a 0.1–0.9 volt switching test?
How do I clear P015B safely?
Sources and Technical Review Notes
- Ford 2024 OBD System Operation Summary — shows one OEM delayed-response monitor using calibrated lean/rich transition timing.
- GM PIP5633 hosted by NHTSA — lists vehicle-specific leak, connector, contamination, purge, fuel and injector checks before sensor replacement.
- Toyota T-SB-0110-14 hosted by NHTSA — confirms P015B direction/location and illustrates a limited calibration-related repair.
0 comments
