Jump to content
SAU Community

Recommended Posts

G'day,

Car is R34 GTT Manual with nistune, been tuned and runs perfectly/idles well. The car doesnt ever stall itself but if i accidentally stall it (new clutch :P ) then when i try start it again it takes a good while to start, just splutters, black smoke comes out of the exhaust, meaning the fuel system is fine, but it doesnt start up.

I switch it on and off a few times then try to restart but it just cranks and chucks out black smoke. After a few tries it finally does start but barely but once its started there is no idle issue, or anything.

Please assist guys :)

Thanks

sometimes with R34 nistune there is a bad read / write and a particular address in the ecu we cannot access to do with crank enrich gets corrupt. Take it back to the tuner, it probably just needs the factory bin relaoded and the tune imported back onto the base.

had this issue with a subaru.

if i stalled my imoboliser would cut off the fuel so the engine would crank. but not start. after a couple of mins would have to lock and unlock the car then it would start....

not saying its your problem, but thought i would try and help!

sometimes with R34 nistune there is a bad read / write and a particular address in the ecu we cannot access to do with crank enrich gets corrupt. Take it back to the tuner, it probably just needs the factory bin relaoded and the tune imported back onto the base.

or its this.

lol.

sometimes with R34 nistune there is a bad read / write and a particular address in the ecu we cannot access to do with crank enrich gets corrupt. Take it back to the tuner, it probably just needs the factory bin relaoded and the tune imported back onto the base.

Had this exact b problem with mine. Tuner finished the tune on the dyno, shut the car down. Un did the straps went to start it and fuel poured out the exhaust. 45Mins later got it going again.

Appears as it might be a Nistune issue, so its best to contact us directly about it for an immediate response and resolution. I've been alerted to this one by Trent so can fill in on this forum. Please email me directly info[at]nistune.com to follow up on this

There was a small batch of Type 4 boards back in May which we have found glitched during programming when flashing the CPLD Xilinx chips on the board.

With the S13 Type-X setup the board would not allow writing, but on ER34 setup the glitch caused intermittent ECU power up issues. It took over a month to identify the problem due to being intermittent and finding it was more than a single board affected. After this we contacted various individuals and tuners with those vehicles to reflash the CPLDs

It could be the case that this problem exists with your board. I can arrange an exchange over board if you contact me directly

sometimes with R34 nistune there is a bad read / write and a particular address in the ecu we cannot access to do with crank enrich gets corrupt. Take it back to the tuner, it probably just needs the factory bin relaoded and the tune imported back onto the base.

I have not seen this before. If you suspect this to be the case please put the board in programmer mode, and read out the board using the Base Image Programmer (Save button to create ENT). Email the ENT file here and I can compare against the matching factory tune to see which maps were changed. So far I have never seen any corruption in Type 2 - 4 boards. The only time I seen it occur is in the vector tables (startup code on the ECU) on a Type 1 board which was 'burned' into the board during tuning after the corruption occurred.

Edited by darkhalf

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