Jump to content
SAU Community

Recommended Posts

Hey all,

This started happening yesterday morning, but was hard to diagnose due to lots of condensation (was a bit chilly yesterday morning). Basically what happened, is when i would drive off, then stop, smoke would come out. And when i accelerate then back off. Smoke would come out again. Doesn't look like it comes out while actually accelerating, only in between. (if that makes sense?)

After work, i got the old man to follow me around, he said only a small puff came out when i left my house then nothing but a bit of blackish/grey smoke under boost (normal i believe with a stock ECU). Did a few tests, light load - high/low revs, 4th under load up hill and WOT. small cloud of smoke under boost. Werid...

Anyway, while i was driving today i noticed quite a alarming rate of smoke coming from my exhaust, i pulled in and took this video.

https://dl.dropbox.c...1009_082732.mp4

It won't smoke when it is idling, but when accelerating it puffs out like crazy, the car was warm when the video was taking. It seems worse when the engine is cold. Looks like a bluey smoke, so im thinking oil??

Tips on how to diagnose whats wrong with my car appreciated!

Temps seem fine, Still goes the same (not that i gave it a hard time due to the smoke screen).

Hoping its turbo related because i am replacing them. I'm scared to drive on it, and you know have this lame thing called work, really don't want my engine to go BOOM

Edited by Booki
Link to comment
https://www.sau.com.au/forums/topic/411139-gtr-blowing-smoke-help-troubleshoot/
Share on other sites

  • Replies 43
  • Created
  • Last Reply

Top Posters In This Topic

Looks like condensation. Chilly morning = condensation, especially if you don't drive the car very much.

Take the car for a long drive and see if it still does it when the weather is warm (read - above 20deg c)

Looks like condensation. Chilly morning = condensation, especially if you don't drive the car very much.

Take the car for a long drive and see if it still does it when the weather is warm (read - above 20deg c)

I thought it was condensation too, But I dunno. It seemed a little "blue" and heavy for condensation.

I will take another vid when I move to my next job site.

Hado - I checked my coolant last night, looked normal green color. Will check it before i drive off again.

Ok, Started it up to go drop it at home.

No smoke...Revved it a little, no smoke. Wasn't even worth taking a video.

Even on the drive home, nothing came out.

Decided to play it safe, and drop the car off at home. Gave it a bit of a rev when i got in the garage and a small puff came out, but then nothing after wards.

Beats me... It was BAD this morning. Now, nothing. Regardless using the bike till i figure out wtf is going on.

and Hado - Coolant levels normal, still green.

Update: checked coolant. Its used some, although it is still clean of what i can see of it. Checked oil cap, and all looks good from that view, as well dipstick oil. Color looks normal. So i don't think its a head gasket (least im hoping not)

Stock turbos

Edited by Booki

white smoke on rb26 usually means turbo seals. have a look in the coolant reservoir tank. can you smell oil? incorrect anti-freeze ratio can also cause white puffs of smoke. do full coolant flush from block and see how it goes from there. my gtr does it on WOT. no biggie.

Starting to replace my turbo's, and noticed the rear one was seeping oil.

Intercooler also had some oil in it too.

So far have all the piping off, turbo heat sheilds off, undone the front pipe bolts to the dumps.

It's coming along alright so far, only because the old man is helping out (by helping out i mean doing 90% of it).

Hopefully we don't get stuck, the job itself doesn't seem hard. Its just all the variables (rusted nuts/bolts, tight space) that make it difficult.

Dam RB26

  • 3 weeks later...

Ok....Started up the GTR with BRAND NEW -7 turbo's, let it idle for a bit while i was putting in my fresh coolant (you know the drill) and the same shitty smoke was there.

No where near as bad as the video posted up, but still noticeable.

Idea's?

Hard to tell, Only started it twice.

Turbo's have only just been put on, have not driven car due to it not being tuned.

The smoke is hard to describe, it looks like condensation but right now its about 22 degrees? So i don't think its condensation.

Smoke comes out on de-acceleration.

Only revved it as high as 2500-3000rpm

I have a similar issue with a customers car. I tried a new pcv Valve to eliminate it from the diagnosis and the issue is still there.

As Dan has said, more than likely valve stem seals.

They are a pain to diagnose tho.

Have u done comp and leakdown test?

Havnt done compression or leak down tests yet. Will do some more trouble shooting when I finish up work for the day. Hoping its not a head gasket or rebuild time, only put 5000kms on it since ownership :(

Will try and get a video up, keep me posted on how you go with your customers car :)

Edited by Booki

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

    • First up, I wouldn't use PID straight up for boost control. There's also other control techniques that can be implemented. And as I said, and you keep missing the point. It's not the ONE thing, it's the wrapping it up together with everything else in the one system that starts to unravel the problem. It's why there are people who can work in a certain field as a generalist, IE a IT person, and then there are specialists. IE, an SQL database specialist. Sure the IT person can build and run a database, and it'll work, however theyll likely never be as good as a specialist.   So, as said, it's not as simple as you're thinking. And yes, there's a limit to the number of everything's in MCUs, and they run out far to freaking fast when you're designing a complex system, which means you have to make compromises. Add to that, you'll have a limited team working on it, so fixing / tweaking some features means some features are a higher priority than others. Add to that, someone might fix a problem around a certain unrelated feature, and that change due to other complexities in the system design, can now cause a new, unforseen bug in something else.   The whole thing is, as said, sometimes split systems can work as good, and if not better. Plus when there's no need to spend $4k on an all in one solution, to meet the needs of a $200 system, maybe don't just spout off things others have said / you've read. There's a lot of misinformation on the internet, including in translated service manuals, and data sheets. Going and doing, so that you know, is better than stating something you read. Stating something that has been read, is about as useful as an engineering graduate, as all they know is what they've read. And trust me, nearly every engineering graduate is useless in the real world. And add to that, if you don't know this stuff, and just have an opinion, maybe accept what people with experience are telling you as information, and don't keep reciting the exact same thing over and over in response.
    • How complicated is PID boost control? To me it really doesn't seem that difficult. I'm not disputing the core assertion (specialization can be better than general purpose solutions), I'm just saying we're 30+ years removed from the days when transistor budgets were in the thousands and we had to hem and haw about whether there's enough ECC DRAM or enough clock cycles or the interrupt handler can respond fast enough to handle another task. I really struggle to see how a Greddy Profec or an HKS EVC7 or whatever else is somehow a far superior solution to what you get in a Haltech Nexus/Elite ECU. I don't see OEMs spending time on dedicated boost control modules in any car I've ever touched. Is there value to separating out a motor controller or engine controller vs an infotainment module? Of course, those are two completely different tasks with highly divergent requirements. The reason why I cite data sheets, service manuals, etc is because as you have clearly suggested I don't know what I'm doing, can't learn how to do anything correctly, and have never actually done anything myself. So when I do offer advice to people I like to use sources that are not just based off of taking my word for it and can be independently verified by others so it's not just my misinterpretation of a primary source.
    • 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. 
×
×
  • Create New...