Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

How To: XTune P2 - Log Review

XrunnIT

Active Member
Joined
Jul 29, 2007
Messages
8,044
Reaction score
1
How To: XTune P1 - Data Logging
How To: XTune P2 - Log Review

In the previous article I walked you through capturing data via the X-1 GUI 'XTune'. Now that you have that data, you probably want to know what the hell your looking at right? Well that's what I'm going to explain here. The X-1 manages more sensors and data then most will ever need. So I'm going to go over the basic ones that will give you a good idea of the health of your motor and tune, as well as an idea on performance.

Start off by opening up XTune, and prep the screen for readability (as noted in the previous How To).

Below is a snap shot of the Main1 datachart. IIRC this is from a URD pullied TRD S/C truck. This is a 3rd gear pull, and is very clean and easy to look at, and you can tell quickly that there aren't any major issues. While this chart has almost all the vital information breaking it down could be a bit crazy. Hence the reason for the sub charts (more specific).

Snap11.jpg


It is good to go over all the data provided as most of it is critical and there for tuning support. But for beginner's, I'll familiarize you with the more important features.

POI - Variable name in XTune
Load - Air.Load
MAF - Air.Maf
TPS - Sensors.Tps
Vehicle Speed - Sensor.VSpeed
RPMs - Sensors.ESpeed
Intake Temp - Sensors.Iat
Coolant Temp - Sensors.Ect
OEM Spark - Spark.SparkAngleOEM
X-1 Spark - Spark.SparkAngle
Commanded AFR - Fuel.AfrCmd
AFR Bank 1 - Sensors.Wraf1
AFR Bank 2 - Sensors.Wraf2
Fuel Correction Bank 1 - Fuel.acFB1
Fuel Correction Bank 2 - Fuel.acFB2
Duty Cycle Bank 1 - Injectors.InjPortDc1
Duty Cycle Bank 2 - Injectors.InjPortDc2
7th Inj. Duty Cycle - Injectors.InjAuxThrDc


Now that you have an idea of what datasets represent what data, lets start examing the data.

Air1
You can see where each line is located for the below variables. The charts are plotted almost the same everytime as far as where the graph is located (example: ECT towards the top, IAT towards the bottom, etc). Once you find the graph your looking for click on it to highlight the line and datarow in the spreadsheet below. Inspect the path of the line. Below is a set of guidelines to use as a reference

Load - the higher the better
MAF - the higher the better
IAT - Cooler air is better for performance
ECT - Cooler the ECT the more it will help repress any knock
RPM - Did you hit redline?

Snap_Air.jpg


Fuel1
Do the same thing with the Fuel1 chart. Click on each line to highlight the data in the spreadsheet that way you can identify the graph.

AfrCmd - This is the desired A/F ratio that the motor should be running at.
Wraf1 - This is the reported AFR for bank 1, you want this as close to the AfrCmd as possible
Wraf2 - This is the reported AFR for bank 2, you want this as close to the AfrCmd as possible
acFB1 - Fuel correction factor. You want this value to be as close to 0 as possible (-0.038 = -3.8%). The larger the percent (pos = adding more fuel / neg = removing fuel) means the X-1 is having to compensate for bad data (MAF).
acFB2 - Generally speaking 5-7% +/- is acceptable. If you start seeing the adaptives in the 15%, 30% region, then you might want to do some investigation.

Snap_Fuel.jpg


Fuel2
You can skip past the Fuel2 for now, we'll come back to that in a more advanced follow up.

Injector1
You can see in this particular pull, the injectors were at 95% out through 4th gear (see arrows), and peaks right at the top of 3rd. Use DC along with AFR to see that you are getting enough fuel.

InjPortDc1 - Duty cycle for the primary injectors is relative. Between 70-90% is acceptable. Higher or lower doesn't mean there is a problem, but if the AFR starts leaning out then larger injectors or upgraded fuel pump would be suggested.
InjPortDc2 - see above
InjAuxThrDc - for the TRD boosted trucks running the 7th, the DC is generally in the 30-50% range.

Snap_Inj.jpg



Spark1
You can use this spark graph to identify engine knock. When knock is detected the ECU will pull timing to protect the motor. In most cases it will slowly re-add the timing. A 1º retard every once in a while is nothing to panic about. If you see a consistent 1º being pulled then you may want to alter your spark table to avoid this. If you see 2-3º of timing being pulled, then you should address why (too much timing, too high ECT, IAT too hot, etc), and correct the issue.

In the first image, you'll see the spark table slowly retard timing, that is fine. There are no issues there. In the 2nd image you will see how the timing was pulled at once, then slowly ramped back in. That is a clear sign of engine knock. I have also seen it where, the ECU will do the reverse, and add 2-3º of timing that results in an audible knock. I'm still researching this issue, and can't explain it at this time.

Snap_Spark1.jpg

Snap_Spark2.jpg

Snap_Spark3.jpg



AFR1
This chart is redundant. Contains the information you'd find in Fuel1 and Hego1

Hego1
Reports the values from the HEGO sensors (heated exhaust gas oxygen). We'll dive into this in the Advanced write up.
 
Last edited:

blackx-runner

"White Flash"
Joined
Jan 14, 2007
Messages
7,581
Reaction score
13
Again. Nice job. :top:
What about modifying values to change timing and fuel. Or is that X-1 part 3?
 

RedXRunner

"Splash Baby Douchecanoe"
Joined
Jan 14, 2007
Messages
7,317
Reaction score
0
if i had an x-1 ... i would just make you drive to houston and tune it. but nice write up for the people that dont live near by members like you.
 

ntinhri

Active Member
Joined
Feb 1, 2007
Messages
8,104
Reaction score
2
Should that log look fimiliar. Wait I don't think I was at a 90+ duty cycle.

Very nice write up. I feel like I should give u a tip for all the info uve provided us on the x-1.

Thank u jas!
 

XrunnIT

Active Member
Joined
Jul 29, 2007
Messages
8,044
Reaction score
1
Should that log look fimiliar. Wait I don't think I was at a 90+ duty cycle.

Very nice write up. I feel like I should give u a tip for all the info uve provided us on the x-1.

Thank u jas!

I'm about 95% certain that its not your log, sorry buddy. I've got them stuffed in a folder around here somewhere. But with all the logs having almost the exact same name, file organization can be tedious.
 
Last edited:

thelostrican

New Member
Joined
Jan 7, 2008
Messages
208
Reaction score
0
thx a lot...were are getting somewhere...this is great this write up should be stickied.....imo
 

gtmoy

New Member
Joined
Apr 3, 2009
Messages
165
Reaction score
0
Why does the SparkAngle separate from SparkAngleOEM in the 2nd pic? Is that what you mean by pulling timing?

Here is a pic of one of my runs. On the right side of the graph, the lines are 10 degrees apart
picture.php
 

5H4D0WD347H

New Member
Joined
Apr 24, 2007
Messages
10,450
Reaction score
0
Why does the SparkAngle separate from SparkAngleOEM in the 2nd pic? Is that what you mean by pulling timing?

Here is a pic of one of my runs. On the right side of the graph, the lines are 10 degrees apart
picture.php

If you are ever curious as to what each plotted line on the graph represents look at the following:

class%20modules.jpg


On the left hand side you have a group of folder trees. Expand the folder tree you are interested in learning about, and click on a class module (in this case I have selected MAF).

At the bottom you will see a small description of that module regarding its purpose.

The X1 adds spark on top of OEM.
 

gtmoy

New Member
Joined
Apr 3, 2009
Messages
165
Reaction score
0
That would explain why the TRD S/C flashed trucks don't deviate like the URD graphs. They already have the spark advance/retard programmed in.
 

XrunnIT

Active Member
Joined
Jul 29, 2007
Messages
8,044
Reaction score
1
Why does the SparkAngle separate from SparkAngleOEM in the 2nd pic? Is that what you mean by pulling timing?

Here is a pic of one of my runs. On the right side of the graph, the lines are 10 degrees apart
picture.php


That separation represents the timing that your running, and the timing that the ECU is calling for. When you look at your spark table, you will see where spark is added or removed based on RPM and engine load.

In the spark table snippet below, you can see timing being added, and removed.

3.0 = 3º of advance
-4.0 = 4º of retard.

Spark_Table.jpg



So with 3º of advance over the OEM spark table, you will have that gap between the SparkAngle (what your really running) and the SparkAngleOEM (what the ECU calls for).

In the graph you posted that 10º difference is because your timing has been pulled back by 10º.

When I say 'timing is pulled', i mean you will see both the SparkAngle and SparkAngleOEM both drop 1-3º. If you look at where the red arrow is pointing, you will see where each graph dropped about 1º almost instantly, that is timing being pulled.

Snap_Spark2.jpg
 

5000XD

New Member
Joined
Jan 15, 2007
Messages
3,774
Reaction score
0
Guys, need some help here. How do I get the spark table snippet as Jason calls it? In which you can see the degrees of correction run.
 

XrunnIT

Active Member
Joined
Jul 29, 2007
Messages
8,044
Reaction score
1
Guys, need some help here. How do I get the spark table snippet as Jason calls it? In which you can see the degrees of correction run.

that 'snippet' is just that, a snippet.

its nothing more then a section I took a screen shot from the spark table.
 

5000XD

New Member
Joined
Jan 15, 2007
Messages
3,774
Reaction score
0
lol, really. In which folder is the spark table then as you posted it? I can't find it somehow. I'm in spark1 tab and it only shows 5 parameters.....I think DS posted the same Spark table you have.
 

T0LLPHR33

"Catwoman"
Joined
Jun 17, 2008
Messages
10,969
Reaction score
0
how to you copy and paste a data log screen that way I can post it and some of the x-1 gurus can help me understand the program better as far as engine knock...etc...
 

XrunnIT

Active Member
Joined
Jul 29, 2007
Messages
8,044
Reaction score
1
how to you copy and paste a data log screen that way I can post it and some of the x-1 gurus can help me understand the program better as far as engine knock...etc...

Print screen, hypersnap, any screen capture app would work. Win 7 has a snap shot tool built in..
 

T0LLPHR33

"Catwoman"
Joined
Jun 17, 2008
Messages
10,969
Reaction score
0
Print screen, hypersnap, any screen capture app would work. Win 7 has a snap shot tool built in..

ok I didn't know if print screen actually printed it or took just a screen shot...thanks jason...:top: I ended up using the Snipping Tool that vista comes with...

here's my 1st data log from this morning...let me know if you see anything abnormal...I can always email you my 1st data log Jason...just let me know...any help would be greatly appreciated...sorry for asking so many questions...as you apparently know i'm a NOOB and have a lot of catching up to do...:laugh:

Data 1 Air
Data1Air.jpg


Data 1 Fuel
Data1Fuel.jpg


Data 1 Spark
Data1Injector.jpg


Data 1 Injectors
Data1Spark.jpg
 

XrunnIT

Active Member
Joined
Jul 29, 2007
Messages
8,044
Reaction score
1
logs are best when you are WOT and with the actual log in hand (can cross reference different variables). A screen shot is ok for looking at particular instances, but having the actual file will provide better feedback.
 
Top Bottom