When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
So, 200 more miles and multiple drive cycles recommended By Jaguar to the CARB referee to me After the speedometer has been repaired and still O2 sensor not ready. Really interested to see if MarinMan has any luck with his dealer visit!
My car is a 2010 Jaguar XK 5.0L Convertible. Failed California Smog Test!!!
Well, I know this thread is almost 3 years old, but there are many other Jaguar Owners that are having this same problem in California right now, including me!
I'm convinced that this problem is a S/W-F/W issue. My car has sat with a dead battery since it failed SMOG in May of 2025.It was my brothers car.
Oxygen Sensor Monitor “INC”,
I put a new battery in it March of 2026. I've been working on it to get the Oxygen Sensor Monitor to become ready ever since. I have no other DTC codes/no engine light, etc... After I cleared all the codes with my scan tool, after I disconnected the Battery once (With the new Battery installed) all the other codes cleared "READY" after just a few short drives, maybe 45 to 65 miles.
I've tried everything listed in this thread, various drive cycles, replaced ALL 4: 02 sensors, oil/filter change, 91 octane fuel, Fuel/enjector cleaner, air filters, had the system checked for exhaust leaks when I had the 02 Sensors replaced. Dealer said they don't work on these 2010's anymore, British European motors in Campbell CA said they can't guarantee by flashing it that it will eventually clear the code. Ran two tanks of fuel thru it. I also beleive that having the fuel tank 3/4 to 1/4 full, helps some of the other INC's to become ready. I have the early 5.0L AJ133 engine.
I found this writeup either on a forum or AI found it for me. 2010 Jaguar XK 5.0L Dealer PCM update to fix a false INCs for the Oxygen Sensor Monitor
Jaguar issued a PCM software update for some 2010-era 5.0L AJ133 engines to correct false or stuck “Incomplete” O₂ Sensor Monitor readiness conditions. These updates were typically applied by dealers through IDS/SDD and were known to resolve cases where the O₂ monitor would not set despite no faults present.
The 5.0L AJ133 V8 uses non‑continuous OBD monitors, and the oxygen sensor monitor requires very specific conditions to run. If the PCM software has a logic issue, the monitor may never complete even when the sensors are healthy. This is exactly the symptom many Jaguar owners reported.
Common Triggers for an O₂ monitor stuck in INC include:
• PCM readiness logic not initiating the test (known issue on some 2010–2012 JLR calibrations)
• Battery disconnect or DTC clear resetting monitors
• Drive cycle conditions not being met (Jaguar’s O₂ monitor has strict RPM/temperature requirements)
• Marginal O₂ heater performance (even without a DTC)Jaguar forums document multiple cases where 2010+ XK/XKR owners had the O₂ monitor stuck in “Incomplete” until the dealer applied the latest PCM calibration. After the update, the monitor completed normally during the next drive cycle. Jaguar’s own service documentation shows that O₂ sensor logic, heater control, and catalyst monitoring are all PCM‑controlled and updated through dealer software (IDS/SDD).
What the Dealer Actually Does or Should Do The dealer performs:
• PCM software update (via IDS/SDD or Pathfinder depending on year)
• Relearn procedures after flashing
• Drive cycle verificationThis update typically includes revised logic for:
• Heated O₂ sensor warm‑up
• Switching response thresholds
• Monitor enable conditionsThese changes correct false “Not Ready” states.
How to Complete the O₂ Monitor After the Update
Jaguar’s O₂ monitor drive cycle is unusually strict. The required steps include:
• Cool engine → warm to >82°C (180°F)
• Hold 3000–4000 rpm steady, then coast to 0 mph with foot off throttle Idle 11 minutes
• Repeat for downstream sensors with 30–60 mph steady cruise and another coast-down event If the PCM software is outdated, these steps may never trigger the monitor — which is why the update is essential. You want the dealer to check whether your 2010 Jaguar XK’s PCM has the latest calibration — because that’s what fixes the stubborn O₂ Sensor Monitor = INC problem on many AJ133 5.0L cars.
Here’s the exact script that gets results, without sounding confrontational at the dealer, they can be very hard to handle.
What to Ask the Dealer (Short Version)
Tell them you want: “A PCM software update check for my VIN, specifically for OBD readiness/O₂ sensor monitor logic.”
That phrasing forces them to look up the calibration history, not just scan for codes.
The Full List (Use These Lines)
Each item below starts with a Guided Link so you can dig deeper if you want. Check PCM calibration — “Please verify whether my PCM has the latest calibration for the 5.0L AJ133 engine. I need confirmation of the current software part number and whether an update is available.” Ask about O₂ monitor logic updates — “Jaguar issued updates that correct false ‘Incomplete’ O₂ sensor monitor behavior. Can you confirm whether my VIN is covered by any of those?”
Request IDS/SDD session printout — “After checking, can you print or email the IDS/SDD session report showing the PCM software level?”
Confirm post‑flash procedures — “If an update is applied, please perform all required relearns and adaptations.”
Verify readiness after update — “After the flash, please confirm that the O₂ monitor runs and completes during the drive cycle.”
Why These Questions Matter? Dealers often only check for DTCs, not calibration updates. Your issue isn’t a broken sensor — it’s the PCM refusing to run the monitor.
Asking for the software part number forces them to look up the technical bulletin and compare your current version to the latest release.
What a Good Dealer Response Looks Like, You want them to say something like this:
“Your PCM is on software level X. Jaguar’s latest calibration is Y. We’ll update it.” If they say:
“No codes, so everything is fine.” …that means they didn’t check the calibration. Push again.
Did you make any progress or get your code to clear? Does anyone else out there have an opinion?
