I'm running 0+ 330 no-smart this is the only time i have seen a knock signal increase since Ive had xede Its in the small data log. I was running v360 w/smart (93oct on both) and knock sig. seldom moved, here is a copy of the data log, with adjusted AFR#'s time and knock.
what should I be looking at to adjust the timing table whats the reference source.
Yes I am a new tuner but you got to start somewhere even if its S L O W.

thanks in advance for support

 

First, you forgot to post the log

Second, what are you using to log knock?

 

yes I know I was at work and it kicked me off before I could go back and edit the post
The input signal I believe is AN0

I changed the file extension to .txt from .csv it will need to be changed back to view the log

 

hah wow that log is useless. who knows how many log events are occuring between your datapoints.


use commslog or pyXede to log, and try again.

EDIT: here i attached one of my logs. once you use a highspeed logger, you can open it in excel, make your corrections, then chart it. you can see how now you have useful information.

the big spikes in the Knock graph are bad

 

Thanks I have to use what i got for now, however, working on getting a high speed data logger

 

working on it? just download it and use it. its not that hard. commslog is the highspeed datalogger built for the xede.

http://www.vishnutuning.com/secret/CommsLog.zip


donor's program pyXede is pretty cool, but you have to know what you are doing to get it running on a windows pc.

http://sourceforge.net/project/showf...roup_id=144766

 

Thanks, got it, I have a couple of kids and my wife works nights so time is very short....... if there is any.