Latest News:

autotechnician - serving the independent workshop - logo
Valeo LB1 September October November and December 2026

Case study: Audi A5 Brake Light Fault

By autotech-nath on October 30, 2026

I am always on the lookout for interesting jobs that would make a good read in the magazine. This car was exactly that. It caused a few head-scratches along the way, but as always, armed with a good process, technical information, and a solid plan ensured the root cause was correctly identified.

The car in question was a 2016 Audi A5, which I was asked to look at for another garage. The customer’s complaint was that all the tail lights were constantly flickering on and off, which had caused the vehicle to fail its MOT inspection. The garage had already done some initial checks and found fault code 00526 - Brake Light Switch (F): Implausible Signal stored in the comfort control module. They replaced it with a new aftermarket part, but the fault code and symptoms remained. After checking a few other bits and pieces to no avail, they contacted me to see if I could get to the bottom of it.

Arriving at the car and confirming the complaint, I noticed that as soon as the ignition was turned on, both LED tail lamps and the high-level brake lamp would flicker on and off repeatedly. This was constant until the key was removed, turning the light switch on and off had no effect. Due to this issue, the rear lamps would not operate correctly, hence the MOT failure.

Questioning the garage staff, I found out that this car had come to them from another workshop that had just replaced the clutch and flywheel. The customer insisted these symptoms were not present before that work was carried out. At this point, I could only go off the garage’s word and start afresh. The garage I was working with also noted that when they initially looked at the vehicle, they found a blown multi-fuse in the fuse box on top of the 12V battery under the bonnet. I took a mental note of this, as it could easily be related to the previous repair.

Live data clues...

Since I had confirmed the complaint, I decided to scan the entire vehicle for fault codes. Carrying out an auto- scan revealed all sorts of faults stored in multiple control units. Reading the comfort control ECU, I found the same brake switch implausible signal fault the garage had mentioned. A quick look at the brake pedal itself revealed a shiny new brake lamp switch, confirming it had indeed been replaced.

Next, I decided to view live data to see if the switch position changed from on to off. However, being a VAG-range vehicle, this particular ECU used binary logic, so I was met with a list of 0s and 1s. Now, I am no expert on VAG, but from previous experience, I have learned that generally, 0 means off or inactive, and 1 means on or active. I decided to loosely use this as my guide, Figure 1.

Figure 1.

Viewing the data, the numbers could be seen cycling from 0 to 1 repeatedly without anyone touching the brake pedal. This perfectly matched the flickering tail lights and looked to be directly related to the fault. I then decided to scope the brake light switch circuit to see if the signal was doing something strange. Accessing the switch revealed three wires: a power supply, a ground, and a signal wire. A little research showed the sensor to be a Hall-effect type, so I expected a clean digital on/off change in voltage depending on pedal position.


Upon measuring the three wires at the switch, I found 12V, earth, and a very small change from around 1V down to 0 and back when pressing the brake pedal. This was clearly wrong. A Hall sensor generally produces a signal with a voltage level matching the supply, though this is not always the case, so it pays not to assume. Interestingly, removing the brake light switch entirely and rechecking the symptoms showed the tail lamps were still flickering. This proved the brake switch issue was merely a symptom, not the cause. I checked the signal wire from the switch to the control units—which on this model splits to the engine ECU and the comfort convenience module in the boot—and found good continuity, low resistance values, and no shorts to positive or ground. I advised the garage that the new aftermarket switch was not working correctly and recommended fitting a genuine unit moving forward, though I noted this alone would not fix the flickering light complaint.

While testing the wiring at the convenience module, I noticed a wire had been de-pinned from one of the connectors. Questioning the garage, they told me they had removed the wire to the high-level brake lamp just in case it was back-feeding something. The connector housing had also been left off, and the module connector was gently pushed onto the bare pins of the corresponding slot. I carried out a few more checks and found nothing wrong, but I heavily suspected something was shorting or back-feeding a circuit. At this point, I had been at the garage for several hours after also looking at some other problematic vehicles. I decided I needed to head back, carry out some product research, gather wiring diagrams, and revisit the vehicle fresh. This would also allow time for the new genuine brake light switch to arrive so I could retest the circuit.

Back to the wiring diagrams...

While away from the vehicle, I printed off the relevant module diagrams and system operations to better understand how the lighting system worked on this Audi. The schematics showed that the convenience control module directly controlled the outputs to both rear lamps and the high-level lamp, while receiving a brake lamp signal input from the switch. I planned to probe every wire on that unit, see if anything looked incorrect, and trace it back if required.

A few days later, I arrived back at the car. The garage informed me that the new genuine switch had arrived, but fitting it had not fixed the brake light switch fault code, and the lights were still flickering. I explained that because the wiring checked out, I needed to retest the signal to confirm my previous findings. Scoping the signal from the new genuine switch now showed a good 0–12V on/off toggle—exactly what I expected, Figure 2. However, just as the garage said, the fault code still would not clear, and the live data still showed a flickering binary value. I was satisfied that the switch was now working correctly compared to the aftermarket sensor, meaning I could ignore it and trace what was actually driving the flickering. I also considered it possible that the flickering issue itself was triggering the brake switch fault code, even though our brake switch input operation was now correct. I should note here that the engine ECU did not log any faults for the brake light signal; the code was only present in the comfort module, even though they shared the same signal wire.

Figure 2.


I now proceeded with my plan to test each wire at the comfort module. Working through each connector, I could not see any abnormal signals. However, the high- level brake lamp wire was still removed from its position in the connector. I reconnected it and measured the wire, only to find a strange, cycling signal that clearly wasn't right, Figure 3. This signal had to be coming from the module itself. To prove this, I de-pinned it again and gently measured directly on the male pin of the module. The same fluctuating signal was present, confirming my theory.

Figure 3.

The next question was: why is this signal being created? Stopping to think for a second, I wrote down the possible causes and a plan. It had to be either a wiring issue (such as a missing or incorrect power/ground supply), a bad input causing the module to react this way, or an internal fault within the module itself. My plan was to test each variable and eliminate them one by one.

Referring back to the diagrams, I verified that all power, ground, and communication signals tested perfectly under load. I ran through all the connected wires and found no issues apart from that strange signal on the high-level brake lamp output pin. Next, I disconnected each ECU connector one by one until I left only the main power connector and the connector containing the CAN bus wiring attached. Even with all other inputs removed, the signal was still present on the output pin. Finally, I removed the module entirely, manually powered it up on a test bench, and measured the output wire. The incorrect signal was still there. This conclusively proved the fault lay within the control unit itself; with zero inputs connected and the module isolated on the bench; no outside influences could affect it.

Repair and result...

I notified the garage of my findings and advised that a replacement module needed to be fitted and programmed, after which the light operation could be tested and the fault codes rechecked. A few days later, the garage called to say the customer had opted for a second-hand unit due to the high costs they had recently incurred with the clutch and flywheel replacement. They decided to send the original ECU away to be cloned so the second-hand unit would be entirely plug-and-play.

After about a week, I received a message confirming that the cloned module had been fitted. The flickering lights were completely fixed, and a quick scan showed no remaining brake switch plausibility faults. This was clearly an internal failure within the old module. I can only presume that whatever shorted and blew the main fuse under the bonnet during the flywheel and clutch replacement also spiked the control unit, resulting in this bizarre output to the tail lights—especially since the customer noted the vehicle was faultless until that work was carried out.

Takeaway...

I asked the garage to take a short video of good binary data from the brake light switch for future reference. Now with the system operating normally, 000 was no pedal pressed, 011 was the pedal halfway and full depressed then changed to 111. As I mentioned at the start of this article, some faults can initially appear tricky to diagnose. However, working methodically will always be the best way to tackle these sorts of problems.

SHARE THIS
ACTronics MPU 300x225 2026 on
ARCHIVES

Archives

About Autotechnician
Autotechnician is a magazine published nine times a year, delivering essential information to independent garage owners and technicians in the UK. Delivered both digitally and in print, autotechnician provides readers with technical, training, business advice, product and news, allowing our readers to keep up to date with information they need to run and work within a modern workshop.
©
2026
Aftermarket Media Solutions Ltd, The Joiners Shop, Historic Dockyard Chatham, Kent ME4 4TZ
T: 01634 816 165
Company no. 09625886
Febi LHS Nov 2026
Valeo Sticky RHS Nov and Dec 2026
linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram