Lots of dash lights after checking horn fuse

[Chruzz]

Thanks Don. Will do. Apologies. Trying my best to work with the only info I have. Cheers. Will post more detailed info once I have Obd11


Sent from my iPhone using Tapatalk

[DV52]

@Chruzz: No apology needed - I understand entirely your frustration!!

Assuming that you will be new to OBD11 and from my moderator experience on the OBD11 forum regarding new-bees - I suspect that that you may have difficulties getting the information on the mobile-phone screens into a form that can be posted here. If so and assuming that you will be using iOS software version of OBD11, here are the steps for digitizing the SCAN reports.

After the OBD11 scan is completed - do this:

1. Exit OBD11 software and start a new session (note: you don't need to plug-in the dongle to the car's OBD port, or connect to the dongle)
2. Click on the Garage tab on the lower part of the Home screen
3. Select the car from the list of vehicles - if you have more than one vehicle registered under your account
4. Scroll-down the car-information screen and click on History
5. Follow the instructions below:
   
6. After you receive the file that you sent to your email in the last step above - attach the contents to a new post here

Don

[Chruzz]

Thanks Don, for helping me with the OBD11 export. I tried copy and pasting full scan but the Forum says it is too many characters. I have uploaded a TXT file to my server: http://halfnine.com.au/OBDeleven_Log_full_export.txt


Since my first post I have replaced water pump and belt, replaced battery, replaced key fob battery. I have also continuity tested all fuses. I have disconnected Brake Control Module cable and sprayed contact cleaner on the terminals.


OBD11 can't scan the Brake Control Module. OBD11 says "Error - Control Unit not responding. Check ignition and try again" This is while I have the ignition on and car running.

Should I be looking at wheel sensors or something else? Maybe I should just take it to a mechanic or auto-electrician?

[DV52]

@chruzz: Hmm........ no offense, but we have gone from the sublime to the ridiculous!! Meaning that you started this thread with very little actual diagnostic information and now we are inundated with an avalanche of diagnostic data!!

So- your "full export" file is replete with both historic errors and with current faults. And the file contains lots of information that really isn't helpful to the subject of your thread - so very confusing!!

I think that we should attempt to distill the diagnostic data to just those elements that pertain to your airbag issue - and the Brake module which appears to be missing from your SCAN reports (which is concerning).

So - in respect of the latter issue - I suggest that you first try to clear ALL errors and then make a fresh SCAN with the ignition-ON and the engine OFF. Hopefully the new scan will include the hex03 module - if so, please post-up just the details for this latest SCAN (ensure that "Full scan" is the only radio button ticked in my 2nd screenshot and cut-and-paste ONLY the latest scan)

Also, your multiple SCANs record the following for the Engine module:
01 Engine

Faults:
U012100 - Lost Communication With
Anti-Lock Brake System (ABS) Control Module
static
Priority - 2
Malfunction frequency counter - 1
Unlearning counter - 255
km-Mileage - 184810 km
Engine speed - 803.50 1/min
Normed load value - 28.2 %
Vehicle speed - 255 km/h
Coolant temperature - 31 °C
Intake air temperature - 15 °C
Ambient air pressure - 1020 mbar
Voltage terminal 30 - 13.264 V
Dynamic environmental data - 209628105F0014CB00
date - 2023-06-20 19:47:56

I've highlighted the aspects of the fault's freeze-frame data that are pertinent to the missing Brake module .

So - the date record for this fault suggests that you "disconnected Brake Control Module cable" last Tuesday @ about 7:47PM. Is this correct?

And, whilst I ask this further question with a degree of incredulity - how the F#ck did you manage to "disconnect the Brake Control Module cable" with the Vehicle speed= 255 km/h?


As for the former matter issue which is really the subject matter of this thread - I note the following from your multiple SCANs:

15 Airbag

Faults:
B13BCF2 - Multiple collision brake
No function
static
Priority - 2
Malfunction frequency counter - 1
Unlearning counter - 255
km-Mileage - 184810 km
date - 2023-05-31 10:18:03

So - the date record for this fault is about 2 x weeks before your first post and the fault descriptor suggests that somehow the Airbag module lost its Multiple collision brake function! Was the car involved in a collision (was this the reason for replacing the water pump/belt and battery)? If not what was the car doing on this date?

And also if not, is this the reason why you "disconnected the Brake control module cable" (i.e. you assume that the fault was caused by a wiring/pin issue at the Brake module connector)?

Don

[Chruzz]

I did clear the errors (twice) and was only doing what I was requested by uploading the whole log file. I am sorry to have confused the issue further. I would have distilled the log file but thought I might cut out important info.


Sent from my iPhone using Tapatalk

[Chruzz]

There was no collision. Water pump was leaking. Problem all started when battery got low, key fob battery was replaced and was looking at fuses for airbag before replacing clock spring.


Sent from my iPhone using Tapatalk

[DV52]

I did clear the errors (twice) and was only doing what I was requested by uploading the whole log file. I am sorry to have confused the issue further. I would have distilled the log file but thought I might cut out important info.


There was no collision. Water pump was leaking. Problem all started when battery got low, key fob battery was replaced and was looking at fuses for airbag before replacing clock spring.

@Chruzz: OK, I meant NO criticism. I agree - generally more information is certainly better than less!!

Given your confirmation that this car wasn't involved in a collision - I researched the literature and I found reference to the B13BCF2 - Multiple collision brake No function error in a VAG Technical Service Bulletin (TSB 69-19-43).

Now, the TSB was released by Audi - but it relates to ALL vehicles that have a MQB platform build. However, whilst this Polo is not quite the same, the 6C0 chassis on this car does share many Volkswagen Group MQB A0 platform features. So, the TSB is also likely to apply to this car! It might be prudent to check this with a dealer

Anyhow - these are the words in the TSB (I've highlighted relevant bits):

Model - ALL

YEAR - 2015 to 2020

Condition

Customer states:

• The airbag warning light is illuminated in the instrument cluster.

Workshop findings:

The following DTC is stored in the airbag control module (J234):

• DTC B13BCF2 (Multiple collision brake No function) and can be active/static or passive/sporadic.

Technical Background

The “Multiple collision brake” is controlled by the ABS control module, J104, (address word 0003) and part of the ABS/ESC functionality.

If the ABS control module detects an ABS/ESC relevant error, the “Multiple collision brake” is deactivated. In addition, the ESC and airbag warning lights are turned on in the instrument cluster and DTC B13BCF2 is stored in the airbag control module.

If the brake system relevant error is passive/sporadic and not detected again, the ESC warning light is turned off after the next ignition cycle. Any DTCs that were stored in the ABS control module will be erased after 40 ignition cycles if not detected again.

In contrast, the airbag warning light will stay on permanently until the DTC B13BCF2 in the airbag control module is erased manually. The “Multiple collision brake” will stay deactivated as long as DTC B13BCF2 is stored in the airbag control module.

Service

1. Connect vehicle to ODIS Service and perform a scan with GFF. Follow GFF for any DTCs that could have caused a deactivation of ABS/ESC functionality. If these DTCs are present, follow GFF to determine and eliminate the root cause. Once the root cause has been eliminated, delete DTC B13BCF2 in the airbag control module.

2. If no DTCs were present that could explain the deactivation of ABS/ESC functionality, erase the DTC B13BCF2 in the airbag control module.

3. Release the vehicle to the customer without attempting any additional repairs.

4. If the customer experiences this concern again, a vehicle scan with GFF should be performed immediately to determine the root cause.

Note:

Replacing the airbag control module does not solve this issue. Claims for replaced parts will be subject to review

"GFF" in the TSB means Guided Fault Finding - which are a set of detailed steps that VAG make available to their technicians (generally GFFs are not available outside dealerships)

Again, I suggest that you make a fresh SCAN with ignition-ON and Engine OFF - my experience is that for a simple SCAN, it's best NOT to ask the Gateway module to function both in diagnostic mode AND as the CAN bus coordinator in engine running mode (when the Gateway module needs to manage lots more CAN messages )

For what it's worth and IMO of course, what's needed here given the information in the TSB is for your SCAN to show the error messages that are recorded in fault memory in the Brake module. As suggested in the TSB, your focus should then be to "eliminate the root cause" of the Brake module faults

After ALL faults are cleared in the Brake module - you should then be able to manually clear the Airbag module error (again, as suggested in the TSB)

Don

PS: you can find the TSB HERE and there's another copy for the NAR market HERE

[Chruzz]

Thanks Don. Happy to receive any criticism. Just trying to figure it out and appreciate the help given. Thank you for your efforts.


Sent from my iPhone using Tapatalk

[MIG]

how the F#ck did you manage to "disconnect the Brake Control Module cable" with the Vehicle speed= 255 km/h?


Don

The speed data in the freeze frame is reported from the ABS unit, 255km is the value reported when there is no signal.

The airbag fault is due to the ABS unit being tied into the auto brake feature after a airbag deployment.

Both faults are consistent with a loss of signal from the ABS unit.

If I was working on this, I would be testing powers, grounds and the CAN signals at the ABS units connector.




Sent from my SM-N960F using Tapatalk

[Chruzz]

OBD11 can't scan the Brake Control Module. OBD11 says "Error - Control Unit not responding. Check ignition and try again"

So testing for power at the BCM would be a good place to start I guess.

Would I be better off with VW service department or independent auto electrician?


Sent from my iPhone using Tapatalk