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

    • 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.
    • Place the new daughterboard in the case and mount it using the 3 small black rivets provided, and reconnect the 3 factory ribbon cables to the new board Then, use the 3 piggyback cables from the daughterboard into the factory board on top (there are stand offs in the case to keep them apart. and remember to reconnect the antenna and rear cover fan wires. 1 screw to hold the motherboard in place. Before closing the case, make a hole in the sticker covering a hole in the case and run the cable for the android unit into the plug there. The video forgot this step, so did I, so will you probably. Then redo the 4 screws on back, 2 each top and bottom, 3 each side and put the 2 brackets back on.....all ready to go and not that tricky really.      
    • Onto the android unit. You need to remove the top screen because there is a daughterboard to put inside the case. Each side vent pops out from clips; start at the bottom and carefully remove upwards (use a trim remover tool to avoid breaking anything). Then the lower screen and controls come out, 4 screws, a couple of clips (including 3 flimsy ones at the top) and 3 plugs on the rear. Then the upper screen, 4 screws and a bunch of plugs and she is out. From there, remove the mounting brackets (2 screws each), 4 screws on the rear, 2 screws top and bottom and 3 screws holding in the small plates on each side. When you remove the back cover (tight fit), watch out for the power cable for the fan, I removed it so I could put the back aside. The mainboard is held in by 1 screw in the middle, 1 aerial at the top and 3 ribbon cables. If you've ever done any laptop stuff the ribbon cables are OK to work with, just pop up the retainer and they slide out. If you are not familiar just grab a 12 year old from an iphone factory, they will know how it works The case should now look like this:
    • Switching the console was tricky. First there were 6 screws to remove, and also the little adapter loom and its screws had to come out. Also don't forget to remove the 2 screws holding the central locking receiver. Then there are 4 clips on either side....these were very tight in this case and needed careful persuading with a long flat screw driver....some force required but not enough to break them...this was probably the fiddliest part of the whole job. In my case I needed both the wiring loom and the central locking receiver module to swap across to the new one. That was it for the console, so "assembly is the reverse of disassembly"
×
×
  • Create New...