The DTC Disable thread (P1235, P1241, P1238, etc)
And P0219 is an issue for 2010 and up ( I think) with built motors. The ECU doesnt like it when I rev to 8200....
EDIT: i just noticed your signature. you have a lot of work done so this may not even get close to applying to your situation but:
p0300 is multiple misfire. did you do anything to change the ignition system?
p0219 is engine over speed. was there a mis shift/over rev?
the ecu presenting both of those codes in combination would lead me to believe the motor over-revved (p0219) and there could be valve damage (presented as misfiring in p0300).
https://www.evolutionm.net/forums/ev...de-help-3.html
p0300 is multiple misfire. did you do anything to change the ignition system?
p0219 is engine over speed. was there a mis shift/over rev?
the ecu presenting both of those codes in combination would lead me to believe the motor over-revved (p0219) and there could be valve damage (presented as misfiring in p0300).
https://www.evolutionm.net/forums/ev...de-help-3.html
The p0219 code will trip if the motor revs to 8k (on a 2010+). Its a permanent DTC and could be serious if your motor is stock, but my motor and head are fully built. revving past 8k isnt an issue, but the ECU doesnt know that.
p0300 is random misfire code, but like I said, I have seen this from a faulty set of DWs and now am seeing it again, which I believe is a result of my lightweight flywheel (just noise).
A misfire code is really only a cause for concern if its cylinder specific.
The p0219 code will trip if the motor revs to 8k (on a 2010+). Its a permanent DTC and could be serious if your motor is stock, but my motor and head are fully built. revving past 8k isnt an issue, but the ECU doesnt know that.
p0300 is random misfire code, but like I said, I have seen this from a faulty set of DWs and now am seeing it again, which I believe is a result of my lightweight flywheel (just noise).
A misfire code is really only a cause for concern if its cylinder specific.
p0300 is random misfire code, but like I said, I have seen this from a faulty set of DWs and now am seeing it again, which I believe is a result of my lightweight flywheel (just noise).
A misfire code is really only a cause for concern if its cylinder specific.
8k is actually pretty mild, Im on a stroker, so we kept the revs pretty conservative. My setup is good to 8500 max. But there are big bore 2.2s out there revving to 9 or even 9.5K. THATS moving.
AWD, I got my OBD pin-8 logging working on the standalone just a couple days ago and it's well worth it (and much less work than the rear o2 tap, imo) now if only I could find a way to get that into EvoScan. I know most of the addresses transfer directly and you just change the "0x" to "23", but since the paramid=8 for the adc logging on standalone, I can't just put "8" in the request id when adding a new data item in EvoScan, right? Still new to this and oh-so lost.
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
Nah, you're not lost. Pin 8 ADC is only accessible via standalone logging... for now.
If I want to log AFR from EvoScan, I just plug in my LC-1 via serial-USB digital link. When I unplug the laptop, standalone logging kicks in via LC1 analogue -> pin 8.
Several of us have raised a change request thingumy with EvoScan, asking for it to support OP2.0's direct-voltage-ADC logging. One day!
Rich
If I want to log AFR from EvoScan, I just plug in my LC-1 via serial-USB digital link. When I unplug the laptop, standalone logging kicks in via LC1 analogue -> pin 8.
Several of us have raised a change request thingumy with EvoScan, asking for it to support OP2.0's direct-voltage-ADC logging. One day!
Rich