Jump to content
SAU Community

Recommended Posts

Hi,

I have just upgraded injectors (nothing rly else that would affect anything) on my R34 GTT. I have nistune and so i changed the k constant by going through the injector resize option and changed from 725cc to 1000cc.

This brought the k constant down from like 394 to 285. Problem is my air fuel gauge shows about 20 on the gauge and it runs pretty choppy. If i move the k constant up closer back to 394 originally the AFRs drop down back to closer to 14.7.

But if i rev it just a tiny bit it jumps up again.

Any suggestion would be appreciative! Just trying to get the car able to be moved to the tuners 350km away.

It already had an existing tune and ran no problem.

Thanks :)

Injector latency is different even between same brand. An example is this pair (Denso made injectors). Sard 700cc 0.65msec, Sard 800cc 0.75msec.. so you can imagine the latency difference between 725cc and 1000cc.

Bring you min injector on time up a little - they are probably be operated outside the non linear range of the injector... Unfortunately it is not an exact science... Especially when your not taking into account latency.

Edited by rob82

Hey guys yeah you were right thanks jacked the latency to 1030. Now its idling perfect at ~ 14.7 AFR and rest of the rev range looks good. Might read a bit more instructions next time ;) There wont be any damages having 20AFR on idle ? Also not having narrowband plugged in is also okay on a 350km trip ?

Narrowband sensors get damaged when they're not powered as the heater can't burn off deposits. It sounds like you're using Nistune, there's are afew ways to ignore O2 feedback, one of them is to set the minimum engine temperature which the ECU will accept O2 feedback (defaults at 30C) to something high 200C where the engine has no chance of getting that hot, this way they will at least be powered.

I have my wideband in its place at the moment, so its not connected at all or screwed inside the dump. I prefer to keep the wideband so i can monitor AFRs on the way there, also just read that i can solder some wires to the ecu to simulatre narrowband signal :O. Its MTXL Innovate one. Or since the AFRs are okay i can just plug in the narrowband so cruise is okay and hope not issues.

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