-= Ultimate Emanage Tuning Thread =-

[2root4u]

Originally Posted by Trevor

See attachment

Thank you sir.

[2root4u]

Originally Posted by Trevor

See attachment

You're welcome!

Trevor,

I'm surprised to see that you have the ignition map zeroed out. I assume the ecu gives you the timing you want?

Is your NVCS map for controlling your alchy?

[Trevor]

Originally Posted by 2root4u

Trevor,

I'm surprised to see that you have the ignition map zeroed out. I assume the ecu gives you the timing you want?

Is your NVCS map for controlling your alchy?

Yeah...i tried pulling moderate timing at 28+ psi around 4800 but I didn't like the EGT's so I went back to a zero'ed timing map. Little did I know alot of people get away with higher EGT's than I though was safe.

The ECU gives me good timing. Aggressive...but good. That's part of the reason I'm going 130 mph on 21-22 psi.

The NVCS map is for my Boost-A-Pump.

[Dj_Frost]

Originally Posted by BlackStealth

Also if your fuel pressure is 44psi at idle then your base fuel pressure isn't set at 44psi.

Ok, now I'm officially

Isnt fuel pressure supposed to be set at 43-44psi at idle? I thought that was the stock figure..

[Elina75]

Originally Posted by Dj_Frost

Ok, now I'm officially

Isnt fuel pressure supposed to be set at 43-44psi at idle? I thought that was the stock figure..

It's 3 bar / 43.5 PSI in atmospheric pressure, vacuum hose disconnected. Idle or not. It's not RPM based, but plenum pressure based.

[2root4u]

Anyone try v2.12 yet? The data sampling feature would be nice to have for tuning, but only if this version is stable.

[Elina75]

Originally Posted by 2root4u

Anyone try v2.12 yet? The data sampling feature would be nice to have for tuning, but only if this version is stable.

All the bugs seems to be there, Greddy is just adding new features and support for new devices

[archangelcomp]

Originally Posted by BlackStealth

archangelcomp: Your sample rates are very low on that palm datalogger, you might consider reducing it to RPMs, Knock, TPS, o2 front, o2 rear so you can get more samples. The narrowband o2 sensors agree that you're running rich only after a long idle. Your fuel trims are normal so it's not like you're past the ECU's fuel trim window. Any reason you didn't pick the emanage datalogger? It would be nice to see wideband AFR results and much faster sampling rates. Both o2 sensors read high so if you had a defective fuel injector there would have to one on each bank. Secondly is it possible your FPR is overrun at idle?

I'll reduce it to just that. Just wanted to make sure I was getting what was needed

The emanage datalogger doesn't log knock, thats why I've been using the palm. I DO have some logs from the emanage though, if you want to see them

And how would the fpr be overrun at idle? I have it set to 44psi right now...how would I check this? I don't think I have a bad injector either.

Thanks!

[Trevor]

Originally Posted by Elina75

All the bugs seems to be there, Greddy is just adding new features and support for new devices

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

[BlackStealth]

I use the emanage datalog for tuning as it captures many interesting data samples/sec and I use the OBDI datalogger for monitoring knock only. If my scanmaster flashes a knock value then I know I have to go check my OBDI datalog results.

I don't know why your car eventually runs rich at idle. I was just trying to come up with some ideas. An overrun FPR will cause your car to run rich at idle, so that's why I asked. Post an emanage datalog run and let see if it will reveal anything and make sure your wideband AFR is datalogged too.

-------------
firmware bugs v2.0 and beyond: Has anyone ever bothered to contact greddy and to let them know this is a problem with 6G72 engines? They've apparently fixed the problems for other engine types in v2.12.