Jump to content
SAU Community

Recommended Posts

I don't know shit about shit when it comes to forums. My name is Ronald I am from the half assed state of Illinois and I currently and likely forever own a TH1 R32 GTR that is undergoing surgery by myself in my garage. I am here to learn as much as I can and come across deals I don't need as often as I can! 

Full strip down of block, getting machined and forged. Stating twin because I appreciate the hidden turbo look that stock layout offers. Painting the engine bay rose gold also! 

IMG_20200201_165340.jpg

IMG_20200130_183930.jpg

IMG_20200124_231018.jpg

IMG_20200201_182255.jpg

IMG_20200124_231015.jpg

  • Like 1
3 hours ago, PLYNX said:

In the first pic . . why are all those guys looking at your Skyline ?  . . . . .ah America . . . I forgot Fast & Furious . . . . . 

Probably much the same reaction you would get here in Oz if you turned up to a car rally in a 78 Pontiac with a massive chook on the bonnet.  Cars are cars and the more diverse you get the more interesting the things are.  Guessing an R32 is an uncommon site in the US.

C'mon feel the Illinoise.

Edited by djr81

Hello Wisconsin!......wait, wrong state, um.....

Hey Kenosha!.....wait. Um. Still wrong. Um...

Gary. The most dangerous city in the mid west. Oh. hell. Still wrong.

Um? Is the wind off the lake cold at this time of year? (I was working on the steel plant on the other side of the state line in East Chicago a few years ago at this time of year and it was focking awful.

Here's some useful math for everyone:

How to convert US Horsepower into actual Horsepower (ATW).

(US HP Claim) x 0.80 = actual HP.

This also works for HSV's except it's (HSV owner claim) x 0.75 = actual HP.

 

 

14 hours ago, RedEmblem said:

Here's some useful math for everyone:

How to convert US Horsepower into actual Horsepower (ATW).

(US HP Claim) x 0.80 = actual HP.

This also works for HSV's except it's (HSV owner claim) x 0.75 = actual HP.

 

 

Well I mean I can dig out my Dyno sheets. 

 

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

    • 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.
    • Nah, that is hella wrong. If I do a simple linear between 150°C (0.407v) and 50°C (2.98v) I get the formula Temperature = -38.8651*voltage + 165.8181 It is perfectly correct at 50 and 150, but it is as much as 20° out in the region of 110°C, because the actual data is significantly non-linear there. It is no more than 4° out down at the lowest temperatures, but is is seriously shit almost everywhere. I cannot believe that the instruction is to do a 2 point linear fit. I would say the method I used previously would have to be better.
×
×
  • Create New...