Triangle of Death... could it be a code that reads as history?

it might. try dr. prius, it might help pinpoint the bad module

 

Ishtar be more than weak, might be shorting out.

 

Two things are being conflated here. P0AA6 and P0A80 refer to two completely different sorts of problem. Of course, there is no reason your car can't have both.

You had the P0AA6 code earlier, but it is not among the codes you have now. I don't know what is so vague about P0AA6; it means that the isolation between the high voltage system and the rest of the car is breaking down. It has a few 3-digit INF codes you can read with a more advanced scanner, to help you pin down whether the fault is closer to the front or the back of the car. But even without those codes you can use careful observation and a megger to find where the problem is. The code means exactly what it means. You fix this sort of problem by finding whatever is conducting electricity that shouldn't be (whether it's under the hood, under the car, or in the battery) and correcting that.

P0A80 means that one or more traction battery modules have deteriorated outside of specs. Usually it's accompanied by one or more codes like the P3022 that you have, to tell you which block of two modules it is talking about. You fix that sort of problem either by replacing the faulty module(s), or avoiding whack-a-mole by replacing the battery.

The brake ECU's C1259 and C1310 are only set because the HV ECU is reporting a code (the P3000). I wish folks would stop doing generic web searches and writing "ac..ve bo..ter sol..oid" for C1310; that's something that code would mean in some completely different car, nothing to do with a Prius. Continually reposting it that way on PriusChat just messes up people's searches.

Because you haven't shown anything but history codes from the battery ECU in this latest batch, there's a slight mystery why the HV ECU P3000 is current, unless the scan tool missed something. It might be good to get access to a scan tool that can read INF codes, and see what INF codes are going with that P3000.

In any case, it looks like you know about two recently detected problems: one involving a marginal battery module or two, in block 12, and one involving a high-voltage isolation fault, somewhere in the car, not pinned down yet.

They probably both will need attention.

 

Yeah, it doesn't do to guess. It's in the battery if it's in the battery, it's in the transaxle if it's in the transaxle, or in one of the other places, and in no event does reality care what your guess is. If the P0AA6 comes back, you just have to find out what the reality is, which will require either having some gear you don't currently have, or getting some help from someone who has it. The INF codes are handy but not super-essential: they just save you the first step of the troubleshooting that's needed anyway to pin it down precisely. Without them, you just have to begin with that step.

and the people who put the database in the scanner just built it by glomming together whatever fortune cookies they could search up for the various codes, for any car on the planet.

Really, my usual advice with the trouble codes is to pretty much ignore the fortune cookies, just take the five-character code straight to the repair manual (more info) and flip to the corresponding section there. That will also start with a fortune cookie, which at least will be the right one for the car, but even those usually aren't worth trying to decipher. What you want is in a box a little further down the page, called the "detection condition". That's where it tells you exactly what reality has to do to the computer, to make the computer report that code. From that, you can really start figuring stuff out.

It's not uncommon on PriusChat to hear of people repurposing an old beater Windows laptop to hook up a cheap J2534 dongle and run some version of Toyota's Techstream software, which is what the dealer uses so it shows you everything the dealer would see. If you go with an officially distributed version, it works for two days every time you feed it $65, a bit annoying, but often less than a dealer appointment to go have them run it, and maybe still less than some "pricey" tools that might not be as useful on a Prius.

 

Following from ChapmanF's info, that Innova scanner might just be able to retrieve INF codes if it has a button (associated with the code) with a 'snowflake' icon or the letters FFD on it. Clicking on this button will open the freeze frame data, which is where you will find the INF or Detail codes.

 

The fault codes for the HV battery indicate that at some point the battery ecu measured a sizeable (something around 0.5V or greater) voltage difference from block 12 compared to all the others. If your scanner can display block voltages then you might want to monitor them while driving the car (safely of course). See what they look like during heavy accel (discharge) and braking (charge). Some faults might only be apparent when the battery is loaded.

Some here use the Dr Prius app with a compatible OBD2 bluetooth adapter (see the website). It's good to view live HV battery data and you can keep it in the car. Hybrid Assistant app (android only) also works and has good data logging and makes a great report afterwards.

Posted via the PriusChat mobile app.