Well, my ongoing turbo install has taken a rather strange turn...
I started a thread earlier in the EMS section of this forum trying to narrow down a problem I'm encountering with the transition to boost. The problem is right at 00 inHg, the car begins to jerk rather violently and then the AFR goes incredibly rich. I checked the spark plug function with a timing light and all is in order, the Interceptor actually seems to be doing its job rather well, as part throttle driving is perfect, the grounds for the ignition set are all correct, as is the other wiring. Despite all this, the car still behaved the same, with the horrendous bucking at the transition to boost.

I had received a CEL and I checked it with a scanner to find the RKE P0039 code, which, from what I've found on this site, is either a generic "Supercharger/Turbocharger" code or a Secondary Shutter Valve malfunction. However, that's all that I can glean from RX8club's forums. Does anyone know how to remedy the situation? I am curious if the addition of positive pressure to the intake manifold is the culprit here, but if this is the case, why haven't I heard of this more often on RX-8 turbocharger installs? (outside of the debate over the Greddy block-off plate for the SSV and its usefulness)

Any help would be greatly appreciated, as after many weeks (and many tribulations) my RX-8 still sits in the garage gathering dust... sigh...

 

https://www.rx8club.com/series-i-tech-garage-22/rx-8-technical-info-cel-codes-pcm-pin-list-collision-guide-26291/

could not help you with the 00039 code as it does not show up in the mazda charts.

good luck.

beers

 

My accessport i got from MM shows that I have this code as well. I have no clue what it is, but I will try calling a Mazda stealership to see if they can help me out.

 

I just had this CEL today. p0039 along with a p0103

I'm thinking coils. I jammed on the throttle when it happened.

I was data logging at the time, so will be able to check out the logs later tonight when I get home.

 

I guess that's sort of good news - I noticed that part of my APV motor was exposed to some pretty high heat, as there's some melted plastic. Possibly a problem with this set of valves opening?

However, ignition could be the problem - are you using an upgraded set?

 

oem coils. NA engine. I really shouldn't have any engine issues at this point and I know the hardware should be functional, since the engine was taken apart and rebuilt from scratch about 5k miles ago.

 

I think I pretty much always have RKE P0039 showing up on my AP... never see it with the CANScan though

 

i used my scangauge2 and it saw my 103 code, but not the 0039

 

here is p0103 there is no p0039

 

lucky I have a second maf sensor

 

BUMP! Hey did anybody figure out what the P0039 code is? I'm not a FI guy like you guys but I got it while checking it with AccessPort

 

i reset the cel and it never came back.

 

I have also seen this code when using the AP only

 

Don't know, but all the 003x's seem to be related to the O2 sensors, so that's a good bet and
I believe it will be the rear.

 

doesn't explain why only the ap picks it up, and other can scanners don't see it.

 

I know...............that's strange..........I guess it means not to worry about it. Maybe the AP is set to a more sensitive number or scaling?

 

Maybe because it says the AF mixture does not comply with Emission standards........

 

would they really make a code for that?!?

 

Same here. With an older version of the AP firmware it reported a ton of different CELs and I'd have to hard reset the ECU to clear them. After working with Cobb and going through a couple "beta" firmwares we got mine to no longer throw any visible CEL but the P0039 is still reported.

Scanalyser is oblivious to it and I never pushed Cobb further... I was just happy for the visible CELs to go away... it was a pain in the a$$ to hard reset my ECU (battery terminal pull) every time I flashed a new map.

 

I have the RKE P0039 as well.
It doesn't set the light - its just in the background.

I sent a note to Cobb about it.

 

I did as well.. but it seems to have disappeared. BTW I'm NA.

 

same here

 

just discovered this on Scremn8's car. N/A, 6 port.
Strange.
Jeff, let us know what Cobb says about it.

 

So far, they haven't said anything.
We are working on an interesting translation table to use the BARO sensor for something different than its current OE implementation, though. (nudge nudge wink wink)

 

what i think it is...?