Jump to content
SAU Community

Recommended Posts

This is some information someone posted on the Something Awful forums...he posted some pretty acurate details of the 350Z a few months before it was released

Whether what he says is true or not is to you to decide, but i tend to belive him

Okay, I was sent this url by a friend on the board that knows my connections with Nissan North America as well as Nissan Japan. When the 350Z was coming out, I reported back on details as well as spy photos a good six months prior to the car being seen anywhere, based off the info my sources had given me. The only thing I was off on was the final hp. I was off by 13, because they detuned more than my source thought they would. I had posted photos as well as tech stats and had Nissan management contacting me to find out who the heck was their leak. Needless to say, I said nothing and I still have my sources, both overseas and here as well.

Don't think I am being an ass by teasing or not going too much into detail. Some shit I can say because I have heard it numerous places, other stuff I can tease around but can't say directly without risk of shit coming down on me, and truth is, there is still things that can change. There is some misinformation thus far mentioned... so let's clear some things up, shall we? (no disrespect meant)

The ONLY photos of the new GT-R that have been seen are the press shots Nissan released two years back of what the car **might** look like. The new images that people are saying are real are photoshopped variations, and not off of other Nissan product, but rather Opel.

http://www.atonal.ca/frugalgarage/gtrpic.jpg <--- photoshopped, sooo not the next gt-r

Okay, engine wise, the car will not have a V8, period. Not open to discussion, this has been set in stone. Quote me if you wish. It will be a VQ with twin turbo. NOT the same VQ that is found in the 350Z though, and that's all I have to say about that.  I got this info from a high up source that was present at the testing of the engine. He's seen it first hand.

Side note... the 350Z gets a MAJOR make over for the same time the GT-R comes out. Both will be debuted in November 2006 at the Tokyo Auto Salon as 2007 models. The 350Z won't be called the 350Z anymore... we'll leave that like that.  

One of the big issues right now for the GT_R, is whether they will release their new 8 speed transmission or not with this car. Paddle shift as an option, just as in the F1 curcuit. Yes, it'll be AWD, but I don't think that's a shock.

The next GT-R will not wear a Nissan badge in North America. Period, not open to discussion. Reason for this is common sense. There are a little over 100 Infiniti dealers in North America where there are over 2000 Nissan dealers. Now if you need to train your techs to deal with the new GT-R's system, are you going to train 5000+ techs or 200+ techs? A $60,000+ car... think that'll move like crazy out of a Nissan dealership? Nope. It will wear the Infiniti badging and will be sold simply as the "Infiniti GT-R". Not the Skyline GT-R. In Japan, it will be sold as the Skyline GT-R.

I have been waiting for some of the spy pix of the car, as there has been over 15 variations to date built as working prototypes since 2002 to now. Nissan knows the shit that went down with the 350Z, and the non porn website I used to own/run (that will remain nameless) was credited in Road and Track with breaking the spy photos of the Z... so Nissan knows to keep security tight both in Japan and Phoenix where testing is currently underway. I speak with my contacts every 2 weeks or so, and usually there is nothing really new to report.

Yes, Lotus was given a shot at doing the suspension, it isn't in stone yet though as Nissan is also creating some ideas that will give Lotus a run for it's money. If you recall, Nissan has had a good career in racing and some of their cars ran side by side with the Jag XH220 and XJ215 series.. that was ten years back, but some of that technology is making it's way into the new GT-R.

As for body construction (not design)... without saying anything... umm... think NSX.

That's pretty much allI can say for now... but I will be back with updates as I get 'em. As always, I know nothing and I made this all up.

Link to comment
https://www.sau.com.au/forums/topic/48839-miscellaneous-gtr-info/
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

    • First up, I wouldn't use PID straight up for boost control. There's also other control techniques that can be implemented. And as I said, and you keep missing the point. It's not the ONE thing, it's the wrapping it up together with everything else in the one system that starts to unravel the problem. It's why there are people who can work in a certain field as a generalist, IE a IT person, and then there are specialists. IE, an SQL database specialist. Sure the IT person can build and run a database, and it'll work, however theyll likely never be as good as a specialist.   So, as said, it's not as simple as you're thinking. And yes, there's a limit to the number of everything's in MCUs, and they run out far to freaking fast when you're designing a complex system, which means you have to make compromises. Add to that, you'll have a limited team working on it, so fixing / tweaking some features means some features are a higher priority than others. Add to that, someone might fix a problem around a certain unrelated feature, and that change due to other complexities in the system design, can now cause a new, unforseen bug in something else.   The whole thing is, as said, sometimes split systems can work as good, and if not better. Plus when there's no need to spend $4k on an all in one solution, to meet the needs of a $200 system, maybe don't just spout off things others have said / you've read. There's a lot of misinformation on the internet, including in translated service manuals, and data sheets. Going and doing, so that you know, is better than stating something you read. Stating something that has been read, is about as useful as an engineering graduate, as all they know is what they've read. And trust me, nearly every engineering graduate is useless in the real world. And add to that, if you don't know this stuff, and just have an opinion, maybe accept what people with experience are telling you as information, and don't keep reciting the exact same thing over and over in response.
    • How complicated is PID boost control? To me it really doesn't seem that difficult. I'm not disputing the core assertion (specialization can be better than general purpose solutions), I'm just saying we're 30+ years removed from the days when transistor budgets were in the thousands and we had to hem and haw about whether there's enough ECC DRAM or enough clock cycles or the interrupt handler can respond fast enough to handle another task. I really struggle to see how a Greddy Profec or an HKS EVC7 or whatever else is somehow a far superior solution to what you get in a Haltech Nexus/Elite ECU. I don't see OEMs spending time on dedicated boost control modules in any car I've ever touched. Is there value to separating out a motor controller or engine controller vs an infotainment module? Of course, those are two completely different tasks with highly divergent requirements. The reason why I cite data sheets, service manuals, etc is because as you have clearly suggested I don't know what I'm doing, can't learn how to do anything correctly, and have never actually done anything myself. So when I do offer advice to people I like to use sources that are not just based off of taking my word for it and can be independently verified by others so it's not just my misinterpretation of a primary source.
    • That's awesome, well done! Love all these older Datsun / Nissans so rare now
    • As I said, there's trade offs to jamming EVERYTHING in. Timing, resources etc, being the huge ones. Calling out the factory ECU has nothing to do with it, as it doesn't do any form of fancy boost control. It's all open loop boost control. You mention the Haltech Nexus, that's effectively two separate devices jammed into one box. What you quote about it, is proof for that. So now you've lost flexibility as a product too...   A product designed to do one thing really well, will always beat other products doing multiple things. Also, I wouldn't knock COTS stuff, you'd be surprised how many things are using it, that you're probably totally in love with As for the SpaceX comment that we're working directly with them, it's about the type of stuff we're doing. We're doing design work, and breaking world firsts. If you can't understand that I have real world hands on experience, including in very modern tech, and actually understand this stuff, then to avoid useless debates where you just won't accept fact and experience, from here on, it seems you'd be be happy I (and possibly anyone with knowledge really) not reply to your questions, or input, no matter how much help you could be given to help you, or let you learn. It seems you're happy reading your data sheets, factory service manuals, and only want people to reinforce your thoughts and points of view. 
    • I don't really understand because clearly it's possible. The factory ECU is running on like a 4 MHz 16-bit processor. Modern GDI ECUs have like 200 MHz superscalar cores with floating point units too. The Haltech Nexus has two 240 MHz CPU cores. The Elite 2500 is a single 80 MHz core. Surely 20x the compute means adding some PID boost control logic isn't that complicated. I'm not saying clock speed is everything, but the requirements to add boost control to a port injection 6 cylinder ECU are really not that difficult. More I/O, more interrupt handlers, more working memory, etc isn't that crazy to figure out. SpaceX if anything shows just how far you can get arguably doing things the "wrong" way, ie x86 COTS running C++ on Linux. That is about as far away from the "correct" architecture as it gets for a real time system, but it works anyways. 
×
×
  • Create New...