-= Ultimate Emanage Tuning Thread =-

[archangelcomp]

How can I tell if my FPR is getting overrun? I have an AEM AFPR with rob beck's adapter and an ek2 gauge.

[BlackStealth]

Originally Posted by archangelcomp

How can I tell if my FPR is getting overrun? I have an AEM AFPR with rob beck's adapter and an ek2 gauge.

I don't think your FPR is overrun since you're using an aftermarket FPR so the problem is some where else.

[Fourdoor]

I have read the thread, and seen that the recomendation to make lots of data logs with an OBD2 logger when stock is good for knowing what to shoot for when setting timing maps and such after you start making changes to the hardware of the engine.... do we have a good knowledge base on this that people are sharing or do we each and every one of us have to do this because nobody is sharing?

I am in the process of planning my first stage buildup, and the E-manage ultimate with boomslang harness, Inovate LC-1 wide band, and greddy injector simulator are part of my plans... does the greddy injector simulator fix the rich idle condition associated with the stage 3 installation (as the boomslang is set up)?

If we don't have a good data base on stock cars, I guess my first purchase should be an OBD2 logger of some kind.... any recomendations? My laptop has serial and USB ports available.

Thanks,

Keith

[BlackStealth]

Actually I recommend making a lot of datalogs using the emanage datalogger on stock injectors as captures at a much higher sampling rate than a OBDI/OBD2 datalogger, although it wouldn't hurt to have both if you already have it. If I still had stock 360cc injectors available to install, I'd reinstall them temporarily just to capture this data and share my findings. This thread is relatively young and I don't know if any new EMU owners had the opportunity to try and datalog stock injectors.

The greddy CEL adaptor is only there to satisfy the ECU injector test. When I had stage 3 wiring + greddy adaptor I had to lean it out at idle a bit.

I wouldn't bother purchasing an OBD2 datalogger as it won't reveal knock on our cars and captures samples way too slow.

[Fourdoor]

Originally Posted by BlackStealth

Actually I recommend making a lot of datalogs using the emanage datalogger on stock injectors as captures at a much higher sampling rate than a OBDI/OBD2 datalogger, although it wouldn't hurt to have both if you already have it. If I still had stock 360cc injectors available to install, I'd reinstall them temporarily just to capture this data and share my findings. This thread is relatively young and I don't know if any new EMU owners had the opportunity to try and datalog stock injectors.

The greddy CEL adaptor is only there to satisfy the ECU injector test. When I had stage 3 wiring + greddy adaptor I had to lean it out at idle a bit.

I wouldn't bother purchasing an OBD2 datalogger as it won't reveal knock on our cars and captures samples way too slow.

Any idea why the stage 3 wiring causes the rich at idle condition? I plan to do the E-manage with the wide band as my first modifications, and do plenty of data logging, and I would share my "bone stock" data logs with the list.... but if the stage 3 wiring throws off the tune at idle, will the data logs be valid for anyone using a lower level of wiring? And is it only at idle that this rich condition occurs?

About the data logging with the E-manage, is the information conveyed in the logs what the ECU thinks is going on, what the e-manage is telling the ECU is happening, or some combination of that information?

For example, if the stock ECU wants to run 10 deg of timing at a given load point, and you are using the E-manage to add 5 deg of timing at that given load point, does the log show 10 deg (what the ECU wants) 5 deg (what the E-manage is adding) or 15 deg (combo of ECU and E-manage)?

One last thing about the Boomslang harness, it has options for "air and water" "knock and water" "knock and air" or "dual knock" inputs. I assume (tell me if I am making an ass of U and Me here) that for the air and water it is talking about temperature? And that in our situation we would want the knock and water as the best choice of what to monitor.

Thanks,

Keith M.

[Gray Haze]

Originally Posted by Fourdoor

Any idea why the stage 3 wiring causes the rich at idle condition? I plan to do the E-manage with the wide band as my first modifications, and do plenty of data logging, and I would share my "bone stock" data logs with the list.... but if the stage 3 wiring throws off the tune at idle, will the data logs be valid for anyone using a lower level of wiring? And is it only at idle that this rich condition occurs?

About the data logging with the E-manage, is the information conveyed in the logs what the ECU thinks is going on, what the e-manage is telling the ECU is happening, or some combination of that information?

For example, if the stock ECU wants to run 10 deg of timing at a given load point, and you are using the E-manage to add 5 deg of timing at that given load point, does the log show 10 deg (what the ECU wants) 5 deg (what the E-manage is adding) or 15 deg (combo of ECU and E-manage)?

One last thing about the Boomslang harness, it has options for "air and water" "knock and water" "knock and air" or "dual knock" inputs. I assume (tell me if I am making an ass of U and Me here) that for the air and water it is talking about temperature? And that in our situation we would want the knock and water as the best choice of what to monitor.

Thanks,

Keith M.

OBD1/2 dataloggers will show what the ECU wants target timing to be, not actual. Some obd1 Dataloggers are off too.

With the boomslang harness you want Knock/Water temp if you plan to use greddys autotune feature.

[Racer_X]

THe e-manage shows actual timing in the datalog, so if yoru ecu is trying to set the timing at 10 Degrees and you advance 5, the e-manage reports 15 degrees, which is what you would see with a timing light.

[2root4u]

Originally Posted by BlackStealth

... This thread is relatively young and I don't know if any new EMU owners had the opportunity to try and datalog stock injectors.
...

Check out jj3kgt's page: http://jj3kgt.googlepages.com/emutuning

"File for Grayson using global injector sizing. This is a map and pics of a sampling map for global injector sizing to find stock hz and a/fs.

Mar-6-07Grasonglobalsettingspull.lg2

Graphs for Grayson:

Airflow : Datasamplingmaprelativepressure-htzM.jpg

Air to Fuel: Datasamplingmapa-fmar-6-07copy.jpg "

[BlackStealth]

It was my experience that my car gave a slight rich idle and only idle was affected, as to what causes that who knows. My guess is the injector duration time was somehow increased by a fixed amount and since idle has a very short injector duration time this small increase was enough to make it rich at idle. Again this is just speculation as I didn't investigate it further and easily corrected it using the I/J fuel map 1. As long as you use the I/J fuel map to make this small adjustment this modification is done after the ECU so your "stock" datalog runs should be valid for the most part. I'm sure the 3S community will thank you if you provide some stock datalog runs to compare including myself.

The emanage datalogger allows you to datalog both before and after the ECU. Example: ECU injector duty cycle is 10ms, and once emanage gets a hold of it the actual injector duty cycle is 7ms, so you can see from both perspectives. Anything the emanage is connected to can be datalogged, so that would include actual ignition timing, real injector duty cycle, etc. When you review a datalog run, your emanage ignition map cell in question would be highlighted in color, but wether or not the datalog run includes the correction I don't know -- I've never looked into that.

Yes air and water refers to air temp, and coolant temp. As already mentioned the water(coolant) temp is important if you want to use the auto tune feature.

[2root4u]

Originally Posted by Trevor

The only bug that I have had problems with is the timing logs going nutty at full throttle. Does 2.12 still do that?

I made to ECG and back on 2.12 without any problems. As you mentioned, the only problem I saw was the timing logs being incorrect.

On a different note, I cannot get my emu to downgrade to 1.14. With 1.14 loaded on my laptop, I continuously get the "Would you like to connect in real-time" or whatever that message is. As soon as I say "yes" to connect, it pops up again. Anyone have suggestions on downgrading?