I think the gist of it is the values in Optimum need to equal (or exceed) the Scaling in Torque to Load. But I'm not sure exactly what drives Optimum, and if I/we go far enough to hit that last row? In my case Tq to Load scaling is 0-80% so if the values in Optimum are 80 in the bottom row I "believe" that puts me on the 80%/max row in Tq to Load. But am I really hitting that last/max row in Optimum? I have raised those #'s and netted nadda so I'm guessing I am hitting it. Or maybe my Torque to Load is set higher than I'll ever get so a 10% loss in math didn't matter? So frustrating not knowing what this stuff is and not being able to see the output math. Trial and error testing is iffy at best. I have similar equipment at work but there I can plug in false values and instantly see what the output is. With HP, or at least my car, I not only can't, but I can't trust the torque reading either. This week for example I was making full power but the torque readings were ~15% lower than last week. I have to measure my speed gains per second in the Scanner to see if it's running right, but then to throw another wrench in there I don't know how far off the speed data is, or if it's consistently off or not. It's correct at steady state, but the faster the change the less I trust it. Same with RPM and other data which I just a post about
:
https://forum.hptuners.com/showthread.php?102508
Since you gained power by raising Optimum scaling, then maybe it works differently in an Audi? I dunno, just that raising the Opt scaling, which I did at least three times, all netted less power. I raised my 180 scaling to 190 and 200, and 190 lost power and 200 lost even more, and I'd estimate it was about the same % power loss as the difference in those #'s, or more. I can only assume raising them to 250, where my Tq to Load values are now, would kill it. Yet somehow it works for you? I dunno, I think that's what you meant in that last part.
As for Optimum Torque (Monitoring), I have its scaling back to the oem 185 but I lowered the values in the max row 10% lower (x.9) and it seems to do the same as oem values but raising the scaling. So either way, raising scaling or lower values net the same result for me, which, imo, is changing the math so the torque # is lower so the boost/power go up. If it were me I'd leave Optimum and (Monitoring) scaling and values oem and just bump your Tq to Load as needed. That way your torque reading should be more accurate? If Tq to Load can't hit the mark you want, then I'd adjust Opt (Monitoring) like I did to trick it into making more power. Or whatever tweaking works for your car.
I still don't know what Optimum Torque is, or wth feeds it? If the above is true and it's values feed Tq to Load, then something is feeding Optimum via the scaling. Nothing I see feeds that kind of #, unless it's fed by the scaling of Optimum Torque (Monitoring). If so, then Monitoring is fed via the values which for me are 0-76 (oem), but now 68 since I lowered them. If so, what feeds that? If it's throttle, via the Driver Command chart which I've always assumed, then 68% of Driver Command is the same as 100%? That can't be right? I guess I should adjust my Driver Command values to cap at 68 and see what happens?
Getting a headache just thinking about it... Why would it be called "Monitoring" if feeds directly into Optimum? And why does any of that crap exist in the first place? It should be pedal position 0-100% feeds Torque to Load 0-100%, the end. But why would they do that when they can make it into a level 10 chinese puzzle?
Per the HP description, which is often wrong imo;
Optimum Engine Torque: A representation of the optimum torque that could be achieved if fuel and spark efficiency were both 100%.
Optimum Engine Torque (Monitoring): Optimum engine torque used in function monitoring, checked against main optimum torque table.
I read that as Optimum is not a factor in actual power output, but instead says "you could make this if everything is working right". Then (Monitoring) seems to be just that, monitoring, does nothing but "check" against the Optimum #'s. Considering (Monitoring) changes will change power, it isn't just checking or monitoring now is it?
Torque to Load makes sense, and is imo a straight up command: Torque to Load: This converts a desired indicated torque to a desired relative air load.
I read that as you want more torque so you raise the values and it commands the air (throttle/boost) to get there. Assuming other limiters allow it.
I'd love to have an actual map for this ECU, and it's programming, to see wth is really going on.
Then there's the whole thing about being "off" on your torque, which clifftoo mentioned in the second post about being ~50 torques off will cause a fault? It can't be actual torque because I break that all the time. My best guess is Optimum Torque vs Optimum Torque (Monitoring), but only because I can't think of anything better. If so, then raising Optimum values and lowering (Monitoring) values, like I've done, puts me at risk? I've had that P061a code he mentioned once or twice, but it was not from messing with either Optimum chart because I got the code before I touched those, and have not had it since touching them, so I don't know what it means.