Jump to content
SAU Community

Recommended Posts

Even though the PFC has more cells to adjust the standard ECU calculates/interpolates better between them. I think the new HPI covered this subject come to think of it. The standard ECU takes TPS into the load calculation. Not sure if all PFC's do that? So if you got your cells as smooth as the PFC with the Nistune then is should calculate the load points better under dynamic conditions. In saying that I don't know if you can adjust the load points, ie if you can't what happens once you go above the standard redline?

That's pretty nifty.

Also interested to know what happens with NIStune chips in regards to exceeding redline and if there are load point adjustments...

That's pretty nifty.

Also interested to know what happens with NIStune chips in regards to exceeding redline and if there are load point adjustments...

What do you mean "exceeding redline"? The standard maps in Nissan ECUs usually have the last cells that are mapped at revs that are well lower than redline. If you want to be able to tune to higher revs, the very first thing you do is rescale the rpm scale. And, if you expect to be making more power than standard, you do the same to the load scale. This has been said before in this thread. And, the exact position of each point on the load and rpm scales is completely arbitrary. You can bunch them up near peak torque or boost transition and spread them out elsewhere, or you can make them equally spaced. Up to you.

The redline is exactly that. A separate number that you can set at any rpm you like. That might be well below the top of the map, or it might be not far after the top of the map (sensible) or it might be well higher than the top of the map's rpm scale (which could be dumb). Whatever, the ECU just does the rev cut at that point, regardless of what the mapping look like.

Edited by GTSBoy

By what I've read, the MAP sensor doesn't rely on air flow but it functions via air pressure which can lead to better response and power output once tuned correctly. D-Jetro also has launch control, fuel / ignition cut, anti-lag, NOS, etc which are some features you may or may not use.

I was going to take this path, but I wasn't aiming for high power so based on my findings and having a NIStune setup, the NIStune is the best bang for buck. Hit up a few searches and this will also confirm what I've just typed.

Power FC is 20 x 20 and NIStune is a 16 x 16 resolution so if it's a high RPM revving monster then PFC should be considered.

I remember reading that NIStune is tuned cell by cell at 500 RPM intervals, think it was ns.com though so take that with a grain of salt.

again with the mis info.

Djetro does not have launch control or ignition cut.

Nistune scaling can be tuned via whatever scale you input.... from 50rpm to 5000rpm...

and reading engine load by air pressure instead of hotwire airflow meter does not lead to better response or more power

hotwire airflow meter measures air directly passing through to give engine its load axis

manifold air pressure sensor measures pressure and guesses engine load based on pressure via a lookup table

when you reach target boost the manifold pressure sensor value remains fixed and you run 2d map from here on

when you reach target boost the airflow meter continues to increase and you run 3d map

Well, sort of. It is actually pretty easy to determine the relationship, for A GIVEN ENGINE, between MAP and air flow (with IAT correction). And it's not going to be much less accurate to calculate it like that than the error that a hotwire AFM will give anyway. Anyone who assumes that a hotwire is 100% accurate, even when brand new, is fooling themselves.

The problems with using MAP come when, for a given engine, you change things like cams or porting or exhaust, or anything that changes the way the engine breathes. This is why back in the day, with early EFI systems that only had MAP for a load reference, if you did any such mods the mixtures would all go to hell and you had to start tricking the system by putting in resistors on water temp sensors and so on. But with an AFM, if you make the same breathing mods, then the AFM just measures the air amount and the mixtures stay the same as original and it basically works OK.

But none of this matters a poop to anyone using a tunable ECU. Doesn't matter if you're using MAP, AFM or just TPS and revs as your load input. This is because even with MAP or TPS only, you don't actually want or need to calculate how much air is being ingested. You just change the multiplier (the value in the fuel map basically) to add or subtract fuel from what was there before to give the correct mixture and hey presto - it's tuned. On that basis, AFM and MAP are essentially equivalent in accuracy - and in reality, given that hot wires tend to get dirty and have their calibration drift over time whilst the basic breathing characteristic of the engine remains essentially the same, then MAP might even be more accurate over a longer period of time than AFM anyway. TPS and revs as load input sucks a bit by comparison, but we're not here to talk about that anyway.

Edited by GTSBoy
  • Like 1

Yeah I always thought a MAF gave your far more information than a MAP + air temp sensor. MAF tells you how much air there is, MAP + air temp lets you guess how much air there is.

another reason why its crazy not to run a AIT sensor with a map based ecu.... its seems nearly every microtech that comes in running like shit hasnt got one.... surely it should not be a an option when you buy one of these things... it should be included as std..

Well, sort of. It is actually pretty easy to determine the relationship, for A GIVEN ENGINE, between MAP and air flow (with IAT correction). And it's not going to be much less accurate to calculate it like that than the error that a hotwire AFM will give anyway. Anyone who assumes that a hotwire is 100% accurate, even when brand new, is fooling themselves.

The problems with using MAP come when, for a given engine, you change things like cams or porting or exhaust, or anything that changes the way the engine breathes. This is why back in the day, with early EFI systems that only had MAP for a load reference, if you did any such mods the mixtures would all go to hell and you had to start tricking the system by putting in resistors on water temp sensors and so on. But with an AFM, if you make the same breathing mods, then the AFM just measures the air amount and the mixtures stay the same as original and it basically works OK.

But none of this matters a poop to anyone using a tunable ECU. Doesn't matter if you're using MAP, AFM or just TPS and revs as your load input. This is because even with MAP or TPS only, you don't actually want or need to calculate how much air is being ingested. You just change the multiplier (the value in the fuel map basically) to add or subtract fuel from what was there before to give the correct mixture and hey presto - it's tuned. On that basis, AFM and MAP are essentially equivalent in accuracy - and in reality, given that hot wires tend to get dirty and have their calibration drift over time whilst the basic breathing characteristic of the engine remains essentially the same, then MAP might even be more accurate over a longer period of time than AFM anyway. TPS and revs as load input sucks a bit by comparison, but we're not here to talk about that anyway.

One fatal flaw in your theory.... on why map is better... have a think about what you've written.

Yeah just checked Google and NS. I can confirm I had fail searches! Thanks for the clear up.

PFC Pro only has launch control.

But I have some points I'd like to clear up too, perhaps STATUS can shed some light on this too:

@ PaulR33 - Your stating that MAP won't produce better results as oppossed with a MAF.

@ PaulR33, Rolls, GTSBoy - If a MAP sensor is based on a table with direct input then wouldn't you be able to tune it finer without having inaccuracies unlike the MAF? If MAP wasn't as good for performance then why is it incorporated with the the PFC D-Jetro (higher end) ECU package?

Sorry if it's starting to sway off-topic, but I believe the nitty gritty bits of information is important before laying cash out for either a PFC or NIStune.

Air pressure does not directly correlate to how much air you have, you need air temperature as well and you need to know load. That is why I believe it can be less accurate, obviously the maf sensor isn't perfect though and only has a certain range that it works in.

Basically Im under the impression that there is more guessing with a MAP + IAT to get a table that can plot load vs rpm in a way that will be correct in all situations. Someone feel free to correct me though, that was just my understanding.

By what I've read, the MAP sensor doesn't rely on air flow but it functions via air pressure which can lead to better response and power output once tuned correctly. D-Jetro also has launch control, fuel / ignition cut, anti-lag, NOS, etc which are some features you may or may not use.

I was going to take this path, but I wasn't aiming for high power so based on my findings and having a NIStune setup, the NIStune is the best bang for buck. Hit up a few searches and this will also confirm what I've just typed.

Power FC is 20 x 20 and NIStune is a 16 x 16 resolution so if it's a high RPM revving monster then PFC should be considered.

I remember reading that NIStune is tuned cell by cell at 500 RPM intervals, think it was ns.com though so take that with a grain of salt.

Tuning resolution has very little to do with the accuracy of a tune. Dont ever let tuning resolution sway your judgement on what ecu to use.

The BA-FG V8 engine is speed density based and only uses 2 1x14 lookup tables to map the entire engine operation. And it still gets through euro3/4 emmissions compliance.

Air pressure does not directly correlate to how much air you have, you need air temperature as well and you need to know load. That is why I believe it can be less accurate, obviously the maf sensor isn't perfect though and only has a certain range that it works in.

Absolutely and not absolutely. Correct about needing air temp - but that's just so you can get the density of the air right. The MAP signal (+ correction via IAT and any other little corrections that may be applied) effectively multiplied by rpm and with a factor for volumetric efficiency vs rpm IS your load signal.

Basically Im under the impression that there is more guessing with a MAP + IAT to get a table that can plot load vs rpm in a way that will be correct in all situations. Someone feel free to correct me though, that was just my understanding.

There's no guessing. It is a calculation to turn MAP into "air quantity". That calculation is actually reasonably simple to implement, and as I said a few posts up, if you get the absolute answer of the calc a bit wrong (assuming we're talking about what happens with a modified engine), you just trim it out in the fuel map.

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

    • For once a good news  It needed to be adjusted by that one nut and it is ok  At least something was easy But thank you very much for help. But a small issue is now(gearbox) that when the car is stationary you can hear "clinking" from gearbox so some of the bearing is 100% not that happy... It goes away once you push clutch so it is 100% gearbox. Just if you know...what that bearing could be? It sounding like "spun bearing" but it is louder.
    • Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
×
×
  • Create New...