Jump to content
SAU Community

Recommended Posts

What's this talk about not doing z32 with your Nistune?

I have a Nistune with no Z32 presently and was about to get one.....

You are starting to worry me...

Regards,

Darren

I always get data corruption issues on the test car, and with the new illustration car it does all sort of random strange things and knock map is not responding to the tune. The test car goes onto the dyno every week so the data in it gets changed quite so often, I'm not sure if that causes the issue. I believe the boards or what ever the ecu its originally made for is ok. The Z32 ECU and nistune chip on R33GTST just didn't work probably on my cars. Which it's also the reason trent stopped doing those.

So are you saying that Trent won't tune my car now that I have Nistune & an r33 on a z32 ecu?

Nooooooo.....

Darren

He did say he will never do another one. Do makes sense after all those stuffing around and no results. Talk to him nicely and see what he says. :rolleyes:

Sorry, whats this prototyoe pu highflow?? The 230kw one, or?

The 230kw one is referred to as the ATR43G1.

The other one is the SS1 PU prototype, which has also been referred to as the SS1.5. I prefer the SS1.5 as its easier to say and type :)

Correct me if I am wrong Tao

I always get data corruption issues on the test car

How do you know for sure its data corruption? Did you read back the maps and they were all spiky or did the ECU stop running? These are the indicators that something is corrupt, otherwise there is a different issue. I have to have a chat to Trent about this one

data in it gets changed quite so often, I'm not sure if that causes the issue.

Shouldnt cause the issue. If unsure read back the maps which were originally in it and compare what was saved on your laptop after burning the tune

The Z32 ECU and nistune chip on R33GTST just didn't work probably on my cars. Which it's also the reason trent stopped doing those.

The main problem with using a Z32 ECU on an RB25DET is the knock sensors. Z32 ECUs use the doughnut SR20 style knock sensors and RB25DET use the hose type knock sensors. I suspect there is more sensitivity and your ECU is jumping to knock maps

We normally recommend disabling knock feedback during tuning for this reason. Also Nistune software will now indicate which maps it is running from at any time. Boards dont lose their tune once a burn is performed as its stored to EEPROM.

Just a follow up. Found out that Pete did the install and was supplied with a 16 bit Z32 ECU

We officially only support (and have tested base maps) for the 8 bit models for RB25. Part numbers listed in our documents for 8 bit models should assist with finding correct units

We have not used 16 bit models so haven't got experience with these but from what Trent indicated there are issues with these ones as well as a glitch found with VE map RPM tracing (fixed in 0.10.9 software release)

spiky or did the ECU stop running.

^^^^^

Yes

Well I'm not a computer gig, I've emailed you all the issues I've experienced as a user, I guess trent will be happy to go into details when he's free.

I'm in the process of getting a LinkG4 will post up some feedbacks once they are installed and tuned.

Interesting. Best thing to do then is read back the tune before pressing the 'burn' button. I'm in the process of putting checksumming over the ECU code to prevent 'burning' with bad checksums. However is taking some time to implement since the ECU doesnt like being paused for too long (ie calculating the checksum takes time)

Well, looking forward to see you guys making some thing work Properly with R33 GTSTs in the near future.

Update:

This is for a set of GTR turbos that we've asked to match port their housings and manifolds then do a high flow. We will be using ATR43G1 profiles in those with FNT turbine modifications, They are expected to make some where close to 350awkws at full capacity as a twin on 98 fuel.

Photos in comparison:

Those are photo of stock GTR manifolds:

gtrextmanifolds.jpg

Photo of the pair that we've ported:

manifolds.JPG

Photo of factory turbine housings:

stockturbinehousing2.jpg

Turbine housings we've match ported:

turbinehousing1.JPG

Profiled turbine housing to suit larger turbine wheel:

turbinehousing2.JPG

Machined and enlarged wastegate port:

wastegate.JPG

Hello there,

I use Nistune with the Z32 ECU and it as never failed me.

The 16-Bit-Z32-ECU is not recommended by Nistune (that's why I bought the 8-Bit back then)

(Though I know people using the 16-Bit-Version, and there were never any problems with data corruption)

Also I change my settings (tune) quite frequently, and this has never been an issue either.

The only problem I ever experienced was due to a bad Consult-To-USB-Cable which caused connection issues and rom-images

not being read correctly. I then ordered a Nistune-Cable, and it works very well.

Maybe your ECU is 'damaged', (lose socket, cold solder, or ...)

?

Well, looking forward to see you guys making some thing work Properly with R33 GTSTs in the near future.

Edited by Torques

They didn't work properly on my cars, the ECUs on them are fine. I don't want to discuss those issues publically, and I believe Nistune is working towards solving those glitches in their systems.

They didn't work properly on my cars, the ECUs on them are fine. I don't want to discuss those issues publically, and I believe Nistune is working towards solving those glitches in their systems.

But don't you have the 16 bit version, not the 8 bit one?

Hello there,

I use Nistune with the Z32 ECU and it as never failed me.

The 16-Bit-Z32-ECU is not recommended by Nistune (that's why I bought the 8-Bit back then)

(Though I know people using the 16-Bit-Version, and there were never any problems with data corruption)

Also I change my settings (tune) quite frequently, and this has never been an issue either.

The only problem I ever experienced was due to a bad Consult-To-USB-Cable which caused connection issues and rom-images

not being read correctly. I then ordered a Nistune-Cable, and it works very well.

Maybe your ECU is 'damaged', (lose socket, cold solder, or ...)

?

Lets get this straight it is not a nistune issue as much as an incompatibility between some Z32 ecu's and the R33 car itself, we have done about 20 or so (upto 400rwkw) and of those 20 about 6 give major headaches (r32 nistuned ecu worked so its not the cars), since i cannot differentiate the exact problems between ecu serials and r33 model series1, 2 or 2.5 i have stopped doing them, Stao's latest issues were the 16bit ecu.

Nistune is a great system and is generally our Number 1 recommendation for S13, S15 and R32 / R34's.... just not R33 with ecu conversions :P

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

    • Look for broken wire or bad connector at the motor. Might not be it, but is worth starting there, as it is easy.
    • Hi everyone, I’m having an issue with my R32 GT-R. Sometimes, when the car goes over a bump or experiences some vibration, the 4WD warning light comes on the dashboard. When I check the code from the control unit in the trunk, it shows Code 19 – ETS Motor. However, everything seems to be working fine — if I turn off the engine and restart the car, the light goes away and everything functions normally. Has anyone experienced this before? Where should I start troubleshooting this issue? Thanks in advance!
    • I'm back from the dyno - again! I went looking for someone who knew LS's and had a roller dyno, to see how it shaped up compared to everything else and confirm the powerband really is peaking where Mr Mamo says it should. TLDR: The dyno result I got this time definitely had the shape of how it feels on the road and finally 'makes sense'. Also we had a bit more time to play with timing on the dyno, it turns out the common practice in LS is to lower the timing around peak torque and restore it to max after. So given a car was on the dyno and mostly dialled in already, it was time for tweaking. Luis at APS is definitely knowledgable when it came to this and had overlays ready to go and was happy to share. If you map out your cylinder airmass you start seeing graphs that look a LOT like the engine's torque curve. The good thing also is if you map out your timing curve when you're avoiding knock... this curve very much looks like the inverse of the airmass curve. The result? Well it's another 10.7kw/14hp kw from where I drove it in at. Pretty much everywhere, too. As to how much this car actually makes in Hub Dyno numbers, American Dyno numbers, or Mainline dyno numbers, I say I don't know and it's gone up ~25kw since I started tinkering lol. It IS interesting how the shorter ratio gears I have aren't scaled right on this dyno - 6840RPM is 199KMH, not 175KMH. I have also seen other printouts here with cars with less mods at much higher "kmh" for their RPM due Commodores having 3.45's or longer (!) rear diff ratios maxing out 4th gear which is the 1:1 gear on the T56. Does this matter? No, not really. The real answer is go to the strip and see what it traps, but: I guess I should have gone last Sunday...
    • 310mm rotors will be avilable from Australia, Japan, and probably a few other places. Nothing for the front can be put on the back.
    • The filter only filters down to a specific size. Add to that, the filter is AFTER the pump. So it means everything starts breaking your pump even if its being filtered out.
×
×
  • Create New...