tables.jpg
Okay, so one thing at a time.
I do not see a "6E_Extended.xdf" on Scott Hansen's site, only 6E.xdf. Scott knows his stuff so if you did get your XDF from him, I have no reason to believe it is incorrect. The labels in your screenshot do not match the labels in mine, so we're definitely not using the same XDF, but again I'd trust Scott's work.
Okay, so now that I see the table I probably know where your confusion is coming from regarding inputted values. As I mentioned earlier, the actual values you see are calculated from 8-bit or 16-bit data (0-255 or 0-65535). That is the maximum numer of possible values, but what that translates to in the particular table depends on the equation GM used. Do open the "Edit Parameter XDF Info" on a table you're interested in and click Conversion. You'll see that for the Spark Advance table, the equation to convert the binary data to human-readable data is:
0.351567 * X + 0.000000
Where "X" is a binary data value. If you right-click in a table and click "Show Raw Hex" you can see what the raw hex data value of a cell is. In my screenshot, the upper-leftmost cell has a hex value of 3D. This converts to 61 in decimal. 61 * 0.351567 = 21.445587, which rounded to the second place gives you 21.45, which is exactly what's shown in my table. That's how this conversion works. Now, let's say I change that hex value from 3D to 3E, just increasing it by 1. Now it's 62 * 0.351567, which comes out to 21.797154. That means any value between 21.45 and 21.80 will be impossible to enter, because the data literally cannot represent it. It can only represent 21.45 or 21.80 but nothing in between.
Now, here comes the tricky bit. On my XDF, this particular table is set to have a maximum human-readable value of 43.00 degrees of spark advance. But you can see in my screenshot that from the factory, the table has values of up to 49.92 degrees! Now obviously it'll never hit that because the maximum spark advance is set to 39.73, but still, the fact remains that the factory data in the table goes way higher. So, what happens if I try to modify the stock table? Say, drop a value from 49.92 to 48 degrees? When I commit changes and then reopen the table, my 48 degrees will magically become 42.89 degrees! This is because the XDF has set a limit for all user-created inputs to 43, and the closest value less than or equal to 43 is 42.89.
You can raise this specific limit by clicking "Edit Parameter XDF Info" and then changing the number in "Use High Range" on the right in the General tab. This is what sets TunerPro's limit for a particular cell. It sounds like your XDF has that limit set to 46 instead of 43.
If your tuner told you nothing about stacking, I wonder if the tunes he was sending you were pre-stacked? I know I'd do the same thing if I knew my end-user was using a chip larger than the BIN. It's easy to tell the difference; a factory BIN is 16KB, while a pre-stacked BIN (like the second one I posted) would be 64KB.
As for the specific issue with smog and valvetrain, yes, if the engine was not fully mechanically sound when doing the tune that will 100% screw up the tune. Fixing vales that weren't opening all the way means you're getting a lot more air into the combustion chamber than you were before, but if your tune was expecting less volumetric efficiency (less airflow into the chamber), then it'll be delivering less fuel than the air you're actually getting in. Classic lean condition, so you're probably spot on the money.
What you can do as an easy test is to just change fuel across the board, and lower spark advance a little across the board. Leave the big tables alone. Just change the Maximum Spark Advance to something lower (factory on the Corvette is 41.84, so try that), and then change "Single Fire FI Size @ 40 psig" and "Double Fire FI Size @ 40 psig" both to a slightly smaller number. This will trick the computer into thinking you have smaller fuel injectors than you actually do, which will have the effect of increasing fuel flow uniformly across the entire fueling table.
Now, here's the bombshell. While getting you information for this post I actually found that the problem may in fact be the ARAR BIN itself. I've never used it; I just had it downloaded from this forum, same as you did. But comparing it against other $6E BINs it has a bunch of data that is just plain wrong. I don't know why it's so wrong, but it's incredibly wrong (for example, it reads as having a rev limit of only 1182 RPM, and fuel injectors that are only 6 lb/hr instead of 22!!!).
I've attached an ARAP file to this post. It's got the same modifications as before (no VATS, cooling fan set to Normally Open), and is stacked for your chip. Give it a whirl.
Reply With Quote
Bookmarks