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

Constant audible tone that increases with speed

Discussion in 'Gen 3 Prius Audio and Electronics' started by Ukajico, Aug 29, 2024.

  1. Ukajico

    Ukajico New Member

    Joined:
    Aug 29, 2024
    1
    0
    0
    Location:
    Chicago
    Vehicle:
    2010 Prius
    Model:
    Three
    Hi. Hoping to get some idea of what may be going on with our 2010 Prius. The hazard lights began flickering eratically and in step with the speed of the vehicle. Not able to stop them even when the car was turned off. After some research online regarding the skid control ecu issue switching the hazards on and off I snipped the pale blue Pin 10 wire and the hazards stopped immediately. I had full control of turn signals and hazards and all was fine until a few minutes into driving there was an audible tone that kind of juttered into existence, meaning it sounded like it was kind of connecting/ disconnecting a few times until it established itself as a consistent beep tone that when stationary, stayed on , but when moving, it began to beep instep with the vehicles speed, just as the hazards had done, only now it was an audible tone. Lots more research and I cannot find anyone online with the same issue as this. The beeping goes away when i disconnect the skid ecu wiring plug, but that makes the car inopperable anyway so not a solution. any advice would be very welcome. TIA !!
     
  2. MAX2

    MAX2 Member

    Joined:
    Aug 12, 2024
    371
    88
    10
    Location:
    Third Rock from the Sun
    Vehicle:
    2007 Prius
    Model:
    N/A
    Problems with the ABS system. This is very serious for safe driving. By turning off the indicator on the dashboard, you did not solve the problem, but only closed your eyes to it. But you still have a sense of hearing, so the hybrid beeps at you - repair the "brake system or don't drive the car"
     
  3. ASRDogman

    ASRDogman Senior Member

    Joined:
    May 29, 2018
    6,426
    3,413
    0
    Location:
    Florida
    Vehicle:
    2010 Prius
    Model:
    Two
    Snipping and cutting only makes things worse!

    Get a code reader that works for the Prius and do a proper diagnoises to find out WHY you are
    getting the beeping.

    Hunting and pecking and hacking will only make things worse....

     
  4. ChapmanF

    ChapmanF Senior Member

    Joined:
    Mar 30, 2008
    24,915
    16,216
    0
    Location:
    Indiana, USA
    Vehicle:
    2010 Prius
    Model:
    IV
    In the case of the "hazards flash at road-speed-proportional rate" known glitch, the problem really is that two adjacent pins at the brake ECU have become shorted together, SP1 and HZRI.

    [​IMG]

    SP1 is an output that gets pulsed to ground at a speed-proportional rate, for use by other things in the car as a signal of road speed. HZRI is meant as a brake ECU input (so the brake ECU knows when you have turned the hazards on, though I've never been sure why it cares), but if you short HZRI to ground it will sho'nuff turn the hazards on, so when that "input" gets shorted to the SP1 output, you end up with your hazards flashing at a rate that gets faster with road speed. (Not just the dash indicator ... the actual hazard lights all around.)

    Cutting HZRI at that point doesn't solve the underlying problem, the short between those two pins that has somehow developed inside the brake ECU. But it does solve the annoying part of the problem, having the ding-binged hazards flash all the time at your road speed. The only problem it creates is that now the brake ECU won't know when you have turned the flashers on (as if anybody ever figured out why it would care). Nobody has yet reported any ill effect from the brake ECU not knowing when the hazards are on.

    This is not the kind of problem that the brake ECU is going to give you trouble codes about. It is an electrical short that has arisen between two of its circuits that are not supposed to be related to each other, a hardware failure that was never anticipated or covered by any self-test. The ECU is just broken, it doesn't know it's broken, and the fix is to swap in an ECU that isn't broken.

    (Therefore, what I would likely do if it happened to me is to just back the HZRI pin out of the connector instead of cutting the wire, so I could just pop it back in later after getting around to replacing the actuator).

    To my knowledge, no one has yet examined an actuator with this problem to determine exactly where the short arises. I think @LeftyLucy checked for obvious bridging corrosion between those two adjacent pins, outwardly visible in the connector, and it wasn't there, but no one later opened the housing further to inspect the inside. I'll do it, if anybody sends me an actuator that was taken out for this problem.

    If it turns out to be something like corrosion between those two pins inside the housing or on the circuit board, there might be an easy fix. But it might turn out to be a short that develops in silicon, and not really fixable.

    The beeping behavior described in this post is new to me. The pulse rate proportional to road speed seems again a dead giveaway for something getting bridged to the SP1 signal. The next question might be: does anything connected to the brake ECU make a beeping noise when grounded?

    Might as well start with the obvious guess: the Skid Control Buzzer Assembly connects to the ECU via the brown wire at pin 13 (BZ), and beeps when the ECU grounds that wire—that's what it's for. BZ (pin 13) is not right next to SP1 (pin 11), but it's pretty close—keeping in mind that no one has looked yet to see just how those circuits are routed inside the ECU.

    It could be that some progressive failure inside the ECU first shorted SP1 and HZRI (as seems to commonly happen), and may now have also shorted SP1 and BZ.

    Pin 12, by the way, is IG2, where the ECU receives power from the IGN fuse. Whatever it is that causes shorting of pins in this area, if it ever ends up shorting SP1 and IG2, either that fuse is going to blow or some more magic smoke will escape the ECU.

    Again, this is the kind of electronic hardware failure that happens below the level of any trouble codes the ECU would give you. It's just broken. The real fix is an ECU that isn't broken. But it would be of definite interest to do a post-mortem on one of these and try to determine what exactly goes.
     
    Brian1954 likes this.
  5. LeftyLucy

    LeftyLucy Junior Member

    Joined:
    Sep 12, 2021
    8
    3
    0
    Location:
    Massachusetts, USA
    Vehicle:
    2010 Prius
    Model:
    II
    I had plans to open up the ECU the next time it generated diagnostic codes (which were always related to speed too low on the right rear as I recall). However, I think I've had only one code in the last two years and it was brief. This is pure speculation, but I've been making an effort to keep the wiper cowling clear of detritus since I cut the wire and this may have helped. That first time, the drain ports of the cowling were clogged, so water may have accumulated and dripped on the ECU housing which shows a lot of evidence of corrosion. Alternatively, the last two winters in the Boston area have been mild and much less salt has been put down on the road.
     
  6. BiomedO1

    BiomedO1 Senior Member

    Joined:
    Mar 27, 2021
    1,836
    934
    0
    Location:
    SacTown, Ca
    Vehicle:
    2021 Prius Prime
    Model:
    LE
    If there's a lot of corrosion on the ECU housing, it may be prudent to place a coat of flex seal or snow roof over it. Just to keep out the moisture. But if that ECU housing is also used as a heat-sink, you run the risk of over heating the circuits within.
    Pick your poison...