Error log entries despite normal function

Hello everyone,

I have also repeatedly encountered the following errors even after clearing the fault memory in Autoscan, although there were no functional issues.

Do you have any tips for me on how to identify the root causes?

131687 - Control unit for emergency call module and communication unit
U1421 00 [00001000] - No communication
[Timeout_Node_0x67_DiagAdress_0075_ConBox]
Sporadisch - bestätigt - geprüft seit letzter Löschung
Environmental Conditions:
Error Priority: 4
Frequency of Errors: 1
Lost Count: 249
Mileage: 29627 km
Date: 2026.05.30
Time: 18:23:09

131830 - Ethernet Emergency Module
U1642 00 [00001000] - No communication
[Timeout_Node_0xF6_conBox_DiagAdress_0075]
Sporadisch - bestätigt - geprüft seit letzter Löschung
Environmental Conditions:
Error Priority: 4
Frequency of Errors: 1
Lost Count: 249
Mileage: 29627 km
Date: 2026.05.30
Time: 18:20:28

262727 - Function restriction due to missing message
U1111 00 [00001001] - -
[BAP_Timeout_ConnectionManager]
Confirmed - Verified since last deletion
Environmental Conditions:
Error Priority: 6
Frequency of Errors: 2
Lost Count: 209
Odometer: 29625 km
Date: 2026.05.30
Time: 18:15:24


Also, the microphone error also reappears after deleting, even though the hands-free function is working perfectly.

Address A6: Microphone (J886) Label file: .420-907-394.clb
Part Number SW: 420 907 394 B HW: 420 907 394
Part: BELTMICBOX H10 0840
Encoding: 0101040202
Operating Number: WSC 02664 785 00200
ASAM Dataset: EV_BeltMicPARAGAU335 003011
ROD: EV_BeltMicPARAGAU335.rod
VCID: 186D1E49321E7F6A563-804C

1 Error found:
0128 - Telephone Microphone
B1048 13 [00001001] - Interrupt
Confirmed - Verified since last deletion
Environmental Conditions:
Error Priority: 4
Frequency of Errors: 1
Lost Count: 208
Odometer: 29625 km
Date: 2026.05.30
Time: 18:14:51

Hello,

In your customer account, VCDS 26.3 is available for download. There may also be new labels for your control units included.

But it has nothing to do with the problem. If the control units are responsive and functioning during the vehicle scan, the problem could also be caused by software errors in the control units, in addition to wiring problems.

The microphone issue appears to be due to a real physical connection problem (cable, connector, or the microphone itself).

If everything works as intended, I would first clear all the errors and then see what happens. Often, throughout the vehicle's lifespan, software updates are available to fix minor issues.

Therefore, I wouldn't get worked up about it right now.

Best regards, Rainer

I have absolutely no knowledge of the R8. Therefore, I can only make guesses. Maybe it will still help.

According to online sources, the "Beltmicbox" module is supposed to have three microphones per belt. The cables are woven into the belt. Probably very thin. Have you ever used the microphone on the ceiling and the two belt microphones when making phone calls to check if each one works? I suspect a single defect that is compensated for by the remaining microphones. Maybe we'll switch completely to the ceiling microphone.
I suspect that there is a broken cable somewhere in the strap. However, you will only be able to replace it completely with a new strap. So, entweder man mit dem Fehler leben muss, oder man kauft einen neuen Gurt.

And regarding the emergency call module, I would either suspect a defect in the module itself, or possibly a subsequent error with the microphone. The microphone harnesses were likely a relatively rare extra (especially for a car that was already relatively rare). Therefore, the question is how extensively the emergency call module has been tested for errors in these additional microphones.

Here's some more information about coding etc. Maybe this will help you: https://www.r8talk.com/threads/seat-belt-mic-stopped-working.141369