Data tracing - Spark advance tabel - Data type/Stock units

18I43R65O72Z · Post by **18I43R65O72Z** » Sat Aug 04, 2012 5:37 am

Hi folks.

Can someone please help me on setting up the right data in TunerPro. I have managed to get connection from the OBD contact to the computer and I’m using the AutoProm as a PROM. So both the “DA link connection” and the “Emulating” connection are working just fine. My goal is to set up the data tracing in the “spark advance table”. I have managed to get the data tracing working for the RPM.

In the “spark advance table” there are two types of data. “Y”, I believe is the RPM from the engine. This has a scale from 400 -4800. But what is the “X” colum? This has a scale from 32 to 208. What kind of setting do I need to do so the “black dot” regulate in both in the “Y” row and the “x” colum?
These are the settings that I have done.

1. From the title bar :
a. XDF
b. View/edit XDF header info
c. DA Assoc
d. Selected the right definition file

2. From the parameter tree
a. Tables
b. Spark advance table
c. “F2”
d. Rows
e. Data type = Engine speed
f. Stock units = Revaluations per minute
g. Row label type = Floating point
h. Colum
i. Data type = ???
j. Stock units = ???
k. Row label type = Floating point
l. DA Assoc
m. X axis DA link – Link mode = ???
n. X axis DA link – Link mode = Explicit = Engine speed

3. From the title bar
a. Acquisition
b. Edit definition
c. Values
d. Engine speed
e. Data types = engine spees
f. Stock units = revolutions per minute
g. Air flow
h. Engine speed
i. Data types = ???
j. Stock units = ???
4. Title bar enabled
a. Data tracing
b. Acquire data (connection)
c. Data tracing

Are there other settings I need to preform?
Are the settings I have set up right?
What are the right settings on 2.i, 2.j, 2.m 3.i, 3.j and why?

Help would be greatly appreciated…

Six_Shooter · Post by **Six_Shooter** » Sun Aug 05, 2012 6:03 am

What XDF and ADX are you using, or what application is this?

18I43R65O72Z · Post by **18I43R65O72Z** » Sun Aug 05, 2012 8:03 am

Thanks for answering.

I’m using the “32.XDF” and the “1227165_160.ADX”

Six_Shooter · Post by **Six_Shooter** » Sun Aug 05, 2012 12:05 pm

The Y axis will either be LV8 calculation or MAF counts. Sounds more likely to be MAF counts due to the range, from the range that you mention.

18I43R65O72Z · Post by **18I43R65O72Z** » Mon Aug 06, 2012 11:27 am

The problem is that I can’t find those calculations. When I try to connect the X row to the “X Axis DA link” (press F2 on one of the tables and go to DA Assoc) the only logical parameter/value that I can choose is the “Airflow”. But this has a scale in a range from around 2000 and up to around 7000 or something like that. This is resulting in an output that is obvious wrong.

I have tried to set up the data type in “tables” to:
-Mass Air Flow
-Load
-Airflow
For the stock units I have tried:
-Grams per second
-Load value(LV8)
For the ADX definition file, I have tried the same for the value airflow.
I think I have been true every combination of these data types and stock units.

Any suggestions? Again, thanks for answering…

Post by **Mangus** » Mon Aug 06, 2012 11:56 am

In general, it's best/easiest to avoid explicit DA Association. That is to say, do not tie the XDF to a specific ADX.

Modify ADX as follows. For the ADX values that you wish to use to trace items/tables in the XDF, set up their data and unit types. For instance:

- For the RPM value in the ADX, set the data type as "Engine Speed" and the units to "Revolutions per Minute"
- For the load value, set the data type to "Load" and the units to "LV8"
- Save the ADX

In the XDF, for the tables that you want to trace:

- Set the axis data type to match what the axis represents. For instance, an RPM axis should be set to "Engine Speed" for data type and "Revolutions per Minute" for units (just like you did in the ADX).
- Make sure the axis output is set to int or float (depending on what makes sense for the axis. For instance, RPM axis should be int). An axis set to type "string" cannot be traced.
- On the DA Assoc tab, set the link mode to "Data Type/Units Match"
- save the XDF

Then close and re-open TunerPro to ensure that the links are reset.

-Mark

18I43R65O72Z · Post by **18I43R65O72Z** » Tue Aug 07, 2012 6:37 am

Tanks’ for answering Mangus. 

I’ve tried ones more, but still no luck…
There is no “Load value” in my ADX file. I have these values to choose from:

- PROM ID
- Throttle Position
- IAC Present Position
- Coolant Temp
- Vehicle Speed
- EGR Duty Cycle
- Engine Speed
- Bare Pulse Correction
- O2
- Knock Count
- BLM
- O2 Cross Count
- Airflow
- Base Pulse With

I’ve tried to set the “Airflow” - value to the different “data types” and “stock units” as described in the last post.

The data tracing are working just fine for the engine speed and the coolant temp. The highlighted circle is moving in the “Y row” in “spark advance table”, but only in the “X column” to the right or left, -depending on my “data type” and “stock units” setting. One setting makes it constantly to the left, another constantly to the right. I’ve also driven the car, just in case it would make any difference. It is the same for coolant temp in another table.

As you posted, I need to set up the load value to data type to "Load" and the units to "LV8", but this load value is nowhere to be find. If you can help me find this value, I believe it would solve my problem…

Again, thanks.

Post by **Mangus** » Tue Aug 07, 2012 7:18 am

The unit type is "load" and the load value is "Load Value (LV8)." They're definitely there; I've just checked a third time. =)

And, really, it doesn't matter what data types and units you choose, as long as you choose them to be the same in both the ADX and the XDF items that need to be linked.

18I43R65O72Z · Post by **18I43R65O72Z** » Tue Aug 07, 2012 8:36 am

Maybe I’m misunderstanding something?
(I do understand -->; And, really, it doesn't matter what data types and units you choose, as long as you choose them to be the same in both the ADX and the XDF items that need to be linked.)

For example, when I did set up the engine speed I did this:
1. Started TunerPro
2. Acquisition
3. Edit definition
4. Values
5. Engine speed
6. Data types = engine speed
7. Stock units = revolutions per minute

This settings do work in the “Spark Advance Table” for the “Y column”

Is this where the misunderstanding is:

In your last post you said that the “load” and “Load Value(LV8)” are definitely there. If you mean the “Load” you can choose from the list number “6.” above, then it is there. Also the “Load Value(LV8)” you can choose from the list number “7.” above, then it is there. But what is the right value in list number “5.”?

This is how I understood your first post:
1. Started TunerPro
2. Acquisition
3. Edit definition
4. Values
5. Airflow <-- This is what I think is wrong… Is it?
6. Data types = Load
7. Stock units = Load Value(Lv8)

Thanks’ for being so patient.

Post by **Mangus** » Tue Aug 07, 2012 9:04 am

The datastream has an explicit value called LV8 that is outputted. Airflow is also there, but the tables that you want to trace in the XDF refer to LV8. The main one that refers to airflow in general is the MAF table (and even then sometimes they're defined in counts, not airflow), and you can't trace that one.

18I43R65O72Z · Post by **18I43R65O72Z** » Tue Aug 07, 2012 10:06 am

So you are saying that all the tables with the value “LV(8 )” are untraceable?

That is:
Spark Advance table
Spark Correction – LV8/2 vs Coolant Temp
Highway mode spark vs. Load
Maximum Knock Retard Degrees When Not in PE
EGR Duty Cycle vs LV8 and RPM
Acceleration Enrichment factor vs Change in LV8
Inj offset vs base PW
Open Loop AFR % Change Vs Load
Fuel PW vs LV8

Post by **Mangus** » Tue Aug 07, 2012 11:12 am

18I43R65O72Z wrote:So you are saying that all the tables with the value “LV(8 )” are untraceable?

Nope, that's not at all what I'm saying.

Email me the XDF and ADX and I'll set them up for you.

Post by **Mangus** » Tue Aug 07, 2012 3:12 pm

I've done this for you and emailed you the results. I had forgotten that LV8 isn't outputted in the 160 baud stream for the 1227165 ECM, so I had to add it based on other values outputted in the stream. More info on how to do that is here: http://www.thirdgen.org/techboard/diy-p ... w-get.html

I recommend that you update to use $6E code instead. Do this by unplugging your cold start injector, then simply start with a 6E bin that makes sense for your vehicle (e.g. ANZA or APYP for manual, ARAP for auto). Then you can use the higher speed connection (8192 baud instead of 160 baud), and the additional data that comes with it.

18I43R65O72Z · Post by **18I43R65O72Z** » Wed Aug 08, 2012 1:29 am

Thanks’ a million times Mangus!!!

Now, it’s working just fine. I had to make some changes though. Just as “billdorn” on http://www.thirdgen.org/techboard/diy-p ... w-get.html I got a LV8 value that was to hi.

By doing as “RBob” described I made it work. The gms/sec needs to be divided on 256.

The airflow is gms/sec * 256, for 23637
gms/sec = 92.3 = 23637 / 256

Thanks for helping me out!