Jump to content
SAU Community

Recommended Posts

Haha that's off the Infiniti Australia website. They are going to have the coupes at the Sydney motor show. They're definitely out there, they started with the 4WDs late August. I saw two of the 5 litre V8's at Brisbane airport today in the carpark..

I didn't believe you, so I went and looked. Thats just terrible.

  • Replies 63
  • Created
  • Last Reply

Top Posters In This Topic

I've been living in a hole, but just saw the release date for both the coupe and hard-top convertible here will be December, only Big Kev would have been more excited (probably)

No doubt I'd be getting those grotty Infinit badges taken off, but wow haven't we come leaps and bounds with getting a few decent Nissan models at last!!!!!

I saw the hard-top 36's in the US and they were porntastic!

Yo Dan, long time no see! I would be excited if I could actually afford one. you got kids yet?

Yeah shame they are going to be the wrong side of $100k ...

There actually have been some V36 convertible coupes in Australia for around 6 months now - someone brought in about 10 from Europe (the only market they are currently sold in), so they were already rhd and had all English buttons and controls ... they were selling on Ebay and CarSales out of a business in Qld for about $55k-$70k depending on kms and spec ....

Yo Dan, long time no see! I would be excited if I could actually afford one. you got kids yet?

Yeah been a while. No kids on the horizon just yet. I'm trying to sort my life out with a few ideas and concepts for a business.

One revolves around pharmacy now I'm registered,the other is tip rope secret until I get the patent lodged. Needless to say it's electronics based...which is what I spend my spare time doing. So much for the pharmacy degree haha. At least I can write medical certs though,and will have limited prescribing rights coming.

I disagree.. when you say GT-R, you think beast race car. The skyline name on its own has been quite varied over the years.. After all there was a Australian Built R31 Sedan and wagon that would hardly fit into the 'race car' catergory and more into the 'company fleet cars', and family wagons.

There were far more R series skylines that I wouldn't consider in the class of 'race car', fitted with RB20DE, RB25DE engines.. or the stock turbo versions of each which still produced less power and torque than the VQ35DE in the V35.

This Skyline history is my wallpaper on my work computer :P I love the old school 71' Skylines.

Its a shame though our G37's will have less power than all the rest of the g37's wordwide, i find that quite ridiculous when you going to charge about 100k for a sports coupe that is now much slower than a lot of its rivals i.e BMW 335. I will hold out and wait for the new shape in 2014, apparently the IPL version will be a serious sports car aimed at the AMG's and M3's. Yes will be expensive but if its available in a Skyline version in Japan maybe we can import them since technically they are different cars.

To be competitive they need to be sub $90k as there are plenty of Euro cars that would demolish them in the market. The performance will keep its price in check Price should be announced at the motor show..as they have various spec levels.

No chance unless they're pre Dec 2012 models.....even then Nissan may have stitched up that loophole already by having them on Aussie soil already to go in warehouses. Cheffy would know the exact details.

I would expect it would be determined by the date they go on sale here in Aust. like they did with the R35 GT-R.

possibly the reason nissan are releasing the V36 here toward the end of its model life instead of wating for the V37.. it will prevent anyone sneaking some V37s in before they can get the infiniti version of the same car on the showrooms here.

^^ interesting. good to see there is still some common sense in our legal system .... don't know how it fits in with this thread though??

Surprising on what you can make bible passages appear say when you fail to quote all of it..

If it is anything like Infiniti USA, it will have the code name G37 and that’s it, and if they are releasing it at the end of this year, it will be the same as the Skyline V36.. when the V37 is released, the G37 will likely be upgraded to the same..

In USA, the Infiniti G35 model covers both the V35 and the V36 and I have only ever seen them differentiated by specifying the year, so I guess there isn't any other code to tell them apart.

However, we should stil be able to import a V36, provided it was originally sold in Japan before the G37 hit the showroom here.

If it is anything like Infiniti USA, it will have the code name G37 and that’s it, and if they are releasing it at the end of this year, it will be the same as the Skyline V36.. when the V37 is released, the G37 will likely be upgraded to the same..

In USA, the Infiniti G35 model covers both the V35 and the V36 and I have only ever seen them differentiated by specifying the year, so I guess there isn't any other code to tell them apart.

However, we should stil be able to import a V36, provided it was originally sold in Japan before the G37 hit the showroom here.

Actually the G37 still runs a V36 chassis code.

http://www.jimwolftechnology.com/wolfpdf/NISSANINFINITICHASSISCODESTO2009.pdf

So chances are once it becomes a fully imported model we won't be able to import them anymore.

yeah looks like you're right we wont be able to import skylines any more. bullocks, im going to keep my v36 for a while then. best thing to do then is save up for a couple of years and try for a 2009 GTR. hopefully they'll be in the 80's by then.

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