After playing around with some matplotlib code I finally started looking at my data in visual form. I know it has too much data plotted at the same time and I have not put the RPM correctly and I am also plotting it against itself which is counterintuitive, but this will get fixed in the future.
Around the 6000 rpm mark where the hp peak is, I start feeling nothing as the RPM increases, it's as if the engine is just roaring but nothing and the rate of change of the RPM starst slowing down significantly.
It is also maddening, that whilst doing this WOT, the AW55 gearbox is deciding not to lock the torque converter. Not sure what the decisions for this were. It gets hot, and I lose 15-20% efficiency. The only reason I can think of is to prevent excessive slipping of the TC while trying to lock it during WOT.
(my intake vvt map)
Generally I find that when overtaking with the automatic transmission with an unlocked converter at second gear I quickly run out of useable torque especialy with that unlocked TC. I've had situations where I was almost overtaken by a 100-120hp peugeot or citroen even as I had stomped the gas pedal and was in 2nd. I am wondering if I slightly increase the advance at high rpm, would that help me more?
I generally am willing to sacrifice top vehicle speed for better acceleration in the high rpm range. I've not needed to exceed 140kmh/80mph except in one instance in the past year. Every single aspect of my driving in the past year has been low to mid RPM, with the occasional high rpm for overtaking or simply testing how the car performs. Torque is apparently king much more than horsepower at particular speeds.
I recently had a small race with a Honda 2.2 140hp. It had 330nm and it absolutely blew me away.
Addendum:
I discovered that the fuel maps modified by BSR do not affect WOT fueling, and it's still lean @ 14,7 up to 5200 rpm. I have since discovered a map which when I modified, I finally got a richer AFR where I wanted.
Additionally, I have discovered that the logging rate decreases with each param I request in Dynamic Records. I am now at 80ms per data frame as such, it's roughly 12hz. I have dug seriously in the timing code and believe I have found a piece of code partially responsible for the Busy bus error. If I patch it out in a way I am thinking, it should only affect dynamic records and allow me more freedom in polling.
I believe if one of the params is 8, then the busy busy function which checks something in SRAM(not ram, but adaptation RAM) returns the value -1 immediately, causing the function to never error out on busy bus. Of course nothing is every this simple, and it is unknown whether the function returning fast means that the data in the dynamic records has been updated faster than 12hz.