Jump to content
SAU Community

Recommended Posts

  • Replies 91
  • Created
  • Last Reply

Top Posters In This Topic

Next door, she drives a R33 GTST S2 97 and just under 300tho I think from memory.

Her engine runs very nicely still. Her ABS just went recently though.

I own R33 GTS 95, NA

102,500

My old R34 was 1999 model with log books for 47,000km....when it was stolen (repairable write-off) in 2005 it had 160,000km.

Reappeared on Paramatta Rd with 35,000kms :P

Current R34 is a 1998 model with log books for 27,000km, just hit 100,000 the other day

mine had 85,000 ks when i got it 3 yrs ago now showing 115.000ks thats about 10.000ks a yr plob slow down a bit now as it just sits in the garage hasent been driven for about 4 or 5 weeks just lost intrest in them really the novelty of been a skyline owner has worn off .

and how many of these odometers are genuwine?????? lol none

I think it's undeniable there is a common trend in odo readings. Although if you've got log book proof, you'd be fine to believe yours is genuine.

The people that have theirs in the 100k+ figures are just people that drive their cars as dailys and manage to clock plenty of kms fast. I've clocked 40 000 odd in the 2 and half years of ownership of my vehicle. Bought it with 97 000, which I knew was a pretty whacked figure for a 93 model car and had to have been tampered with.

Edited by KeyMaker

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