E-manage ultimate tuning on Blitz s/c

[GTSspeedfreak]

So I literally spent 10 hours of tuning with my tuner on the EMU with the map sensor. I can definitley say that the map sensor on the emu responds better to a boosted car. My Blitz supercharged car revs up so much faster and I can definitely feel more power. I am awaiting a dyno in the next week or two. Anywahys, we managed to tune out the hesitation off idle when the car is warmed up. When the car is cold the car still hesitates....I have rc injectors.

We took the LTFT's from 20% down to about 10% at partial throttle and the WOT LTFT's from 5% to about 4%. However, we are still struggling with this as the LTFT's jump around a lot from 14% to like 7% at partial throttle. Tuning these LTFT's out is literally a full time job.

The cel for P0300 is still coming on even when the LTFT's are as low as 1-2%.
I do not think the LTFT's is causing the engine to misfire
I have changed virtually everything on the car that can be related to an engine misfire which leads me to believe that my car does not like the EMU.

Anyways my question is how long does it take for the stock computer to start overriding the emanage tune at WOT and partial throttle when LTFT's are sitting around 10% Is it a couple of days or is it after like 1 month or is it after like 6 months.

My tuner was thinking of finishing this off on the dyno and then re-uploading this tune as well as resetting the stock ecu every month or so. Let me know what you guys think

[jlitman]

Read my tuning sticky on a fast, reliable way to do this. Also, I would use the target AFR map to help keep your open loop AFR's more stable.

The ECU won't override anything -- it will apply the one trim you see carried into open loop, in your case 4%, which is nominal. If you can further minimize the other trims, it shouldn't change much if at all. Just check it periodically.

Also, you may want to replace the primary 02 sensor -- you tend to see bigger fuel trims when the O2 sensor is getting a bit laggy.

This misfire could be caused by a lot of things and may or may not have anything to do with the EMU. A few had a faulty ignition chip that caused misfires, but it could easily be something else.

For cold enrichment, have your OBDII datalog recording as soon as you start the car. Take note of the engine coolant temp while the car is in open loop at start up (note when STFT's come on line, that's how you can tell you are in closed loop!).

A few degrees below that temp, you can add fuel, and it shouldn't adversely affect anything.

Actually, to be more accurate, you are in open loop for up to 12 seconds while the ECU allows the O2 sensor to heat up, but you can't add fuel according to time, so it's easier to datalog the temp you're at on a cold start, and just add fuel according to that.

[GTSspeedfreak]

O.K. thanks for the advice.

This is getting frustrating because I am doing the datalogging just as you mention in your sticky. However, just when you think you have the fuel trims tuned out, all of a sudden it jumps to 20%! For example, tonight I am driving and I notice WOT is 5.5% while partial throttle is 20%.

I might have to change the O2 sensor just like you mentioned.

Anyways, I know you mentioned that the ecu does not overide but I do notice that it really does not take long before my driveability gets bad, partial throttle seems to change much quicker than WOT, I find that usually within a week to 2 weeks after a street tune I get the hesitation again.

I am going to try using the target AFR map.....I never did use that before and I think that should at least take care of the open loop afr.

I will let you know how the dyno goes since you seem to be the only one who is interested in tuning with the emanage ultimate. I have not given up on the emu as of yet because your advice and stickies do seem sound.

[jlitman]

^^^ Are you tracing back each LTFT to a specific cell in the EMU inj map? You do realize that there is a LTFT for every cell -- i.e., MULTIPLE fuel trims.

The only single fuel trim is the one carried into open loop. I nclosed loop there are many, many fuel trims and each one has to be dialed out individualy.

Are you resetting the ECU in between tuning sessions or at least every other tuning session?

The LTFT's associated with each cell will change a small amount due to things like weather conditions, but in general, if you see a a +5% fuel trim associated with a given EMU inj map load cell at a given RPM it should not suddenly change to -20%!

If the changes to LTFT's associated with a specific map cell are chaging erraticly it may mean either (1) you have some uneccesary airflow correction dialed in at part throttle throwing things off in unpredictable ways, (2) your MAF is in need of some cleaning (getting erratic airflow voltage readings) or (3) your O2 sensor is seriously laggy, and the ECU is overcorrecting sometimes in an attempt to bring the car to stoich in closed loop.

Zero out the airflow map in the cells associatd with part throttle (i.e., low load), clean the MAF, reset the ECU and start again.

Eventually you should be able to get all LTFT's < +/-5% (at worst, < +/- 10%, which isn't great, but acceptable), and even after an ECU reset, you shouldn't see a huge fluctuation in the LTFT's associated with each cell in the EMU inj map.

Major weather changes might require a retune (+/- 20* F) and because there will always be a little variablity in the LTFT carried into open loop, I recommend using the AFR target map. My advice is to get it dialed in with rapid correction (20 msec) and relatively small changes (~3%) to keep the tune where you want it even if the weather or the FT changes.

Oh, and to clarify you are using the EMU to "override" the fuel trims. If the ECU adds fuel, you counter by adding fuel in a corresponding map cell, if the ECU subtracts fuel, you counter by subtracting fuel in a corresponding map cell. The ECU won't trim fuel if YOU do it in the correct amount and map location first.

The ECU doesn't care about your EMU (or know it's even installed). All it cares about is that it sees .45 volts on the primary O2 sensor in closed loop. The STFT's reflect immediate corrections to fueling to try and hit .45 v (it always under or overshoots, so the STFT's will constantly fluctuate); the LTFT's are an aggregation of the STFT's, and more stable so the LTFT's are what you adjust your tune around.

One other suggestion -- tune the injector accelleration and ign acceleration map to improve drivability.

[GTSspeedfreak]

For the P0300 code you mentioned that it could be a faulty emanage......

"This misfire could be caused by a lot of things and may or may not have anything to do with the EMU. A few had a faulty ignition chip that caused misfires, but it could easily be something else."




I do know that I had the P0300 problem fixed for about a year. Then I installed the ultimate emanage and left it at zero tune for about 1-2months. The cel P0300 never came on at that time. As soon as I had the emanage tuned for a N/A engine the code came on about 2-3 days later.

My question is, if it is a faulty emanage would the code not come on when the emanage was installed even with a zero tune?

thanks

[jlitman]

For the P0300 code you mentioned that it could be a faulty emanage......

"This misfire could be caused by a lot of things and may or may not have anything to do with the EMU. A few had a faulty ignition chip that caused misfires, but it could easily be something else."




I do know that I had the P0300 problem fixed for about a year. Then I installed the ultimate emanage and left it at zero tune for about 1-2months. The cel P0300 never came on at that time. As soon as I had the emanage tuned for a N/A engine the code came on about 2-3 days later.

My question is, if it is a faulty emanage would the code not come on when the emanage was installed even with a zero tune?

thanks
I'm not sure... could be a problem with the ignition harness or the faulty ignition chip like I was describing. You could always open he case and check it out

See further here http://www.mohdparts.com/emanage/emu_missing_chip/index.html