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

Request instruction to clear C1203 C1451 C1345 with techstream

Discussion in 'Gen 3 Prius Care, Maintenance & Troubleshooting' started by moon_tanner, Apr 7, 2020.

  1. moon_tanner

    moon_tanner Junior Member

    Joined:
    May 29, 2016
    7
    1
    0
    Location:
    NW Florida
    Vehicle:
    2010 Prius
    Model:
    One
    Vehicle: 2010 Prius base model

    Hello,

    After replacing the Brake Actuator, I have three codes left to clear. How do I clear these codes with techstream?

    I know the C1203 must be cleared first, followed by C1451, then C1345.

    [​IMG]

    [​IMG]
     
  2. ChapmanF

    ChapmanF Senior Member

    Joined:
    Mar 30, 2008
    24,910
    16,215
    0
    Location:
    Indiana, USA
    Vehicle:
    2010 Prius
    Model:
    IV
    I'm not sure how you know that. I don't think I know that.

    The C1203 you can probably take care of any time. If you clear it and it comes back, the brake ECU isn't able to talk to the ECM, which would require you to figure out why, and fix that. After that, clearing the code should leave it cleared.

    The C1451 can't be cleared; it it means you have to do a bleed sequence. It is even kept in nonvolatile storage, so even if you unhook the battery, when you reconnect, it will still be there, saying "really, I mean you have to do a bleed sequence."

    The C1345 means you have to do the linear solenoid offset learning procedure. You probably have to take care of C1451 first, because I think the motor has to be able to run for the linear solenoid procedure.
     
    #2 ChapmanF, Apr 7, 2020
    Last edited by a moderator: Aug 23, 2022
    moon_tanner likes this.
  3. moon_tanner

    moon_tanner Junior Member

    Joined:
    May 29, 2016
    7
    1
    0
    Location:
    NW Florida
    Vehicle:
    2010 Prius
    Model:
    One
    Thank you for the info! I thought I read somewhere that you needed to do C1203 first.

    I'll look into why it's not communicating and go from there.