So far, I've been using WinALDL to log but I want to try to use TunerPro because it just seems better in general, more advanced, additional features etc.


I can get TunerPro to connect ( I think ) because it says DA: Connected when I go to "Start/Stop Data scan".

However.... in the "Data Acq./Emulation" tab in the "Tools --> Preferences" menu, it says that I'm not connected... "Cable not found or not functioning (tested at 8192 baud)" is the error message I receive when I click on "Test for valid interface using settings"...
It's set to "Standard Serial" and COM3 which is the port that works for WinALDL....


Also,
The item list seems to be there... but the Dash and History Tables tabs have nothing????


I'm Using the 42.adx data-definition file.....


Why can't I get TunerPro to work for datalogging???

Please help.

 

? bump

 

Ok I guess I was making a dumb mistake of using the ads file that is for TunerProV4... I switched the datastream definition to the $42-1227747-V3.adx and all is well it seems.


Okay so in the 7747 thread, there is this .xdf file posted "$42-1227747-V4.xdf" I also have the $42-HIWAY.xdf.... Which one is better or which one should I be using?

 

I've had no luck even getting my tunerpro to read the ecm... what do you do if you dont have the .xdf or the .bin file???

 

To answer the question I asked earlier about the 42-hiway.xdf versus the other .xdf file :


You don't need either .xdf or .bin files just to scan the ECM....

Remember... 1.)The .bin is the binary file which is the calibration that runs the ECM

2.)The .xdf is the definition file that lets you edit the .bin without having to mess with hex

3.) The .adx is the datastream definition file that lets you connect to the ECM for scanning/logging purposes.

You need a current copy of TPRT (version 5 preferably), and the PROPER datastream definition.

I tried to upload both a binary definition (.xdf), and, also, a datastream definition (.adx) for you to use...

Just remove the .txt extension when you get to that point so that TunerPro knows what to do with the files....