ATTN: Steve-o or anyone familiar with EEHACK

[ThatDude-98]

i am finally understanding tuning, this has been a lengthy process of about 2 yrs. Do I understand correctly I can data-log using EEHACK, then go under analyze and find precisely where my ECM added fuel or subtracted fuel, as well as where I have knock retard? If that is the correct I can then go in to TunerPro and under those specific areas EEHACK showed I can then add or remove the ammount of fuel EEHACK showed, where needed, as well as retard the timing where EEHACK showed knock? Then flash my corrected file to my ECM using FLASHHACK? Thanks all. - AJ

[steveo]

that's the idea, yep

logging for a long time in various conditions will give you the best results

eehacks analyzer is best with big logs

repeating the process a few times is good too

this will only work if your o2 sensors, knock sensors, ignition system, and engine in general is good

if you use a maf sensor you tune fueling with your maf table

if you dont use a maf sensor you tune fueling with your ve tables

that process will only tune areas where you aren't in power enrichment (mashing the throttle)

[ThatDude-98]

YOU THA MAN BROTHA!! that is genius! say I had a lumpy cam I.E 230+ duration and when the engine went to CL the O2 sensors fought the idle, etc...so I turned the CL enable temp to max to disable CL, now i would be tuning with no O2. Does everything still apply as far as the tuning process like I described?

Went ahead and sent ya a friend request, I´d like to buy ya a beer or 2 or 3 (if thats your thing lol) i am sitting here with my jaw on the floor at the simplicity of tuning these $EE LT1s thanks to your technology. Out of curiosity how long did it take you to develop the program(s)? Thanks- AJ

[LeMarky Dissod]

... say I had a lumpy cam I.E 230+ duration and when the engine went to CL the O2 sensors fought the idle, etc.
So I turned the CL enable temp to max to disable CL, now i would be tuning with no O2.
Does everything still apply as far as the tuning process like I described?

These also might help:
https://fbodytech.com/tutorials/idle-stabilization/
https://fbodytech.com/tutorials/tuning-for-headers/

Once again, many thanks to steveo.

[WASyL]

True, Steveo made awsome job.
As for tuning with his software also it is good to go thru this write up: https://translatedby.com/you/the-bas...iginal/?page=2

Best regards

[steveo]

Out of curiosity how long did it take you to develop the program(s)? Thanks- AJ

thousands of hours for sure. i didn't keep track and i'm not the fastest programmer, i had to learn a lot as i went along

so I turned the CL enable temp to max to disable CL, now i would be tuning with no O2. Does everything still apply as far as the tuning process like I described?

it does have to be in closed loop to generate the trim data and corrections used for the analyzer. so no it wont work.

i would work on stabilizing your idle.

after doing the tips that lemarky linked you to, use the control section in eehack. from warm idle in closed loop play with your idle target speed and timing advance until it's stable, then use the values you found to modify settings in your bin.

big cams usually need more timing and a bit higher idle speed but every build is a bit different

[WASyL]

it does have to be in closed loop to generate the trim data and corrections used for the analyzer. so no it wont work.

is it with NB only or i'm doing something wrong. i run SD OL with WB, log and get Analyzer to show AFR (or % ) for VE table and WOT. only CL performance won't pop up data but OL is much more fun when You don't have to run cats.

best regards

[steveo]

yes its definitely different if you're logging a wideband
the original poster was talking about tuning fuel with trims

[ThatDude-98]

Appreciate the input everyone, if i have any more questions arise ill be in touch again, thank you.

[Sledhead2]

Ok here's my newbie question, what is benefits of EEHack vs TunerPro Rt? I know TunerPro will data log and upon playback it will show BLM Fuel Changes, Timing and Spark knock counts as well.

My first thought is EEHack did it first and then TunerPro caught up?

[WASyL]

EEhack has built in analyser, some realtime change features what makes easier to tune. TunerPro is very good tool for working with bins, works where EEhack can't, but for EE mask there is no better tool to choose.

[NomakeWan]

Ok here's my newbie question, what is benefits of EEHack vs TunerPro Rt? I know TunerPro will data log and upon playback it will show BLM Fuel Changes, Timing and Spark knock counts as well.

My first thought is EEHack did it first and then TunerPro caught up?

In my honest opinion, if you have an $EE car, then TunerPro never caught up. There is no better realtime tool for $EE than EEHack, period, end of story.

The only thing you'll need TunerPro for is making changes to the BIN. Everything else is better done with EEHack, Flashhack, and Trimalyzer.

[steveo]

My first thought is EEHack did it first and then TunerPro caught up?

they are totally different programs

tunerpro was made a long time ago to log and tune any old gm ecm

eehack was made only to log and do some actuator tests just for 1994-1995 lt1 engines

then i built an analyzer into it and some other tools that i found useful

eehack is way way newer than tunerpro is

[Sledhead2]

So for a 95 Chevy Truck, 16197427 ECM, is EEHack a better option, I am not tuning an LT1

[ThatDude-98]

So for a 95 Chevy Truck, 16197427 ECM, is EEHack a better option, I am not tuning an LT1

EEhack and Flashack are for $EE ‘94-‘95 LT1 only, not tbi, tpi, etc, etc. TunerPro would work good for your application (tbi)