Parking sensors - aftermarket head unit retrofit
On plenty of cars the parking beep never came from a buzzer of its own. The factory radio made it. Pull that radio out and the sensors keep working while the sound has nowhere to go, so you drive away with a screen you like and a parking system that has gone quiet. A parked car and a few minutes tell you which way yours is built, and that answer decides whether the fix is a menu setting or a wire.
A parking aid system is really two halves, and most people treat it as one. First there are the sensors in the bumper and the module that reads them. Then there is whatever turns that reading into a noise you can hear. A screen swap touches the second half and leaves the first one alone, which is why the sensors carry on clicking while the car goes quiet at the same time.
On a number of Volkswagen and Audi models the workshop literature describes the parking aid control unit as not driving a sounder of its own. The warning tone is output through the vehicle loudspeakers, so it depends on the audio system being fitted, powered and awake. BMW's workshop documentation describes a similar split for its chime, which the audio system generates rather than a standalone buzzer. Build a car that way, take the radio out, and the tone has no home left.
Other cars keep it simple. A small piezo sounder sits behind the dash or in a rear quarter panel, clipped to a bracket with a two-wire pigtail, and the parking module drives it directly. Swap the radio on a car built like that and the beep carries on, because the radio was never part of that circuit. Yours won't stay a mystery for long. It's one or the other, and occasionally a mix of both.
So which one is yours? You can find out in a car park, and it doesn't take tools or a wiring diagram.
The two builds sound identical and behave completely differently once the fascia is off. Here is what separates them, written as things you'd notice rather than as specifications.
| What you remember | Its own sounder made the tone | The audio system made the tone |
|---|---|---|
| Where it came out | One sharp spot under the dash or behind a rear trim panel | The door speakers, spread around you |
| Radio volume at zero, reverse selected | Beep still sounded | Beep went quiet |
| Turning the radio up mid-beep | No change at all | Beep got louder with the music |
| What the screen swap changed | Nothing, unless the install disturbed the sounder's wiring | The tone stopped, because the part that made it is in a box now |
| What usually brings it back | Reseating the sounder connector | A decoder with a tone output, or coding at a workshop |
Some cars feed the tone at a fixed level, so a beep that ignores the volume knob isn't proof on its own. Read the rows as a set rather than picking one.
A decoder translates messages the car already puts on its bus - steering wheel buttons, illumination, climate state, sometimes distance figures - into something the head unit can read. That's a data job. It doesn't put a sound into the cabin by itself, and carrying the distance data is not the same thing as driving a sounder.
Which is how you end up with a parking display and no beep on the same car. A decoder can give you the distance bars without giving you the tone. Check what your wiring actually provides before you assume a firmware update will fill the gap.
Three questions, all answerable from the driver's seat.
Turn the radio's volume right down, select reverse and listen. If the beep still sounds, its source isn't the radio's amplifier output. If it goes quiet, the audio system was making it.
One sharp point under the dash or behind a trim panel means a dedicated sounder. Sound spread around you means the speakers. That single observation saves you a wiring diagram.
If your retrofit draws distance bars that move as you close in, vehicle data is arriving. Bars without sound narrows the fault to the tone output rather than the sensors.
Two of those three cost you nothing but a parked car. I'd run them before ordering a decoder, a sounder or anything else, because the answer changes what you should buy. The common mistake is the other order: buy the part first, then discover your car didn't need it.
There's a fourth thing worth checking while you're sitting there, and it's the one that gets forgotten because it isn't a fault at all. Does the car's own menu still have a parking aid volume or tone setting, and is it still switched on? On some models a battery disconnect during the install resets settings like that, and a parking volume that has quietly gone to zero looks exactly like a dead sensor from the driver's seat. Annoying, but cheap to rule out before you spend anything.
Which path your car uses decides what to try, and no single part covers both. Work in this order, cheapest and most reversible first.
Start in the head unit's own menus. Many retrofits keep a parking or radar sound level in the factory settings, sometimes behind a password, and on some builds the same control sits in the CANbus app instead. This is the one place where a silent unit is usually a setting rather than a wiring problem, and it's the cheapest thing on this list to check.
Then look at the decoder. Some carry a dedicated tone output - a wire meant to drive a small external sounder, or a buzzer built into the box. Others don't, and no menu change creates one that isn't there. Ask for the wiring diagram for your model rather than assuming, and compare the pinout you have against a car where the beep worked.
The screen swap probably didn't kill the sounder. It disturbed a connector, pinched a wire behind the new frame, or left the pigtail unplugged while the fascia went back on. A knocked connector is the usual suspect here. That's a reseat, not a replacement. It goes back to whoever fitted the unit, and it's worth telling them what to look for instead of asking them to fix the beep.
Run the checks above. Guessing costs more, because the two answers lead to different parts and different money.
Here is where the budget goes, and it's worth being blunt about the order. Menu work is free. A decoder with a tone output costs what a decoder costs, and it only helps if your car's tone was coming through the audio system in the first place. Coding means a workshop visit and a bill to match. Where a model's decoder gives you a tone output, that shows up in the fitting notes for that model on our product pages, so you can check before you order. A photo of your connector is usually enough for us to tell you which of the two cases you're in.
Two failures get blamed on the screen because they land in the same week, and both of them predate the install.
A single dead sensor is the first one. One failed sensor can leave the system beeping oddly, beeping short, or silent on one side, and because it lands in the same week as the install it often gets misdiagnosed as the screen's doing. The screen didn't do that. Listen to which side beeps and which stays quiet, then have the sensor checked.
The second is the sounder coming loose. If a dedicated sounder's connector was knocked during the install, the module still works, still measures, and still says nothing. A workshop can reseat it in minutes, and there's no reason to buy anything for that one.
There's a third possibility that only a scan will settle. On some cars the parking module logs a communication fault when a node it used to talk to disappears from the bus, and it can stop reporting until somebody clears that fault. You can't read it off the dashboard, and you can't fix it from the head unit's settings. A workshop scan tells you whether the fault exists, which is the difference between a loose connector and a module that has parked itself.
That's the honest boundary of what you can do yourself. Listening, reading menus and taking photos are yours. A scan and anything behind the trim belong to a workshop, and knowing which side of that line you're on is what actually breaks the guessing habit before it costs you money.
Still quiet after the checks? Then the connector and the decoder are the next things to look at together.
Ask our support deskHave the unit model, the build string, the decoder you fitted and photos of the parking connector ready, and the answer will match your car.
Zhuhai WITSON Industrial Co., Ltd. - Tel: +86-756-8120312, 8120211, 8120212.
No. The sensors are fine.
Sometimes, and it depends on which half was making the noise. If the tone came through the factory audio system, you're trying to rebuild a sound path that the swap removed - a decoder with a tone output is the usual answer, and coding is the expensive one. If a dedicated sounder was making it, that path is still in the car and you're hunting a disturbed connector instead. Same symptom, very different bill.
That the vehicle data is arriving and only the sound is missing. If the bars move as you close in, it isn't the sensors. Check the unit's parking or radar sound level first, then the decoder's tone output.
Not always. A decoder is there to translate vehicle messages. Whether it can also produce a tone is a wiring question for your model, and plenty of decoders carry the distance data without driving a sounder at all.
Rarely. A new build can change how a tone gets generated, but it can't add an output the harness doesn't have.
