Okay. I attached the testing. More then likely you jumped a tooth in the timing and it is setting this code. We need to run through all this testing and see what happens. Clearly we can't guess at it as there is not a next most likely cause. Normally it is a sensor but we need to run through this to find out where the issue is.
Let me know if you have questions. Thanks
Images (Click to enlarge)
Monday, September 14th, 2020 AT 6:56 PM