Jaguar F-Pace Forum banner
1 - 6 of 6 Posts

· Registered
Joined
·
4 Posts
Discussion Starter · #1 ·
Got a Check Engine Light and the issue was with the O2 sensor so got it replaced (Bank1 sensor 3)
CEL was not showing up and went for Vehicle Inspection but the tool showed "OBD system not ready". I have driven the car for around 200 miles after the sensor replacement but was not following any specific cycle.

Can anyone help with the steps to reset the OBD cycle and or provide the guide for F-pace specific OBD cycle.
Also if there are ways to confirm the readiness either through OBD tools or some other ways.
 

· Registered
Joined
·
39 Posts
Many OBD2 tools will output the status of state OBD checks such as catalyst, O2 sensors, misfire, evap, etc. The dealer should have reset/erased the O2 sensor codes following service. It can take a while driving for some of the checks to complete. I just mentioned this in another thread... Evap takes the longest to cycle, and you need to make sure fuel tank is near full at the start, and don't top off, just let it run down to 1/4 tank before refilling. Most automotive stores have OBD2 scanners that they will read codes for you for free if you don't know someone who has one or want to make a small investment. My Actron has paid for itself many times over. Good luck and report back.
 

· Registered
Joined
·
4 Posts
Discussion Starter · #3 ·
Many OBD2 tools will output the status of state OBD checks such as catalyst, O2 sensors, misfire, evap, etc. The dealer should have reset/erased the O2 sensor codes following service. It can take a while driving for some of the checks to complete. I just mentioned this in another thread... Evap takes the longest to cycle, and you need to make sure fuel tank is near full at the start, and don't top off, just let it run down to 1/4 tank before refilling. Most automotive stores have OBD2 scanners that they will read codes for you for free if you don't know someone who has one or want to make a small investment. My Actron has paid for itself many times over. Good luck and report back.
Thanks for the information.
The CEL does not come up but the codes show as stored/permanent codes and it was mentioned that they should clear themselves after some time of regular driving if the issue is fixed. Is this not the case?
I will try to follow some general cycle procedures like continuous highway driving, cruise stop, idling for some time, etc mentioned for other jaguar versions but I was wondering if there is a similar set of instructions for F-Pace specifically.
 

· Registered
Joined
·
39 Posts
You need to determine which monitors are complete and more importantly which are not. I'm not aware of any specific FPace procedures. I don't know if all trouble codes self-erase, so I have typically erased them. The downside to doing so is that it forces a new start on the monitors. Things like number of engine start/stop cycles and adequately heating the catalyst (highway driving) may all come into play. But the fuel level issue for Evap is by far the most important thing you need to consider. Did you get the OBD not ready report from a self-serve kiosk, or from a manned emissions center?
 

· Registered
Joined
·
4 Posts
Discussion Starter · #5 ·
I got the not-ready report from a manned emissions center. I was able to borrow an OBD and it shows INC (looked up and stands for incomplete) for certain checks mainly related to O2 sensors.
I am also apprehensive about deleting the codes now (should have done them initially) mainly as it'll reset the drive cycles. I am hoping permanent codes go away on their own, as have read some states' emission checks fail if the scan shows permanent codes even if the system status is ok now and there is no CEL light
I'll try following some generic drive cycles and some specific to Jag and monitor the system status using the OBD scanner and hopefully, it'll be OK.

Thanks again for the details and will keep posted on how it goes.
 

· Registered
Joined
·
4 Posts
Discussion Starter · #6 ·
The issues with the monitors not being ready got resolved after I did a couple of long drives with steady speeds (40 ~ 60 mph) and also tried to follow deacceleration from around 40 mph without using breaks and some acceleration runs to make rpm reach above 3K.
The monitors for O2 sensors showed ready after 1 of these drives and once I repeated it a few more times the scanner stopped showing the permanent codes too.
 
1 - 6 of 6 Posts
Top