I know what it is but can't figure out how to set it up. I've read the thread regarding "string" and "X" / "Y" axis but still dont get it or havent found the correct Tab to open to set it up. I say that because when I am playing back a datalog, and select Data Tracing, nothing happens. There doesnt seem to be anything else (Data Tracing related) to set it up (x/y axis)? Everything else is working great for me, emulate, datalog...etc.

How do I get the Data Trace feature to work?

 

I'm assuming you meant this thread.
https://www.thirdgen.org/forums/diy-...ght=DATASTREAM

The items are setup in your XDF file definition.
When yo hit "F2" to edit the selected item, there will be a tab that says "ALDL Assoc"
That is where you would pick the item from your currently selected ADS file.

HTH

 

Yep, that's the thread. Thanks for the additional info, I'm off to try it again!

 

Still no joy.

Here's where I'm at; open Tuner Pro, click "XDF", then click "View/Edit XDF Header Info", click the "ALDL ASSOC." tab... only one line appears stating "ALDL Definition File to Link to this XDF", I click browse and select my 1227730_corrected.ads file, click apply, then close. At this point I still havent seen any hint of "X"/"Y" axis or "String, INT or FLOAT"

(missing a step here to identify x/y axis???)

Next, I select a datalog, press play, open my VE tables and thats all I get is a VE table, nothing highlighted or any tracing happening during playback.

I know I'm getting closer but still need some additional guidance. Thanks in advance!

 

After you have selected your aldl def and saved it.
Mark a table (ex ve table) go to xdf/ view/edit item info
Set the general output type to floating point.
Go rows at the row label type set it to integrer or floating point.
Go to columns set the column label typ to integrer or floating point.
Go to aldl assoc set the X and Y axis and hit apply.
Save det xdf file.
Enable ALDL data tracing.
Open the ve table.
Playback the file you have.

work for me.

 

Like Honken said,
You have defined the ADS to use for the tracing (XDF header info) but have not set up each individual item you want it to work with.
Editing each definition item in the XDF allows you select the "X"/"Y" associations if its a table or a single item to display if the XDF item is a constant.

 

WOOHOO! It works now. Thanks guys!

 

I just set this up and its pretty cool. I have some questions though.
Why is the data tracing displayed as four highlighted boxes on my spark map? I thought it would trace as one box, to indicate where I am precisely. On my spark map, MAP vs RPM, why is the data tracing ahead of the actual RPM? The four boxes are always one step higher in the RPM scale than the dash value indicates. Example; RPM=1425 yet the data tracing shows the 1800 and 2000 blocks highlighted. The MAP value is correctly traced.

 

The ECM interpolates between cells. Since the current incarnation of TunerPro can't proportionally "place" the highlights, I need to highlight all active cells that the ECM is using for its final value in the table.

For instance, let's say a table you're tracing has 2 rows, 500 and 1000 (Y units), and 2 columns, 1.0 and 2.0 (X units). Let's say your engine is currently running at 750 Y units and 1.1 X Units.

Your ECM would interpolate the Y value to be somewhere between the two Y axis cells (exactly halfway in this example), and somewhere between the two X axis cells (10% pass the first cell, in this example).

In this example editing any of the four cells would have an effect on the engine when it runs under these exact conditions. Now, it is true that the cells are "weighted" based on how close the engine is actively running from a particular cell, but currently TunerPro doesn't distinguish which of the four cells is closest to the current conditions. In the future it probably will.

So, in a nutshell, what this means is this: editing any of the yellow cells means it will affect on the tune at that point in time (i.e. under the conditions at that point in time).

You still need to do some work to figure out which cell is closest to the current running conditions.

Hope that helps explain it.
----------
That I don't know off the top of my head. However, if you send me a short datalog and the XDF and ADS file you're using, I can take a look.

 

Thanks Mangus, I will send you something or post it here when I get home from work tomorrow.

 

Here is a screenshot example of what I am seeing. The error only seems to be in the spark map. The VE table seems to be OK. In the example the engine rpm is 1150, and the spark map is highlighted in the 1200 and 1400 boxes which seems too high, yet the VE table has the 800 and 1200 boxes highlighted. Here is another at 1400 rpm, same results.

 

Weird. If you could zip up the log and ADS and email them to me, I will be able to actively debug it and either fix it or tell you how to do so.
PS - if you edit your XDF for those tables and add a lower and upper range, the tables will be filled in with pretty cell coloring to indicate value.

PPS - set your Axis output types to INT. You currently have them set to FLOAT, which adds the unnecessary decimal point.

 

I will try to get it to you within the next day or so, I am at work untill tomorrow.

 

I as well am having a hard time getting the data tracing to work . I am able to log and emulate using tp rt with my ostrich . I tried linking the individual tables , but it doesnt highlight the "select x axis aldl item" box when clicking each one . It only gives me the option to link them if I click :

Fueling
Spark/Timing
Acceleration
Deceleration
Boost Control
Tcc
Idle
Egr
Cold Start/Run
Other

I wasnt sure if they all were X=map 3bar , and Y=rpm .Do I need to link all the ones above ? From reading I have seen that I should change the output types to Integer from Floating type , but say I do that in the Fueling aldl assoc , do I have to change the same output types in the actual F31e,F29,F30,F28,F31m,F31,F77,F92,F94 tables as well ?

 

Those items look to be catergories assigned to different XDF items.
Select "any catergory" to display them all at once.
Same with the "levels", do "show up to" and "All levels"

You do need to link each one individually in the XDF definition of the item.
Set up the XDF header info "association" first so you know the ADS you will be linking to.
(Keeps the path and names of the two files relative)
Then set the parameters for each association as needed.
The integer Vs floating point is just if you need to see decimal point values, other wise just use integer.
As long as the values coming from the ADS are within range of the XDF definition, they should display fine.

 

One more thing, when I hit the F2(?) to edit the association info it usually opens the table at the same time. If I enter the info, and select the X anY it wont datatrace until I close the table and re-open it. Try entering all the info, closing the table and re-opening it.

 

Mangus, I finally sent you those files. Let me know if you didnt get them, or need anything else.