listings for tunurpro rt
Thread Starter
Junior Member
Joined: Dec 2004
Posts: 50
Likes: 0
From: stamford ct.
Car: 88 iroc-z
Engine: 5.7 zz4
Transmission: megaraptor 700r4
Axle/Gears: 3.73 10 bolt posi
listings for tunurpro rt
hello new to tuning have a 88 iroc with stock ecu modified engine
i have been reading a lot of the posts ,but am still learning.
using tunurpro rt , dont understand a lot of the listings in the bins
most of the constants are pretty easy to understand(example:
fan on,fan off,vatts enable,etc.) but their area lot of others that are listed that i have no idea what they mean?? is their a list of definitions plain english explaination of what they all are???
thank , any help whould be great!!!
i have been reading a lot of the posts ,but am still learning.
using tunurpro rt , dont understand a lot of the listings in the bins
most of the constants are pretty easy to understand(example:
fan on,fan off,vatts enable,etc.) but their area lot of others that are listed that i have no idea what they mean?? is their a list of definitions plain english explaination of what they all are???
thank , any help whould be great!!!
Joined: Apr 2004
Posts: 3,180
Likes: 3
From: Browns Town
Car: 86 Monte SS (730,$8D,G3,AP,4K,S_V4)
Engine: 406 Hyd Roller 236/242
Transmission: 700R4 HomeBrew, 2.4K stall
Axle/Gears: 3:73 Posi, 7.5 Soon to break
That is just part of the learning curve.
Basically its like this...
A bin is hacked and documented as to the addresses of the "adjustable" calibration items. (spark, fuel...)
The ECU or XDF (TDF if TunerCat) file is a roadmap of sorts to this informations location within the bin file.
It is a format that lets you say you want to edit an item by a description that you can understand.
First you need to know "What does this address do" in the operation of the program.
If you don't know what it does, Don't mess with it!
You will make matters worse and you will be chasing your tail because you don't know what should have happened because of the change you made.
Instead, Do some searching and grap a copy of a documented hac of the bin you are running and try to understand what it does.
The ECU/XDFs are created by people mostly as individuals. Some files are better than others, and should be checked if things don't show the reaction/result of a change. This leads you back to more investigation to know "what does it do".
To make matters worse, the author of the ECU/XDF file can call the function anything they desire. Most of the time the text is the same as the hack document but the same function can have a bunch of similar names within different ecu's and make it confusing when you ask a question about that item.
Most of the common bins have existing ecu files out there and should be able to be found with some searching.
Best bet is to use an existing file that "seems" to be the most widely used and do some checking if the file indeed makes sense according to a hac.
If you come across something that doesn't seem correct, ask the question. Then one more thing with that particular file is enhanced and can be documented so the next guy is that much farther along when starting out.
Hope that helps
Basically its like this...
A bin is hacked and documented as to the addresses of the "adjustable" calibration items. (spark, fuel...)
The ECU or XDF (TDF if TunerCat) file is a roadmap of sorts to this informations location within the bin file.
It is a format that lets you say you want to edit an item by a description that you can understand.
First you need to know "What does this address do" in the operation of the program.
If you don't know what it does, Don't mess with it!
You will make matters worse and you will be chasing your tail because you don't know what should have happened because of the change you made.
Instead, Do some searching and grap a copy of a documented hac of the bin you are running and try to understand what it does.
The ECU/XDFs are created by people mostly as individuals. Some files are better than others, and should be checked if things don't show the reaction/result of a change. This leads you back to more investigation to know "what does it do".
To make matters worse, the author of the ECU/XDF file can call the function anything they desire. Most of the time the text is the same as the hack document but the same function can have a bunch of similar names within different ecu's and make it confusing when you ask a question about that item.
Most of the common bins have existing ecu files out there and should be able to be found with some searching.
Best bet is to use an existing file that "seems" to be the most widely used and do some checking if the file indeed makes sense according to a hac.
If you come across something that doesn't seem correct, ask the question. Then one more thing with that particular file is enhanced and can be documented so the next guy is that much farther along when starting out.
Hope that helps
Thread Starter
Junior Member
Joined: Dec 2004
Posts: 50
Likes: 0
From: stamford ct.
Car: 88 iroc-z
Engine: 5.7 zz4
Transmission: megaraptor 700r4
Axle/Gears: 3.73 10 bolt posi
i am using tunerpro rt with a ( 6e or Ge xdf ) does this sound right?
the xdf came with the tunerpro. i dont understand what certin things do or what they are ??
example:
spark correction-LV8 vs coolant temp
accel enrich%BPW factor vs async pulse
what is lv8?? what is %bpw factor??? what is async????
am i going about this the correct way ? or am i already screwed up before i even started??
the xdf came with the tunerpro. i dont understand what certin things do or what they are ??
example:
spark correction-LV8 vs coolant temp
accel enrich%BPW factor vs async pulse
what is lv8?? what is %bpw factor??? what is async????
am i going about this the correct way ? or am i already screwed up before i even started??
Last edited by spacgost79; Jun 1, 2005 at 09:43 PM.
Thread
Thread Starter
Forum
Replies
Last Post
Dragonsys
Engine/Drivetrain/Suspension Parts for Sale
2
Sep 25, 2015 03:51 PM





