Earlier this week a friend and I went out and fiddled around datalogging in with my CA. (Didn't have a wideband yet so that's absent.) Anyway, we did a 4th gear pull from a 50km/h roll and I'm getting injector pulswidths that spike and/or don't match up with the cells the ECU is accessing in the fuel table.
I'm unable to discern any cause-effect relationship for the spiking as there doesn't seem to be any corresponding change with any of the other sensors.
Also, my pulsewidths are a helluva lot shorter under higher load than what's on the fuel tables, yet the engine feels like it's running great.
Would it still be running in closed loop down lower? But even then the O2 sensor doesn't budge from 0.3volts.
Any ideas?
Thanks,
Kenji
Pulswidth spiking, i r confused
Moderator: Matt
Pulswidth spiking, i r confused
- Attachments
-
- NIStune_2008-06-15_2036_50.csv
- (21.3 KiB) Downloaded 222 times
Pulsewidth spikes are probably just load enrichment, dont want any flat spots under acceleration.
Actual pulsewidths will never match exactly whats on the fuel tables. Fuel table settings are simply a starting point, ecu then looks at a myriad of other inputs and then TRIMS the base settings to end up with actual pulsewidths. Engine temp, air flow (which includes air density changes through air temps) and so on.
I would advise getting a wide band asap.
Actual pulsewidths will never match exactly whats on the fuel tables. Fuel table settings are simply a starting point, ecu then looks at a myriad of other inputs and then TRIMS the base settings to end up with actual pulsewidths. Engine temp, air flow (which includes air density changes through air temps) and so on.
I would advise getting a wide band asap.
Try using the S13_CA18_256_E_fix.adr file in the misc directory and see if this fixes the injection reporting guage at all.
Earlier boards had the wrong memory address programmed in the board, so we put together this address file to enable an override with the correct injection (verified by measurement on the scope)
Earlier boards had the wrong memory address programmed in the board, so we put together this address file to enable an override with the correct injection (verified by measurement on the scope)
Well the pulsewidth spiking I was seeing seems to be normal behaviour. Though I may have mitigated it somewhat by replacing the FPR vac line that may have begun to leak. At any rate my AFR's are looking good. I had no idea the stock maps were so conservative though, 9.5 to 10:1 AFR's at the top end? Good grief, that's piles of room for improvement.
I'm pumped to get started.
I'm pumped to get started.