TunerPro RT help
#1
Junior Member
Thread Starter
Join Date: Jun 2005
Location: Sevierville, TN
Posts: 35
Likes: 0
Received 0 Likes
on
0 Posts
Car: 84 Z28, L69
Engine: 5.0 HO
Transmission: 700R4
TunerPro RT help
Some background is in order. I have TunerPro RT up and running on my laptop because I use it on my Turbo Buick.
With the proper .ads and .xdf files, can it be hooked up to my 84 Z28?
If so, does anybody have the needed .ads and .xdf files for this application?
And what type of hookup do I need from the laptop to the ALDL connector?
Can this be done?
TIA
With the proper .ads and .xdf files, can it be hooked up to my 84 Z28?
If so, does anybody have the needed .ads and .xdf files for this application?
And what type of hookup do I need from the laptop to the ALDL connector?
Can this be done?
TIA
#2
TGO Supporter
iTrader: (1)
Re: TunerPro RT help
I dont believe so. Here is a list of definition files from TP.
http://tunerpro.markmansur.com/downloadBinDefs.htm
Now I looked at TC. Same story. http://tunercat.com/tnr_desc/ecm_sup.html
I see 1984 Buick V6 turbo is supported! Convert !
If you want to tune you will need to swap in a supported ECU. GM 7747 and 8746 and EBL (dynamicefi.com) come to mind. Something tells me you need to repin your harness(see TurboCity, Painless Wire) to do so OR modify the ECU board called HAM see Speedtronics.net
http://tunerpro.markmansur.com/downloadBinDefs.htm
Now I looked at TC. Same story. http://tunercat.com/tnr_desc/ecm_sup.html
I see 1984 Buick V6 turbo is supported! Convert !
If you want to tune you will need to swap in a supported ECU. GM 7747 and 8746 and EBL (dynamicefi.com) come to mind. Something tells me you need to repin your harness(see TurboCity, Painless Wire) to do so OR modify the ECU board called HAM see Speedtronics.net
#3
Moderator
iTrader: (1)
Join Date: Mar 2002
Location: Chasing Electrons
Posts: 18,432
Likes: 0
Received 227 Likes
on
212 Posts
Car: check
Engine: check
Transmission: check
Re: TunerPro RT help
Some background is in order. I have TunerPro RT up and running on my laptop because I use it on my Turbo Buick.
With the proper .ads and .xdf files, can it be hooked up to my 84 Z28?
If so, does anybody have the needed .ads and .xdf files for this application?
And what type of hookup do I need from the laptop to the ALDL connector?
Can this be done?
TIA
With the proper .ads and .xdf files, can it be hooked up to my 84 Z28?
If so, does anybody have the needed .ads and .xdf files for this application?
And what type of hookup do I need from the laptop to the ALDL connector?
Can this be done?
TIA
The only downside is that most likely a 10K resistor will be required between A&B on the ALDL connector. This is required to get the CCC ECM to send data. And of course, also puts the ECM into diagnostic mode which changes how it runs the engine.
Check the Tuning Guide Book sticky for information on the CCC setups. There may be something there that will help with the required files and such.
RBob.
#4
Junior Member
Thread Starter
Join Date: Jun 2005
Location: Sevierville, TN
Posts: 35
Likes: 0
Received 0 Likes
on
0 Posts
Car: 84 Z28, L69
Engine: 5.0 HO
Transmission: 700R4
Re: TunerPro RT help
Thanks guys. I was afraid the carburated 84 L69 wouldn't be supported. No big deal really. I just thought it would be another use for the TunerPro RT that I'm running on my 86 GN.
Since I'm trying to sell my 84 Z, I really don't want to have to change anything just to data log. It's almost 100% original and I'd like to keep it that way.
Since I'm trying to sell my 84 Z, I really don't want to have to change anything just to data log. It's almost 100% original and I'd like to keep it that way.
#5
Re: TunerPro RT help
There are some files on moates download pages.
http://www.moates.net/fileman/index....ock%20Binaries
Didn't see any .xdf files, but that particular set of .bin files is for the '82-87 Camaros with the ZZ4 engine kit and CCC if I interpret them correctly.
Hope that helps....
http://www.moates.net/fileman/index....ock%20Binaries
Didn't see any .xdf files, but that particular set of .bin files is for the '82-87 Camaros with the ZZ4 engine kit and CCC if I interpret them correctly.
Hope that helps....
Trending Topics
#8
Member
Join Date: Jun 2004
Posts: 157
Likes: 0
Received 0 Likes
on
0 Posts
Car: 93 GMC Typhoon
Engine: 4.3L V6 Turbo Charged
Transmission: 4L80e
Re: TunerPro RT help
From my understanding it just tells you what addresses it HIT, and not the data at those addresses. Also you are talking about hundreds of hits per second. I need to play with the address tracing some more to make sure this is correct.
#10
TGO Supporter
Join Date: Jan 2000
Location: In your ear. No, the other one.
Posts: 1,861
Likes: 0
Received 0 Likes
on
0 Posts
Car: '89 Trans Am WS6
Engine: 350 TPI
Transmission: T5WC
Axle/Gears: 3.08 posi
Re: TunerPro RT help
That would "kind of" work, but would be very convoluted and prone to error and innacuracy. For one, address hit tracing misses about 75% of actual hits (it's good for rough indication of where you're running in a table, when ALDL data isn't available for the correlation). Second, the value for an address hit is relevant only to that value in the calibration, and that doesn't necessarily reflect the value in RAM that the ECU is actually functioning off of. For instance, an address hit might indicate that a value in the spark table was requested, but that value in the table might not (read: probably doesn't) reflect the final spark that's being outputted, since the final spark takes into account spark correction, base timing setting in cal, ALDL spark, etc.
Good thinking though!
#11
Moderator
iTrader: (2)
Re: TunerPro RT help
What's "address hit tracing" and how do I get it?
That would "kind of" work, but would be very convoluted and prone to error and innacuracy. For one, address hit tracing misses about 75% of actual hits (it's good for rough indication of where you're running in a table, when ALDL data isn't available for the correlation). Second, the value for an address hit is relevant only to that value in the calibration, and that doesn't necessarily reflect the value in RAM that the ECU is actually functioning off of. For instance, an address hit might indicate that a value in the spark table was requested, but that value in the table might not (read: probably doesn't) reflect the final spark that's being outputted, since the final spark takes into account spark correction, base timing setting in cal, ALDL spark, etc.
Good thinking though!
That would "kind of" work, but would be very convoluted and prone to error and innacuracy. For one, address hit tracing misses about 75% of actual hits (it's good for rough indication of where you're running in a table, when ALDL data isn't available for the correlation). Second, the value for an address hit is relevant only to that value in the calibration, and that doesn't necessarily reflect the value in RAM that the ECU is actually functioning off of. For instance, an address hit might indicate that a value in the spark table was requested, but that value in the table might not (read: probably doesn't) reflect the final spark that's being outputted, since the final spark takes into account spark correction, base timing setting in cal, ALDL spark, etc.
Good thinking though!
It was just an idea, but I guess it won't work.
Thread
Thread Starter
Forum
Replies
Last Post