setting up tuner pro rt question
These are all text files and you can open them in NotePad or any other plain text editor.
It's definitely not HTML either. Those files always have "<html>" somewhere near the beginning and end with "</html>".
Last edited by Cliff Harris; Jun 14, 2013 at 01:55 AM.
Yes, that is what I found as well. I not a computer guy, and there is a learning curve here for me. Any suggestions on what to do would be appreciated.
I am not a computer guy either. I have been struggling for weeks to get Tunerpro RT V5 running for my 95 LT-1.
You can not double click on the blue named files on the tunerpro web site. You must RIGHT click and save it that way. The words will be different depending on the browser your using. In firefox right click and then click on save link.
In weeks, I have not received any useful help either from the Tunerpro forum or on this forum. Seriously, nothing that a non computer guy can understand. That all changed last night.
I have been googling for answers for weeks. I live very remote in the mountains and my internet connection is dial up at 24.K. Last night I found a Tunerpro RT V5 Tutorial on the LS1Tech forum. The person who wrote the tutorial did a wonderful job, along with screen captures all the way. He even gives you the asd file with his dashboard so you dont have to make one. Granted his tutorial is for a LT-1 engine, but you just select the proper files for your engine and then follow his tutorial.
I set up my computer and tunerpro rt V5 last night per his tutorial, this morning I took it to the shop and was scanning my 95.
Here is the direct link to the tutorial, Read it thru first, then follow his examples (dont be creative) LOL.
http://ls1tech.com/forums/lt1-lt4-mo...-tutorial.html
8Valve
Last edited by 8valve; Jun 14, 2013 at 05:16 PM. Reason: typo
I'm not sure what the $da3.xdf file is.
I use a $da2.xdf defintion file to tune my supercharged 93 6spd vert.
The definition file is a critical item and it must be decoded correct. Some of them out there are hacks. So beware you could screw your car up if you get some bogus file.
There are a couple $da2.xdf files I know about floating around out there. Id be happy to send you the one I am using to read the .bin that I have used/modified for my supercharged car. Note I'm still running the stock 1 bar map sensor so this definition file shld work fine on your car as well.
This doesn't apply to you, but I'm told that tunercat has a 2 bar $da2 definition file out there fornthe boost guys. Id love to experiment with that because right now I have to assume 1 bar is full 13 psi boost.
Send me your email in a pm and I will send you the best $da2.xdf file I know about. Again I caution to be aware that sometimes the .bin file needs that same .xdf file that was used to tune it. So... you might want to spend some time going over your .bin to make sure nothing shows up wrong when you read it with a different .xdf file than what was used to tune it.
It's the .BIN file's job to screw your car up (before anybody gets weird: just kidding!). That's the file that you're going to put into your ECM. Make sure you back up everything so you can put it back to original if something goes wrong.
The Best of Corvette for Corvette Enthusiasts
I am confused by TunerPro using the DA3.xdf file for the 93 Y body and the DA2.xdf file for the 92 Y body.
Given that I have both cars, I am going to keep using TunerCat so I don't get confused. No reason to have problems by screwing up the tune in one or the other.
I am on the 54th iteration of my Y body tune and around the 30th iteration of my F body tune. Both are 383s built by the same shop with the same parts but the tunes do have to be a bit different to work well.
Confusion with a definition file is not a good thing.
Perry
















