CK5
Register an account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members.

Data Logging/ 95 Yukon

GalDemSuga

1/2 ton status
Joined
Nov 2, 2008
Posts
590
Reaction score
0
Location
ATLANTA, GA
Folks
I'm trying to log my Yukon for propose of burning my own chips etc.
I have WinALDL and TunePro RT but neither program reconizes my 427 PCM.

I found Dave_W thread, its got some good info. I went to TunePro site and saw the difinition files there.
 
Last edited:
Been a long time since I used WinALDL but I don't remember it being able to do your 427.

Get the right definitions for TP first. ADX for logging and XDF for changes to bin. Then you just have to get the settings right in Tools, Preferences, Data/Aquisition. Plug in cable, restart computer, reopen TP, check device manager to see cable is on comm 3 (best for TP). Sometimes it's a pain but that's the life with comm ports always changing with USB devices.
 
I gave up on WinALDL, I will keep if for the K5 logging as it works perfectly on that truck.

I have my cable setup on com 4 but I can change that around, I am also using Windows 7 and not Windows XP. I did download the xdf files, so maybe thats why I had issues. My PCM is 16197427 with BJYL bin on the sticker. I have searched the TP site and couldnt find that bin file.

Been a long time since I used WinALDL but I don't remember it being able to do your 427.

Get the right definitions for TP first. ADX for logging and XDF for changes to bin. Then you just have to get the settings right in Tools, Preferences, Data/Aquisition. Plug in cable, restart computer, reopen TP, check device manager to see cable is on comm 3 (best for TP). Sometimes it's a pain but that's the life with comm ports always changing with USB devices.
 
I was able to connect to the PCM using the A218_OD_Trans1_v250 ADX file the others wont work. They cause the TP program to crash. Once connected all I get is the dash and a few sensors. I will screen cap it and post it.


You need $OD XDF to make changes to chip. You need $OD ADX to datalog.
http://www.tunerpro.net/downloadBinDefs.htm

Make sure to read the Read Me file under scalers when you get them loaded. I think they come setup for Wide Band O2 and have to change something...
 
I just read a stock BJYL chip from a 16197427 PCM and it is an $OD.

Try to download the ADX again, are you clicking on it or right click save as or save target as now in IE 9.
 
I am right clicking and saving target as. I will download it again. Can you email me the files if you have them? ADX, XDF and bin?

I just read a stock BJYL chip from a 16197427 PCM and it is an $OD.

Try to download the ADX again, are you clicking on it or right click save as or save target as now in IE 9.
 
Your doing it right.:waytogo:

If they don't work you PM your email I could send them.
 
Ok good news. With the files you sent I was able to log into the PCM. I noticed that the first definition file from each ADX option ($0D,$0E,$31 or $E6) worked with this PCM. However, I got the most data using A205 $E6 TP5 V250. The others didnt show the knock retard but this one did.

Now, how do I actually log here?

Your doing it right.:waytogo:

If they don't work you PM your email I could send them.
 
When your hooked up and receiving data click on Aquisition then record, when done hit stop and it will prompt you to save the file with a name.

Still weird that I have a BJYL 16197427 ECM, right here on the bench, read the chip and the $OD XDF worked fine? So the ADX should also be $OD...

EDIT: and the mask ID for that bin says OD
 
When your hooked up and receiving data click on Aquisition then record, when done hit stop and it will prompt you to save the file with a name.

Still weird that I have a BJYL 16197427 ECM, right here on the bench, read the chip and the $OD XDF worked fine? So the ADX should also be $OD...


That is true, it does work. They all do but I noticed more data from the $E6 file. I will use the OD file to log when I get off work in the morning and post the results here.

I appreciate the help.:D
 
You didn't quote my EDIT.

EDIT: and the mask ID for that bin says OD

Your looking at a highly improved definition files. Read the Read Me files!

I will email you the simple stock versions. Try them first!
 
Hey mark

I finally logged some data this morning. What files should I export since exporting them all looks like an insane mess.


You didn't quote my EDIT.

EDIT: and the mask ID for that bin says OD

Your looking at a highly improved definition files. Read the Read Me files!

I will email you the simple stock versions. Try them first!
 
I PMed dave w to help you on that. He is way better with 427 PCM and with Excel and csv export.

Always save the log first in TP by just stopping, it will prompt you to give it a name and place. This is what I use to look at data in TP. You can always reopen it and then do the export to csv. If you email me the XDL file I'll take a look.

Since I tune live with AutoProm I don't use exported csv files that much. I am done by the time I need data becase I am looking at/adjusting the whole time... and I suck at excel but have been forced to use it and learn the program... a little. :whistle:

WinALDL data was to easy back then as an excel csv file, just use sensor data. Probably same here... BLM, TPS, MAP, Coolant temps, etc... as long as you know there are no codes set.
 
I PMed dave w to help you on that. He is way better with 427 PCM and with Excel and csv export.

Always save the log first in TP by just stopping, it will prompt you to give it a name and place. This is what I use to look at data in TP. You can always reopen it and then do the export to csv. If you email me the XDL file I'll take a look.

Since I tune live with AutoProm I don't use exported csv files that much. I am done by the time I need data becase I am looking at/adjusting the whole time... and I suck at excel but have been forced to use it and learn the program... a little. :whistle:

WinALDL data was to easy back then as an excel csv file, just use sensor data. Probably same here... BLM, TPS, MAP, Coolant temps, etc... as long as you know there are no codes set.

I'm limited on time. Here are couple screen shots for exporting to .csv. Maybe these pics help? I've spent some $$$ developing a VE fixer program for the '427.

Export Log 01.jpg

Export Log.jpg

Export Log 02.jpg
 
Dave
I've gotten that part done. I was hoping to export the only necessary data needed otherwise its a crazy mess:)
 
No codes were present and the xdl is on the way:D


I PMed dave w to help you on that. He is way better with 427 PCM and with Excel and csv export.

Always save the log first in TP by just stopping, it will prompt you to give it a name and place. This is what I use to look at data in TP. You can always reopen it and then do the export to csv. If you email me the XDL file I'll take a look.

Since I tune live with AutoProm I don't use exported csv files that much. I am done by the time I need data becase I am looking at/adjusting the whole time... and I suck at excel but have been forced to use it and learn the program... a little. :whistle:

WinALDL data was to easy back then as an excel csv file, just use sensor data. Probably same here... BLM, TPS, MAP, Coolant temps, etc... as long as you know there are no codes set.
 
Dave
I've gotten that part done. I was hoping to export the only necessary data needed otherwise its a crazy mess:)

Look closely at the screen shot pictures. You have the option of manually selecting what is exported. I have selected the data used most of the time.

dave w

Export Log 03.jpg

Export Log 04.jpg
 
light bulb:D It makes sense now. I will adjust the IAC and relog the data tomorrow and then move forward from there.

Look closely at the screen shot pictures. You have the option of manually selecting what is exported. I have selected the data used most of the time.

dave w
 
Top Bottom