1. Attachments are working again! Check out this thread for more details and to report any other bugs.

Triangle with Exclamation Loss of Acceleration

Discussion in 'Gen 2 Prius Care, Maintenance and Troubleshooting' started by cmw1275, Feb 3, 2007.

  1. cmw1275

    cmw1275 Junior Member

    Joined:
    Feb 3, 2007
    13
    5
    0
    Location:
    Florida
    Vehicle:
    2012 Prius Plug-in
    Model:
    Plug-in Base
    Hi...I have a 2001 Prius I bought with 35,000 miles about 3 years ago and it now has over 85,000 miles. On Tuesday the orange triangle with exclamation point, check engine light, and car with exclamation point came on. I drove it home (7 miles) and parked it until Friday when I drove it to one of the Toyotas of Savannah (43 miles). Note: Toyota advisor told me it was safe to drive it in. They had it for an hour, pulled a couple of codes, and reset the lights they told me. On the way back home (about half way) the warning lights came on again. I drove the rest of the way home as the service dept. would have been closed by the time I got back there. About half way there the next morning the same warning lights came on and my car lost acceleration. I pulled over and turned the car off. I waited a few minutes and started it up again. The warning lights came on but it accelerated for about a mile then it happened all over again. I had the car towed the rest of the way. Has this happened to anyone else?
     
  2. unruhly

    unruhly New Member

    Joined:
    Jan 5, 2006
    205
    0
    0
    Without knowing the codes that the dealer "reset" there's little we can do to help.

    I'm real surprised that the dealer just reset them and sent you on your way with no explanation. Something just doesn't sound right with your story.
     
  3. cmw1275

    cmw1275 Junior Member

    Joined:
    Feb 3, 2007
    13
    5
    0
    Location:
    Florida
    Vehicle:
    2012 Prius Plug-in
    Model:
    Plug-in Base
    <div class='quotetop'>QUOTE(unruhly @ Feb 3 2007, 08:50 PM) [snapback]384984[/snapback]</div>
    I was surprised myself - I fully expect them to have the car all weekend and into next week. I should have been suspicious when they called me 90 minutes later.

    These are the codes they provided on the receipt:
    Codes: P300, P3006, PO303
    Note on receipt: Cannot duplicate at this time. If light comes back on will need to leave overnight

    Any idea what the codes mean?
     
  4. hobbit

    hobbit Senior Member

    Joined:
    Mar 23, 2005
    4,089
    468
    0
    Location:
    Bahstahn
    Vehicle:
    2004 Prius
    Model:
    N/A
    P0300 and P0303 are misfire codes, specifically cylinder # 3, but
    one should check what's known as "mode $06" data which has better
    detail on how many misfires are detected per 65536 engine revolutions.
    I wouldn't worry about those too much in cold weather; they could be
    artifacts from startup. The P3006, "Battery SOC are uneven",
    translates from the jinglish as voltage mismatches between cell
    blocks and could indicate corroded connections. Have you had the
    SSC-40G battery bus-bar cleaning/sealant fix done? The other possible
    cause is a cell going bad in one of the modules. Either way, Toyota
    may give you a new pack under warranty. Your dealership may be
    fully aware of this and is just trying to avoid telling you..
    .
    _H*
     
  5. cmw1275

    cmw1275 Junior Member

    Joined:
    Feb 3, 2007
    13
    5
    0
    Location:
    Florida
    Vehicle:
    2012 Prius Plug-in
    Model:
    Plug-in Base
    They ended up replacing the battery pack. Fortunately, it was under warranty. So before 100K I have had the computer system and battery pack replaced. I thought an 01 was a safe bet b/c they were in production in other countries prior. Guess not. He now has 95,000+ miles...so far, so good. I'm averaging 47mpg.
     
  6. jk450

    jk450 New Member

    Joined:
    May 11, 2005
    596
    54
    0
    <div class='quotetop'>QUOTE(hobbit @ Feb 4 2007, 10:28 PM) [snapback]385334[/snapback]</div>
    Since the original post said "P300" (and given the other codes), it's likely that it was actually a P3000...