UPDATED: Got the Code Reader Tonight - Help me Figure this out guys...
OKie Dokie - finally was forced into buying a code reader from this thing popping codes like popcorn on a movie night... ...
More specifically it's because it died on the highway once a month ago, then did some wierd limp mode on me this afternoon.
I was at the dealer a couple weeks ago, and he reset all of the codes at that time, so we started with a clean slate.
So, tonight, pulled the codes, and here's the raw list:
#1 P0222 - (Idle Validation Sigs Both Low Problem detected w/ idle validation circuits within APPS. )
#2 P1689 - (No Communication Between ECM and Injection Pump Module)
#3 P0237 - (Map Sensor Voltage Too Low MAP sensor voltage input below the minimum acceptable voltage. )
#4 P0237 - PENDING
#5 P1689 - PENDING
#6 P0222 - PENDING
OK, so now let's start with some very important information in order to help you understand the situation.
After the Dodge tech reset me ECU codes a couple weeks back, I went and picked up a brand new APPS sensor and installed it a couple days later, since it had previously tripped several APPS codes, so we figured it was short for this world.
Ever since I installed the new APPS, there was not a single problem with the truck at all, no CEL (MIL) until... ...
I made a stupid mistake when installing my new shocks. I needed to get my arm down into the engine compartment and had to disconnect my EZ box MAP connection from the engine ECU. I later had to start the truck to turn the wheel to get better access, and of course... . big red CEL came on. DUMB*****!! - realized immediately that not hooking up the MAP sensor would trip a code. And it did!
After a few trips, that CEL light of course went out, and all was well... ... ...
UNTIL TODAY! Took a short trip to town, and about 300 yards from the driveway, the truck stumbled, had almost the "dead pedal" for about 40 seconds and the CEL came on right away. The truck came back to life then, and drove away as normal.
This is where it gets wierd... ...
Looking at the list above, I can explain what happened for most of them as such in the order they happened... .
#1 P0222 - Remaining code from my old APPS after Dodge tech reset codes, but before I installed the new APPS.
#2 P1689 - Happened sometime before new APPS. No drivability issues.
------------------
Installed new APPS about here in the timeline
-------------------
#3 P0237 - PENDING - Definately happened with my accidental MAP disconnection during shock install.
#4 P0237 - PENDING - Same as above.
#5 P1689 - PENDING -
#6 P0222 - PENDING -
Tonight after clearing the above codes, I intentionally recreated the MAP disconnection, and sure enough, as soon as you turn the key to "on" (not start), the CEL comes on, and after you start it, you get the second "pending" version stored in memory also.
I can somehow explain what MAY have happened with #5 and #6 ignoring the "pending" portion of it:
I started the truck up the other morning to rotate the tires and the engine had a massive lope to it, and immediately set the CEL. Perhaps this was #5 and subsequently perhaps #6 was the stumble and limp "dead pedal" that I had this afternoon... .
BUT..... My understanding is that PENDING codes do NOT set the CEL until they happen on the second consecutive trip, at which point it sets the CEL.
I can track back the timelines vs the codes, and perhaps it makes sense, but this PENDING thing throws a monkey wrench into the works for me.
So, anyone with any ideas?
Thanks,
Shawn
OKie Dokie - finally was forced into buying a code reader from this thing popping codes like popcorn on a movie night... ...
More specifically it's because it died on the highway once a month ago, then did some wierd limp mode on me this afternoon.
I was at the dealer a couple weeks ago, and he reset all of the codes at that time, so we started with a clean slate.
So, tonight, pulled the codes, and here's the raw list:
#1 P0222 - (Idle Validation Sigs Both Low Problem detected w/ idle validation circuits within APPS. )
#2 P1689 - (No Communication Between ECM and Injection Pump Module)
#3 P0237 - (Map Sensor Voltage Too Low MAP sensor voltage input below the minimum acceptable voltage. )
#4 P0237 - PENDING
#5 P1689 - PENDING
#6 P0222 - PENDING
OK, so now let's start with some very important information in order to help you understand the situation.
After the Dodge tech reset me ECU codes a couple weeks back, I went and picked up a brand new APPS sensor and installed it a couple days later, since it had previously tripped several APPS codes, so we figured it was short for this world.
Ever since I installed the new APPS, there was not a single problem with the truck at all, no CEL (MIL) until... ...
I made a stupid mistake when installing my new shocks. I needed to get my arm down into the engine compartment and had to disconnect my EZ box MAP connection from the engine ECU. I later had to start the truck to turn the wheel to get better access, and of course... . big red CEL came on. DUMB*****!! - realized immediately that not hooking up the MAP sensor would trip a code. And it did!
After a few trips, that CEL light of course went out, and all was well... ... ...
UNTIL TODAY! Took a short trip to town, and about 300 yards from the driveway, the truck stumbled, had almost the "dead pedal" for about 40 seconds and the CEL came on right away. The truck came back to life then, and drove away as normal.
This is where it gets wierd... ...
Looking at the list above, I can explain what happened for most of them as such in the order they happened... .
#1 P0222 - Remaining code from my old APPS after Dodge tech reset codes, but before I installed the new APPS.
#2 P1689 - Happened sometime before new APPS. No drivability issues.
------------------
Installed new APPS about here in the timeline
-------------------
#3 P0237 - PENDING - Definately happened with my accidental MAP disconnection during shock install.
#4 P0237 - PENDING - Same as above.
#5 P1689 - PENDING -
#6 P0222 - PENDING -
Tonight after clearing the above codes, I intentionally recreated the MAP disconnection, and sure enough, as soon as you turn the key to "on" (not start), the CEL comes on, and after you start it, you get the second "pending" version stored in memory also.
I can somehow explain what MAY have happened with #5 and #6 ignoring the "pending" portion of it:
I started the truck up the other morning to rotate the tires and the engine had a massive lope to it, and immediately set the CEL. Perhaps this was #5 and subsequently perhaps #6 was the stumble and limp "dead pedal" that I had this afternoon... .
BUT..... My understanding is that PENDING codes do NOT set the CEL until they happen on the second consecutive trip, at which point it sets the CEL.
I can track back the timelines vs the codes, and perhaps it makes sense, but this PENDING thing throws a monkey wrench into the works for me.
So, anyone with any ideas?
Thanks,
Shawn
Last edited: