8E Module Nonsense Fault Code

[GilliamOS]

So this is the third time I've gotten this "factory" code. When I get it, it of course takes ACC and brake guard with it, which is annoying. The main code and resulting codes can be cleared and I can go on my way. I can also restart the car and even with the faults stored, use lane departure and ACC normally. It's dumb and I'm kinda frustrated there's almost nothing document about this. The code only shows up on startup, never when driving. Idle time between starts seems to not matter either.

I have a feeling there is a intermittent failure in the IP module in the passenger footwell and that's my culprit. I wonder if turning off lane departure in coding would stop this code, but allow me to retain ACC. Last time I had my maps updated at the dealer, my codings were reset, but they somehow didn't get lane departure enabled, yet I seem to recall the car didn't care and ACC worked regardless. I could also be misremembering as it was years ago.

Anyone know what I should be chasing or am I just going to replace the controller under the carpet? Is it there a TSB talking about this and maybe a firmware update the dealer can do? I saw a similar TSB for the Euro version that has firmware updates for the module.

                Address 8E: Image Processing       Labels: 4H0-907-107-V2.clb
Control Module Part Number: 4G0 907 107 E    HW: 4H0 907 107 
  Component and/or Version: BV-SG         H31 0041
           Software Coding: 04C198180111
            Work Shop Code: WSC 45876 528 143098
              ASAM Dataset: EV_BC7 001001 (AU57)
                       ROD: EV_BC7.rod

1 Fault Found:

0003 - Data Set Implausible 
          B2012 00 [008] - -
          [New feature! Extended UDS fault detail is only supported by current gen. interfaces]
          Intermittent - Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 3
                    Fault Frequency: 1
                    Reset counter: 72
                    Mileage: 134932 km
                    Date: 2020.08.27
                    Time: 22:01:56

                    Outside air temperature: 28.0 °C
                    Voltage terminal 15: 13.1 V
                    Control Module temperature: 0.0 °C

[3g_bishi]

Yuck. Them
Kind of
Codes suck. Check all the fuses. Did any water get on that area?
Might be the module. You really
Need ODIS for this as it can help with guided fualt
Finding.


Sent from my iPhone using Audizine

[GilliamOS]

The only way water might have got in there was from washing the car. I live in Utah, we don't exactly get a lot of rain lol. I don't have ODIS or any of the tools/software/etc for it. Haven't had a need to go that far (yet). I'd think if it was a fuse, it'd be completely dead. Module is most likely on its way out, though checking for water anyway is going to happen sooner than later.

Thanks.

[daytona rs7]

a quick search of the B2012 code results with module calibration being the solution.
since it doesnt sound like you've replaced the module (which would then require calibration) I would assume failing module as well.

as 3g_bishi suggested, you most likely need this resolved by a dealer or shop with better diagnostics.
If you want to just throw parts at it, you coudl try to replace the module yourself. but im fairly certain you will need calibration and possibly component protection set. At that point, you would end up at the dealer anyway.

[GilliamOS]

Uwe himself gave me some cool insight on the issue:

Agreed. The ACC is unhappy about not having video info, presumably from the 8E - Image Processing module, which has an Invalid Dataset fault, but it's quite curious that this fault is "Intermittent". That module in turn seems to be unhappy about "External Flash ROM". However, I don't see any newer software available for that module.

If it were mine and this only happened occasionally after start-up, and that was required to make the ACC work again is an ignition cycle, I wouldn't go replacing any modules just yet. Fact of life: Modules sometimes wake up on the wrong side of the bed. My guess: It's some kind of race condition in the 8E module where it's doing an integrity test on the dataset flash too quickly after power-up.

-Uwe-

I have a VAS6154 on order with ODIS in tow. I have been using VCDS for 16 years now and VW must think techs are stupid. Everything is "guided fault finding". There aren't any fault code tables, troubleshooting pathways or security codes anymore in the service manuals. VW expects you to have ODIS, so it can do all the work.

[GilliamOS]

Update: The module has gotten "worse", but an ignition cycle can reliably bring it back working, which I've tracked down to being a parameterization issue. I have ordered a VAG CAN Pro to re-parameterize the unit and hopefully address this software issue.

I think I'll even try enabling traffic sign recognition, because why not.

[Sima-Koya]

Better to use ODIS to do parametrization than VCP.VCP has generic files,while ODIS will match it 100% to your car via SVM.

To be honest,I dont think parameter loading will solve this problem.In my experience reflash + parameters + coding solves this.

[GilliamOS]

To be honest,I dont think parameter loading will solve this problem.In my experience reflash + parameters + coding solves this.

I had ODIS and a terrible VAS6154 clone that I ended up returning to the seller. It was a nightmare. Would a reflash require recalibration of the unit?

[Sima-Koya]

No,calibration is lost only when unit sees another VIN.
But it is highly recommended because your unit has corrupted the internal memory.

6154 doesnt exist,it is repackaged vxdiag passthru.
Vas5054 works,member Audisthesia got,so you if you want,contact him and make a deal if he wants to loan it.

[janhe]

Sorry for the thread hijack but since there’s quite a lot of different VAS5054A’s up for sale on Aliexpress, is there a way to tell which work as intended or are they all more or less the same and good?

[GilliamOS]

No,calibration is lost only when unit sees another VIN. But it is highly recommended because your unit has corrupted the internal memory.

6154 doesnt exist,it is repackaged vxdiag passthru. Vas5054 works,member Audisthesia got,so you if you want,contact him and make a deal if he wants to loan it.

Yeah, the 6154 whatever was hot garbage and exactly VXDIAG. Hated it. I might just bite the bullet and give specific instructions to the dealer on what I want done, especially if calibration is needed anyway. Knowing what I do now, I cancelled my VCP order if it's not going to properly fix it anyway, and save the money for the correct fix.

How likely is the dealer to succeed? The module failed for a reason and that is probably a failed NVRAM chip. I don't want to spend the money and have them fail when I could instead have them just do the work on a different module that is good instead.

Thanks for the insight.

[vimo1604]

I am currently having the same issue on my Audi A7 2013.

My image processor 8E has fault code B2021 - Data set implausible
My ACC radar unit 13 also has a fault code U111300 - Function limitation due to received malfunction value

Both are static. I'm not sure what has happened. Do we think the ACC radar unit has failed and that makes 8E to fault too? - In that case does it require a trip to the dealer to recode and calibrate after replacing?

If we think 8E has lost its parameters, is there a way to re parameterize it DIY ?

Can this be done in any way without a trip to the dealership?