Jump to content
SAU Community

Recommended Posts

Drift seats installed.....

DSC00403.jpg

Helen & I got the stag washed today for the meet. The only part about washing the car I hate is after admiring how sweet it looks nice & clean. When you take a real close look all the stone chips & imperfections are visible. Oh well.....

Bit of an experiment, fitted a K&N pod filter to the stag today.

Needs some brackets to hold it in place but does the job, checking the Informeter readouts. Should also give me room for the catch can.

Tomorrow will fit the HDi Intercooler I got from Cam (Thanks mate - looks great!).

Finished up the install today for the iPhone connection via the AV input on the Commsman tuner. I used a little Narva push switch fitted in the coin storage inside the console to switch the tuner to the AV input.

Happy with the end result with everything tucked away out of view and neat and tidy when using it. The iPhone connect I bought doesn't support video on the iPhone but I only use it for music and I use the USB for movies, plus it was only around $30 delivered from the US. It does charge the iPhone so thats a plus.

Next on the list is a reverse camera once I decide which one to use.

Edited by slippylotion
Next on the list is a reverse camera once I decide which one to use.

Looks good. Should check out my reverse camera. Not installed yet, but it's wireless and replaces one of the number plate lights with the camera and an LED. Not quite the right size, needs an adapter made up as it's designed for a 350Z and is a bit too small.

I had a busy weekend, but still found some time for some Stag love.

First, I removed the airbox and test fitted a pod filter. The definite pro is that it makes plenty of room for a catch can, and flows more air. The con is that it now maxes out the injectors, and I need to check the intake temps. Not sure at this stage if it's worth keeping or not, but if I keep it I'll be replacing the temporary K&N filter with something non-oiled.

Today I started fitting the HDi intercooler. Underestimated how quickly it would get dark, and ended up trying to fit it in the dark. Not fun. Stopped for the night and will continue tomorrow, with the epic battle between myself and the standard hot-side intercooler hose :domokun:

New thermo fan doesn't exactly attach up as per the instructions either, but I'll play with it tomorrow in the light and work it out.

I just bought the similar camera but for the x-trail but not wireless. Looks easy to get to fit.

What resolution are our factory screens?

Depends which one. I think mine was 350Z/early X-trail? Just needs a surround to mount it up to the standard bolt holes.

Not sure on standard resolution, just know they're NTSC. Ask Brad or Leon, they'll know for sure.

Had a 70% (?) tune done on Saturday.

No a full tune as we had fuel failure, either filter or pump :(

On the plus side, no more "boost/fuel/air flow/whatever you wanna call it" cut and a different throttle feel.

Throttle is a bit soggier at the moment, but at least I know it can definitely be modified :whistling:

Edited by iamhe77

Had a 70% (?) tune done on Saturday.

No a full tune as we had fuel failure, either filter or pump :(

On the plus side, no more "boost/fuel/air flow/whatever you wanna call it" cut and a different throttle feel.

Throttle is a bit soggier at the moment, but at least I know it can definitely be modified :whistling:

Is this the stock pump or aftermarket?

I think mine managed 248awkw on the stock pump...

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