Yes sir I drove it around for about 20min. Total misfire count was 15.
Excellent! That's a
huge improvement from earlier!
Please give me DTC's that I need to put in on the dashboard. That way I'll know for sure what I'm doing....idk what's REALLY important and what's not, if that makes sense.
Try not to confuse DTCs (Diagnostic Trouble Codes) with PIDs (Parameter IDs). DTCs are "problems". PIDs are the things you monitor -- sensor values, etc -- when diagnosing. (I frequently say "DTC" when I mean "PID" and vice-versa, so don't feel bad!)
It can be helpful to unplug sensors and check for DTCs, but that's not what I was suggesting in my previous post. And (
back on my soapbox, forgive me) when you "reset codes" you will also reset the vehicle monitors' completion status (causing the P1000 DTC again and again, until you drive the vehicle enough to re-run all the "monitor" tests) and you will blow away the PCM's "freeze frame" data. So try to keep "code resets" to a minimum, when possible. (Off soapbox now.
)
Having said that, those 3 bold names in my previous post are the names of the
PIDs that I think you should monitor at some point. Sorry for not being clearer about that. Basically, when you drive around, have someone watch those values to see how they react to your vehicle's speed. Practice monitoring those PIDs while sitting still first -- it will help, I suspect.
I don't know how FORScan Lite (for Android) shows the list of supported PIDs compared to FORScan for Windows, but I suspect that they both use the same PID
names. If you're confused, don't hesitate to ask some questions and I'll try to clarify.
For some reason I can't run a full key on engine running test. It stops at about 85% does that have anything to do with the p1000 code?
I don't know. It might. I wouldn't worry too much about that just yet.