Nistune Forums

Hi all, I have an issue with a mate's car that is running very very very rich when I hit the gaz , the cars slows down, with very high injection time that drop after that and when the injector comes good the car goes fine until red line normaly

I started to see the increase fuel VS TPS voltage table but It has no influence at all and it seems that it is not read too ...

maybe wrong adress for this table ?

here is the log with the problem and of course the .bin

what is the rest of the setup of the car ?
like, what turbo, what afm, front mount intercooler or the stock one ? that kind of stuff

TOMEI Cams 270° 8.8mm
SARD 800CC injectors
Z32 AFM
GT3076R garrett turbo T3 flange A/R .63

and off course all of the normal stuff for a 500hp engine ....

the problem occurs only if the gaz pedal is hit fast, in 3rd 4th 5th gear it is ok but in 2nd and in 1st it occurs at any time

I have load your BIN and CSV file in nistune,
It seems that your ecu keep using the knock timing map,
Around 1:56 in the log file,
The primary ignition timing is 27,28,29
The knock ignition timing is 18,19,20
In between 1:53 to 1:59, what gear and boost pressure are you running ?
What fuel press ?

I've been tuning a CA18DET with similar set up,
27X In/Ex Cam
Sard 800cc top feed injectors (light green)
fuel press 3.5bar at idle and 4 bar on boost
Z32 AFM
TD06-25G

Although the official latency setting from SARD is 1.1 millisecond,
I've tried different K Constant and Latency combination,
The values are between
K Constant 240 Latency 880
K Constant 270 Latency 600
With the same "increase fuel" table
When the setting is step by step changing from 240/880 to 270/600
The A/F reading while hit the gas padle will goes richer and richer.
After the throttle pump effect, the A/F readings of reving up to red line is the same.

Did you try different K Constant and Latency combination ?
Did you try to check your Latency with all 0 in the Min TPulse witdth ?

Hi all !

After many many things tried, the probleme was allways there ...

the car has a MECD 003 ECU ( 36F00) with a type 1 board 36F00
whe tried another ECU : MECD 009 ( 44F07 ) with a 44F07 board and we wrote the same .bin on it, and the problem is not there ..


then we tried the 36f00 ecu with the 44f07 nistune board, and it works fine too ...

so maybe a compatibility problem with the 36f00 board ?

generally with CA18s I do not like swapping images between 36F00 (JDM), 39F00 (EDM) and 44Fxx ECUs becaue there are differences between the vehicles and ROM images. I know that O2 feedback was one factor and there were several other differences between models

Either use in that ECU as it seems to work the other way around, or you will need to reprogram the board

how can I reprogram the board ?

what is different beetween 36f00 and 44f07 ?

We tried the 36f00 board in the 44f07 ecu and it is making the same problem.

what will be the more simple ? reprogram the board or send it to you ?

Base Image Programmer required to reprogram boards. Probably easiest to send back to me and I'll reflash and sent it back

I don't have the base image programmer ... so I will send it back to you .

do you think the ENT file is just wrong ? or something else ?

I would start with ENT file wrong and then work from there. get the matching part number and it may all work properly again. We have seen too many issues with mismatch part numbers where 23710-XXXYZ where the XXX is different and causes issues. The YZ part doesnt matter so much unless auto/manual differences matter

in australia what type of CA18 ECU do you have ? 36F00 ?

What can cause this type of problem in the NET file ? I don't know what is in this files ?

We import the JDM variant of these vehicles (so the 36Fxx ecus)

Using a european image in a JDM variant can cause these issues. Problem is not the ENT file itself, but using the wrong part number

wrong part number ? of the ECU or of the board ? I don't understand what can cause this problem ... in fact I don't know what is the ENT file for.

My mate is sending you back the board.

Mismatch between part number in EPROM/Nistune board(ENT preloaded) and the ECU hardware part number

Ie. if the ECU is 36Fxx and you run 39Fxx chip/Nistune board in it then there could potentially be issues due to part number mismatch

Its not a Nistune specfiic thing, its running Nissan ROM image for one vehicle (eg JDM) in hardware for different vehicle (eg EDM)