Jump to content
SAU Community

Recommended Posts

The question is more do you want a Stagea?

The VE on paper is better for everything you are looking at; cheaper parts, more modern, better climate control, safer, cheaper to run and likely better resale.

The only pro for the Stagea is that it is a Stagea.

Don't get me wrong, I love mine - and I bought it with the idea of it being the Daily and eventually Family Wagon.

But I also bought it because I wanted a Stagea, if I had only wanted a Family wagon I would go VE in a heart beat.

The rear ducts were an option on the M35 I believe, however its been shown that it can be retrofitted with ease as the ducts just terminate under the center console/arm rest.

The NA model PM35 is a better option for parts as it shares an engine with 350z's and V35's and its upkeep is likely less being naturally aspirated and RWD.

I also imagine you could easily get away with 95 octane in the NA - I wouldn't use anything but 98 in the turbo myself (it can still likely run on 95 though).

I disagree, the service costs and parts availability are cheap and easy to come by. I paid $7,000.00 for my C34 S2 Dayz edition Stagea with 90,000 km on the clock the 100,000 km service cost me just shy of $450.00 for all the parts with a new in cabin air filter.

I find it very interesting the amount of miss information floating around. To fully insure the car is only $500 per year through famous car insurance.

My C34 S2 Days edition is RWD 2.5 Turbo, it uses 8.5L on the highway and betwen 9.5 and 10 around town.

At the end of the day the VE wagon is not a better option, truth be told they are crap, they do not hold there value and are over priced in the market as it is.

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

    • 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. 
    • Holy hell! That is absolutely stunning! Great work!!!
×
×
  • Create New...