Troubleshooting and repair for On-board Charger (OBC)

[kiev]

The P1A12 DTC indicates an abnormal stop occurred during charging, but there could be numerous causes and it doesn't point to any specific circuit.

The MUT tool is required to read the specific OBC fault code (listed on page 1) that identifies the problem area and triggered the DTC.

Unfortunately the OBC is too smart to allow bench testing by simply connecting AC to the leads. Some sort of simulator would be needed to provide all the control signals necessary to set the current level and start the charging, plus a HV battery would be needed on the output side as a load. Let me know if you figure out a way to do this, i need it too.

[ZsoZso]

Hi All,

I have a 2011 i-Miev that stopped charging a couple of days ago. Tried to make an appointment at the local dealer, the first available time is in 2 weeks, so I got an iCarsoft reader to try to figure out what is the problem.
When I plugin the AC charger, the car shows the icon for the plugin but does not charge.
It also shows the red battery icon as well as the yellow drivetrain error (car icon with exclamation mark).
I only have 3 bars of charge left so I am not sure I could reach a DC fast charger to test if that works.

Anyway, the iCarsoft code reader got me the following error codes:
U1109
U1160
P1B18
P1AA7

It also has messages about EV-ECU signal time out and
EV-MSG lost (MCU)/EV CAN timeout

Could anyone help me understand what these codes / messages mean ?
Thank you very much!

[kiev]

Sorry to hear you have trouble.

From the FSM there are troubleshooting steps for all the trouble codes, for example in your case
=====
CODE NO. P1AA7: EV-ECU SIGNAL TIME-OUT
BMU
The signal sent by the EV-ECU through the CAN cannot be received.
=====
CODE No. P1B18 EV-ECU LOST
EMCU
If the CAN data from the EV-ECU cannot be received for 0.3 seconds or longer, the EMCU will set the diagnosis code No. P1B18.

PROBABLE CAUSES
The CAN bus line is defective.
Malfunction of the EV-ECU
=====
Which all sounds scary but none of these is related to the OBC.

The Uxxxx codes are related to CAN buss errors, and from multiple instances over the years we have found that an old, weak or worn out 12V starter battery can cause a multitude of faults such as you have found. Fully charge it or replace it with a new one that you also fully charge. The chances are very good that all these codes will clear and you will be fine. (Assuming nobody has been rooting around under the back seat with the EVECU and BMU connectors; if that has occurred then all bets are off).

[ZsoZso]

Thanks for the explanation of those codes.
I have replaced the 12V battery and put in a fully charged new one.
Now, I got 2 new codes:

P0A09 DCDC converter fail
P1A12 On board charger abnormal stop

[kiev]

Did the other codes go away?

Based upon those 2 codes, i suspect that the fuse under the access cover in the Motor Control Unit may be blown. If so then the puzzle becomes why did it blow. Also if so then the snubber capacitors on the power board in the OBC are likely blown too.

What happens when you plug in the EVSE to charge--any relays clacking or lights on the dash, does it attempt to charge but then stops, does the contactor in your EVSE unit engage, etc?

Has there been any mains power outages while the car was charging, lightning storms, someone snatching the EVSE handle out of the socket while charging, etc.

What was the voltage on the old 12V, was it fairly worn out or old?

Will your scan tool read the OBC error codes, e.g. 26 charging current limited due to excessive temperature.

[kiev]

If the DCDC doesn't start for 4 seconds or more after being commanded ON.

P0A09
When the DC-DC converter drive stop state continues for 4 seconds or longer while the DC-DC converter driving approval is underway, the diagnosis code No. P0A09 will be set.

Probable cause
Damaged wiring harness or connector(s)
Malfunction of system cooling
Malfunction of the DC-DC converter
Malfunction of the EV-ECU

=====
The P1A12 code
When the diagnosis code (except for No. 26, No. 32) is set to the on board charger, the diagnosis code No. P1A12 will be set.

Any OBC fault except 26 and 32 will cause this DTC.

[ZsoZso]

Taken apart the OBC,.
Looks like I got a fried capacitor:
https://photos.app.goo.gl/pzE6NvqwundQ5w489
hmmm, need to figure out how to post image, google photo link does not seem to work...


It is the top blue one in the doghouse surrounded by the black conformal coating on this picture (this is not mine, copied from upthread):



The old errors are still there too.
The communication problems are probably due to the broken data connector (1 pin is missing):
https://photos.app.goo.gl/fVEcwGe3Ywp7txx29
That pin just fell off when I was lifting the board up.

The old battery was a bit low (60% SOC, was reading 12.8V), but it seems to be still OK, I just charged it up without problem.
So I think it was just low because it did not get charge due to the DC-DC not working.

[kiev]

Yes if one of the blue snubber caps has blown, then the fuse in the MCU will be also, and the DCDC will have no power to work and charge up the 12V battery. Check the diode drops in the waffle plate first. If the plate has damage then that is more serious.

[edit Did you find any spattered metal from the blown capacitor on the control board?

[coulomb]

need to figure out how to post image, google photo link does not seem to work...

With Google photo, it is really hard to find the URL of a photo, and if you do, it's really long (like 1000 characters), and if you use it, you find that the URL changes in a few days and the link is bad anyway. Google is a small family run business, and can't afford to host everyone's photos Use imgur.com instead.

The old battery was a bit low (60% SOC, was reading 12.8V), but it seems to be still OK, I just charged it up without problem.
So I think it was just low because it did not get charge due to the DC-DC not working.

Yes, that sounds quite OK, given that the DC-DC would not be working. You'll have to source a replacement fuse; read the index of this topic for details.

[coulomb]

... but never seen it blow the connector right off the board.

I think he's desoldered it (a really neat job, bravo), because one pin is missing. It might be difficult to source a replacement, but perhaps an unused pin could be moved into place?