ECtune
#62
Re: ECtune
It's pretty sweet. You can see where lambda logging dopped out because everything was happening too fast as the turbo spooled and torque came up so quickly, but eCtune still retained the info it logged to plot out an AFR vs RPM vs boost graph. Sorta like tuenaring on a dyno... well, we are, but the Dynocom unit's lambda logging is still fucked to the max because I've been too busy to calibrate the 14point7 JAW unit to it's stupid ------- peculiarities.
Anyway,
600+ whp or bust, kids, should be going down tonight. Wish me luck.
#63
Guest
Posts: n/a
Re: ECtune
Hell yeah. Thats exactly the kind of log you need for street tuning. Rust watch the torque curve and see how changes to AF and our timing affect it. If it gets steeper your making power if it drops of your doing the wrong thing.
I really can't wait to get my hands on it.
I really can't wait to get my hands on it.
#65
Guest
Posts: n/a
Re: ECtune
Originally Posted by Joseph Davis
Green line is boost, not torque. For this engine and setup it might as well be torque - seriously.
Thats pretty cool though how after 6k that motor is basicaly holding it's peak torque, it looks like all the way past 8k. That thing will pull out some really high trap speeds.
#68
Re: ECtune
eCtune is a hog. My laptops are marginally faster than JD's, and it's still not fast.
P4m 1.2ghz ("2.0 gig") 512mb RAM XPPro
P4m 1.5ghz ("2.4 gig") 1gig RAM XPPro
The faster one is aiight but just barely. eCtune after 5 minutes of use easily occupies 225Mb of RAM.
P4m 1.2ghz ("2.0 gig") 512mb RAM XPPro
P4m 1.5ghz ("2.4 gig") 1gig RAM XPPro
The faster one is aiight but just barely. eCtune after 5 minutes of use easily occupies 225Mb of RAM.