GCC Spec Subaru Legacy BL 2009 Speed Limit Chime

[tafa]

Hi all,

First post here. I've just come across FastECU and the BIU work going on around it, and it's exactly the kind of thing I've been hoping existed. Big thanks to everyone contributing.

• Car details:
  Model: 2009 Subaru Legacy 3.0R (BL chassis, sedan)
  Engine: EZ30 H6
  Transmission: automatic (5EAT)
  Market: GCC / Gulf spec, Saudi Arabia
  VIN: JF1BL09H79G052504

The problem. Here in Saudi Arabia every car sold new has a mandatory speed warning: a continuous beep that sounds the whole time you're above 120 km/h. On mine it's constant and pretty maddening on the open road, and I'd like to understand it properly and switch it off at the source rather than just muffling it.

I don't really know yet how it's done on this car. What I've heard from others is that it's either a buzzer inside the speedometer/cluster, or possibly an option somewhere in the BIU. I've also heard that the sound comes from the buzzer on the Body Control Module. and that's about as far as my understanding goes right now.

So I'm starting the journey: I want to use FastECU and the open-source tools around it to actually find out how the warning is triggered on a Gulf-spec car, and hopefully find a clean way to disable it. Happy to go slow, read first, and document everything as I go.

One more thing I've heard: even if there turns out to be no BIU setting for the speed warning, FastECU can do live reading and logging. So my plan is to connect, read and log while driving above 120 km/h (with someone else at the wheel), and watch what changes when the chime kicks in, to work out where it is actually coming from.

A few questions to get me started:

What's the recommended way to begin reading my BIU with FastECU on this generation? Anything Gulf-spec I should watch for?
Is there any BIU customise/option that could plausibly relate to a speed warning, or is the cluster the more likely home for it?
For cables, what is recommended to get me started without issues? don't care about price.

I'm one of many here in the Gulf living with this chime, so I'm taking this on as a bit of a mission, hopefully to save others in the region from the same misery. Gulf-market cars might be less common in your data, so I'm very happy to run any READ commands and share my results to help the project, even if it takes a while to crack. I've heard our destination code is KS

Thanks again for building all this. Looking forward to getting stuck in.

[MiikaS]

@rimwall do you have any suggestions?

[rimwall]

Hi, FastECU cannot read or modify the BIU ROM.

However, FastECU does replicate some SSM BIU commands that can be used to change some of the BIU settings. SSMIII can also be used to change some of the BIU settings.

Perhaps the first step is to see if you can get the BIU module of FastECU working with your car. Try reading the current BIU data as the first step.