Okay, kinda new to this datalog thing...I did a 3rd gear pull using CommsLog and here is the .log file.

I know it's askin alot, but I'm confused as hell as how to actually interpolate these values into a chart I can read. Which is KNock, which is timing, which is AFR? etc. I know how to use Excell, I just don't know what it is I'm really lookin at with the data. I was wonderin if someone had a little time and could actually run some charts for me using my log, and let me know what areas I need to work on. I can "reverse engineer" the spreadsheet for future use...

Thanks..

BTW, got Xede w/SMART

 

anybody?

 

So NOBODY can help me out?....man.....

 

Have some patience. Seriously, it's friday night -- a lot of people are out.

Assuming you're using SMART. Knock is AN0 in and the LC-1 wideband reading is AN1 in. RPM is obvious, as is time. Freq0 in/out is your MAF reading. WGSol is the signal sent to the boost solenoid.

Crunch on those for a while, then reiterate your question.

You can do you analysis in Excel, or you can download my program (http://pyxede.sf.net) and use the import feature to load that log.

cheers

d

 

lol...as soon as I posted that, I figured I'd get the response you sent...apologies for my impatience. I am assuming we at EvoM live, eat, breath, ****, sleep and dream Evo's 24/7, lol. Yeah, I know...I'm usually out but I'm just chillin at the house this friday..puttin back a few beers and BS'n with the fellas tellin "lies" (my phrase for swappin war stories).

BTW, whcih value is timing?

Thanks in advance and I'll be sure to put back a few more, lol

I love ownin a Blackberry, lol, instant notification on the hip...

 

okay, how's this look? Does it look like I did the calcs correctly? How is she runnin? What areas should I adjust? Thanks again.

http://fyrfytr_engn1.homestead.com/files/XEDE_Data.zip

 

bump....anybody? Need help...

 

bump...

 

okay...maybe this will help some..figured out how to make em JPGs to upload.

SOMEBODY please tell me how these graphs look. Am I right in assuming the my AFRS are lean down low (13s) and rich up top (9s)? Is the target 11ish? I'm pretty sure I'm runnin hella rich cuz I am guzzlin gas like crazy, even more than I think I should. I used the formulas:

AFR=((22.39-7.35)*((AN0*100)/255)/100)+7.35
Knock=(AN1*100)/255
Timing=(Timing Shift Out*100)/255
Boost=(WG Sol Out*100)/255

Am I correct here?

How bout the knock/timing graph? How bad/good does this look? Hows teh boost graph lookin? I'm still learnin about this tunin stuff and wanted to get an assist on problem areas as well as some hints on what type of changes and where in XMap...

Thanks...

 

bump again...

 

No, you are incorrect. At low load, AFR values will be close to stoichiometric (14.7:1) for efficient combustion. As load increases they enrich to avoid knock.

For some people. The base maps for pump gas usually go richer than that at the higher rpm band. 10:1 is fine. My car is very similiar. Maybe you can get a little more power by enleaning that to 11:1 or 11.2:1. Ask shiv.

Doubtful. If you're using a lot of gas, it is because you're heavy on the skinny pedal. The stock ECU is going to trim AFR's to stoich at low load, regardless of your tune. Forget trying to tune to get better mileage. The only way you're going to cut down on fuel consumption is to drive less aggressively and what fun is that?

Close enough, but there's no need to multiply by 100 and then divide by it. Drop those terms.

yah, yah, yah.

Take a look at this plot.

http://pyxede.sourceforge.net/screen...r_knock_ts.png

Green is AFR, white is knock. That's a pretty famous run on dustin's car when the smart kit was being developed. There you can see 3 distinct knock events. It looks a lot like yours (excepting the knock of course). So you're pretty much ok.

Boost is actually not very interesting. As most Xedes are configured the boost table just feeds a direct duty cycle to the boost solenoid. Logging it is kind of useless because what you log isn't actually boost, but the signal that the Xede is sending. However, you already know those values because you put them in the table in the first place. In other words, the logged data will always look JUST like the table, regardless of what the boost curve actually looks like. This is why some of us are talking about installing a MAP sensor.

d

 

Ahhh, many thanks!!! So there are some things I can change to get rid of some of that knock?

Not really tuning for better mileage, but it seems like it is REALLY drinkin gas...lol. I used 3/4 a tank in 1.5 days and I really dind't drive but locally runnin errands (MAYBE 100 miles total)

 

iirc AN0in=knock buffer, AN1 is the wideband

I use timing shift out -128 and the returned value is the same as the corresponding cell in the Xede crank table plus or minus smart correction.

To eliminate knock you may have to reduce timing on your base map, Use your logged timing as a reference to see where smart reduced timing from your base map and by how much.

 

To me it looks like alot of knock.

 

There's really not much anybody else can say without knowing specifics of your situation.

a) what modifications do you have
b) where you are located (atmospherically)
c) what kind of fuel you're using.

d