When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I know this can happen, I did it before, but I am a little bit rusty on this one. I recently made 2-30 minute datalogs, road tests, on my '90 Y-body L98 car. The BLMs are high, (lean) like around 150+. I have the latest rev of TP, and I want to get the running average of BLM vs VE., so I can copy paste the values into excel sheet, and get some new VE values. Running a modified S_AUJP v6.XDF, if that helps. Havent done any tuning on this ride in 7 years, but have tried to keep up with things. Been mostly focusing on my '88 F-body, which is a MAF car. Thanks!
Any help here? Shouldnt be that hard to do.....i can look at any data parameter, in the monitors screen, but i need to see the average BLMs vs VE in the histogram. Then I can copy/paste into spreadsheet, to modify the VE tables to get my BLMs in line. I know there is a way......
Thanks,
So, FYI, this issue has been resolved. Basically the ADX that I was using, to look at a log file had a problem, or else the histogram tables were not setup correctly. I got ahold of a different ADX file, a version of S_AUJP, from a fellow TGO'r. Thanks ULTMZ!!! You basically play back the log file, and let the histogram tables fill in. If you have a long datalog, you can speed up the playback. However, I cannot connect to the ECM with this newer ADX file, get the usual errors and screen flashes, so I have log data with a different ADX, namely 8D_90-91_Corvette.adx, which connects fairly quickly, and produces reliable log data. I will have to study the 2 ADX files, and see what the differences are......
. . . . However, I cannot connect to the ECM with this newer ADX file, get the usual errors and screen flashes, so I have log data with a different ADX, namely 8D_90-91_Corvette.adx, which connects fairly quickly, and produces reliable log data. I will have to study the 2 ADX files, and see what the differences are......
Interesting. Your observation seems opposite of what should be observed. You should have difficulty using the Corvette ADX if that's the one that's working because it contains Central Control Module (CCM) and possibly Body Control Module (BCM) commands at the top of the ADX only applicable to features of the 'vette but not your car. This is why $8d Corvette users upgrading to S_AUJP have to ensure the commands in their ADX are moved to the S_AUJP ADX. Again, interesting. Might compare commands.
Interesting. Your observation seems opposite of what should be observed. You should have difficulty using the Corvette ADX if that's the one that's working because it contains Central Control Module (CCM) and possibly Body Control Module (BCM) commands at the top of the ADX only applicable to features of the 'vette but not your car. This is why $8d Corvette users upgrading to S_AUJP have to ensure the commands in their ADX are moved to the S_AUJP ADX. Again, interesting. Might compare commands.
This is an easy mystery to solve, Elky. I AM connecting to a Corvette!! Original post, above, states that, I am testing my L98 1990 Corvette, which is a Y-body car. This car has a speed density system, not MAF like my '88 IROC. So just tonight, i made a road scan connecting with the 8D_Corvette.ADX, logging data for about 14.5 mins. It connects up fairly quickly, stays connected, and gives me reliable data. Then, I move the data over to my newer Win10 laptop, and use a version of S_AUJP v5......adx to look at the data. I playback the log file, and let the histograms fill in.
Now, what you are saying, about $8D corvette users switching to S_AUJP, having to copy the commands in the ADX over, is likely what i need to do. I have looked at them, comparing, and there many differences. Not sure how to copy them over.....could use some help with that.
This is an easy mystery to solve, Elky. I AM connecting to a Corvette!! Original post, above, states that, I am testing my L98 1990 Corvette, which is a Y-body car. This car has a speed density system, not MAF like my '88 IROC. So just tonight, i made a road scan connecting with the 8D_Corvette.ADX, logging data for about 14.5 mins. It connects up fairly quickly, stays connected, and gives me reliable data. Then, I move the data over to my newer Win10 laptop, and use a version of S_AUJP v5......adx to look at the data. I playback the log file, and let the histograms fill in.
Now, what you are saying, about $8D corvette users switching to S_AUJP, having to copy the commands in the ADX over, is likely what i need to do. I have looked at them, comparing, and there many differences. Not sure how to copy them over.....could use some help with that.
Sorry, I misread the post about having vette. Makes sense now. There is no way to "copy" the Commands or even the actions within each command. Grrr. The only way short of using a text editor, which should not be done, is to literally add to the S_AUJP ADX commands in your ADX that are not in S_AUJP. The easiest way is to load 2 instances of TPro (Tools>Custom Tools>New Tunerpro instance). Minimize each and move so they are side by side. Load corvette ADX on left and S_AUJP on right. Open Commands area. Add any items in vette ADX not in S_AUJP. You should not have to remove any S_AUJP commands unless the title/action conflicts with S_AUJP. Below are commands from a '90 vette ADX I have (yours may be different) and v7 S_AUJP. I see no deletions that need to be made. Don't worry about all those in S_AUJP that vette does not have.
90 'Vette
v7 S_AUJP
When you select to add a command, you'll get a menu like that below. I can find no way in TPro to determine what type of command it is other than to compare the format of vette command with that provided by one of the 5 selections below, and use that one. For example, the "Connect" command which is absolutely critical is a "Macro" because the vette format matches a Macro format. Repeat for all other commands. Where actions of common commands are the same, no need to do anything. but there may be subtle differences like those in "Mode 1 ALDL Dump" items:
One more thing. If you're going to do all this work, why do it to an ADX that's years out of date. Why not upgrade to v7 S_AUJP. That ADX provides much more valuable information, but you'll also need to use the v7 BIN, which provides many more additional features, and transfer your calibration to it. It's simply a matter of copying an area of your BIN to S_AUJP just like doing a cut and paste with any text editor, but using a hex editor. If you don't feel comfortable doing it yourself, post your bin and I'll do it. Takes 1 minute.
Sorry, I misread the post about having vette. Makes sense now. There is no way to "copy" the Commands or even the actions within each command. Grrr. The only way short of using a text editor, which should not be done, is to literally add to the S_AUJP ADX commands in your ADX that are not in S_AUJP. The easiest way is to load 2 instances of TPro (Tools>Custom Tools>New Tunerpro instance). Minimize each and move so they are side by side. Load corvette ADX on left and S_AUJP on right. Open Commands area. Add any items in vette ADX not in S_AUJP. You should not have to remove any S_AUJP commands unless the title/action conflicts with S_AUJP. Below are commands from a '90 vette ADX I have (yours may be different) and v7 S_AUJP. I see no deletions that need to be made. Don't worry about all those in S_AUJP that vette does not have.
90 'Vette
v7 S_AUJP
When you select to add a command, you'll get a menu like that below. I can find no way in TPro to determine what type of command it is other than to compare the format of vette command with that provided by one of the 5 selections below, and use that one. For example, the "Connect" command which is absolutely critical is a "Macro" because the vette format matches a Macro format. Repeat for all other commands. Where actions of common commands are the same, no need to do anything. but there may be subtle differences like those in "Mode 1 ALDL Dump" items:
One more thing. If you're going to do all this work, why do it to an ADX that's years out of date. Why not upgrade to v7 S_AUJP. That ADX provides much more valuable information, but you'll also need to use the v7 BIN, which provides many more additional features, and transfer your calibration to it. It's simply a matter of copying an area of your BIN to S_AUJP just like doing a cut and paste with any text editor, but using a hex editor. If you don't feel comfortable doing it yourself, post your bin and I'll do it. Takes 1 minute.
HTH, Elky
It does help, Elky. you certainly know your stuff, with this business. You said what I was afraid you were going to......about not being able to copy commands over easily. The commands you listed, in both ADXs, are exactly what i am seeing. It must be just one certain command, in my vette ADX, that connects up reliable. I should be able to load the 2 instances of TP, and insert the new (corvette) commands into the S_AUJP ADX. Maybe i just try one at a time, and see if I can connect. I certainly dont want to mess things up.
As far as updating, I am using version 6, for my XDF, and I started with a version 6 bin. When covid started last year, i had some time to switch things over. As far as version 7, ya, I could go there, I notice you keep updating things.....but my vette is mostly stock, and will likely stay that way.....dont need turbo features or launch control......there are so many cool things in S_AUJP.....i just dont need them all! I did switch to using the extended VE table. I just want my ride to run the best it can.....just made a new chip tonite...put HM back in, as I took it out to tune part throttle BLMs...pretty happy with what i got. Ya, I know, some of my methods are outdated, but they work for me. The older Corvette ADX connects and stays connected, giving me good data. Maybe this winter I will have time to upgrade!
Tune On!
It does help, Elky. you certainly know your stuff, with this business. You said what I was afraid you were going to......about not being able to copy commands over easily. The commands you listed, in both ADXs, are exactly what i am seeing. It must be just one certain command, in my vette ADX, that connects up reliable. I should be able to load the 2 instances of TP, and insert the new (corvette) commands into the S_AUJP ADX. Maybe i just try one at a time, and see if I can connect. I certainly dont want to mess things up.
As far as updating, I am using version 6, for my XDF, and I started with a version 6 bin. When covid started last year, i had some time to switch things over. As far as version 7, ya, I could go there, I notice you keep updating things.....but my vette is mostly stock, and will likely stay that way.....dont need turbo features or launch control......there are so many cool things in S_AUJP.....i just dont need them all! I did switch to using the extended VE table. I just want my ride to run the best it can.....just made a new chip tonite...put HM back in, as I took it out to tune part throttle BLMs...pretty happy with what i got. Ya, I know, some of my methods are outdated, but they work for me. The older Corvette ADX connects and stays connected, giving me good data. Maybe this winter I will have time to upgrade!
Tune On!
Understand and makes sense. As you've figured out with using S_AUJP v6 that many don't understand is that once an existing calibration is copied to a S_AUJP bin, it will operate exactly as before without any of the added features and may report additional data via the ADX. But it makes those features available if later desired.
Understand and makes sense. As you've figured out with using S_AUJP v6 that many don't understand is that once an existing calibration is copied to a S_AUJP bin, it will operate exactly as before without any of the added features and may report additional data via the ADX. But it makes those features available if later desired.
Yes, agree on that. Copying over an existing cal is not that hard to do, and it is the right thing to do, when upgrading........However, a little more to my story. So last year, after converting to S_AUJP, I just figured my existing tune was fine, as i had it pretty good previously. Thus, I never did any datalogging, last year on the vette. I was spending more time with my IROC. This year, finally got a chance to datalog, and WTH, my tune was quite lean, BLMs were high, like in the 150 range. So i had some work to do. Now given that I hadnt datalogged my vette, much, even BEFORE i switched, I didnt think it would be that far off......after all, i hadnt really done anything to the vette, that would warrant a new tune.
