MIB2 - fault 7223 - Function Restricted due to Missing Message(s)

[ZERO815]

Hey,

Car is a NA '17 GTI SE that came w/ MIB2, carplay, RVC, bluetooth, no NAV. Last fall I retrofitted the 8"screen from a MK7.5 to it. Ever since I have the following fault although everything appears to be working correct:

Address 5F: Information Electr. (J794) Labels:| 5G0-035-MIB-STD2.clb
Part No SW: 3Q0 035 844 A HW: 3Q0 035 844 A
Component: MU-S-S-US 710 0751
Serial number:
Coding: 027300000000000051110002001B0A009F0203F40120010002
Shop #: WSC 12345 123 61029
ASAM Dataset: EV_MUStd4CDELP 001001
ROD: EV_MUStd4CDELP_VW37.rod
VCID: 2D1208E47C4044EE90-8078

Operating And Display Unit 1:
Subsystem 1 - Part No SW: 5G6 919 605 A HW: 5G6 919 605 A
Component: ABT_Std-2 H50 8130
Serial number: VWZ6ZJT1811284

7223 - Function Restricted due to Missing Message(s)
U1111 00 [009] - -
[ENI (0x37) - function restriction due to communication error - BapErr_retry not successful]
Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 6
Fault Frequency: 1
Reset counter: 0
Mileage: 60501 km
Date: 2020.07.18
Time: 21:25:54

Voltage terminal 30: 12.0 V
BAP-BAP_Function_ID: 02

Does anybody have any idea why I have this fault? Erased DTCs and it comes back immediately. Of course I have googled the fault code already and interestingly it even shows up on ross-tech page under Reference Scans and Maps of Non-Broken Cars ... 2020 Golf, 2.0T DKFA | Ross-Tech Forums (ross-tech.com)

 

[esteticu]

Not sure what it is, I had it also after MIB2 retrofit, probably the donor car had something you did not, but you can disable it with VCDS / Adaptations:

Address 5F,5NA 035 042 A,channel ENG122229-ENG125829-Car_Function_List_BAP_Gen2-ENI_0x37,adapted from,activated ,to,not activated ,Monday,04,September,2023,10:51:49:58756

 

[DV52]

@ZERO815 : Hi
Look at the freeze frame data in your error- notice the date = 2020.07.18. If VCDS is reporting date correctly (sometimes it doesn't) - this is the date that this fault was first registered in the module's fault memory.

Now notice Fault Frequency =1. This means that in the period between the date of the VCDS scan and the date above (i.e. the date when first registered), the same fault has NOT been re-registered in fault memory in a subsequent ignition cycle.

So, again assuming that VCDS is reporting date correctly - this is what I call an "aged DTC". If it can't be cleared - not worth worrying about!! Also notice Priority: 6. This is a low priority rating - so not serious in VW's view!

To confirm the date entry - how does Mileage: 60501 km compare with the odometer reading when the SCAN report was made?

Don

PS: BapErr_retry not successful does provide some intelligence to the nature of the DTC . Bap Protocol (Bedien und Anzeige/Control and display) is a Transport Protocol developed by VW - it's used for exchanging information between different devices on the CAN network. The error descriptor suggests (to me at least) that the coding in the hex 5F module was inconsistent with the other modules in the car (as @esteticu says)

 

[ZERO815]

Thanks for your replies.

The Mileage is about right, and Priority 6 made me forget about it. However: "ENG122229-ENG125829-Car_Function_List_BAP_Gen2-ENI_0x37,adapted from,activated ,to,not activated" fixed it! Thank you @esteticu for your suggestion.

 

[Cuzoe]

I just want to chime and say that I appreciate your post, as it will help in my 5F adaptation "clean up" project. I don't have any faults, but I don't like that I have some menus "activated" but the actual function is not activated.
I have no idea what "ENI" is, and the adaptation you changed was already set to "not activated" but the menus were still active... not anymore.

ENG122229-ENG125829-Car_Function_List_BAP_Gen2-ENI_0x37	not activated
ENG122229-ENG125830-Car_Function_List_BAP_Gen2-ENI_0x37_msg_bus	Comfort data bus

ENG122227-ENG126144-Car_Function_Adaptations_Gen2-menu_display_ENI	activated > not activated
ENG122227-ENG126147-Car_Function_Adaptations_Gen2-menu_display_ENI_after_disclaimer	not activated
ENG122227-ENG127000-Car_Function_Adaptations_Gen2-menu_display_ENI_clamp_15_off	not activated
ENG122227-ENG126145-Car_Function_Adaptations_Gen2-menu_display_ENI_over_threshold_high	activated > not activated
ENG122227-ENG126146-Car_Function_Adaptations_Gen2-menu_display_ENI_standstill	not activated

 

[DV52]

@Cuzoe: Yeah - me too!! I was intrigued by "ENI". Tried to find-out what the acronym meant, but no success.

As for the magic ENI channel ENG122229-ENG125829-Car_Function_List_BAP_Gen2-ENI_0x37, it appears that lots of cars have it activated and many do not - see HERE

Given the accompanying BAP error, it seems reasonable (to me at least) to assume that the status for the channel setting is linked to the presence of a particular module on the CAN Network (because BAP is an interchange comms protocol). But looking through the SCANs in my link - I have no idea which module? Maybe you can find a pattern?

Don

 

[Cuzoe]

@DV52 I missed the link in your post. I'm legitimately looking forward to digging through those results while I sit through the Monday morning Zoom/Teams meetings.