Odd spark behavior in SD

[dlatsch]

I never considered setting "Not Report" for MAF fail, I always just mod the low octane table. That's a tip I'm going to have to try.

[robof16]

I was just experimenting trying to keep the low/high octane table functionality you get with COS3/5. The COS upgrade tutorial and all the recommendations I've seen say you have to have a DTC with the failed MAF but I have confirmed everything working correctly with "not reported", even the log showing "CL" mode while in semi-closed loop, and the transition to "OL" when tripping PE. The tutorial also says you have to go MAFless when running a 2 or 3-bar MAP sensor and I've confirmed that is not the case.

[robof16]

Fixed, smooth, as-commanded spark
Two things:
1. Burst Knock Retard was the culprit. Zeros in B6212, and maximum value in B6208 to disable. Somehow, running in SD triggered Burst Knock.
2. I was incorrect about being able to set P0101-P0103 to "Not Reported" and run SD, you cannot, just like the instructions say