Cool! Keep us posted. That sounds like a neat(still bad)problem.

 

All of your issues started after you changed your mounts, correct? Having solid mounts can explain the knock sensor acting up as they amplify mechanical noises through the engine and transmission as well as the chassis. None of those sensors share a common plug (that I know of) but they all share the same harness, which if I remember correctly runs right next to the rear(firewall side) mount. I know that the rear mount is a pain in the butt to remove from the car(even on a lift) so you may want to check the harnesses in that area of the car for any kind of damage. You may also want to check for damage to the harnesses running under the battery box (since the vehicle speed sensor is there and the harnesses for the knock sensor/injectors run under the battery).

Oh, you might want to put that 100 amp fuse you removed from the positive terminal back on. It's what keeps your alternator from frying your electrical system.

 

Oops! Yeah I missed that on the first read through. Yeah you wanna put that back on.

 

Yeah, shortly after posting i looked up what that fuse was and wired in an in-line fuse. Well, if i shorted out the electrical system i would have had to rewire and probably would have found the source of this weird issue lol.

I got under the car and tried to check for the wiring you mentioned streetevo. Ill have to put the car up on some ramps and see if i can get a better view tomorrow as i didnt have much time to check tonight.

One of the original solutions i had was to swap ecus as both the barometric and speed sensors are located next to each other on the ecu (pins 85 & 86). Or somehow the wiring got damaged as they were likely run together in much of the loom.

I loaded up a reworked rom tonight and will wait and see if it retriggers the CEL. Thanks for all the help guys and ill keep you posted.

-Matt

 

Problem solved! After having the same barometric pressure cel with an E8 maf ruled out that my E5 maf was bad but rather there was a bad connection somewere.

So reinstalled the E5 maf with its tune and did some logging of the Barometric Pressure, at first everything seems fine and pressure was being logged, then suddenly the engine light came on and the barometric pressure reading in Evoscan went to a solid 0, typical of bad connection/signal.

Now I took the maf out (again) and cleaned all of the 7 protruding conectors on the MAF with some tweezers (all four sides of each connector cleaned) and also aligned them evenly and gave them a very slight upwards direction (for better contact with the maf plug). Also cleaned the MAF plug conectors with a needle, sprayed some contact cleaner and put everything back together; no more code 25 (barometric pressure for Evo 5 ECU) and car feels smoother than ever.

I´m very relieved this got solved, now time to enjoy the car and look out for other gremlins...

Also wanted to mention that the joining pins 1 & 4 seems to be a better diagnosis method than Evoscan, as with Evoscan I constanly get a combination of these codes:

Vehicle speed sensor
Injector circuit
Fuel pump relay
Knock sensor (fewer times and only when car is not running)

But the joining of pins 1 & 4 is now telling me there are no codes and the car runs great. I´ve read something here regarding these common "phantom" codes that Evoscan puts out.

Cheers,

Ricardo

 

Having the same problems! Throwing all the same codes. I was scared when I saw the knock code with my tuner. We were both stunned when we saw it was throwing fuel pump relay; and every other Phantom code. After doing a nice pull thinking; "Well it didnt throw any counts of knock, but then again! Your sensor may be bad! LOL".... He assumed it was a ground and it will be replaced today! Thanks for starting the thread!! Phantom codes....

 

Its been a little over a year and this problem has just returned on my car. Ive changed a bunch of parts on the car since than and havent had this problem untill ive been working with a tuner on tuning my car. I used to run a 965 rom and have just switched over to the 9417. Since the switch ive been getting these codes again.

I think in my case my codes get thrown due to the scaling of the injectors being off. Im going to import my old rom settings to the new rom and see if that stops the problem from reappearing after a few miles.

 

figured it was linked to the battery