Jump to content
SAU Community

Recommended Posts

Lots of mis-information there ^^^^

In regards to...?

BTW to correct my last post, Power FC D-Jetro has a lot more tuning capabilities so don't get me wrong. In terms of tuning it's a big deal but in terms of power difference then there wouldn't be a big difference between a NIStune and PFC.

Most of it came from NS, so...... :glare:

This is true but how well it's paid off? We'll see how the flames go.

I would have thought that if the Nistune handles the Z32 AFM's and aftermarket injectors etc that it would be the better option. That is if it can control the idle better than a PFC and peg back the timing it it is knocking. If it doesn't then it is going to be pretty similar as far as I can tell. I haven't read up much on the Nistune as I have a PFC which is why I'm not too sure about it's exact pros and cons. If if is the change in AFM that causes the idle issues with PFC then maybe Nistune is in the same boat depending on what it can adjust for idle?

Is there a better option for Nistuning an R33 GTST, ie any pros and cons of Z32 or R32 ECU's?

Z32 can control the VCT and it has something else that it can control better, I can't remember but pete from nistune was telling me, might have been something with the knock sensors I can't remember.

But you can easily control the VCT via an MSD window switch or an eboost street (with built in window switch). There is plenty of discussion on the nistune forums and on here regarding the differences if you do a search though. :)

I would have thought that if the Nistune handles the Z32 AFM's and aftermarket injectors etc that it would be the better option. That is if it can control the idle better than a PFC and peg back the timing it it is knocking. If it doesn't then it is going to be pretty similar as far as I can tell. I haven't read up much on the Nistune as I have a PFC which is why I'm not too sure about it's exact pros and cons. If if is the change in AFM that causes the idle issues with PFC then maybe Nistune is in the same boat depending on what it can adjust for idle?

Is there a better option for Nistuning an R33 GTST, ie any pros and cons of Z32 or R32 ECU's?

Nistune can be set up to idle really well with most changes, but as with all such things, spastically large injectors or massive AFM capacity mean that you're working at the very bottom end of the scale (pulse width or AFM voltage) when idling, so you'll still end up with fluffy behaviour once you go past a certain point. It is the factory ECU in all respects except that you can change the maps and the various other values. So the code that makes it run remains the same - the same smarts. I suppose there are probably a number of places where we push the tuning out past where the ECU designers expected it to operate and so the code might not be smart enough - but it still works pretty well even when pushed. The main place where Nistune falls down is when you want to do things that you can do with aftermarket ECUs like run aux outputs and ECU based boost control.

The other place where Nistune suffers is that the factory ECU sometimes sucks at reliably detecting knock and switching to the knock maps. Some will work fine. Some will change to the knock maps when there's no real knock at all, and others won't change when it's pinging its tits off. Mine was wrongly convinced it was knocking, so we ended up having to make the knock maps the same as the main map to keep the tuning as we wanted it. Some years later, it's still running that way and it's perfectly fine.

If you use an R32 ECU to run an RB25, the main thing is you need to use an external control box to switch the VCT at the right points. If you use a Z32 ECU, it can do the VCT already and you just have to rewire the outputs for the different firing order. They are otherwise all almost the same ECU. The tunability and so on is all pretty much exactly the same. The Z32 is probably the easier option overall.

There may be other points for an aganist, but that's pretty much the core of it.

  • Like 1

Yeah do not trust the knock sensors, I had audible knocking that was not picked up with them. From talking to pete he is in the mind that due to overwhelming engine noise above ~5k the knock sensors increase the threshold massively and basically ignore knock, hence if peak torque is above 5k then it will probably ignore knock, where as with the stock turbo peak torque (and hence where knock usually occurs) is around 4k

Edited by Rolls

I bought into Nistune since I wanted to have data logging and the ability to map

via a connected PC with all the data presented nicely.

I do map myself, but if you're not into that kind of stuff you might consider the PFC.

Knock detection display is still under development with Nistune, so if you want some flashing lights

at knock events you better go for the PFC.

Also the Z32 ECU is not directly a plug in ..

The ECU printed circuit board has to be slightly changed.

So for a tuner the PFC is probably the easier option (as for installation)

Yeah do not trust the knock sensors, I had audible knocking that was not picked up with them. From talking to pete he is in the mind that due to overwhelming engine noise above ~5k the knock sensors increase the threshold massively and basically ignore knock, hence if peak torque is above 5k then it will probably ignore knock, where as with the stock turbo peak torque (and hence where knock usually occurs) is around 4k

You don't have to rewire the firing order ...

That was a misconception and has been corrected in the Nistune documentation.

If you use a Z32 ECU, it can do the VCT already and you just have to rewire the outputs for the different firing order. They are otherwise all almost the same ECU.

Edited by Torques

I'm a tuner, I do powerfcs, Vipec, and Link.

Played with a nistune, it is by far the best on a budget, and just as capable as the powerfc, if not more capable.

The others are for higher performance applications.

Correct.

A few things like fuel temp sensor needs to be changed inside the z32 ecu.

Ill be doing a z32ecu to rb25 on my new 32gtst drifter.

Just need to find an ecu for cheap.

You can get them from the states pretty cheap. I paid ~US$50 + Postage.

have you got a link at all??

That was second hand (of course) and was through eBay and was 18 months ago so no link but i'll have a look now. There were a number at that price back then.

EDIT!! Here's one close to that price,

http://www.ebay.com.au/itm/1990-NISSAN-300ZX-ECU-Engine-Computer-A18-A68-MB1-/170669745331?pt=Motors_Car_Truck_Parts_Accessories&hash=item27bcb5a4b3

Edited by D_Stirls

What are some stand out features of the D-Jetro that make it better than a nistune for tuning? and have you personally used both to determine these differences?

By what I've read, the MAP sensor doesn't rely on air flow but it functions via air pressure which can lead to better response and power output once tuned correctly. D-Jetro also has launch control, fuel / ignition cut, anti-lag, NOS, etc which are some features you may or may not use.

I was going to take this path, but I wasn't aiming for high power so based on my findings and having a NIStune setup, the NIStune is the best bang for buck. Hit up a few searches and this will also confirm what I've just typed.

Power FC is 20 x 20 and NIStune is a 16 x 16 resolution so if it's a high RPM revving monster then PFC should be considered.

I remember reading that NIStune is tuned cell by cell at 500 RPM intervals, think it was ns.com though so take that with a grain of salt.

By what I've read, the MAP sensor doesn't rely on air flow but it functions via air pressure which can lead to better response and power output once tuned correctly. D-Jetro also has launch control, fuel / ignition cut, anti-lag, NOS, etc which are some features you may or may not use.

I was going to take this path, but I wasn't aiming for high power so based on my findings and having a NIStune setup, the NIStune is the best bang for buck. Hit up a few searches and this will also confirm what I've just typed.

Power FC is 20 x 20 and NIStune is a 16 x 16 resolution so if it's a high RPM revving monster then PFC should be considered.

I remember reading that NIStune is tuned cell by cell at 500 RPM intervals, think it was ns.com though so take that with a grain of salt.

Even though the PFC has more cells to adjust the standard ECU calculates/interpolates better between them. I think the new HPI covered this subject come to think of it. The standard ECU takes TPS into the load calculation. Not sure if all PFC's do that? So if you got your cells as smooth as the PFC with the Nistune then is should calculate the load points better under dynamic conditions. In saying that I don't know if you can adjust the load points, ie if you can't what happens once you go above the standard redline?

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

    • I would just put EBC back on the "I would not use their stuff" pile and move on.
    • Can I suggest you try EBC directly again and link them to as many competitor catalogues as you can to show their listing is incorrect, eg https://dba.com.au/product/front-4000-series-hd-brake-rotor-dba42304/ If you have access to an R33 GTST VIN and your VIN, you could also use a Nissan Parts lookup like Amayama to show them the part number is different between 33 GTST and 34 GTT which may get their attention
    • So i got reply from EBC and they just this site where you can clearly see those 296mm fronts on R34 GTT. I send them photos and "quotes" that 296mm are not for 34 GTT and they are too small. But it will be very hard to return them cuz nobody here knows 100% and they just copy those EBC catalogue :-D https://ebcbrakesdirect.com/automotive/nissan/skyline-r34
    • Hi, is the HKS  Tower Bar still available ? negotiable ? 🤔
    • From there, it is really just test and assemble. Plug the adapter cables from the unit into the back of the screen, then the other side to the car harness. Don't forget all the other plugs too! Run the cables behind the unit and screw it back into place (4 screws) and you should now have 3 cables to run from the top screen to the android unit. I ran them along the DS of the other AV units in the gap between their backets and the console, and used some corrugated tubing on the sharp edges of the bracket so the wires were safe. Plug the centre console and lower screen in temporarily and turn the car to ACC, the AV should fire up as normal. Hold the back button for 3 sec and Android should appear on the top screen. You need to set the input to Aux for audio (more on that later). I put the unit under the AC duct in the centre console, with the wifi antenna on top of the AC duct near the shifter, the bluetooth antenna on the AC duct under the centre console The GPS unit on top of the DS to AC duct; they all seem to work OK there are are out of the way. Neat cable routing is a pain. For the drive recorder I mounted it near the rear view mirror and run the cable in the headlining, across the a pillar and then down the inside of the a pillar seal to the DS lower dash. From there it goes across and to one USB input for the unit. The second USB input is attached to the ECUtec OBD dongle and the 3rd goes to the USB bulkhead connected I added in the centre console. This is how the centre console looks "tidied" up Note I didn't install the provided speaker, didn't use the 2.5mm IPod in line or the piggyback loom for the Ipod or change any DIP switches; they seem to only be required if you need to use the Ipod input rather than the AUX input. That's it, install done, I'll follow up with a separate post on how the unit works, but in summary it retains all factory functions and inputs (so I still use my phone to the car for calls), reverse still works like factory etc.
×
×
  • Create New...