Please help decipher OBDII report.

have you tested the 12v?

 

you want the voltage after the car has been off a few hours. as for obd, many readers aren't specific enough for prius.

 

You need to get a mini-vci obd2 reader w/techstream software and a dedicated laptop, preferably with winxp os. This will give you the same info the dealership techs will see and charge you about $100 for it.

The mini-vci and techstream will cost less than $50, look on Amazon or Ebay, the laptop your call.

The obd2 readers you have, while useful in a generic sense, is not going to be as informative as the mini-vci. If you plan to keep your Prius for more years, getting one will be worth it.


2006 Gen 2
2014 Gen 3 v wagon

 

It does sound like you may have a problem with the traction battery ECU.

The attached may be of interest, however since your log shows module pair voltages, the TSB probably does not apply.

https://priuschat.com/attachments/t-sb-0166-09-pdf.32383/

 

patrick ^^^ knows way more than me. so if he thinks your reader is fine, and it's the battery ecu, i would listen, and ask him questions.

 

Well, if you intend to rely upon the local Toyota dealership for service, then I suppose you should take the car there and see what happens.

If you believe you can DIY, then I suggest you get Mini VCI so that you have access to the three-digit subcode that is recorded along with DTC P3000 as that would give you a further clue about what is wrong with your car.

Your post #5 mentions that P0A80 was logged, which indicates the traction battery has a problem with at least one module. However that fault code did not show up in the pdf that you provided. If P0A80 is actually present, this will be visible with Mini VCI.

If it turns out that the traction battery ECU has failed then you could buy a used unit from eBay and install it yourself. If you rely upon dealer service then expect the repair bill will be in the high hundreds, if not getting into the $1K range. Good luck.

 

It is not going to be easy to determine the exact issue without Mini VCI. It needs a laptop that uses Windows XP or Windows 7, 32 bit OS. You can buy a used laptop on eBay for ~$100 or so but may also need to replace the laptop battery before it can be productively utilized.

It will be difficult to achieve your bottom line without having perfect information about the nature of your car's fault. At this moment I believe you lack such clarity.

I DIY repairs and maintenance on my vehicles because I have found that the bottom line which you expressed can be very difficult to achieve. If I am going to go to the trouble of figuring out what is wrong and what is the appropriate repair for that issue, I'd might as well exert the effort to implement the remedy myself.

 

I'll say something here based on the Gen 1 manual because I don't have a Gen 2 one handy, but a P3000 on a Gen 1 was an example of what you might call a hearsay code: there are several computers in the car, they talk to each other, and some of them will log a certain code just to confirm hearing about a problem from one of the other computers.

In Gen 1, P3000 was a code that the HV computer would set, just to indicate it had received notice from the battery computer of a problem detected there. To find out what was really up, you would then go request codes from the battery computer.

(Another example of this kind of code is the C1259 that the brake computer will always report, if it got a notice of a problem from the HV computer.)

Again, I don't have a Gen 2 manual handy. If you want to be sure you're not getting bad diagnoses, you could spend $15 in lots worse ways than going to techinfo.toyota.com and checking the repair manual for your model and year.

But so far the indications are that the battery computer detected a problem in its own jurisdiction, so to speak, and told the HV computer about it.

-Chap