Jump to content
SAU Community

Recommended Posts

10 hours ago, JB4U said:

Thanks!! Series 3? No idea how to read these haha

Certainly not the '95 in your profile hey!

FAST is the source of all truth but Mark pulled all that info and put it in the form of http://gtr-registry.com.

You can bang yours into http://gtr-registry.com/en-bcnr33-vin-table.php and you can verify that it is indeed a s3, and all the option codes from FAST are translated too. (large front spoiler!) =-D

 

 

2019-08-20 08_14_28-GTR-Registry.com - Nissan Skyline BCNR33 VIN Table.png

  • Like 1
41 minutes ago, RANDY said:

Certainly not the '95 in your profile hey!

FAST is the source of all truth but Mark pulled all that info and put it in the form of http://gtr-registry.com.

You can bang yours into http://gtr-registry.com/en-bcnr33-vin-table.php and you can verify that it is indeed a s3, and all the option codes from FAST are translated too. (large front spoiler!) =-D

 

 

2019-08-20 08_14_28-GTR-Registry.com - Nissan Skyline BCNR33 VIN Table.png

Sweet! Thanks man! Looking at buying it but wanna make sure all is in order before doing so! 

21 minutes ago, DaveO74 said:

Thanks Randy,

So do you know what the model is telling me?

 

6th digit is a "Q", which apparently is not a S or PS. It would also have 18's rather than 19's?

2019-08-27 22_04_46-server - TightVNC Viewer.png

  • 6 months later...
41 minutes ago, borka1975 said:

Can some one do a FAST check on my 32R

model: BNR32-221852

any info would be great, Km traveled in Jap (last rego check) options included etc...

thanks in advance

The FAST system is just Nissan's build database, so it only shows how your car rolled off the production line.

You can check the options decoded from the "Model", but GTR registry has already translated it all for you.

 

 

2020-03-19 22_23_12-NFA010 Nissan FAST for Windows [1].png

2020-03-19 22_26_34-GTR-Registry.com - Nissan Skyline BNR32 VIN Table.png

4 minutes ago, RANDY said:

The FAST system is just Nissan's build database, so it only shows how your car rolled off the production line.

You can check the options decoded from the "Model", but GTR registry has already translated it all for you.

 

 

2020-03-19 22_23_12-NFA010 Nissan FAST for Windows [1].png

2020-03-19 22_26_34-GTR-Registry.com - Nissan Skyline BNR32 VIN Table.png

Thanks Randy, not clear on the blank between the S and AA ,GTR registry quotes V-Spec 17" Tyre but X clearly states its a GTR not a V-Spec
only 3 V-spec's in 09/92 as per GTR registry?
what's your take on that info?

cheers, bob

9 minutes ago, borka1975 said:

Thanks Randy, not clear on the blank between the S and AA ,GTR registry quotes V-Spec 17" Tyre but X clearly states its a GTR not a V-Spec
only 3 V-spec's in 09/92 as per GTR registry?
what's your take on that info?

cheers, bob

I imagine it's just a 17" wheel option that the V-Spec gets by default. Just a guess.

On 19/03/2020 at 7:36 PM, borka1975 said:

Thanks Randy, not clear on the blank between the S and AA ,GTR registry quotes V-Spec 17" Tyre but X clearly states its a GTR not a V-Spec
only 3 V-spec's in 09/92 as per GTR registry?
what's your take on that info?

cheers, bob

Hey Bob,

Actually the text in http://gtr-registry.com/en-bnr32-vin-table.php#OptionCodes was slightly incorrect as I had series 2 and 3 combined and yet the code for the 11th digit is different for blank for series 2 and 3.

I've split them up into their own sections and adjusted the text accordingly, so it is more accurate and clearer. Thank you for posting this.

On 3/27/2020 at 7:04 PM, sin- said:

Hey Bob,

Actually the text in http://gtr-registry.com/en-bnr32-vin-table.php#OptionCodes was slightly incorrect as I had series 2 and 3 combined and yet the code for the 11th digit is different for blank for series 2 and 3.

I've split them up into their own sections and adjusted the text accordingly, so it is more accurate and clearer. Thank you for posting this.

Hey Mark,

Is this now 100% correct or we think it's 99%?
cheers Bob

  • 3 months later...
7 hours ago, PriceyENR34 said:

Hi guys I've been having troubles trying to find out the year of the rb26 that went into my enr34

engine number is

rb26034074A

Just wondering if someone could look it up for me?

 

I don't think that's possible to look up without the VIN of the car it came from.

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