Fun Engine Codes

[ATL_Rubi]

I had a Christmas tree of lights when I turned the Jeep on this morning, and the steering wheel was immobilized. Codes are as follows:

P062A -- Fuel Pump "A" Control Circuit Range/Performance
U0109 -- Lost Communication With Fuel Pump Control Module
P2AF5 -- Starter Relay 3 Stuck On
P0564 -- Speed Control Switch 1 fault
P2504 -- Charging System Output High


I had to clear the codes to drive the Jeep as the steering wheel wouldn't move and would not go into gear (I had an appt I couldn't miss), and of course, the dealer can't do anything without the codes in the system now.

A quick search of the forum turned negative for a few of them . Anyoe had any of these codes or a combo of them?

added video of the codes and of the gauge cluster

Sponsored

 

[Max-t]

When ya get all that stuff it’s likely none of it and a low battery scenario and ohms law got together to make your computer crazy.

they didn’t come back?
Did it crank slow?

 

[ShadowsPapa]

Those are not untypical of CANBus issues...

When you started it did you look at the voltage with it running to see if the charging system output really WAS high, or if it was lying to you?

Take a volt meter to the battery with it not running.
Start it, do the same - check voltage to see if that one code was a lie or a communication/connection issue.
I'd bet on a communication issue - although if it was sitting there with a low aux battery.

Pretty simple to check at least that one code.

And the U code is related to communications between the modules.

You can check with a volt meter to see if the charging system output is really high - that would be an odd thing since the PCM controls that - and since it does, makes me wonder again about communications.

 

[Minty JL]

Damn dude.

I'm almost at 11,200 miles now with no issues........as I proceed to knock on wood now

 

[ATL_Rubi]

When ya get all that stuff it’s likely none of it and a low battery scenario and ohms law got together to make your computer crazy.

they didn’t come back?
Did it crank slow?

It didn't crank slow but once it did crank the rpms stuttered (dropped to 700ish) then hit high idle and that's when all the lights flipped on.

Those are not untypical of CANBus issues...

When you started it did you look at the voltage with it running to see if the charging system output really WAS high, or if it was lying to you?

Take a volt meter to the battery with it not running.
Start it, do the same - check voltage to see if that one code was a lie or a communication/connection issue.
I'd bet on a communication issue - although if it was sitting there with a low aux battery.

Pretty simple to check at least that one code.

And the U code is related to communications between the modules.

You can check with a volt meter to see if the charging system output is really high - that would be an odd thing since the PCM controls that - and since it does, makes me wonder again about communications.

I didn't get a chance to check any of the systems, I kept an eye on the volts for the remainder of my drives today and nothing was out of the norm, 13.7-14.0 during driving and never dropped below 12.3 during ESS. I went ahead and undid the tazer, perhaps that caused some issues. My guess is as you mentioned, likely a communication issue that then just sent a frenzy of systems into chaos.

Damn dude.

I'm almost at 11,200 miles now with no issues........as I proceed to knock on wood now

I know! It was going so well. After clearing the codes it all seems fine but now I'm waiting for it to happen again.

 

[Max-t]

These stellantis vehicles are super sensitive. Super complicated. I do not envy anyone doing diagnosis on them that goes beyond grounding and battery health.
I have a couple bugs that keep popping up. I’ve checked everything I can. Found nothing. I think it may be programming in my car’s case.
I dropped it off and the answer I got was “recommend further diagnosis” but they didn’t have anyone free for months apparently (the other dealer shut down for an ownership change and shunted everyone to one service dept.

Anyway. Having it go nuts on startup could just be a weird one off or a failing battery. Or lord knows what else.

Having the two batteries apparently makes it difficult to see if one battery is weak. Ya get thevolts But no amps available.

 

[ShadowsPapa]

I didn't get a chance to check any of the systems, I kept an eye on the volts for the remainder of my drives today and nothing was out of the norm, 13.7-14.0 during driving and never dropped below 12.3 during ESS. I went ahead and undid the tazer, perhaps that caused some issues. My guess is as you mentioned, likely a communication issue that then just sent a frenzy of systems into chaos.

Then battery is likely fine. They can easily drop below that during an ESS stop event. The fact it held that voltage while supporting the electronics and other functions tells me you aren't in a bad place there.
Still do check battery voltage at rest, but that 13.7-14.0 is 100% normal, absolutely, and indicates the charging system is functioning normally - at least during the time you watched it.

Having the two batteries apparently makes it difficult to see if one battery is weak. Ya get thevolts But no amps available.

Wrong - if it didn't have the ability to maintain the amperage, volts would drop drastically. Please don't confuse things with tossing mud and guesses.
Volts drop fast once a battery loses capacity.
Electric is my specialty - in practice and training.
It's really not that difficult.


ESS worked in his truck - it's extremely likely his batteries are ok, otherwise ESS won't be allowed to work. In fact it doesn't take much to make ESS stop working.
He had issues related to lack of communication - that's where I'd start.
If that aux battery doesn't check out during the startup sequence, it won't allow ESS to work. If it sees battery or batteries as being low, it will give an Auto stop/start not ready, battery charging message.
In his case it's working and the voltage is fine - and that means the batteries are at least mostly charged, a decent SoC even if not a 100% SoC.

 

[ATL_Rubi]

Then battery is likely fine. They can easily drop below that during an ESS stop event. The fact it held that voltage while supporting the electronics and other functions tells me you aren't in a bad place there.
Still do check battery voltage at rest, but that 13.7-14.0 is 100% normal, absolutely, and indicates the charging system is functioning normally - at least during the time you watched it.




Wrong - if it didn't have the ability to maintain the amperage, volts would drop drastically. Please don't confuse things with tossing mud and guesses.
Volts drop fast once a battery loses capacity.
Electric is my specialty - in practice and training.
It's really not that difficult.


ESS worked in his truck - it's extremely likely his batteries are ok, otherwise ESS won't be allowed to work. In fact it doesn't take much to make ESS stop working.
He had issues related to lack of communication - that's where I'd start.
If that aux battery doesn't check out during the startup sequence, it won't allow ESS to work. If it sees battery or batteries as being low, it will give an Auto stop/start not ready, battery charging message.
In his case it's working and the voltage is fine - and that means the batteries are at least mostly charged, a decent SoC even if not a 100% SoC.

Agreed on all fronts. Measured everything last night and this morning, all within my personal specs of okay, 12.5+ sitting.

Here’s what’s interesting, the P0563 code is the TCM voltage regulator fault. I went to check codes this morning just to be safe and that was the only one left over. Could that code be a side effect of the transmission problems I’ve been having? E.g. hesitation in 3rd gear.. just a thought.

 

[ShadowsPapa]

Voltage fine, batteries likely fine. Still question bus communication but sounds like that final code is more trans related.

 

[ATL_Rubi]

Voltage fine, batteries likely fine. Still question bus communication but sounds like that final code is more trans related.

Yep.. makes me think that it's related to the hesitation I get in 3rd gear. I hate that I erased the codes. Heres to hoping they come back!

 

[ShadowsPapa]

Yep.. makes me think that it's related to the hesitation I get in 3rd gear. I hate that I erased the codes. Heres to hoping they come back!

If it's related to communications - it may or may not come back, and if it does, it would possibly be different codes.
When mine came up with a weird list of codes with 1 or 2 of them being communications related, it only happened a couple of times and was different each time other than talking about the shifter and some missing message. I'm guessing the dealer took care of it by messing with the star connectors behind the glove box. they never wrote anything down, but there was evidence someone was in that seat and the glovebox contents moved and it's not happened in almost a year now. The service advisor said "yeah, he took care of that, too" but it wasn't on the invoice

Sponsored