Issues with Data Tracing

kmfdmk · Post by **kmfdmk** » Mon Aug 30, 2010 2:18 pm

I'm having issues with ALDL Data Tracing not functioning.

Fresh XP Install on laptop
TunerPro RT 4.14.0381.00
TunerPro520Vehicle2.xdf
TPRO520.ads

v5.22 currently running on MAFT-Pro.

I can get emulation to work, and the ADLD Dash/Monitors to work, however I cannot get the ALDL Tracing to highlight the cells the MAFT/ECU is currently referencing.

And another small thing, I noticed that the MAP Rows in the VE Table change their range from 0-320 (from TunerPro500Vehicle2.xdf) to 26-250 (when loading the TunerPro520Vehicle2.xdf) file.

I'll never see 36psi, so 250 is fine for me, and actually I was wanting more fine tuning capabilities down lower smoother transition and better fuel economy.

Is there a problem with going ahead and switching to the 520Vehicle2.xdf file?

Post by **robertisaar** » Mon Aug 30, 2010 3:35 pm

unless the XDF directly reads a value out of the BIN to determine value spacing(in which case another XDF should show the same spacing), you can't just change to a different XDF and expect it to react well, since the ECM itself is using the actual MAP values, not what someone has determined to be the correct values, wether they are right or not.

kmfdmk · Post by **kmfdmk** » Wed Sep 08, 2010 8:24 pm

Well to be honest Robert, I lack enough knowledge to understand fully understand what's going on to justify a proper response.

Whether or not swapping XDF's from TunerPro500Vehicle2.xdf to TunerPro520Vehicle2.xdf is going to create issues for the system isn't my direct issue at hand.

The problem I am having is that TunerPro RT is not highlighting the current set of cells which the MAFT-PRO is currently referencing for fuel map correction. Therefore it makes it much more painstaking to locate where in the fuel map I am, and it make tuning my car a bigger PITA than it should be. And I did pay for the software, so I was hoping for a wee bit of support. However I haven't yet emailed the creater of TunerPro yet to inquire about it.

And for the record, I have the same problems in the BETA of V5 as well (installed into a separate directory).

Post by **Mangus** » Fri Sep 10, 2010 1:59 pm

Is the definition you're using set up to trace? If not, it won't work. You should ping Bob to find out.

turbodave · Post by **turbodave** » Sat Sep 11, 2010 2:38 am

kmfdmk wrote:Well to be honest Robert, I lack enough knowledge to understand fully understand what's going on to justify a proper response.

Whether or not swapping XDF's from TunerPro500Vehicle2.xdf to TunerPro520Vehicle2.xdf is going to create issues for the system isn't my direct issue at hand.

The problem I am having is that TunerPro RT is not highlighting the current set of cells which the MAFT-PRO is currently referencing for fuel map correction. Therefore it makes it much more painstaking to locate where in the fuel map I am, and it make tuning my car a bigger PITA than it should be. And I did pay for the software, so I was hoping for a wee bit of support. However I haven't yet emailed the creater of TunerPro yet to inquire about it.

And for the record, I have the same problems in the BETA of V5 as well (installed into a separate directory).

Why are you using vehicle2.xdf? Is this a Buick or something else?