How is injector duration (ms) calculated?
Moderator: Matt
If you can send through a log of that I can play it back and have a look
Got another CA18 ECU here now with knock detection board working on it... so can have a look at knocking problems too
The Injection value, I have used reverse engineering and routine comparison against the R32 skyline again for this value. It is what the ECU is reporting for this value, and we do no additional calculation on it
What I can do (raised a CR on this) is look at the R32 and see if the pulsewidth on my scope matches that of the reported value. Then plug the CA18 ECU in and see if it does the same. Its the best way to check and measure this stuff
Also with the % adjustment.... I was thinking I can do this... using the current K value, mulitply by 1/ X% will give you a new K value which you can up/down adjust to and make changes in realtime so you can hold a button down and hear the engine change. item added for upcoming version
Got another CA18 ECU here now with knock detection board working on it... so can have a look at knocking problems too
The Injection value, I have used reverse engineering and routine comparison against the R32 skyline again for this value. It is what the ECU is reporting for this value, and we do no additional calculation on it
What I can do (raised a CR on this) is look at the R32 and see if the pulsewidth on my scope matches that of the reported value. Then plug the CA18 ECU in and see if it does the same. Its the best way to check and measure this stuff
Also with the % adjustment.... I was thinking I can do this... using the current K value, mulitply by 1/ X% will give you a new K value which you can up/down adjust to and make changes in realtime so you can hold a button down and hear the engine change. item added for upcoming version
Here is a log, you will see that ~6 times during the 2nd gear run injection time changes from ~10ms to ~5ms and back
- Attachments
-
- nistune_2007-06-28_0158_02.csv
- (23.13 KiB) Downloaded 128 times
trying to look for correlation. seems to follow TP but just goes really rich some of the times (like spikes)
perhaps O2 sensor feedback related? i also draw O2 against it and was looking for correlation. something is making it richer
this log has some extra empty columns in it. had to remove those from the CSV file to get it working. fixed in latest NIStune version when you record now
perhaps O2 sensor feedback related? i also draw O2 against it and was looking for correlation. something is making it richer
this log has some extra empty columns in it. had to remove those from the CSV file to get it working. fixed in latest NIStune version when you record now
- Attachments
-
- ca18_inj_investigation.JPG
- log playback
- (165.58 KiB) Downloaded 2919 times
this requires a serial number to install...E-manage ultimate has the nicest way about it. Software is freely available here: http://www.mohdparts.com/emanage/pc/ult ... 9_full.zip
O2 area is the left part, but here all action happens in the 1-2 right columnsMatt wrote:trying to look for correlation. seems to follow TP but just goes really rich some of the times (like spikes)
perhaps O2 sensor feedback related? i also draw O2 against it and was looking for correlation. something is making it richer
this log has some extra empty columns in it. had to remove those from the CSV file to get it working. fixed in latest NIStune version when you record now
I just compared logs from 2nd gear and 4th gear pulls. Resume:
1st switchover appears to be dependent on AFM reaching 4.9-5V, because it happens at differerent revs and TP values
2nd switchover happens at ~6000 at both cases, but MAF is maxed out, respectively TP values are the same at this point, so can't really tell what is the reason.
Investigate item for CA18 injection resolved
Before I do that ... see if there is a way I can make the consult table updateable in the firmware for future changes
10393 CA18 Injection not reflecting actual injection?
This will require a firmware update on the boards (ie send here for reprogramming)Current value X004D change to X1050 (LHS_INJECT_TIME_MSB)
Before I do that ... see if there is a way I can make the consult table updateable in the firmware for future changes
-
- Posts: 69
- Joined: Sat Jan 19, 2008 11:44 pm
- Location: toulouse FRANCE
Hi all ! have same problem on my CA18DET
AFM Z32, 550cc injectors GT2871R turbo
at 1.1bar of boost TP calculated is 88-90
the AFR expected is 11.5, my innocate mesure 11.5, so map is ok.
but nistune calculate a pulswidth of about 14ms and also a duty cycle at 7400rpm of 82% wich is surprisely high....
but consult mesure a pulsewidth of 8ms ( about 50% of duty at 7500rpm )
off course I prefer what is reported by the consult, but I would like to know wich one is the accurate value.
Is it possible to correct the values in the map if they are false ?
AFM Z32, 550cc injectors GT2871R turbo
at 1.1bar of boost TP calculated is 88-90
the AFR expected is 11.5, my innocate mesure 11.5, so map is ok.
but nistune calculate a pulswidth of about 14ms and also a duty cycle at 7400rpm of 82% wich is surprisely high....
but consult mesure a pulsewidth of 8ms ( about 50% of duty at 7500rpm )
off course I prefer what is reported by the consult, but I would like to know wich one is the accurate value.
Is it possible to correct the values in the map if they are false ?
-
- Posts: 69
- Joined: Sat Jan 19, 2008 11:44 pm
- Location: toulouse FRANCE
The fuel map in its raw form contains values 0 - 255 these translate to:
O2 FLAG OFF (< 128)
0 = 14.7:1 AFR .... 127 = 7.38:1 AFR
O2 FLAG ON (> 128)
128 = 29.4 AFR .... 191 = 14.82 AFR
192 = 14.7:1 AFR ... 255 = 9.55 AFR
Now these are target values for the ECU to inject based on current RPM/TP. We translate them to target AFR, duty cycle and pulsewidth
They are based around the following calculation
target pulsewidth = base pulsewidth (16.5ms max) * (filtered raw value/128) * TP column value
Changing scalers, Injection multiplier (K) will affect end calculations
Use the consult reported injection amount since I measure this out on the oscilloscope for the injector output to verify it. Latest NIStune versions will fix a problem the older CA18 boards which reported the wrong injection pulsewidth address (hence wrong values displaying)
O2 FLAG OFF (< 128)
0 = 14.7:1 AFR .... 127 = 7.38:1 AFR
O2 FLAG ON (> 128)
128 = 29.4 AFR .... 191 = 14.82 AFR
192 = 14.7:1 AFR ... 255 = 9.55 AFR
Now these are target values for the ECU to inject based on current RPM/TP. We translate them to target AFR, duty cycle and pulsewidth
They are based around the following calculation
target pulsewidth = base pulsewidth (16.5ms max) * (filtered raw value/128) * TP column value
Changing scalers, Injection multiplier (K) will affect end calculations
Use the consult reported injection amount since I measure this out on the oscilloscope for the injector output to verify it. Latest NIStune versions will fix a problem the older CA18 boards which reported the wrong injection pulsewidth address (hence wrong values displaying)