Jump to content
SAU Community

Recommended Posts

the 'fluttering' that i think you are describing is called 'compressor surge'. it happens when the bov it sprung too tight or when you don't have a bov (ie not a skyline).

when the throttle body closes (like taking the foot off the accelerator), the comressed air hits and reflects back in the direction it came. in a skyline the bov would open and air would pass out through this making a 'ppsssssshhhhhhhhhh' sound. if no bov, then the air goes back through the intercooler and passes through the compressor side of the turbo in the opposite direction to the spinning blades and as mentioned by obseshn this 'chops' the air up making a fluttering noise. as you can imagine it ain't good for the turbocharger even if it sounds good.

hope that helped.

Waz.

Have a friend who ran a turbo for quite a while with no BOV and it was still fine. Unsure about my car but it's making a fluttering/chattering/chopping noise so either the BOV's pretty tight or the previous owner removed it. Will have to perform a more thorough investigation but everything's in good nick!

definitely not wastegate. on closed throttle there's no air going through the engine so the wastegate opening and shutting wouldn't do much. Either the BOV fluttering or compressor surge with air reverting back through the turbine compressor blades.

This "fluttering" is also a major factor in engine stalls when comming to a stop. I was investigating stalling issues on my car a while back and did some measurements with an oscilliscope on the AFM. I've attached an image of AFM voltage with a "loose" and "tight" BOV. Note that the "tight" setting produced audible "flutter" through the AFM after a rev, and this is seen as the severe oscillations in the trace indicating reversion due to compressor surge....

phantom

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

    • 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.
    • I don't think it's a good buy, the trend looks bad     lol.
×
×
  • Create New...