Oil Sensor Issue - B104129/B104135 - New Instrument Cluster?

[TacticalBrick]

Jan 2018 (67 plate) - CXEB - 204 - SWB.

I had my van in for a new EGR valve, headlight levelling sensor and sporadic "oil sensor: workshop" warning, with the auto stop/start not working when this flagged up. The auto stop/start I'm assuming errors because of the oil sensor.

When it went in, I read the code with Carista and it was: B104135 error (Oil Level Thermal Sensor: Signal Too Long High).

The VAG specialist replaced the sensor (& oil) and cleaned up the contacts. They checked the wiring and said it all looks fine. They also checked by the front-left wheel which was my suggestion from this forum as apparently it can become unclipped/bent by water spraying against it. They took it for a drive and the error came back (they didn't specifically state which code), cleared it again, drove it more and it didn't come back.

However, now I've had the van back I'm still getting "Error: stop/start" on the dash intermittently, but sometimes it works as expected. I scanned the code and now it's a new one (although still oil related): B104129 error (Oil Level Thermal Sensor: Range/Performance).

There's also the code: U101900 - Instrument Cluster Control Module: Missing signal oil level/temperature, which has remained consistent with both codes.

Although, I've yet to have the "Oil sensor: workshop" yellow warning appear again, so it's like they've fixed something. They've said the next stage according to TPS is to replace the entire instrument cluster, but I'm dubious. Also, whenever I check the oil temp it's visible on the dash whereas previously it occasionally showed just "---".

Has anyone got any other suggestions (aside from fitting a digital dash, which is actually cheaper than fitting a new OE dash)?

 

[manfrotto]

It sounds like they have used this Tech tip and just coded out the fault for B104135

https://static.nhtsa.gov/odi/tsbs/2019/MC-10158527-9999.pdf

Maybe ask if that is what they have done.

 

[TacticalBrick]

They said there was a bulletin about a software fix but it was already applied. Odis wouldn't allow it to be repeated.

They're a very well regarded specialist, so I doubt they'd just code it out without telling me.. also wouldn't that then remove the oil temp from the mfd?

 

[manfrotto]

Based on error code: U101900 - Instrument Cluster Control Module: Missing signal oil level/temperature you have, you probably won't be seeing the temp in the MFD now either .

 

[TacticalBrick]

But it is there. I'm looking at it right now and I've left it on that mfd option since getting it back?

Unless that's for something other than the oil temperature?

 

[mmi]

B104129 error (Oil Level Thermal Sensor: Range/Performance).

That's implausible signal - so what are reported oil level and temperature? Any logged freeze frame data at the moment when the fault was registered? Can you make a log to see if there are any glitches in the values? Does the engine see oil level and temperature?

U101900 - Instrument Cluster Control Module: Missing signal oil level/temperature,

Is this permanent or intermittent fault?

headlight levelling sensor

sporadic "oil sensor: workshop" warning

They checked the wiring and said it all looks fine.

Exactly what wiring was checked? Oil level/temperature sensor shares the same supply among other things - with headlight levelling sensor...

I scanned the code and now it's a new one (although still oil related): B104129 error (Oil Level Thermal Sensor: Range/Performance).

There's also the code: U101900 - Instrument Cluster Control Module: Missing signal oil level/temperature, which has remained consistent with both codes.

Are these the only fault codes of the entire vehicle? Anything not working - e.g parking sensors?

Please share "Detailed ECU info"-report (under Carista Service menu)

 

[TacticalBrick]

That's implausible signal - so what are reported oil level and temperature? Any logged freeze frame data at the moment when the fault was registered? Can you make a log to see if there are any glitches in the values? Does the engine see oil level and temperature?

Sorry, new to all this, how do I make a log to find the glitches? The engine seems to be reporting the oil temp between 98 and 115 on the last few runs on the MFD.

Is this permanent or intermittent fault?

I'm not sure, how do I tell?

Exactly what wiring was checked? Oil level/temperature sensor shares the same supply among other things - with headlight levelling sensor...

Sorry, not sure! I'm assuming just the wriing near the sump and where it joins near the left wheel.

Are these the only fault codes of the entire vehicle? Anything not working - e.g parking sensors?

That an another one around the infotainment which I haven't got to yet. I found another post saying to disable the startup picture or something for that code. Although, haven't researched that fully. It used to have an Alpint unit in it, but it's been reverted to stock (MIB 2, which all works fine).

Everything else works fine, except the auto stop/start occasionally appears as "Error: Auto stop/start".

ECU Info:

ECU info obtained with Carista 9.3.1 for Android:

VIN: WV1ZZZXXXXXX94996

CAN network gateway
Part #: 7E0909901
Component: GW-K-CAN TP20
Software version: 0752
ASAM/ODX identifier: [none]
Coding: 042305 (hex)
[No fault codes]

Engine
Part #: 04L906056KN
Component: R4 2.0l BTD
Software version: 3776
ASAM/ODX identifier: EV_ECM20BTD03004L906056KN
Coding: 00254014437601080000 (hex)
[No fault codes]

High beam assist
Part #: 7E0857511F
Component: FLA
Software version: 0003
ASAM/ODX identifier: EV_HighBeamAssisAU316
Coding: 040401E200000100000000 (hex)
[No fault codes]

Transmission
Part #: 0BT300012C
Component: DSG DQ500-7A
Software version: 5302
ASAM/ODX identifier: EV_TCMDQ500021
Coding: 0014 (hex)
[No fault codes]

ABS
Part #: 7E0907379Q
Component: ESC
Software version: 0133
ASAM/ODX identifier: EV_Brake1ESCCONTIVN75XGP2
Coding: 307E8098656B84820C7E017FA688219379F700 (hex)
[No fault codes]

Steering angle
Part #: 6R0959654
Component: LENKW.SENSOR
Software version: 0070
ASAM/ODX identifier: EV_LWSKLOVW25X
Coding: 01 (hex)
[No fault codes]

Airbags
Part #: 7E0959655G
Component: VW10Airbag021
Software version: 0018
ASAM/ODX identifier: EV_AirbaVW10BPAVW12X
Coding: 000000000000000000000000000000003231 (hex)
[No fault codes]

Instrument cluster
Part #: 7E0920970S
Component: KOMBI
Software version: 1107
ASAM/ODX identifier: EV_Kombi_UDS_VDD_RM09
Coding: 740F010300 (hex)
Fault codes:
B104129 Oil Level Thermal Sensor: Range/Performance

Infotainment system
Part #: 5K7035200K
Component: MU-S-D-ER
Software version: 0468
ASAM/ODX identifier: EV_MUStd4CTSAT
Coding: 065700003C00000011111104008808001F0100960020010003 (hex)
Fault codes:
U101400 Control module coded incorrectly

Immobilizer
Part #: 5K0953234
Component: IMMO
Software version: 1107
ASAM/ODX identifier: EV_Immo_UDS_VDD_RM09
Coding: 000000 (hex)
[No fault codes]

Headlight aiming
Part #: 6R0907357C
Component: AFS-ECU
Software version: 0050
ASAM/ODX identifier: EV_HeadlRegulVWLWRCC
Coding: 0FCE020001000000 (hex)
[No fault codes]

Heater & air conditioning
Part #: 7E0907047AC
Component: Climatic-T5
Software version: 0708
ASAM/ODX identifier: EV_ClimaticT5
Coding: 0000000003 (hex)
[No fault codes]

Parking/steering assist
Part #: 7E0919475AA
Component: PARKHILFE 8K
Software version: 0212
ASAM/ODX identifier: EV_VW75XParkAssis8K
Coding: 31890C (hex)
[No fault codes]

All-wheel-drive system
Part #: 0AY907554L
Component: Haldex4Motion
Software version: 7620
ASAM/ODX identifier: EV_AllWheelContrHA1VW37X
Coding: 0501 (hex)
[No fault codes]

Central electronics
Part #: 7E0937090C
Component: BCM PQ25 Max4
Software version: 0752
ASAM/ODX identifier: [none]
Coding: 66DCFB3A0E63340393284F606CEB8EF4C084738960ED79603304003F0860 (hex)
[No fault codes]

Trunk
Part #: 7E0959107A
Component: HDSG-Modul
Software version: 0653
ASAM/ODX identifier: EV_HDSGVN46T
Coding: 19730D4003 (hex)
[No fault codes]

Battery regulator
Part #: 7E0907534
Component: Batt.regelung
Software version: 0752
ASAM/ODX identifier: [none]
Coding: 330B1A73 (hex)
[No fault codes]

Trailer
Part #: 1K0907383H
Component: Anhaenger
Software version: 0130
ASAM/ODX identifier: [none]
Coding: 410D000103000000 (hex)
[No fault codes]

Adaptive cruise control
Part #: 7N0907572C
Component: ACC Bosch PQx
Software version: 0211
ASAM/ODX identifier: EV_ACCBEGVW361
Coding: 00005800FE0779 (hex)
[No fault codes]

 

[TacticalBrick]

Freeze frames as requested, although this morning there's nothing on Carista showing "U101900" and I haven't cleared any faults.

(I did click the download button and the data is identical to the screenshots.)



Edit: Here's the screenshot I took the other day when U101900 was showing, but could be missing some values as I didn't realise there was a download button until about 5 minutes ago:

 

[mmi]

They said there was a bulletin about a software fix but it was already applied. Odis wouldn't allow it to be repeated.

Strange as the software identifiers have not been changed since factory - neither Engine nor Instruments

Engine
Part #: 04L906056KN
Component: R4 2.0l BTD
Software version: 3776

Instrument cluster
Part #: 7E0920970S
Component: KOMBI
Software version: 1107

Sorry, new to all this, how do I make a log to find the glitches? The engine seems to be reporting the oil temp between 98 and 115 on the last few runs on the MFD.

Not sure if Carista has such an essential feature. Would definitely be helpful to have a log to see any discrepancies - e.g. because of intermittent data dropouts. Does Carista show actual oil level?

I'm not sure, how do I tell?

Does the fault counter step up with every ignition/driving cycle?

ECU Info:

There's also the code: U101900 - Instrument Cluster Control Module: Missing signal oil level/temperature, which has remained consistent with both codes.

But currently there is no such a fault in the ECU info listing??

 

[TacticalBrick]

Strange as the software identifiers have not been changed since factory - neither Engine nor Instruments

That is concerning and would be an easy win if that's all it is. What versions should they be on? Do you know what version the TPS bulletin they referred to with the engine oil sensor was fixed on? This was their report:

Replaced Oil level Sensor & Carried out Oil change. Road tested and
Fault for instrument cluster control module, missing signal oil
level/temperature passive sporadic. Fault on dash (NOT engine light) will
require more diag. Checked TPIs and found relevant TPI for fault. TPI states
to carry out software update.
Software already up to date according to Odis. Tried to update via activation
code said it was already up to date. Tried to update 01 (ECM) already up to
date and tried to update 17 (instrument cluster) already up to date.
Fault is intermittent unsure of where to go with this because we have done
everything the Tpi says and replaced the oil level sensor.
Road tested again and no light on

The follow-up recommendation was a new instrument cluster at £800-900.

Not sure if Carista has such an essential feature. Would definitely be helpful to have a log to see any discrepancies - e.g. because of intermittent data dropouts. Does Carista show actual oil level?

I can't see the option in there if it does. I don't have VCDS. Does the T6 have an oil level on the MFD or just temperature? Because I only see an option for temperature.

Does the fault counter step up with every ignition/driving cycle?

I will drive to tonight and check. Got a long run from Nottingham way up to North Yorkshire next week, so will be able to give it a good test then too.

But currently there is no such a fault in the listing??

Correct, it was there when I last drove it Tuesday evening, but appears to have disappeared now.

 

[mmi]

That is concerning. What versions should they be on? Do you know what version the TPS bulletin they referred to with the engine oil sensor was fixed on? This was their report:

The way I understand the report - there was no update re the sensor for this engine (or instrument cluster).
The TPI unfortunately does not identify the versions. I would take the the software(s) are up-to-date.

Post in thread 'Mfd Oil Temp'

8 May 2023

I followed your advice, dear friends ... I bought Carista and I was inserted tester beams of the Beta version, now 5.5, magically the engine oil temperature (which had disappeared)

Well, it seems that also VW has a solution for missing oil temperature in T6 dash.
Can be found as TPI 2047638/3 (released 21-Dec-2022).
Basically the TPI tells that ECU software update resolves also this issue (the update which has been available since October-2019)

*) TPI=Technical Product Information

Spoiler: Fault code

• mmi

• 

Also according to my own bookkeeping the software is up-to-date.
Well, however, this exact engine can be updated to a newer version. See details in below

T6s used in the evaluation - MY18 DSG 4Motion​

Engine from factory: CXEB 04L 906 056 KN version 3776 - EU6 150kW/204PS

Thread '[T6_measured] NOx emissions, AdBlue consumption, DPF regeneration - Before and after ECU update'

6 Jul 2022

Introduction​

An update campaign for T6 EU6 diesel engines took place in 2019-20. Affected engines were on van of model years MY16-MY18, including some of MY19.

For M1 class (passenger carriers, VIN WV2...) the update was an official recall.
For N1 class (VIN WV1....) the update was not classified as mandatory but was/will be done if faults (especially P204F, P20EE) show up. So basically the decision is left to service center.

In the paperwork it was mentioned that the update might increase AdBlue consumption slightly - as a compensation free AdBlue fill-ups were offered.

T6s...​

• mmi
• adblue ecu update nox t6_measured
• Replies: 15
• Forum: Engine, Gearbox, Exhaust, Drivetrain

• 
• 

Correct, it was there when I last drove it Tuesday evening, but appears to have disappeared now.

That might be just a Carista feature - a cleanup of ancient codes.

previously it occasionally showed just "---".

Oil temperature is shown only from 50 °C upwards.

I don't have VCDS.

Perhaps you should - especially if desiring to keep the van in future...

 

[TacticalBrick]

Oil temperature is shown only from 50 °C upwards.

Yep - it showed as "---" occasionally on a drive when already up to temp, but it's not done that since the new sensor went on. Not that I've noticed anyway.

Well, however, this exact engine can be updated to a newer version. See details in below

Is there any way to tell if I've had this update? I did actually get the advanced info off VCDS from a friend when I was trying to work out if it'd had a remap. I don't think it does as it doesn't feel as fast as another I test drove that definitely had a Stage 1 map. There's nothing in the vehicle's provided history (and it's extensive) to say it has. The only suspicious thing was "Programming Attempts(application): 0/2/2" but I can't see what actually means anywhere.

I was assuming these would just be VW updates for this issue, because as you say there was an engine update and an instrument cluster update. Would it be worth calling VW Commercial to see if they have a record of this van having any updates? It's classed as N1 on the V5C, so wouldn't have been mandatory according to the info on your post.

Wednesday,09,July,2025,21:54:13:15881
VCDS Version: Beta 25.6.0 (x64)
Address 01: Engine
Control Module Part Number: 04L 906 056 KN
Component and/or Version: R4 2.0l BTD H03 3776
Software Coding: 00254014437601080000
Work Shop Code: WSC 02739
VCID: 035456022B96F882861-8056

Advanced Identification/FAZIT
Identification: DH1-00S
Revision: 23101001
Date: 18.11.17
Manufacturer number: UPS6
Test stand number: 1972
Flash Status
Programming Attempts(application): 0/2/2
Flash Date-Workshop ID-Status:
--.--.-- 2097151 1023 131071 (OK) | 00.00.00 50316 790 02739 (OK) | 00.00.00 50316 790 02739 (OK)
Misc.
Hardware number: 04L 907 445 A
Workshop System Name: 2D2D2
Workshop ID (Adaptation): 50316 790 02759
Workshop ID (Coding): 50316 790 02739
ASAM Dataset: EV_ECM20BTD03004L906056KN
ASAM Dataset Revision: 004004
Car Info
Chassis Number: WV1ZZZXXXXXXX4996
Engine code: CXEB
Immobilizer
General immobilizer info :
Life status: 2
Identity counter: 1
Brand identification: 3
Power class: 0
Power class 2: 80
Power class supported: 80 00 00 00 00 07 04 01 00 00
Count of adapted keys: 0
Count of keys to be adapted by download: 0
Count of keys to be adapted by adaptation: 0
Minutes remaining for Terminal 15 ON: 0
Configuration status: 0
Reserved: 0
Lock times in minutes :
Lock time download: 0
Lock time password reset: 0
Lock time login/Terminal 15 ON: 0
Lock time key adaptation: 0
Lock time leaving key adaptation: 0
Lock time login special function: 0
Immo Challenge: X
VCDS Info:
VCID: 035456022B96F882861-8056
Labels: 04L-907-309-V2.clb
Readiness: No script available
ROD: EV_ECM20BTD03004L906056KN_004.rod

 

[mmi]

but it's not done that since the new sensor went on. Not that I've noticed anyway.

That's good news.

Is there any way to tell if I've had this update?

Control Module Part Number: 04L 906 056 KN
Component and/or Version: R4 2.0l BTD   H03 3776

Yes. Definitely has not got that factory update - still has factory software version identifier 3776

The only suspicious thing was "Programming Attempts(application): 0/2/2" but I can't see what actually means anywhere.

Indeed - from factory it's normally 0/1/1.

VCDS from a friend

Any chance to take advantage of your friend and provide engine's blockmap data etc. for a comparison

Ignition ON - engine OFF
VCDS > Applications > Controller Channel Map >


Tick/fill boxes as above and click Go
The result files blockmap-01-... etc. will be in folder C:\Ross-Tech\VCDS\Logs\.... (or C:\Ross-Tech\VCDS-Beta\Logs\....)

 

[TacticalBrick]

I've been unable to collar my friend with VCDS as of yet, hopefully I'll be able to get to him one night this week.

After a long trip to N Yorkshire I've noticed that the temperature sensor seems to work for a while, but then shows "---", then it either starts showing the temperature again or it just disappears from the MFD entirely until the ignition is turned off and on again.

I have both fault codes back again (B104129 & B104135).

 

[TacticalBrick]

@mmi as if by magic! Hope this is what you were after.

 

[mmi]

@mmi as if by magic! Hope this is what you were after.

Thank you very much. Exactly the package.

I was trying to work out if it'd had a remap.

The only suspicious thing was "Programming Attempts(application): 0/2/2" but I can't see what actually means anywhere.

The ECU has been reprogrammed once since it left the factory.

Interestigly the calibration identification (software ID) is still as from factory.
However, the calibration verification and checksums don't match factory setup.
Thus I would say the ECU definitely has been remapped.

 

[TacticalBrick]

I found this post with someone else with the same checksum:

Post in thread 'EML Light on, VCDS scan implies an SCR fault?'

30 May 2024

Calibration identification and verification are not listed.

Code checksum is 02 49 F6 F0
Data checksum is F2 8E 79 AD

• RobJH

• 

I've reached out in a PM in case he has any idea what the change was.

I guess going forward I'll get a 2nd opinion on whether it's a new instrument cluster vs a break in the wire and take it from there.

Or I need to get to a dealer and get the latest ECU update on it and start burning more AdBlue. Ideally I'd like to not have a performance remap on a van that is already 204bhp, but it could also be driveability remap for the DSG that I wouldn't want to lose.

 

[TacticalBrick]

Unfortunately he never found out and just got the latest software put on. I guess I'll do the same for some peace of mind.

 

[mmi]

get the latest ECU update on it and start burning more AdBlue

Well, on the positive side would be burning less diesel thanks to less frequent DPF regens.

 

[TacticalBrick]

@mmi is there anything I can do in VCDS to get live reading from the oil level/temperature sensor to work out if it's working OK and it is the instrument cluster?

I've been looking through the blockmap data and it seems there's a lot of information available, I'm just not sure what I should be looking at.

IDE00151 Oil fill level 90 mm
IDE00152 Oil warning threshold 60 mm
IDE00196 Engine oil temperature 64.9 °C
IDE00495 Calculated oil temperature 70 °C
IDE00497-MAS00627 Status of oil pressure switches-Oil pressure switch for high pressure Open
IDE00497-MAS00628 Status of oil pressure switches-Oil pressure switch for low pressure Open
IDE00699 ESI: minimum oil level in service interval 0 mm
IDE00700 ESI: maximum oil level in service interval 0 mm
IDE06386 Oil level: static measurement -32767 mm
IDE06387 Oil level: last valid dynamic value -32767 mm
IDE06388 Oil level: condition for static measurement fulfilled Condition not met
IDE06389 Oil level: maximum value -32767 mm
IDE06390 Oil level: minimum value -32767 mm
IDE11574 Status max. oil level dynamically exceeded No
IDE11575 Status max. oil level permanently exceeded No
IDE07233-MAS07412 Bit string for status of oil level-Oil level OK not active
IDE07233-MAS07413 Bit string for status of oil level-Checking oil level not active
IDE07233-MAS07414 Bit string for status of oil level-Oil level monitoring not active
IDE07233-MAS07415 Bit string for status of oil level-Top up oil not active
IDE07233-MAS07416 Bit string for status of oil level-Top up oil immediately not active
IDE07233-MAS07417 Bit string for status of oil level-Reduce oil level not active
IDE07233-MAS07418 Bit string for status of oil level-Oil level not available not active
IDE07233-MAS07419 Bit string for status of oil level-Measmnt. not possible while engine running not active
IDE07233-MAS07420 Bit string for status of oil level-Engine not at oper. temp. not active
IDE07233-MAS07421 Bit string for status of oil level-Vehicle not in level position not active
IDE07233-MAS07422 Bit string for status of oil level-Oil level display not active
IDE07233-MAS07423 Bit string for status of oil level-Sensor faulty not active
IDE07234 Status bid for valid static oil level Condition not met
IDE07235 Status bid for dynamic oil level Condition not met

90mm oil fill level looks like maximum from reading on the forums, but it's not showing max on the dipstick (just below half) and I was going to add some more in.

I'm assuming IDE00699 & IDE00700 are 0 because it's not in extended service mode?

IDE06386 - IDE06390 are all showing -32767 mm, is that normal? This was taking with the ignition on, engine off, after a 10 minute drive.