Jump to content
SAU Community

Recommended Posts

anyone with a aftermarket FMIC on their m35 ...what was the dimensions you used without having to butcher the front bar to buggery?

and was that a relatively easy fit?

Doesnt need to be huge. infact id rather it quite thin but long. Anything has to be better than the standard one on there.

any feedback on dimensions would be great so i know what to buy before tearing the front bar off.

cheers

keir

Link to comment
https://www.sau.com.au/forums/topic/336689-m35-fmic-dimension-limitations/
Share on other sites

anyone with a aftermarket FMIC on their m35 ...what was the dimensions you used without having to butcher the front bar to buggery?

and was that a relatively easy fit?

Doesnt need to be huge. infact id rather it quite thin but long. Anything has to be better than the standard one on there.

any feedback on dimensions would be great so i know what to buy before tearing the front bar off.

cheers

keir

Mine has a 600 x 220 core now I modified it, bolts under the bar, just.

Most of the guys run a standard 600 x 300 but you have to remove the thermo fan and replace it with a thinner one, core sits behind the bar.

I used to run a 450 x 300 which fit beside the thermo fan motor but it wasnt ideal.

There is enough width to run maybe 800mm if you really wanted but you are stuck with standard core sizing usually.

yeah i was thinking something along the lines of this.

but its a bit short.

http://cgi.ebay.com.au/ws/eBayISAPI.dll?Vi...e=STRK:MEWAX:IT

you reckon its feasible?

or should i go something longer and thinner?

Best cooler will be a 600 x 300 x 76 and a thinner fan, The HDI kit would be the go if you have the coin. All the piping is plastic and will need to be changed so factor that in.

Do you have a power goal? Mine keeps raising... ;)

Best cooler will be a 600 x 300 x 76 and a thinner fan, The HDI kit would be the go if you have the coin. All the piping is plastic and will need to be changed so factor that in.

Do you have a power goal? Mine keeps raising... ;)

I've got the HDI FMIC kit....no complaint's and easy to install yourself....big improvement over the standard one especially in summer.

yeah i was thinking something along the lines of this.

but its a bit short.

http://cgi.ebay.com.au/ws/eBayISAPI.dll?Vi...e=STRK:MEWAX:IT

you reckon its feasible?

or should i go something longer and thinner?

If you want one that will fit nicely under the reo, maybe look at this Trust unit?

http://cgi.ebay.com.au/TRUST-GReddy-Interc...9#ht_1694wt_911

Is looking more and more like the way I go and get some 1-piece mandrel bent inlet and outlet piping done locally.... will have to make up your own brackets though

But then again, I am not going for 300awkw

Edited by iamhe77
hrm i can afford the HDI kit... is anyone still supplying them.. i saw danny or someone in another thread was making up kits or am i mistaken?

You'll have to contact Josh (I think?) at http://www.hybrid-power.com/index.php]HDi

02 9620 7388

[email protected]

Edited by iamhe77

Hey mate,

For a little variety I went the Blitz CS FMIC kit for the M35 from Just Jap. Cheaper than the HDi unit also (last time I checked). It was $999 + around $50 postage to the Gold Coast. If you would like to see it/drive it, come on down.

Blitz FMIC

Core Size - 620 x 266 x 76mm. Only the reo bar had to be cut back a tiny bit. Could not be happier though.

Cheers

PS: Glad theres more M35s in Qld now.

Hey mate,

For a little variety I went the Blitz CS FMIC kit for the M35 from Just Jap. Cheaper than the HDi unit also (last time I checked). It was $999 + around $50 postage to the Gold Coast. If you would like to see it/drive it, come on down.

Blitz FMIC

Core Size - 620 x 266 x 76mm. Only the reo bar had to be cut back a tiny bit. Could not be happier though.

Cheers

PS: Glad theres more M35s in Qld now.

You cut back the alloy reo? How is the air going to flow to that part of the cooler? Maybe you should have put a thinner fan on instead.

You cut back the alloy reo? How is the air going to flow to that part of the cooler? Maybe you should have put a thinner fan on instead.

I had just replaced the fan with a new OEM one so I was not going to do that again. Plus, it was my Mechanic who did it without telling me prior to him installing it. Sucks to be me.

Hey mate,

For a little variety I went the Blitz CS FMIC kit for the M35 from Just Jap. Cheaper than the HDi unit also (last time I checked). It was $999 + around $50 postage to the Gold Coast. If you would like to see it/drive it, come on down.

Blitz FMIC

Core Size - 620 x 266 x 76mm. Only the reo bar had to be cut back a tiny bit. Could not be happier though.

Cheers

PS: Glad theres more M35s in Qld now.

hmm... Hdi's kit should set you back around the $800 mark. Can't remember if that included shipping or not though.

Also, the HD' GT2 core is significantly more efficient than the Blitz unit

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