I'm preatty new to the tunning subject and I need some help with explaining Xede variables. I'm posting all the variables and with the help from all of you I wish that we can come up with the conclusion for all of us that are starting to play with the Xede. If I'm missing anything let me know I will update the very first post so it is clear and informative.

AN0 In - Knock
AN0 Out - Knock
AN1 In - AFR
AN1 Out - AFR
AN2 In - ???
AN2 Out - ???
Freq 0 In - MAF
Freq 0 Out - MAF
Inj 0 Out - ???
Inj 1 Out - ???
WG Sol Out - ???
Timing Shift Out - calculated from CAS in/out difference
Spray Out - ???
Marker - ???

Also from the informations that I gathered around the forums I found few equations, can somebody verify those

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

 

it has to be somebody that know those things, vishnu guys????

 

I think you answered part of your own question

AN0 = AFR
knock = AN1

I think the ultimate answer depends on if you have SMART installed or not. I think there is a different configuration used for SMART and the knock buffer.

But, I would also like more consice answers too.

 

MAF
Is actually calculated from CAS in/out difference.

d

 

Three questions about MAF and Frequency. When we are logging Frequency In and Out, the Out is following In? What are we actually looking for by logging those values? Also, when the Commslog is dataloging the Freq values, are they displayed in Hz or some other value?

About the Timing Shift Out when I started logging it was at 128 at 2000 RPMs by the time it got to 7000RPM it dropped to 113, does this mean that the timing was advanced by 15 degrees? Or do I have to use the formula to get the exact timing degree.
T1 = 128*100/255 = 50.196
T2 = 113*100/255 = 44.314
T = T1-T2 = 5.88 degrees

I'm sorry if I'm asking a stupid questions but I'm trying to understand what exactly is going on when I get all the parameters

 

????????

 

Anyone, anybody, someone has to have an answer ????

 

I just downloaded all the pyxede stuff that donour has worked on. it is really easy to use. haven't figured it all out yet, but 10 minutes to download and install. did one run and did the high speed datalog. ended up with one file in an excel format and it lists rpm, time, a/f, boost solenoid duty, timing and a few other things. very easy to install, even on windows and even easier to use to get an excel file. anxious to figure out the graphing software and start using it. I have not ever used the commslog, but I understand that you have to convert everything. pyxede is in plain values.. great tool and I would recommend it....

just my .02

 

Timing shift out results in the timing value in the timing table(pos or neg) . I use (113(timing shift out)-128)/10= -1.5 degrees.

 

OK I get the timing shift, so I gues that I was almost right in my first assumption, I just need to divide this number by 10. Since we can calculate the degrees of timing the way you put it Jorge, so what do we need the equation that I wrote in the first post???

How about my first question about MAF???

 

Can you please restate the question?

The frequency sampled to a 10bit value by the Xede.

It's a duty cycle, range = 0.0 - 100.0%.

This is definitely _not_ a stupid question. I always assume it was the former (15 degrees). Now I'm thinking you might be right. Lemme think some more...

d

 

donour - after logging the Freq In and Freq Out looks almost identical up to 4.5K then Freq In has a little higher value than Freq Out, any reasons for that? What is actually happening that Freq In has a higher value than Freq Out, any adjustment or changes done by the Xede??

There is not much that I'm logging at this time since the SMART is not yet installed, but from the logs that I have collected after I corrected the boost cut at around 4K the revised graph looks as following. Here is the Excel sheet.

Also I don't have the knock sensor installed yet, but is my engine knocking at 3188 and a little before that?? Or this is still related to the boost comming up too quickly and timing beeing pulled. There was not much tuning done since this was a first day of collecting data after Xede install. File test6... is with the boost cut, and file test7... is after I adjusted a boost table a little bit. Once again, besides small boost adjustment there was no other adjustments done.

 

?????

 

That is perfectly sensible. At higher RPM, your map is probably pulling fuel. However, the Xede (and like every other piggy back in the world) doesn't control fuel injectors directly. Instead, it modifies the airflow signal (Freq0) which the ECU uses to determine how much fuel to inject.

I'll take a look. But you really don't want to take my word. Vishnu employees should chime in directly.

d

 

Just noticed with smart installed it is like this:
AN0 = knock buffer signal
AN1=AFR from LC-1