1996 Express Van TunerPro RT v5 Definitions Setup Help

[FattyBlaster6]

Hey there, thanks for caring enough to click on my post! First off, please repost if there is a better spot on this forum relative to my questions. I'm trying to save the little hair I have left by coming directly to the experts here. I am just putting the finishing touches on the mechanical aspects of my Express Van Project and need to start gathering info for the software side. Here is the rundown on my project.

I own a 1996 Chevy Express 1500 CONVERSION Van in which my family uses for long road trips or group outings. It has the 305 4l60 drivetrain. About a year ago the rear main seal began leaking. Rather than going through the work of fixing it I decided I'd rather upgrade the drivetrain to a 350 4l80 setup so I can have a more robust drivetrain. I added some rear main seal stop leak which helped slow the leak and began my search for a doner. Well I found a great deal on an 1997 Chevy Express 2500 Basic SERVICE/WORK Van with the desired drivetrain. After weighing the pos/neg between chassis differences I ended up swapping the entire chassis over. Long story short, I've completely rebuilt the 5.7 l31 with a stage one camshaft, Hooker Cast Exhaust Manifolds, EFI Connection 24x Kit (https://www.eficonnection.com/home/prod ... istributor), Coil Near Plug Conversion.
I have done the 0411 swap to control the whole shabang. Initially was thinking of using the HP Tuners platform for mapping but it is far too costly in my opinion for a single project use. That is when a came across the TunerPro software. Seems exactly what I need. I have downloaded the latest RT version but have not registered yet as it recommends not doing until verification of successful interface. Also, I have downloaded the latest version of LS Droid for Windows and just received my OBDX Pro VX Cable.

Questions I have:

1. What is my next step, can I just download the current .bin from the 0411 to see what I have or do I need to download the definitions first. I think I remember having to download the definitions first when I did something very similar to this with for my Subaru w/ romraider and ecuFlash. Lost a lot of hair on that one through the learning process but hopefully that experience will largely apply to this. I believe that in that case the definition file I downloaded contained pretty mush all the Subaru models available at the time. Not a single vehicle specific file. So far I have seen conflicting info on this.

2. What OS? I read somewhere that it is best to Flash the most recent OS onto the PCM regardless of the year. Obviously I haven't hooked the computer up to the van yet so I have no idea what vehicle it came out of. It was however being advertised as a 2001-2002 PCM ( I guess this means it is a P01 PCM? https://www.ebay.com/itm/187035941377 ). Searching on the TunerPro site itself I did not see an obvious .bin or .ads file that matches what I think I need originating from an 01+ Chevy let alone model specific. I many options here
( https://github.com/BoredTruckOwner/LS_B ... Repository ) but not sure which is the one for me. If I were to find the correct .bin and .ads files for an 01 Chevy Express 2500 5.7 4l80e would the correct operating system not come with it? Not sure where to start here. The van is still Drive by Cable by the way and I have no intention of going DBW so maybe the OS is moot?

Thanks in advance for any help you can provide and have a great day!!

[1project2many]

Hello and welcome.

The 0411 swap is really your key to success tuning the van. There isn't much support for the older "black box" pcms.

I believe I have posted a few one ton 2001-2002 G van calibrations. These are for 5.7 / 4L80E vans with 4.10 rear gears. They are not agressive calibrations but they are a good start for tuning. There is a 2002 L31 / 4L80E calibration here: https://www.gearhead-efi.com/Fuel-In...rPro-Bin-Files. The OS is part of the calibration so you will have to do a "full write" if the OS programmed into your pcm is not the same as what's in the file. There are different versions of xdf to use with Tunerpro and some may need a checksum. If you do not find a working xdf I can try to find one.

[FattyBlaster6]

Hello and welcome.

The 0411 swap is really your key to success tuning the van. There isn't much support for the older "black box" pcms.

I believe I have posted a few one ton 2001-2002 G van calibrations. These are for 5.7 / 4L80E vans with 4.10 rear gears. They are not agressive calibrations but they are a good start for tuning. There is a 2002 L31 / 4L80E calibration here: https://www.gearhead-efi.com/Fuel-In...rPro-Bin-Files. The OS is part of the calibration so you will have to do a "full write" if the OS programmed into your pcm is not the same as what's in the file. There are different versions of xdf to use with Tunerpro and some may need a checksum. If you do not find a working xdf I can try to find one.

Great! Sounds like I'm on the right path for my goals. Not sure if it's even necessary, other than that it will confirm I am communicating with the pcm, to try to use LS Droid for Windows to pull the current map off the 0411 pcm tomorrow. I downloaded that .bin you suggested as it seems like a safe place to start. Not sure what you mean by "full write." What other kind is there? My plan is to simply load that bin into tunerPro, do the modifications for VAT Disable, EGR Delete, Single Knock Sensor, Firing Order, Rear o2 Delete, etc. and then flash it to the pcm. Will it give me an option to do a "full write" including OS or partial without OS at that point or are you saying it is just going to take longer because it has to replace the OS as well at the changes?
Yes, I am now on the search for the correct .xdf and .ads.. Thanks for helping point me in the right direction!

[FattyBlaster6]

Found this. Seems like the one for the above .bin but can't figure out how to get it into tuner pro.
https://github.com/BoredTruckOwner/L...0512k%20V1.xdf
Maybe the file just isn't really there anymore?

[FattyBlaster6]

Found this. Seems like the one for the above .bin but can't figure out how to get it into tuner pro.
https://github.com/BoredTruckOwner/L...0512k%20V1.xdf
Maybe the file just isn't really there anymore?

Nevermind...had to click on the "Raw" button to download file then open TunerPro and click on xdf button then chose xdf from downloads. Now to find the .ads

[FattyBlaster6]

Have not found .ads yet. Been modifying above .bin though for my van and have a few questions:

1. Can I go ahead and change the VIN number to match my Van without causing problem?

2. I noticed in table g1207 Vehicle Platform Options that there are 3 Options "present" on my model. First two are for Alternator Terminal L and F which I have no idea what that means or if it is correct, the third is for 4x CKT low resolution crank sensor. I am running the 24x reluctor wheel along with the sensor supplied by efi connection. Do I need to change that to a 0 so it is NOT present?

3. I'm running a 265/70/17 tire which I believe is larger than stock. What table should I modify to make up for the taller tire and is there a magic number or is it going to be a trial and error deal with gps?

4. Is there a way to expose the DTC descriptions? All I see is the actual code. There are quite a few that have been disabled and I need to know what they are. Do I need to just find a description list elsewhere so I know what is what?

5. Tried to save the revised .bin file but gives me a check sum error. Not sure what to do about that.

[Fast355]

Hey there, thanks for caring enough to click on my post! First off, please repost if there is a better spot on this forum relative to my questions. I'm trying to save the little hair I have left by coming directly to the experts here. I am just putting the finishing touches on the mechanical aspects of my Express Van Project and need to start gathering info for the software side. Here is the rundown on my project.

I own a 1996 Chevy Express 1500 CONVERSION Van in which my family uses for long road trips or group outings. It has the 305 4l60 drivetrain. About a year ago the rear main seal began leaking. Rather than going through the work of fixing it I decided I'd rather upgrade the drivetrain to a 350 4l80 setup so I can have a more robust drivetrain. I added some rear main seal stop leak which helped slow the leak and began my search for a doner. Well I found a great deal on an 1997 Chevy Express 2500 Basic SERVICE/WORK Van with the desired drivetrain. After weighing the pos/neg between chassis differences I ended up swapping the entire chassis over. Long story short, I've completely rebuilt the 5.7 l31 with a stage one camshaft, Hooker Cast Exhaust Manifolds, EFI Connection 24x Kit (https://www.eficonnection.com/home/prod ... istributor), Coil Near Plug Conversion.
I have done the 0411 swap to control the whole shabang. Initially was thinking of using the HP Tuners platform for mapping but it is far too costly in my opinion for a single project use. That is when a came across the TunerPro software. Seems exactly what I need. I have downloaded the latest RT version but have not registered yet as it recommends not doing until verification of successful interface. Also, I have downloaded the latest version of LS Droid for Windows and just received my OBDX Pro VX Cable.

Questions I have:

1. What is my next step, can I just download the current .bin from the 0411 to see what I have or do I need to download the definitions first. I think I remember having to download the definitions first when I did something very similar to this with for my Subaru w/ romraider and ecuFlash. Lost a lot of hair on that one through the learning process but hopefully that experience will largely apply to this. I believe that in that case the definition file I downloaded contained pretty mush all the Subaru models available at the time. Not a single vehicle specific file. So far I have seen conflicting info on this.

2. What OS? I read somewhere that it is best to Flash the most recent OS onto the PCM regardless of the year. Obviously I haven't hooked the computer up to the van yet so I have no idea what vehicle it came out of. It was however being advertised as a 2001-2002 PCM ( I guess this means it is a P01 PCM? https://www.ebay.com/itm/187035941377 ). Searching on the TunerPro site itself I did not see an obvious .bin or .ads file that matches what I think I need originating from an 01+ Chevy let alone model specific. I many options here
( https://github.com/BoredTruckOwner/LS_B ... Repository ) but not sure which is the one for me. If I were to find the correct .bin and .ads files for an 01 Chevy Express 2500 5.7 4l80e would the correct operating system not come with it? Not sure where to start here. The van is still Drive by Cable by the way and I have no intention of going DBW so maybe the OS is moot?

Thanks in advance for any help you can provide and have a great day!!

You need to start with a 6.0L/4L80E calibration as that is the easiest starting point. 6.0L was DBC through 2002 in trucks so it is not a hard file to find. You will also need an L31 Express van file to copy the VE tables, Spark Advance tables, Injector Bank selection, diagnostic firing order, etc. Luckily I have done a few and beat you a bit on getting my 97 Express fired up with a 24x CNP 383 although mine is DBW using a 2005 P59.

This was the first start

https://youtube.com/shorts/Sq6wjrm-Q...3jMiifwtxSo6Wy

After making coil brackets, cleaning up a lot of the harness and some preliminary tuning.

https://youtu.be/2WbNdRJhV0Y?si=4xOpMYYzsnPAqmVm

[FattyBlaster6]

You need to start with a 6.0L/4L80E calibration as that is the easiest starting point. 6.0L was DBC through 2002 in trucks so it is not a hard file to find. You will also need an L31 Express van file to copy the VE tables, Spark Advance tables, Injector Bank selection, diagnostic firing order, etc. Luckily I have done a few and beat you a bit on getting my 97 Express fired up with a 24x CNP 383 although mine is DBW using a 2005 P59.

This was the first start

https://youtube.com/shorts/Sq6wjrm-Q...3jMiifwtxSo6Wy

After making coil brackets, cleaning up a lot of the harness and some preliminary tuning.

https://youtu.be/2WbNdRJhV0Y?si=4xOpMYYzsnPAqmVm

Wow, that is a pretty sweet setup you've got. Going to be quite the beast. Congratulations on getting it going! Jealous of that intake.
Thanks for the recommendation. Just curious as to why you would recommend the 6.0 .bin over the one I posted above? Seems exactly what I need being pretty much the same drivetrain setup as mine, just from a newer model with the same computer Im installing? Is it that with my mods the 6.0 will be closer for correct afr's? Thanks for the info!

[Fast355]

Wow, that is a pretty sweet setup you've got. Going to be quite the beast. Congratulations on getting it going! Jealous of that intake.
Thanks for the recommendation. Just curious as to why you would recommend the 6.0 .bin over the one I posted above? Seems exactly what I need being pretty much the same drivetrain setup as mine, just from a newer model with the same computer Im installing? Is it that with my mods the 6.0 will be closer for correct afr's? Thanks for the info!

The problem is a 4x file will not run a 24x engine and flipping that system option bit for crank resolution is only a small part of the differences in the calibrations that run each style of ignition system. You have to start with a file that has the correct settings for the ignition system. You can copy alot of the other parts of the calibration from the L31 Van file though. There are numerous things like injector bank assignment, firing order, knock sensor settings and more that need to come from the 350 file.

[1project2many]

You need to start with a 6.0L/4L80E calibration as that is the easiest starting point.

Agreed. I missed the 24X sensor mentioned in the original post. Copying tables from the 5.7 calibration is likely to be faster than working to convert the distributor calibration to 24X. There is a "Comparison Tool" which allows multiple tables to be quickly copied.

Yes, it's ok to change the VIN.

There is a "checksum plugin" that needs to be saved to the Tunerpro "Plugins" folder. I believe the checksum plugin needs to match the OS.

Full write.. from https://pcmhacking.net/forums/viewto...101896#p101896

ALWAYS do a Test Write first, if you get any errors, think twice before proceeding.
An OS change is done using "Write OS, Calibration, & Boot" or "Write Full Flash (Clone)" menu option.

[FattyBlaster6]

Ok, I was able to successfully pull the current .bin file from the pcm today using LS Droid...yay! The PCM has same operating system as the .bin I was modifying 12212156. Looked up the VIN and it is out of an 02 Silverado. Thanks for redirecting me to the 6.0 .bin and the warning about test writing first (that I'm familiar with from my Subaru meddling)... I'm super greatfull to have guys like you helping to keep me from chasing my tail too long...LOL. So now I guess I'm back to searching for a new .bin, .ads, and checksum plugin which matches the OS. Thanks again!

[FattyBlaster6]

Starting to lose more hair here. Is there some kind of conspiracy to make it as difficult as possible to find files on this forum as possible? The LS Repository is a great ladder style index to search through but is just lacking the files relative to my build. I feel like the more I read on this forum the more confused I'm getting. Anyhow, I'm ready for my first startup and all I need is to upload a good .bin. Unfortunately for me this seems easier said then done.
I tried to attach both the 6.0 .bin and checksum .dll that I found to this post but I only see the .bin. The checksum .dll file description only refers to the pcm type and not the OS which I thought needed to match. I've added the .bin and .dll into the same folder as TunerPro as instructed. Hopefully I have the right files, and hopefully there in the right spots to interact with each other correctly.
Having zero luck finding the .ads or .adx file to add so I can view real time pid info? Seems to be referred to as both and is very elusive. I did an advanced title only search for ".ads .adx 12212156" and get zero exact matches.... Is that something that comes with the "key" that is issued when you register? I think I read somewhere that the registered version of TunerPro is the only one that allows real time pid viewing. However the TunerPro site says the registered version is exactly the same as the free version and only gets rid of annoying startup prompt. I registered this morning but haven't received any emails from Mark yet. Hopefully I get something from him soon.

Questions:

1. What is the best way to verify correct checksum? Right now all I know is to load .bin, modify it and then try to save it and hope for no error. Does the error mean I have to go back and modify all the tables again? Regardless, that is most likely what I will do.

2. I've been using the compare .bin feature to compare the above 5.7 file to the loaded 6.0 file and if any are different then copy from 5.7 and save. Is this a sound way to go about this?

3. Where is the .ads or .adx file found?

4. Does the checksum plugin have to match OS or PCM?

5. The 6.0 .bin I am trying to use has two VIN tables. The first has a funky lower case y in every cell/block. There is a warning about modifying the table only if the current VIN in the table is a proper VIN configuration which this clearly is not. VIN table 2 is an alternate and does appear to have a proper VIN. However, when trying to save or "commit to change" button on VIN table after modifying the number, for some reason the last number always reverts back to a 9 regardless of what I put there. What is going on there? Is this part of the checksum issue?

6. Anyone know if TunerPro Mark is EagleMark? Did he pass away in 2014? If so, who is now collecting the registration fees and issuing keys?

Thanks again guys!

[FattyBlaster6]

Just got an email with my registration Key from Mark Mansur Author of TunerPro. Clearly he is still alive.

Just tried to save the .bin file after adding the checksum plugin. Same thing:

" Error- One or more checksums could not be updated. Check checksum addressing, etc., for validity. "

Admittedly I have no idea what it means other than something isn't correct...DUNNO.
Guess I won't be getting my glorious first start today. Really have no idea what to do next. I see it did save a file but I assume there is something wrong with it and is probably not wise to try and flash it onto the pcm. Going to go find some Tylenol now... or maybe something stronger.

[FattyBlaster6]

Ok, so the Tequila last night must have helped clear my head... LOL. Tried to just save the 6.0 .bin without modifying it. It still threw the Checksum error. That tells me there is something not right with the file or the location of files. At this point I've collected a lot of "possible contender" files and it was becoming a mess. Also wanted to eliminate the possibility of any of these files causing background issues in TunerPro so I decided to delete all the files I had and start over again. While searching I came across this which really helped simplify things.

https://github.com/BoredTruckOwner/L...etting-Started

Except for the actual .bin files (not to say you couldn't get them here, I just happened to find them already on this forum), I believe I sourced all of the other files from here:

https://github.com/BoredTruckOwner/L...epository/wiki

After uploading all the files I placed them in there corresponding folders which TunerPro has setup already. .xdf in Definitions file, .bin in BIN file, checksum .dll in plugins folder, etc..

Then opened TunerPro, opened the 6.0 .bin, choose the correct XDF file.

Did a test save and NO ERROR! Yay!
Then modified a couple of tables and did another test save. Still NO ERROR... so I think we got that checksum problem figured out.
One of the tables I modified for testing was the alternate VIN table which I mentioned above in my previous post. The last digit for some reason would not save as what I put in the cell/block. In this case there was a 9 in that box but I wanted an 8. Every time I would hit execute or commit to change(save?) it would revert back to a 9. Then I noticed that the header for that table has options for Functions. It was set on offset +/- with a value of 1.0. first I tried to change the function to insert value but that resulted in weird numbers when I tried to save. Put it back to offset function with the value set to 00 and now it seems to be fine. When I "commit to change" the numbers now stay as I desired. Not sure why the offset was only affecting the last block, perhaps if I dig deeper there is an option somewhere to only affect desired boxes. I noticed all the boxes have different colors and maybe that is relative to that...

I am attaching the files I am currently using below. The 6.0 4l80e .bin is the one I am modifying and the 2002 l31 (5.7) .bin is the one I am comparing and copying tables from. These files are all for the 12212156 OS which I am running on the p01 ...0411 pcm. For some reason the checksum .dll files don't show up when attached so here is the link I found mine at.

LS_Based_Engine_Repository/.XDF Files/Checksum Plugins at master · BoredTruckOwner/LS_Based_Engine_Repository · GitHub
Hmm...weird when I paste the address here in post it is messed up but works fine when I post it in address bar. They really don't want make it easy...LOL. Just paste it into the google search and you'll find it.

Note: It would appear that TunerPro came with an XDF file named 6e.xdf which I replaced with the 12212156....xdf Not sure if that was causing any issues but I do notice the file sizes are vastly different with the 12212156 being almost 5 times larger (more info).

Ok, time to go back through all these Tables again and hopefully upload a good .bin to the PCM. Once I have it loaded I will then try viewing live data and see where I stand with this .adx file thing. Crossing fingers...LOL
Oh yeah, and I did come across this regarding the .adx
https://www.gearhead-efi.com/Fuel-In...unerPro-How-To

[FattyBlaster6]

Some Table questions:

1. Scaler-Engine Type: Says table should not be modified but gives engine options so I changed it to match 5.7. Was this wrong? Should I put it back to 6.0 even though I'm actually running an L31 5.7?

2. Scaler Table G1204 and G1205 for Tach High and Low Pulses- The 6.0 bin has the number 6 in both tables with says it is normally used for 4 cylinders. Should it not be number 3 which is normally used for 8 cylinders? The 5.7 has a 1 selected and is probably because its using the 4x reluctor so that won't work. Im using the 24x reluctor. Has to be 6 or 3. Considering I don't even have a Tach I'm just going to leave it a 6 for now. It'll be the first thing I suspect if I have timing issues though.