Just reviewing a log I did of a highway cruse, and 2 things caught my attention, one spot where my secondary fuel injectors were open for 33ms along with 12ms for my primaries, and one spot where my leading and trailing plugs were at -30 timing. Both at different times.

Where my fuel injectors opened up was right after closing the throttle, at time 37.066s into the attached log. The ignition went from 18BTDC to 30BTDC then to 21ATDC in 2 frames at 337.087s into the log. this was just after a light throttle application at 1800RPM, just before this, I recorded a pump value of 16.9, which seems huge too. In this location, my fuel injector opening time is normal at around the 3ms time, secondaries stayed closed.

What causes these erratic readings? I would like to know why my fuel injectors just opened up a huge amount at the wrong time. I am also worried that having a spark event so retarded at a non idle rpm could ignite the chamber in the compression stage, causing major issues.

Engine is a Turbo II engine, no turbo right now, running S4 TII rotors, 3mm apex seals, S5 housings, street ported S4 irons. FC igniton, FC CAS, FC 460cc non turbo primary and secondary injectors, stock FC plugs.

I have just tried running a larger than normal amount of negative spark split, have been reading up on it, and I like the results, since I have the lowest compression ratio rotors, and no turbo, its the safest time to try it.

 

You are hitting decel fuel cut. It is located in the power cut section. If you dont want to use it set it above your rev limiter.

Thanks,

Shawn Christenson

 

Its set to come on at 8800RPM, and come off at 8000RPM. My rev limit is 7400RPM.

 

Shawn. Think before posting. OR AT LEAST LOOK AT THE LOG AND FILE. For that matter what he described is the exact opposite of a deceleration fuel cut, which wasn't turned on.

This is odd. I wish there was a way to play back the log on the ECU file such that you could watch the calculation trace page and see exactly what fueling trims went into this, but to my knowledge there isn't. Is there any sort of deceleration enrichment feature in Eugene that may be causing this fueling issue?

As for the ignition jumping erratically, I would look into the Transient Ign. Advance Gain and Maximum Transient Advance/Retard settings. These have to do with the ECU applying an sharp ignition trim when a transient throttle even is sensed and I can imagine your gain is likely too high and causing the ignition to be erratic and jump like that at sharp throttle.

I'll spend more time with the log this afternoon and see if I can't figure out why the pri/sec fueling split that way.

Skeese

 

Thanks Skeese, let me know if you find anything. I have been tuning and making log files, I have changed a bunch of things since the map above, specifically, I finally found an OEM S4 IAT sensor resistance values, and 460CC Low impedance injector dead times.

As for the issues above, I cant see any reason to do those 2 things, could it be an error logging? I am using Eugene V1.52 I think.

I have noticed recently, that I have been generating a bunch of dud log files. Eugene will say logging, everything goes good, but when I go to open the file with MegaLogViewer HD, it says "Log file contains no data or is not recognised", I notice all of the files that do this are 516 bytes in size.

 

I haven't had a chance to go through it yet, but forwarded it to my work email so I'll check it out tomorrow at lunch if I get a break. I don't think dead time differences would be substantial enough to cause your secondary's to be spraying triple the ms value of your primaries when primary staging is supposed to peak and hold at 97%. I still don't understand what is going on there...

You aren't the first person to have logging issues with this ECU. Part of the reason I moved away from it was that Wari kept dropping communication with my ECU and I kept having this huge log gaps where the log would for instance skip from 135.XXX seconds to 155.XXX seconds where I'd conveniently lose a chunk of data, that more often that not seemed to be the data I needed. Seems like a sketchy gamble with a bunch of expensive parts to me...

I changed cables, changed laptops, tried V13-V15, reloaded all the software/firmware and at one point even made an entire new replica tune file off from "save as" version of the basemap to eliminate a file corruption error...same ****. Sketchy part is without a log you are left to wonder...is it just you being left out on the data? or is the ECU running blind too?

Then they moved to Eugene and left Wari half broken and full of glitches. Sad to hear Eugene has the same logging issues. I don't know if Eugene logs to something other than a .csv file or in a different format, but know I've loaded Eugene logs into MLV before. If its something that works right sometimes and not others....that would sketch me out. Something hardware/software isn't right.

Skeese

 

I've noticed the same thing on my old laptop. I ended up reloading my laptop as it isn't used for anything else now. And the issue went away. Double check your usb drivers also. May want to see if there is an update to the firmware/drivers.