Don't slaughter me too hard, or do if you please. I've searched to no avail.

07.5 LMM 12628594 os, dsp5 conversion. 12mm stroker, 100 overs, 68mm vgt in valley, 480 over. Truck has been driven well on purchased tunes without 480 for 5-6 years. Added more air, wanted more duration to compliment that air. A little data logging gave me some limits to work around.

I modified the duration, and timing of the non dsp slot and slot 4, adjusted pedal position a to 886 in the bigger end and tapered it back, I figured I'd get those bugs worked out first.

non dsp or dsp 4, truck main injection flow rate does not even come close to calculated flow rate until about 3200rpm. Once I breach 3200 it comes alive. The injector pulse being commanded matches closely to the main injection flow rate.

I can not seem to record torque data on v7.5. says gm.trqeng_b is not a valid pid when I'm connected the e35b lmm ecm. no torque pids are once connected.
So I added it in on bbx and used the v2 for what it's for, not worrying about your laptop flying when having to brake hard. Pulled log through explorer, loaded it on the 7.5 scan, won't play back.
I've read about this somewhere else. I haven't researched it yet, but v2 is all up to date, as is software. So next step, watch the data and worry about that other stuff later.

So I go on another run, find that the trqeng_b maxes out at 443 ft lbs. this can't be right, I haven't changed any torque based fuel tables, pedal position should be requesting 897 ftlbs, it's main fuel rate is 72mm3, calculated fuel is 95mm3, but pulse time is 931uS which is in between 70-75 @ 180 MPa which pressure was at. Once I reach 31xx-32xx the main rate goes to 105 and calculated is within ~10

does this on the non dsp and dsp 4. so I know I'm sharing the issue in another table. I have at this point maxed b1117, b1118, b1119, b1186, b1128, b1192, b1152, b1153, b1154, b1155, b1156, b1157, I've modified d5196 in the tcm played with d5197 on every setting.

obviously I've got to get some data recording figured out, It clearly not going to help much if the v2 trqeng_b is real, so it would track in the wrong parts of the tables. I am not commanding 72 anywhere in the 443 sections.

I do not see what is requesting the reduction in any multiplier but allows it to go away at 3100-3200 area. Outside of continuing this trend of table by table disabling shit until it cooperates, It's making me nutty. I appreciate all opinions and thoughts.