Jump to content
SAU Community

Recommended Posts

Hey, im having an issue with my rb20det before 4k revs it felt very boggy and then after 4k revs it felt fine till 6k then it felt like it had no power

it has a 25det gearbox and a r34 neo turbo fmic 3inch exhuast

 

ive tried to turn boost up and down didnt do anything ive also tried resetting timing and the timing was off but now its set but its become worse where if it gets any boost at all if just boggs down

 

have no idea what this could be or what to even look up any help is appreciated

Just now, wildeagle44 said:

Could be a boost leak or it might be pulling timing. Have you checked for fault codes?

havent checked for fault codes as dont have the right reader for r32 dont think its a boost leak as boost doesnt fall off or anything

R32 ECU diagnostic can be triggered with a screwdriver or a paper clip. Read all about it.

It will be a boost leak, or a dying fuel pump as #1 suspects.

After that, it is absolutely everything else in the engine bay. all the usual suspects. read all about it.

Just now, GTSBoy said:

R32 ECU diagnostic can be triggered with a screwdriver or a paper clip. Read all about it.

It will be a boost leak, or a dying fuel pump as #1 suspects.

After that, it is absolutely everything else in the engine bay. all the usual suspects. read all about it.

yeah i suspect fuel pump or the regulator, i was told to block off the regulator return and see if problem still happens

5 minutes ago, GTSBoy said:

No. Put a fuel pressure gauge on it and drive it under load. This is proper diagnosis, not half-baled diagnosis. If the pressure doesn't do what it is supposed to do, then you blame the pump. Your reg is very unlikely to be crook.

alright ill try do that, i just did a ecu diagnostics and got code 34 which is knock sensor 

Just now, GTSBoy said:

Bypass knock sensor with (500k resistor - I think. Look it up, it's findable). If the knock sensor is crook and it's running on the knock map, it will feel doughy. This should make it feel better. Then you  just buy a new one.

I just had a look and I actually have no knock sensor loom at all, both knock sensors are there just no loom, going to borrow a friends and see if that fixes my issues. Have never had a check engine light tho but its always had this issue since I owned the car so its never had knock sensor loom.

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