XJR8 Driver's side upstream lambda...
Discussion
Big Rod said:
Already had the code reset and read again. P1647.
I guess the PO could be fibbing, but he swears he replaced it and his eBay history verifies that he bought one.
Saw that too on his history. Am I wrong in assuming he has history for 2 sensors at 2 different times recently?I guess the PO could be fibbing, but he swears he replaced it and his eBay history verifies that he bought one.
No, I don't think so.
He initialy bought a diff locating bush, (there was a rattle from the back end. I heard it when I was taken out in it back in October.), which apparently the nugget that sold him the car told him was wrong with it. It wasn't.
Turned out to be the lower shock absorber bushes which he bought from ebay and replaced both.
The other ebay purchase, (besides the other odds and ends), was the lambda. I don't remember seeing two of them but I may be mistaken.
ETA:- Just checked and he only bought one on the 25th May.
He initialy bought a diff locating bush, (there was a rattle from the back end. I heard it when I was taken out in it back in October.), which apparently the nugget that sold him the car told him was wrong with it. It wasn't.
Turned out to be the lower shock absorber bushes which he bought from ebay and replaced both.
The other ebay purchase, (besides the other odds and ends), was the lambda. I don't remember seeing two of them but I may be mistaken.
ETA:- Just checked and he only bought one on the 25th May.
Edited by Big Rod on Thursday 14th June 22:12
P1647 is not on my list of Jaguar specific codes... Are you sure that's the right number?Might be worth buying your own OBD11 scanner. You can find one for under £20 that'll not only read the code but tell you what the fault actually is. There may be a code stored from a momentary maulfunction dating back months or even longer that is not relevant to the car now too. I'd get hold of a scanner, clear all the memory out and start from a known point in time and then run the car and see what happens.
Edited by Jaguar steve on Friday 15th June 06:18
It could be faulty sensor and the swapping idea above will help. But it could be something else that is causing the sensor to give a reading that is out of range (and thus generate the dtc).
So plug in a reader that will give live data and that may point you in the direction of the fault.
So plug in a reader that will give live data and that may point you in the direction of the fault.
SV8Predator said:
It could be faulty sensor and the swapping idea above will help. But it could be something else that is causing the sensor to give a reading that is out of range (and thus generate the dtc).
So plug in a reader that will give live data and that may point you in the direction of the fault.
Done already and the operator reckoned it was reading normally. (Granted he's not a Jag expert but he builds race engines from scratch.)So plug in a reader that will give live data and that may point you in the direction of the fault.
The thing is that I'd expect the EML to indicate immediately an error is encountered but it seems to wait until I restart the car. Would this be 'normal' Jag' behaviour?
BTW, the car passed emissions with the error showing so it seems everything is doing it's job.
Very odd one. (To my mind at least)
I think the swap over idea is the way to go.
Just out of interest...
I found on my first proper long trip in the car that sometimes it feels a little hesitant to 'unleash its wrath'.
I immediately thought it'd be the traction control but the warning doesn't flash.
It's like it backs off intermittently during enthusiastic acceleration but doesn't feel like a misfire.
Would the lambda error cause this or should I be looking at something else?
I found on my first proper long trip in the car that sometimes it feels a little hesitant to 'unleash its wrath'.
I immediately thought it'd be the traction control but the warning doesn't flash.
It's like it backs off intermittently during enthusiastic acceleration but doesn't feel like a misfire.
Would the lambda error cause this or should I be looking at something else?
Big Rod said:
Already had the code reset and read again. P1647.
I guess the PO could be fibbing, but he swears he replaced it and his eBay history verifies that he bought one.
Hi,I guess the PO could be fibbing, but he swears he replaced it and his eBay history verifies that he bought one.
You might like to know that my x308 xjr had the same fault code and the garage said it was Bank B upstream lamba sensor failure. Lamba sensor on the invoice was £120 (ouch!) for the part, not sure what the labour was but would guess an hour or so to diagnose, purchase and fit it.
Cheers,
OneJag
Thank you.
It's going in to have it 'fixed' on Thursday.
In the meantime I'll be getting down and dirty with the throttle body, airflow meter and a can of carb cleaner as it's showing classic symptoms of those needing attention.
Might just treat it to a new set of plugs too.
FWIW, the upstream lambda sensor is a new one quite obviously so I reckon it's duff off the shelf or the connectors have got swapped at some point.
We'll see.
Lovong it so far except for the almost lethal tendency it has to tramline. It makes me clench a bit sometimes!
It's going in to have it 'fixed' on Thursday.
In the meantime I'll be getting down and dirty with the throttle body, airflow meter and a can of carb cleaner as it's showing classic symptoms of those needing attention.
Might just treat it to a new set of plugs too.
FWIW, the upstream lambda sensor is a new one quite obviously so I reckon it's duff off the shelf or the connectors have got swapped at some point.
We'll see.
Lovong it so far except for the almost lethal tendency it has to tramline. It makes me clench a bit sometimes!
Gassing Station | Jaguar | Top of Page | What's New | My Stuff