Jump to content
SAU Community

Recommended Posts

Make:Mazda

Model:Cosmo

Milage:78,000

Colour:Blue

Location:Sydney, North

RWC supplied?n/a

Currently registered?Y

Price:$21000 or open to trade for GTR (32/33) with cash either way

Contact: PM or [email protected]

Comments / Modifications:

<edit> Price Drop to $21K - Includes Work Wheels (worth $3K)

I've just started a new job and the Cosmo is not practical for me (either is the S12). So I need to sell (or trade) the beast.

I've had the car for about 2 years - bought it from the bloke that originally imported it. When I got it, it was totally stock. Now, not so stock.

I've spent way over $50K on this car and I know I won't get it back - so my loss is your gain.

For those that don't know:

JC Cosmo 1990

20B, ECCS model

Motor rebuilt by Race Solutions < 5000kms ago - Race Spec internals

HKS T04Z Turbo

HKS GT2 Wastegate

1600 cc/pin secondary injectors

DMRH FM Intrecooler

Oil Cooler - with GREX S/W plate inc thermostat

B&M Tranny Cooler

MV Autos - Stage 2 Race transmission

Haltec E11V2 ECU - tuned by Hitman

K-Sport Coil Overs

K-Sport 8 piston calipers, 330mm slotted rotors

Sard BOV

Custom Air box

Work Wheels - 18"

Pioneer Stereo (HU) ipod USB i/f - Response Amps and Speakers, JBL Sub

4.5" Exhaust with SMB Mufflers and Cat (Best money can buy)

Dual Walbro 255l/h fuel pumps

Wideband O2 Sensor and guage

Boost, Oil Pressure, Water Temp Guages, Nokia Blue Tooth handsfree

I'm sure I have left some other stuff off too - can't think......

This is an extremely fast car - the gear changes are savage (quick)

Currently running 10 PSI and has 450HP at the rears. Capable of 600 if the boost is increases. This is a genuine 10 second capable car - And I only say 'capable' as I haven't yet run it down the quarter mile.

There are some minor things that need attention.

* With the lowered suspension, the front wheel arches rubbed on the guards and some paint came off - I repaired the damage - but did a rough spray job in blue around the affected area to stop rust etc (the car is blue), as I had planned to get the guards repainted along with the boot (see next point).

* The boot was replaced (the original boot had a spoiler, which I didn't like plus has some rust in it from the spoiler install) the new boot is an ever so slightly different shade of blue - hardly noticeable. The original boot comes with the car too.

Price - I'll take offers around the $25K mark - I have no idea how much the car is worth as I have spent sooooo much money on it. Also open to trades (looking for a stock, rear/all wheel drive, manual, sporty looking car of some type - perhaps a GTR or something)

NO TEST PILOTS PLEASE - Genuine buyers only !

Contact via PM or b-man(at)skylinesaustralia(dot)com

Mobile: 0402 030 038

Images:

rs1.jpg

page0-1003-full.jpg

Link to comment
https://www.sau.com.au/forums/topic/193168-mazda-cosmo-20b-sold/
Share on other sites

For those who have asked:

Motor is fully dowelled, race seals, springs, extended port, S6 Exhaust Sleeves, etc

Wastegate is 60mm

Stall Converter is about 3000 RPM - perfect for boosted launches.

Daily Drivability - You will beat most every car on the street. Daily driving is fine. It's a bit loud - not Peripheral Port loud - but loud enough to set car alarms off in car parks. The stally drives well, you can still creep along, but when you out the foot down the revs go up pretty quick.

Fuel Economy - With 3 x 550cc/min (pri) and 3 x 1600cc/min injectors (sec) - you work it out. (ask any GTR owner that has 6 x 1000cc/min injectors and turbo that support this)

I have an Audi a4 quattro wagon, I would swap for your car if you want. it is a 98 2.6 v6 manual awd, "motor sport" edition. features factory lowered suspension, factory body kit and 16" alloys. It has a 5 speed manual, and is dark blue. mileage is high at 214000, but has a full has been very well maintained and still drives like a new car.

I also own a mitsubishi rvr sports gear. its an awd turbo 5 speed and has done 159000 km.

Both cars are for sale, so if you are interested, we can come to an arrangement.

The cars are both at sunshine coast, Queensland.

  • 2 weeks later...

Price Drop to $21K - Does not include Work wheels anymore - but does include 2 x 18" BA Falcons wheels on front and 2 x 16" 300ZX wheels on read. Rears are shod with Mickey Thompson 255 ET street slicks (legal on the road).

  • 2 weeks later...
  • 3 weeks later...

im in melbourne

id be intersted in a swap i have r32 gtr its in the forsale section dude.

it needs some love but there would be cash your way.

any chance of a roady as well

cheers

Trade for XR5T + cash my way??

15,000ish kms.

Also is your car maual or auto?

Seriously interested

+ Photos of the boot + interior + the pannels with diff paint thanks.

Edited by UNTS-1
  • 2 weeks later...

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

    • Nah. For something like boost control I wouldn't start my design with PID. I'd go with something that originates in the fuzzy logic world and use an emergency function or similar concept. PID can and does work, but at its fundamental level it is not suited to quick action. I'd be reasonably sure that the Profecs et al all transitioned to a fuzzy algorithm back in the 90s. Keep in mind also that where and when I have previously talked about using a Profec, I'm usually talking about only doing an open loop system anyway. All this talk of PID and other algorithms only comes into play when you're talking closed loop boost control, and in the context of what the OP needs and wants, we're probably actually in the realm of open loop anyway. Closed loop boost control has always bothered me, because if you sense the process value (ie the boost measurement that you want to control) in the plenum (after the throttle), then boost control to achieve a target is only desirable at WOT. When you are not WOT, you do not want the the boost to be as high as it can be (ie 100% of target). That's why you do not have the throttle at WO. You're attempting to not go as fast as you can. If the process variable is measured upstream of the throttle (ie in an RB26 plenum, or the cold side pipework in others) then yeah, sure, run the boost controller closed loop to hit a target boost there, and then the throttle does what it is supposed to do. Just for utter clarity.... an old Profec B Spec II (or whatever it is called, and I've got one, and I never look at it, so I can't remember!) and similar might have a MAP sensor, and it might show you the actual boost in the plenum (when the MAP sensor is connected to the plenum) but it does not use that value to decide what it is doing to control the boost, except to control the gating effect (where it stops holding the gate closed on the boost ramp). It's not closed loop at all. Once the gate is released, it's just the solenoid flailing away at whatever duty cycle was configured when it was set up. I'm sure that there are many people who do not understand the above points and wonder wtf is going on.  
    • This has clearly gone off on quite a tangent but the suggestion was "go standalone because you probably aren't going to stop at just exhaust + a mild tune and manual boost controller", not "buy a standalone purely for a boost controller". If the scope does in fact stop creeping at an EBC then sure, buy an EVC7 or Profec or whatever else people like to run and stop there. And I have yet to see any kind of aftermarket boost control that is more complicated than a PID controller with some accounting for edge cases. Control system theory is an incredibly vast field yet somehow we always end up back at some variant of a PID controller, maybe with some work done to linearize things. I have done quite a lot, but I don't care to indulge in those pissing matches, hence posting primary sources. I deal with people quite frequently that scream and shout about how their opinion matters more because they've shipped more x or y, it doesn't change the reality of the data they're trying to disagree with. Arguing that the source material is wrong is an entirely separate point and while my experience obviously doesn't matter here I've rarely seen factory service manuals be incorrect about something. It's not some random poorly documented internal software tool that is constantly being patched to barely work. It's also not that hard to just read the Japanese and double check translations either. Especially in automotive parts most of it is loanwords anyways.
    • If you are keeping the current calipers you need to keep the current disc as the spacing of the caliper determines the disc diameter. Have you trial fitted the GTS brakes fit on a GTSt hub or is this forward planning? There could be differences in caliper mount spacing, backing plate and even hub shape that could cause an issue.
    • Hi there I have a r33 gts with 4 stud small brakes, I'm going to convert to 5 stud but keep the small brakes, what size rotor would I need?
    • 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.
×
×
  • Create New...