Didn't I just make a post yesterday about how the car was running peachy and that I wanted to do a little tuning up, plugs/coils what have you, well this morning the good Ol' Jaggy poo wants to through some codes at me.

Joy. I am up for the challenge.


I wasn't driving, I received that text that every man loves getting when his wife is driving the car and he is busy tending away at the things a man does. A picture of a check engine light surrounded by that unmistakable wood grain.


I ran my generic elm scanner that I use from time to time, but something isn't right, at least to my knowledge, and by that I mean the car responded in a way that it hasn't previously when I used the same scanner.

When I plugged it in with the key in position ll, all of my warning lights came on. Brake fluid, Transmission error, you name it. My phone is dead as of this very moment so I will post it's results when I get the chance, but it pulled 8, 3 of which were faults the others were pending. I just thought I would mention this because it was odd.

The code that concerned me was our sexy friend p0455. I assume the main culprit.


So I ran up to autozone and had them do a scan, I believe the codes are the same, like I said above I will double check this evening. But here was the write out from there scanner and I just used some google foo for the definitions:

P0455 Evaporative Emission Control System Leak Detected Gross Leak

P1638 Can Link ECM/INSTM Circuit / Network Malfunction

P1642 Fuel Pump Monitor Circuit High Input

P1797 Neutral Switch Circuit Malfunction

P1111 Intake Air Temperature (IAT) Sensor Circuit Intermittent High Voltage

(I thought P1111 was drive cycle complete?)


I had him note the screenshot fuel trim from when the p0455 occurred:

LT1 = 1.6
LT2 = 2.3
ST1 = 16.4
ST2 = 15.6




I had a local shop perform a smoke test, which turned up nothing. I had them do an in depth diagnostic which pulled a total of 32 codes, I am assuming these are stored data entry's and not actual "codes". I can post them If you should like.


I have yet to clear any codes or have them do so. I figured I would wait to hear out from you guys.


SO, where to begin? Gas cap is on tight. LOL

Car is not really showing any signs of distress, has been running well.

 

Here is the screenshot from my scanner.

 

Best guess is you have 2 faults possibly 3 with the high fuel trims
The trims are not big enough to trigger a fault but something is out of wack but you dont say what was happening when you go those readings. So the reading may be normal as both banks are the same Id need some more info.

To break them down
1. P1638 Can Link ECM/INSTM Circuit / Network Malfunction

Do a battery check and take a look at this TSB http://www.jagrepair.com/images/TSB/...%20Cluster.pdf

2. The other Codes
Assuming battery passes tests id reset them and see what happens before going further

3. The Fuel Trims
As you have done a smoke test 3 things come to mind. You may have a leak in the exhaust, check the flanges upstream on the o2 sensors and the manifold bolts.
You may also have a leak in the "Evaporative Emission Control System" which is at the tank and may not be spotted in the smoke test. Finally a leak may need heat to be found

Again fist step battery test and rest the codes. Check the exhaust and After a run do another smoke test and check from the engine bay back to the tank for leaks

Here is how you can make a smoke tester for a few bucks
https://www.jaguarforums.com/forum/x...-leaks-117917/



Cheers
34by151

 

P1 codes are make/model/year-specific so you need very special reader or look them up in jag doc. The latter works.

Don't assume the trims are a problem as they probably aren't. Work on the codes.

 

Hey guys, I used my scanner to clear the codes, unplugged the beast for a few minutes, reconnecting the battery left me with a 'config b' warning and dual flashing lights.

Disconnect then 're connecting the battery once again, cleared the config B error.

But still left me with a CEL

I checked the codes, drove for a short time, then checked them again.

Codes remained the same. See screenshot bellow.

So the emissions code has not returned 'yet', we will see on that, but the other CAN related codes remained.

Q. Is that service bulletin relevant to MY 03?

My scanner is still not friendly with my car whenever I plug it in. I am met with the Christmas tree effect and dead gauges, which makes me ponder if the scanner is leaving those codes as an artifact, OR causing an error.

The scanner at AutoZone and the local mechanic did not cause this effect.

I guess my next step will be to take it to my actual regular mechanic, have him clear the codes and see what happen.

I have my mongoose cable, but I uninstalled my SDD from British Diagnostic after my suspension fiasco. I may try to contact Moscow Leaper and see if he wouldn't mind taking me through the install process.

Any thoughts?

 

You really need SDD to track it down

Also do a battery check, check the volts don't drop below 12.2 when cranking as it all may be battery related

Assuming the battery is OK clear the codes with SDD and see what happens

Id work on the coms issue first, take a look at that TSB as it will clear up the coms issues. My guess is this or the battery is causing most if not all of the codes

Cheers
34by151

 

Naso,

I used this sticky thread from the UK jaguarforum to install SDD. Hope these help you

Mongoose V134 install

Mongoose V134 install

 

Thanks for the advice guys, after I cleared the codes the last time I made a post, after a long enough cruise the drive cycle turned over and the codes vanished.

Codeless for a few days now. That 0455 codes must have triggered the CEL, and my scanner must have created those CAN related codes as artifacts of a poor communication.

That is my best guess anyhow.

 

Most of the time its an early indication of the battery failing other than that it is an intermittent coms failure

I have had both

On my car I would see the "gearbox failure" on the message center followed by the the speedo not working, cruise, abs fail ect ect.

The issue turned out to be the pin on the ecu. It looked ok but fixed the issue after replacing the pin. The second time it occurred was aprox 6 months after first clearing the codes. Then it started to get more frequent.

After the fix, while doing other work I also replaced the pins on the IC, and ABS just for good measure.

That TSB will give you all the related pins. Id suggest if you get it again to just replace them all in one go. The sequence of the codes (if you see it occur) will tell you the exact pin but you need to be lucky to see that

Cheers
34by151

 

Thank you again for that bulletin brother, I don't really suspect the battery as it is just a few months old and tests just fine.

In the future if it happens again I will further investigate the pins and such.

 

I would have said battery also, Multiple codes thrown like that are a good indicator that the battery is on its way out (typically the crank amps, from my experience in these matters).
Once that battery is checked properly and the codes are still being shown would mean further investigation into the real culprit.
I am glad you have this sorted now though.

 

Just an update, I haven't had the smallest of issue since this event.

No codes, no anything.