Jump to content
SAU Community

Recommended Posts

Have almost the same setup at 264rwkws. Injectors are the go then increase boost. 18lbs would be the aim and I think your turbo will show what it's capable of. Interestingly, You have a Sard BOV when all indications are that the standard BOV is the best way to go. It has been proven time and time again standard BOV's work well. Is yours leaking ? Is there enough spring pressure ? Put the standard one on for next tune. I replaced all my clamps for the BOV and idle control with proper screw type clamps and noticed an improvement in holding boost. Especially the clamps from BOV to intake return. But if you haven't already bought the injectors get the 740's for future experimentation with E85. mmmmmmmmmmE85.

around 4750rpm is where your curve starts to fall

it's definately some kind of flow limitation

always start with the cheapest and easiest possible solutions:

if you've got a 2835, surely you'd have the full 3" exhaust from the turbo back, high flow or no cat, straight as possible.

check your fuel pump and ensure that it's grounded properly and is getting the correct voltage.

check your sensors etc.

does the Wolf V500 an AFM type ecu?

limits of the stock rb25 afm are around around 230rwkw, alot of people upgrade to a z32 using a power fc at this stage.

1.1 bar should be enough boost, once you've got your 550cc injectors in, get an adjustable fuel pressure regulator and up the fuel pressure a bit.

Edit: oh yea, also what type of "aftermarket fuel pump do you have?"

bosch 044s are much much better than their 040 brothers.

Why would you raise the fuel pressure when the fuelling issue is already fixed with the injectors. An 040 is more than adequate for the power he is making. Wolf is map sensored.

Based on feedback, looks like things I can check are;

1. BOV leak

2. Fuel pump voltage

3. FMIC

However it sounds like I am on the right track with fuel injectors at least.

I do not have AFR's from my last tune which was some time ago now.

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

    • 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. 
    • Holy hell! That is absolutely stunning! Great work!!!
×
×
  • Create New...