Jump to content
SAU Community

Recommended Posts

  • Replies 175
  • Created
  • Last Reply

Top Posters In This Topic

Hi Jimx, the Apexi drag R33 GTR (V-Max) makes "over 1,000 hp" using a PFC and AFM's. It ran an 8.75, so I suspect it's was closer to 1,100 hp but that's what Apexi quoted. On a 1,000 hp RB I would personally use a Motec M8 (min). Compared to the cost of building and maintaining that sort of engine, the extra cost of a Motec is relative peanuts.

Plus I would almost certainly run a Motec dash and interface the ECU so I could data log every race/run That way I have all the necessary data to make the car faster.

We run Datalogit on the Power FC's in the race GTR for exactly the same reason.

Steve-SST is absolutely correct, each ECU has its strengths and weaknesses.

Hey Steve-SST,

Does the Wolf 3d you have mentioned have fully sequential injection for the R33???? Or does it have only the 4 injector drivers requiring a semi batch arrangement.

I cant help thinking this is pivotally important in explaining the great power outputs you've achieved with this ECU. According to my knowledge, fuel pressure increases do not equate linearly to injector flow. I know Sydneykid made some calcs previously and relieved his puzzlement, but he also suggested linear flow increases with pressure. Unless someone can confirm this relation, this leaves the sequential/batch argument for the explanation. Does this explain the huge power levels with plenty of reserve duty cycle that keeps being mentioned???? With any batch firing the injector would fire twice for each cylinder rather than once per 2 revolutions as per full sequential, thus explaining the ability of 370 cc injectors with only marginal pressure increases being able to support such outputs. Firing twice would make a 370 cc injector appear like a 740cc, except that half the fuel waits around for a bit before being ingested. In the FC with its sequential firing, does this explain its quick duty cycle limitation. In this system the injector has only a certain number of cam shaft degrees when the inlet valve is open to squirt in the fuel. As it ALL has to be injected at once, and since the inlet valve is only open for so long, the "duty cycle" limit simply means that the valve has closed and so fuel injection can no longer occur. If it were to keep going passed the closing, then the sequential idea would be lost and it would essentially become a batch system.

I have no intention of making a wolf/FC comparison here...I just want to know whats going on.....

the phantom, I had the exact same thought. But I researched batch firing a little more and found it doesn't make a difference to duty cycle like I thought it would.

With batch fire, the ecu fires off two injectors at once. That doesn't mean each injector is fired once a revolution. The two injectors triggered are chosen such that their respective cylinders are fired in succesive order. The two injectors are timed to trigger at the beginning of the first cylinders firing event. This means one cylinder gets fuel at the right time while the second cylinder has fuel sitting in the inlet tract for a short time before the valves open.

So each injector is fired once per two revolutions as normal, just that half the cylinders will have less than perfect atomisation and ultimately, more emissions and less effeciency.

just had a look on the wolf site

noticed theres a v4 and now v4 Plus. Differences between the 2 are here: http://www.wolfems.com.au/products/enginem...ersion4and4plus

are you stocking the v4 Plus yet Steve SST? Are they much more pricey in comparison to v4?

Power FC knock detection update.

I just had a look at my pistons (head is off), and the things look almost new (except they are black of course).

60,000kms on the clock and they are pristine (also the bores are perfect with no lip, and the chambers look spot on too) absolutely not one sign of any detonation at all.

In the past I have had knock readings as high as 98, but always backed off as soon as the check engine light has flashed.

I know this isnt a quantifyable example, but at least I know its doing its job, so I am happy.

And for all you wolf, microtech etc guys that dont have in built knock detection, I would go out and spend the 200 odd dollars to buy one:D cant hurt.

Hi Guys, been in Perth checking out the import seen (not really, work actually). But I didn't notice any more Skylines than we have in Sydney.

Couple of people asked some questions...........

Duty cycle of 80% means the injector is open 80% of the time. Not just when the inlet valves are open. So 100% means they never close.

A true rising rate regulator increases the fuel pressure at a rate greater than the boost increase. So 50 psi fuel pressure at idle (zero boost) may be 60 psi at 6 psi boost, 70 psi at 9 psi boost, 80 psi at 13 psi boost and 90 psi at 17 psi. If the pump will support that level of fuel pressure of course.

A rising pressure regulator (as distinct from rising rate) will follow the boost. So 50 psi fuel pressure at idle (zero boost) will be 56 psi at 6 psi boost, 59 psi at 9 psi boost, 62 psi at 12 psi boost and 65 psi at 15 psi.

Using a rising rate regulator can easily give the sort of fuel flow required to make 400 + rwhp out of standard injectors, but it stresses the injectors way past their design limits.

Obviously squirting fuel into the inlet port when the inlet valves are closed means that the fuel has to wait until the valves open before it can enter the combustion chamber. While it is waiting, the fuel de-atomises and therefore when it finally flows into the combustion chamber, it doesn't mix with the air as well. This adversely affects both power and economy.

This is one of the reason why the Group A Skylines ran an engine driven fuel pump, it gave very high pressures and excellent atomisation of the fuel which facilitated more power. I have seen as much as 140 psi at the fuel rail. Injectors have come a long way in the last 10 years and don't require the same pressures to achieve good atomisation.

Hope that answers the questions

Thanks Gradenko and Sydneykid,

So past a certain duty cycle, the whole argument of sequential vs batch becomes irrelevant, as the distinction between the two then dissapears???

Sydneykid, can you confirm that with standard rb25det 370cc injectors that going from 38 to say 76 PSI fuel pressure doubles the flow to 740cc, ignoring the reliability issues you have warned about??

Mr Walker asked "past a certain duty cycle, the whole argument of sequential vs batch becomes irrelevant, as the distinction between the two then disappears???"

You are correct at 100% duty cycle it makes no difference. The more you move away from 100% the more relevant it becomes. The real issue here is you can get more power and better fuel economy from a 700 cc injector at 50%, than you can from a 350cc injector at 100%. As long as your ECU can accurately control the 700cc injector of course, not all can. I have used 1300cc injectors with Power FC’s and they control them perfectly.

The Ghost Who Walks also asked "standard rb25det 370cc injectors that going from 38 to say 76 PSI fuel pressure doubles the flow to 740cc"

I can absolutely say this is not the case, although fluid dynamics is not my specialty. I would have to dig up my notes, but from memory, it is close to an inverse logarithmic increase. This is why true rising rate regulators are calibrated this way.

Hope that answers the questions

Ants GTR has 1600cc injectors and this thing will be one of Australias fastest true street Skylines. Fabs GTR found the limits of the PFC and its now been sold (the ECU).The worst thing about PFCs and big low impedance injectors is the need for a risistor loosing the fine control needed for large injectors.Keep an eye out for our cars showing the results as i think real results are the only indication needed not fancy words.We often have feature cars in Oz mags, the next is Dragster Australia.

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...