Ice not starting

I'm going to go out on a limb here and question the validity of all those codes. I don't think any of them are even possible Prius codes.

Perhaps whatever you're using for code reading isn't speaking the correct language to understand Prius diagnostics? Of course, this assumes you're working on a Gen 2 Prius, since it's a Gen 2 forum.

 

Never heard of prius doctor, or of anyone using it before. Doesn't look like it's been updated in 3 years?

Instead you should try Dr Prius (Dr Hybrid), or Hybrid Assistant. https://apkpure.com/dr-prius-dr-hybrid/com.nexcell.app

If you can handle the learning curve there is also an App called Torque, though not that user friendly. Many others prefer using a "mini-vci cable" (20usd) and Techstream (dealer technician software) installed on a windows device.

Maybe @PriusCamper has some other recommendations worth trying out.

 

The first thing you need to do is get a voltmeter and check the battery voltage at the battery and at the "jump points" when the failure occurs.
Just because the battery is new does not necessarily mean that it ever was fully charged or that the main cable connections are solid.

Given your car's age, there could be a LOT of places that a corroded or loose electrical connection could be causing an intermittent problem.

 

I could find the pending P1116 in a 2006 manual, but not the others. The P1116 is related to the coolant thermos; I don't think it would be the cause of a no-start.

 

DTC P0300 is an intermittent misfire code.
Please fill out car details in your Bio.. How many miles on it, has it ever been in a front end collision? The battery and connectors are a good place to start - also check and clean all your ground points; especially to the engine. Pull-off the plastic covers and check the wiring harness for rodents gnawing on your wires.
How were your spark plugs; did any of them look like they were running lean or rich? An intermittent ignition coil can cause a P0300 error code. If your just throwing money at it; replace all four; but check the harness and connectors.
The P1116 code is the coolant temperature sensor, engine not getting to operating temperature - will cause lean/rich fuel burn. The car's CPU can't determine proper combustion mixture; if it doesn't get the proper information. This could be due to poor ground points.
Check your fuel pressure, on your fuel rail - you may have put some bad gas in, clogging your fuel filters.

Good Luck..

 

P1116 is the Coolant heat storage tank outlet temperature sensor, not engine coolant temperature. But considering the total lack of accuracy of the other "codes", I would put no faith in the accuracy of this one either.

 

wasn't the ins cluster caps causing a similar problem?

 

Click on the snowflakes for more info .

Post the screen shots from those sub menus and it'll give more data.

Getting closer to an answer though.

 

B1421

Don't worry about this code unless you scanned the car in bright sunlight. In any case, it is the least of your concerns at this point.


C2121/3/4

These codes are "No Signal from Transmitter ID1/3/4 in Main Mode" respectively. The battery in three of the tire pressure sensors has probably died.


C2328

The parking lock mechanism cannot be switched on a hill. This is a Low Voltage Error (Power Supply Malfunction). You need to establish why the parking lock mechanism is not getting the correct voltage.


U0123/3/6

The yaw rate (deceleration) sensor detects any gravity applied to the vehicle and transmits the signal to the skid control ECU via the CAN communication system (vehicle equipped with Enhanced VSC). The deceleration sensor is built into the yaw rate sensor and detects the vehicle condition in the 2 systems (GL1, GL2).

When a malfunction occurs in the communication line with the yaw rate sensor, DTC U0123 (blink code 62) – "yaw rate sensor communication malfunction" and DTC U0124 (Blink code 95) – "deceleration sensor communication malfunction" are output.

The skid control ECU inputs the steering sensor signal through the CAN communication system. When a malfunction occurs in the communication line with the steering sensor, DTC U0126 (blink code 63) – "malfunction in communication with steering angle sensor" is output.

As with any "lost comms" type of error, it can be very involved in tracking down the cause.


I'd suggest you check the 12V battery and make sure it fully charged. Then whenever diagnosing the car, make sure you have the charger in the battery.

Next, now that you have a record of the codes that are there (you saved the scan file in Techstream, right?), I'd go ahead and clear the codes. Do a test drive and see what codes come back. Do a second health check scan.

Let us know how you get on.

 

Don't clear codes just yet. Click on the snowflake symbol to the left of some of the codes. That brings up the "freezeframe" data- info that the ecu saw when the code set. This can be very helpful when diagnosing the problem. Take screen shots and post them here.

Posted via the PriusChat mobile app.

 

This is good advice, but as long as the file of the health check is saved, the OP can reopen the file at any time and look at any of the codes plus FFD if they need to check or inquire on anything that they might want to review in the future.

Before deleting any codes. Open the saved Techstream scan file and ensure all the information you might want to look up at a later date is there. If not, do another scan and save it again. You do this when you exit and return to the home screen.