Enable data Tracing in TunerPro How To!

[EagleMark]

I noticed today while playing with data tracing in $EE that when there are 2 tables it will hover in first row of second table while jumping around in first table. Then when you get into higher RPM of second table it will move in second table but hoover in lower row of first... so I guess tha't how it works untill we suggest a fix for next version of TunerPro.

I also noticed that Explicit and choosing the correct Paremeter x axis and y axis is way better then data types! And Explicit link is not needed and long as your adx has all values set for Data Type and Stock Units.

[Six_Shooter]

That's how it's supposed to work.

[EagleMark]

But the darn instructions are very clear files have to be in same folder and linked! and they don't, and that has confused me since beginning...

[JeepsAndGuns]

When I had both my spark tables open, the circle was on the same spot on both tables all the time. All rpm's and all map readings. It was on the same area on both tables. Oh well. Atleast I got it working.

[EagleMark]

Your probably talking about Idle and Off Idle? If both tables are the same then yes the circle/shadow will be in same spot. Mine was main table and extended table, both had same MAP across top but RPM was lower on main and higher on exteneded.

This is where explicit and linked to an adx file may come into play if two tables are involved? and set differant in adx...

[rts91tsi]

This write up is awesome! Thank you EagleMark! Your wisdom has saved me from a lot of headaches, since I have gotten started stock ECU tuning!

[EagleMark]

Just sharing back what I learned from others!

[JeepsAndGuns]

Your probably talking about Idle and Off Idle? If both tables are the same then yes the circle/shadow will be in same spot. Mine was main table and extended table, both had same MAP across top but RPM was lower on main and higher on exteneded.

This is where explicit and linked to an adx file may come into play if two tables are involved? and set differant in adx...

Yea, the idle (closed throttle) and main (open throttle) tables were the ones I had open. The tables themselfs are the same, but the data in the tables is diffrent. I originally started out with them both the same, but I have done some work to the ilde table, and recently did some more tweeking to my main table. So now they are far from the same. So the tables are the same, but the actual data in them are way diffrent. I later switched and closed the timing tables and opened the idle and main fuel (VE) tables. It did the same thing. There was a bubble in both tables all the time, unless I reved the engine higher than the idle table went.
I was kinda hoping that the bubble would only be in the table it is actually using, and then jump to the other one when it switched. I was really curious about when it actually switched.
The whole "explicit and linked" thing is still japaniese to me, you pretty much have to put it in picture ilistrated laymans terms for me to understand it....lol

[EagleMark]

I've been curious about the same thing and explicit linking to adx from xdf may be the answer, just have not had time to explore it yet.

Just spent four hours doing a write up on how to make history table thread, it's in a hidden forum, till I get some sleep and coffee in morning to proof read and God knows I need Spell check!

Godd nite...

[Six_Shooter]

There would have to a byte or two in the ALDL datastream that would indicate which table is being used, which I have not seen. I'm not even sure there is the programming in Tuner Pro to have the tracing switch between the tables, even if there was the information in the datastream to indicate.

The only way I can think of that might work is to use data hit tracing with an Ostrich 2.0 and the latest firmware. I've never tried it myself, so I don't know how it works.

[gregs78cam]

In '7427 there is an 'Open TPS VE flag' and there is an 'Idle spark enable flag', so those could be used to distinguish which table is being referenced, but I don't think TP has the abilty to turn one highlight (trace) on or off. Maybe it's there.


[code]
L5222 FDB $004F ; 23, MW1, MINOR LOOP MODE WD 1
;
; b7 1 = ENGINE RUNNING
; b6 1 = MAJOR LOOP EST MONITOR ENABLE
; b5 1 = VE INT RESET
; b4 1 = RUN FUEL
;
; b3 1 = OPEN TPS VE FLAG
; b2 1 = LOOP OVERRAN 6,25 MS PERIOD
; b1 1 = CHECK ENG LIGHT DELAY
; b0 1 = RETARD FLAG 0 = ADVANCE
;---------------------------------
L5224 FDB $0050 ; 24, MW2, MINOR LOOP MODE WORD 2
; b7 1 = IDLE FLAG
; b6 1 = IDLE SPARK ENABLED
; b5 1 = REF PULSE HAS OCCURRED
; b4 1 = DIAGNOSTIC SWITCH IN DIAGNOSTIC POSITION
;
; b3 1 = DIAGNOSTIC SWITCH IN FACTORY TEST POSITION
; b2 1 = REFERENCE PULSE OCCURRED
; b1 1 = O/L IDLE FLAG FOR AIR SWITCH ENGAGE AT IDLE
; b0 1 = SYNC MAP SENSOR READS IN EFFECT
[code]

[EagleMark]

If it is in the XDF it can! You would have to have both them open and both VE fuel table open, all set up for data tracing of course. Then it would tell you which fuel table it is using.
b3 1 = OPEN TPS VE FLAG worded Idle Off/on and Off
b6 1 = IDLE SPARK ENABLED worded Idle On/On and Off or whatever you want them to say?

[JeepsAndGuns]

Its gonna take someone smarter than me to figure that out. Once it gets into the actual code and whatnot, its way over my head.

[EagleMark]

I found those 2 in the ADX, but not sure what to match them to in XDF? Looking at $OE...

If someone has an $OE data log I may be able to get it to work?

[Six_Shooter]

AFAIK there is no way to have the bubble jump from one table to another.