UPM was airflow per minute or the axis used on most of the tables. In my case the concern is mostly just the ignition table. I've done some research and found that the car has a VR6 MAF and "green giant" 440cc injectors installed. I expect this explains why the car never goes above 50% load yet the fuel is perfect.

I'm thankful for the help people have been providing but a simple answer "won't work" explains nothing to me. At present the car runs, starts, idles and drives reasonably well considering. The load numbers do need to be corrected so the timing map can be used properly but I'm not seeing anything here that is so critically wrong.

Why will the NA firmware not run boost?

Ok, I understand. I know that a number of NA cars have items that actively prevent you from going into boost so I needed to make sure it would not suffer from that.

The car arrived running like crap and it blew up an engine before it came to me. While I'd love to do a perfect job this project is being done as a bit of a favour and to get some bosch experience. I pulled a bunch of timing out of it to stop it from detonating and the guy already thinks it's amazing. With limited resources and no budget to replace sensors, ecu and wiring for a boosted ecu there are not many options. Hope this explains why I didn't go ahead and swap it over to a 1.8t. I'm not going to pay money to work on a guys car.

I'm going to rescale the injector and MAF table to gain the amount of load I need. If the torque system gets in the way too much then I'll strike a balance between the extra 30% power it needs by underscaling them slightly.

With the MAP/Injectors scaled correctly can anyone point out which tables I'm going to need to adjust for the torque system? In other ECUs I'm used to having a gas pedal (APS) versus torque or airflow type table that attempts to achieve the desired airflow based on the APS position. I've been reading the functions descriptions documents but it feels like there should be a strategy document like seimens does to better explain each module and how it operates.

Personally, what he's achieved so far is well beyond that of a noob, and his understanding of terms and what he's doing seems to be a little underestimated. 

I really think for what he's done so far deserves a pat on the back; and I don't think he's "that" nooby.  It's been said time and time again that this isn't the right method for doing what he's doing, we get that. 

I'd try and rescale the injectors and MAF, but I think you're going to hit a limit, so while I'm all in for trying, I don't think it's gonna work.  Try it first and see how you get on, and document what you're doing and how you're finding it.

If it doesn't work, stop spending time on it, hand it back and get on with more important things in your shop.

I don't like to go on a site and talk about what I know and what I've done in the past. It is far from my first time at the rodeo and I've worked on ECUs and tuning professionally for over 15 years. I've written firmware for standalone computers and I've worked on OEM software so I have a pretty good idea how most strategies work and I've seen Bosch is pretty similar to siemens which I know a thing or two about.

Back on topic. I tried following the instructions for rescaling the MAF. Google told me that the stock size was 65mm and that the VR6 was 73mm. So I tried a 26% gain. I also hacked up a real VR6 file but was told that copying the MAF table from that would not work. I wasn't very successful at finding the stock size injectors to scale the injector size so after a few tries I managed to get about 10%. The load is now maxing out at 70% so it's going in the right direction.

The car idles with a -15% o2 correction but driving it's more like -2% so I think I will go find a file from a car that had the green giants from factory and steal the latency table. For the MAF I'm just going to scale it another 10% to expand the range of the load value. The driveability has gotten a bit better too. Given that this thing is probably going to add only 30% more power I don't think a maximum of 100-110% load is going to have any significant downsides in driveability.

I also invested some time and wrote a tool to decode my collection of A2L/.hex files and find a file that is better matched so in a few hours I managed to buid a competent mappack. I have had no success with me7logger or visualme7logger. I've been logging the blocks using eurodyne.

I also hacked up a perl script to process the logs. The output looks a bit like this:

./stft.pl *.csv
Processing 1445815696.csv
Processing 1445821450.csv
           0.00  500.00  750.00 1000.00 1250.00 1500.00 1750.00 2000.00 2250.00 2500.00 3000.00 3500.00 4000.00 5000.00 5500.00 6000.00 7000.00 
   0.00  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------ 
  32.00  ------  ------    5.08    6.58    7.75    1.90    7.91    8.24    5.64    5.88    3.70   -3.71   -3.60   -1.17  ------  ------  ------ 
  48.00  ------  -11.59   -0.99    1.34    1.66   14.73   -0.72   -0.98    1.16    3.35    0.43    1.55   -0.78  ------  ------  ------  ------ 
  64.00  ------  ------    0.49    2.68   -1.70    6.88    1.60   -3.84   -0.97    2.41    0.09    2.32   -0.59  ------  ------  ------  ------ 
  80.00  ------  ------   -0.48    1.35   -2.34   -0.40    3.50    0.09   -0.66   -0.17    1.51    2.70   -0.39  ------  ------  ------  ------ 
  96.00  ------  ------   -1.51    0.29   -0.64   -0.61    2.95   -1.57    0.92   -0.06    0.31   -0.29  ------  ------  ------  ------  ------ 
 128.00  ------  ------    0.20   -0.72   -0.69   -1.58   -2.42   -2.86    2.37    0.72    6.79    8.12  ------  ------  ------  ------  ------ 
 160.00  ------  ------   -2.93   -0.78   -1.19   -2.28   -3.91    0.08    6.02   -0.18    8.74   14.71  ------  ------  ------  ------  ------ 
 192.00  ------  ------  ------   12.89   -2.34   -3.16    8.05    6.28    5.00   -0.09   -2.00  ------  ------  ------  ------  ------  ------ 
 224.00  ------  ------   13.28  ------  ------   -1.95    1.09    3.20    1.80    3.61   -2.93  ------  ------  ------  ------  ------  ------ 
 256.00  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------ 
 288.00  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------  ------ 

Excuse the fact this example is not actually from a ME7 but you get the idea.

Does the stft perl script average values for every load/rpm from a long log file to present that table? If so, would you mind sharing it?

I LOVE IT

BTW you might want to exclude accell/decel conditions as well, not sure how much filtering it does, but it should throw out samples where rpm or load is changing...

or, even better, generate accel/decel graphs separately!

not talking about total throttle off or WOT, there are partial throttle cases where you are still closed loop (even narrow band)