Jump to content
SAU Community

Recommended Posts

M-Spec are in R33 too,

i had one myself. 1996 models onwards, as far as i know it was mainly the front lip, side skirts and rear bar which was different. Also newer interior etc but that was more to the fact it was a series 2 upgrade as opposed to M-Spec.

Link to comment
https://www.sau.com.au/forums/topic/344330-m-spec-skyline/#findComment-5550331
Share on other sites

r33 gts-t are type M, not M spec. it's just that 90% of people don't know this so just refer to them as M spec.

as for what it means, it means jack all in the r33 range. pretty much every gts-t r33 is a type M, except for a rare 4 door auto gts-t which is a type G or something like that.

in the r32 gts-t the type M meant bigger brakes and leather gear boot and handbrake boot, or something like that. but even then, most of them were type M as well.

Link to comment
https://www.sau.com.au/forums/topic/344330-m-spec-skyline/#findComment-5550534
Share on other sites

M-Spec are in R33 too,

i had one myself. 1996 models onwards, as far as i know it was mainly the front lip, side skirts and rear bar which was different. Also newer interior etc but that was more to the fact it was a series 2 upgrade as opposed to M-Spec.

pretty sure that more comes down to the options chosen. front and rear bars don't mean much as they can easily be replaced. my type M didn't have the more aggressive front bar on it because it had been damaged and it had just had the non turbo front bar put on it.

Link to comment
https://www.sau.com.au/forums/topic/344330-m-spec-skyline/#findComment-5550544
Share on other sites

M-Spec refers to the R34 GTR M-Spec / M-Spec Nur.

Never heard of a M-Spec in the R33 range, as far as I know.

LOL sorry but this is wrong. M (Motorsport) Spec was released on r32, r33 and r34 single turbo skylines. My R32 is M Spec :D 33s and 34s changed it slightly to Type M.

Edited by plan-b
Link to comment
https://www.sau.com.au/forums/topic/344330-m-spec-skyline/#findComment-5550589
Share on other sites

my bad. 34s didn't adopt the 'M'. I thought they did...but i guess that's why I drive a 32. Yeowww

Thats a dope link as well. Should sticky that if not already.

Edited by plan-b
Link to comment
https://www.sau.com.au/forums/topic/344330-m-spec-skyline/#findComment-5550611
Share on other sites

Not everything in those factory specs is 100% correct.

For example, they list the "standard features" (in my eyes, every car has regardless) as having fog lamps. Mine does not. It has the switch for them, but it has the GTR style OEM front end on it without the space for fog lamps.

Link to comment
https://www.sau.com.au/forums/topic/344330-m-spec-skyline/#findComment-5550903
Share on other sites

LOL sorry but this is wrong. M (Motorsport) Spec was released on r32, r33 and r34 single turbo skylines. My R32 is M Spec ;) 33s and 34s changed it slightly to Type M.

:D

Type M it is.

M-Spec = R34 GTR variants.

:)

Link to comment
https://www.sau.com.au/forums/topic/344330-m-spec-skyline/#findComment-5551720
Share on other sites

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