Jump to content
SAU Community

Recommended Posts

Hey Guys

Got sick of my engine light being on this week so I did the self-diagnostic test as seen on this website and it flashed the code 33 which apparently means heated oxygen sensor. I just had installed a KLS split dump pipe (with the correct thread for the sensor) and now it wont turn off

Anyone had this problem before or know how I could go about rectifying it?

Geoff

Edited by neopowered34

So I played round with the connections as the exhaust shop left one half clipped and the light has gone off after a good drive, fingers crossed it stays off!

Edited by neopowered34

So I played round with the connections as the exhaust shop left one half clipped and the light has gone off after a good drive, fingers crossed it stays off!

Check the fault code again. Although the light isnt on it may still be faulty. My 34 has the code 33 at the moment, my 02 sensor is shagged but the light doesnt always come on.

  • 2 months later...

Mine threw up this code yesterday, it came on after a bit of a spirited drive. It went away for around 30 mins but came on this morning on the way into work.

Definatley a dud sensor then, or does it just overheat when on boost and then come good? My car too has a split dump pipe

Mine threw up this code yesterday, it came on after a bit of a spirited drive. It went away for around 30 mins but came on this morning on the way into work.

Definatley a dud sensor then, or does it just overheat when on boost and then come good? My car too has a split dump pipe

Mine ended up staying off so was the connection that the exhaust shop left off. Just double check them and if your sensor is dud move it off for a new one :)

Yeah I unplugged it and gave it a quick spray with rp7, been good since.

Checked the air fuel ratio on the dyno and it was a constant 13.7/1 at cruising speed/throttle

Yeah I unplugged it and gave it a quick spray with rp7, been good since.

Checked the air fuel ratio on the dyno and it was a constant 13.7/1 at cruising speed/throttle

is that a typo? Should be 14.7

is that a typo? Should be 14.7

Nah, defiantley was between 13.2 - 13.7 under reasonably light load / light acceleration up to crusing speed.

I woulddn't have thought you'd acheive perfect stoich mixture, even at idle?

Anyhow, car was on the dyno making sure the Nistune I put in was functioning right, and it was only the WOT settings that ended up being tweaked to suit. We'll be looking at the light load stuff when I've got a bit more time.

So far though, I'm getting better economy than the stock ECU which means its all going in the right direction

  • 2 months later...

Hey Bryce, Jeremy just got one from Ebay which I installed for him. Seems to have stopped his Engine light coming on.

It was a PEC brand which is what his old one was too. You just need to connect it to the stock Plug.

Vulture Motorsport sells them on here. :thumbsup:

Edit* Linkages ---->> http://www.ebay.com....#ht_3034wt_1245

---->> http://www.skylinesa...n-sensor-59-ph/

  • 4 weeks later...

Josh, sorry for the noob question, understand that there are 2 oxygen sensors on the RB25DET? Kudos only sells 1 kind, does it fit for both? I too have a fault code 33. Cheers!

there's only one, the other sensor is a cat overheat sensor for the dash

Oh, thanks very much Johnny, I was informed by my mechanic that there were 2 different sensors. Any idea if it's easy to DIY? Cheers!

Yes mate, very easy to do. Al you need is (from memory) a 21mm spanner. Unbolt old sensor, bolt in new sensor. It is located behind the turbo.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • That's awesome, well done! Love all these older Datsun / Nissans so rare now
    • As I said, there's trade offs to jamming EVERYTHING in. Timing, resources etc, being the huge ones. Calling out the factory ECU has nothing to do with it, as it doesn't do any form of fancy boost control. It's all open loop boost control. You mention the Haltech Nexus, that's effectively two separate devices jammed into one box. What you quote about it, is proof for that. So now you've lost flexibility as a product too...   A product designed to do one thing really well, will always beat other products doing multiple things. Also, I wouldn't knock COTS stuff, you'd be surprised how many things are using it, that you're probably totally in love with As for the SpaceX comment that we're working directly with them, it's about the type of stuff we're doing. We're doing design work, and breaking world firsts. If you can't understand that I have real world hands on experience, including in very modern tech, and actually understand this stuff, then to avoid useless debates where you just won't accept fact and experience, from here on, it seems you'd be be happy I (and possibly anyone with knowledge really) not reply to your questions, or input, no matter how much help you could be given to help you, or let you learn. It seems you're happy reading your data sheets, factory service manuals, and only want people to reinforce your thoughts and points of view. 
    • I don't really understand because clearly it's possible. The factory ECU is running on like a 4 MHz 16-bit processor. Modern GDI ECUs have like 200 MHz superscalar cores with floating point units too. The Haltech Nexus has two 240 MHz CPU cores. The Elite 2500 is a single 80 MHz core. Surely 20x the compute means adding some PID boost control logic isn't that complicated. I'm not saying clock speed is everything, but the requirements to add boost control to a port injection 6 cylinder ECU are really not that difficult. More I/O, more interrupt handlers, more working memory, etc isn't that crazy to figure out. SpaceX if anything shows just how far you can get arguably doing things the "wrong" way, ie x86 COTS running C++ on Linux. That is about as far away from the "correct" architecture as it gets for a real time system, but it works anyways. 
    • Holy hell! That is absolutely stunning! Great work!!!
    • It does when you start adding everything else in. But it's not just compute. It's the logic. Getting your timing right (I'm not meaning ignition timing for the engine). Making sure of your memory mappings, seeing your interrupts. Microcontroller devices only have so much capacity. For the most part, you want all those timers and interrupts in use on your engine control, which means you're left with less than ideal methods for timing and management of other control functions.   Let's put it this way, my job is all about building custom hardware, that goes into cars, and integrates with them. We're also waiting on a media confirmation from SpaceX too fora world first we've just completed with them in NZ too. It's not just the little toys I play with. But you know, you can think and believe what you want.
×
×
  • Create New...