Jump to content
SAU Community

What do you drive as a Daily Driver?


Recommended Posts

  • Replies 54
  • Created
  • Last Reply

Top Posters In This Topic

Daily Driver: Ford XLS Ute

Year: 2000

Color: Navy

Best Features: You can chuck sh1t in the back. Work pays for the fuel.

Worst Features: Where to start?? Firstly I guess - its a Ford! Others include lack of passengers (my other car is a 2 seater as well currently), guzzles fuel - I know I said I dont have to pay but I have to fill it with 80L on a regular basis which anoys me!, damn dodgy to drive in the wet (but fun!)

Would I drive it again by choice: No

What Would I Drive Again if by Choice: If I had to still have the tray for work Id like either a Nissan Nivara or Holden Rodeo both 4x4 Dual Cab. Or if I could make it a wagon an Audi Allroad Quattro 2.7T would do just fine!

CAR: 1975 Mitso Galant coupe.

FEATURES: 1600 Engine, wheels, working Air con and stereo.

WHY? It cost me $300!

FUTURE PLANS: When the skyline is finished it will get painted and a 2.6 engine swap, with quad throttle EFI.

Car : 1985 Mitsubishi Colt 45

Colour: White, with Colt 45 Racing Stickers, Blue Racing Interior and racing seat cover, along with racing gearknob and pedals

Best Feature: use it only for taking dogs to the vet, needing to park anywhere i want, 4speed manual, front wheel drive (meaning i cant break something from wanting to go farm and do burnouts)

Worst Feature: its a mitsubishi colt

Performance: can do burnouts in 1st when dry, 1st and second when wet

Would I drive it again by choice: no

What i would prefer as a daily driver: Suzuki Carry Van 1983 :P

My Daily Driver

Car : BNR32

Colour: Black

Year: 1994

Best Feature: Decent stereo, good clutch :P

Worst Feature: the inconvenience of 2 doors, boot space, warm up time

Performance: not bad... (as rated by some guy in a VN)

Would I drive it again by choice: Yeah sure

What would prefer as a daily driver: S2000

Dislike Factor: 0/10

My Other Cars

Car : Mazda Astina

Colour: Blue

Year: 1996

Best Feature: Comfy ride, big boot, cup holders

Worst Feature: Its only the 1.8L version

Performance: No rating

Would I drive it again by choice: yes

Dislike Factor: 2/10

Car : Toyota Corolla

Colour: Blue

Year: 1994

Best Feature: Its the car we take when we do dirty jobs (ie: dumping at the tip, carrying plants, etc). Its got a towbar and roof racks!

Worst Feature: No aircon

Performance: No rating

Would I drive it again by choice: not really

Dislike Factor: 6/10

The Mighty Daewoo Matiz - Van Version (Work car)

Best features - Cup holder, tight parking is a breeze and I dont pay a cent on anything which means more $ for mods.

Worst feature - It's a Daewoo, It's a Matiz, It's a Daewoo Matiz, Only 3 cyl 725cc, oh did I menttion it's a Daewoo Matiz?

Who ever said chicks dig small cars should be shot and so should my boss for buying them! :D

As well as the Civic I forgot to admit to the Bike.

Motorcycle : Suzuki GSX550EF

Colour: Red Blue White Black Gold (not kidding, needs paintjob.)

Year: 1985

Best Feature: The freedom and fun of two wheels...

Worst Feature: Volvo drivers. (if you ride, you know what I mean)

Performance: Enough to get into and out of trouble.

Would I ride it again by choice: No, If I get another bike after this one it will be a "Sunday ride only" Ducati. Commuting is just too bl00dy dangerous. ( DAMN, I'm getting old! )

What would I prefer as a daily driver: Still something like a 3 series Beemer.

Like Factor: (the glass is half full ): 6/10

Up untill two months ago I had a Range Rover as my daily driver.

Color: Red

Year: 1993

Best feature: I could drive over anything or anyone !!

Worst feature: lots and lots of fuel, break downs and headaches

Performance: really hard to get it going, but cruised well on the freeway, and was great off road- I think thats what killed it !

I would love to have a 4X4 for camping, and even with all the hassels the rangie gave me I would still have another one.

I'm driving my GTR every day at the moment- its loud, fast and a bugger in traffic but I love it !!!!

like factor: 7/10 for the rangie and the GTR is of the scale

Well I've two others ;)

1)

'81 280zx, Black with silver bonnet, 5 spd manual & targa roof. 2.5" from the manifold back sounds cool for an old girl :P

Hmm, good for a cruise with the roof open and a 2:24 around Philip Island, that was fun! Kept in fornt of the V8 Hillmen and almost kept up with the SII RX7 :D understeers like a bastard tho. Haven't driven for a while and is for sale! Offers?? $$$$

2)

'92 MR2 GT-S Red

Quick, nimble and its an MR! handles like a go-kart and yes that's a good thing! Great ****pit for excellent sound with the stereo!

Will be going on the market once I replace the boot lining. Made a pasta bake in the boot after a trip back from Apollo Bay along the great ocean road. If only the pasta had of cooked as well I would have had diner ready to serv :(

Don't smell too good now. Will miss it when it goes tho...

Just need a need a silver BMW M5 parked along side the R33 now...

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