With all those CANbus timeouts, I'd be looking for wiring damage—rodents perhaps?

Alternatively, if it starts okay after charging the 12V auxiliary battery, and it floats at ~14V when in READY, it's probably time for a replacement 12V.

 

Do a search for P1A15 both here and on Mitsubishi I-Miev Forum - Index page there are many threads detailing this problem and various attempts to repair it at a component level.

Unfortunately it is becoming a common fault and there is not just one cause. Some have been repaired successfully some have not.

 

As DBMandrake said, the significant error code is "P1A15", which refers to a fault in the motor control unit ( the MCU - the inverter, the right-hand box above the motor ). The main control computer ( ECU ) may be erroneously deciding that a smoothing capacitor in the MCU is not being charged by the high-voltage traction battery quickly enough. Solving this error used to require replacement of the inverter, which is often not cost-effective. Thanks to the knowledge and hard work of some members of the MyiMiev forum, a replacement for a component that degrades with age has been developed, and this may apply to your situation.
How long after the code was cleared was the car still driveable? How far had you driven just before the last failure? What was the ambient temperature at that time?

 

Do you have a direct link to discussion about this replacement component ? I don't have a triplet anymore so I haven't been following the progress of P1A15 solutions recently but I'm curious to know what the latest knowledge on this is.

 

The development of the alternate isolation amplifier solution, using an Analog Devices component instead of the Nihon Pulse ISA215 hybrid board, starts here:

[ The P1A15 Troubleshooting Thread ] No READY. P1A15 error. Condenser charge timeout.

INDEX to this thread. [ @kiev Edit, moved Lic's original fault history to post #5] [Edit, june 22, 2023 after going thru entire thread] This is a P1A15 INDEX Post with links to help find pictures and info quickly. This problem is usually caused by a defective hybrid board in the MCU that...

myimiev.com