BMW E90 Cluster Lighting Always On: M_TAG_SKALENBELEUCHTUNG Coding

On the E90, keeping the instrument dials lit even with the headlights off is done by setting M_TAG_SKALENBELEUCHTUNG in the KOMBI module to aktiv. From the factory this illumination comes on only with the headlights; after coding it stays on whenever the ignition is on. Why was the factory behaviour designed this way? Tying dial illumination to the headlights is a deliberate design choice that hands the driver a visual cue. Dim dials mean the headlights are off, and at dusk that difference works as a silent reminder to switch them on. Setting the parameter to aktiv removes the cue, and the cluster then looks the same in every condition. Module: KOMBI Parameter: M_TAG_SKALENBELEUCHTUNG Value: aktiv Function: dial illumination stays on independently of the headlights Factory behaviour: illumination only with headlights on Safety effect: the visual cue that the headlights are off disappears Risk: low as a coding change, but it asks more of the driver Which E90 model years does it cover? The source list carries no model-year marks for this parameter. In other words there is no record of which years it was verified on; the line itself is documented but its applicability is not stated. The only reliable answer is to read your own KOMBI data and see whether the line is present. • The source list gives no model-year marks, so coverage is unverified. • If the line does not appear in your KOMBI coding data, your car does not support it. • Do not confuse this with daytime running light coding; this parameter affects cluster lighting only. • Model-year coverage comes from community-compiled E90 coding lists; the binding source is your own car's FSW/PSW data. How do you code it? The change is a single line in the KOMBI module. OBDThink is an independent BMW coding and diagnostics app and is not affiliated with BMW AG. Note your service information and trip computer records before writing; per the source list, cluster coding can reset these values on some cars. • Note the current service display and the clock setting before you code. • Set the instrument brightness wheel to mid position, then switch the ignition on without starting the engine. • Connect with OBDThink and bring the KOMBI coding data up on screen. • Save a backup, find the M_TAG_SKALENBELEUCHTUNG line and set it to aktiv. • Write the change; do not lock the car or turn the ignition until the write finishes. • With the headlights off, switch the ignition on and confirm the dials are lit. Reading headlight status live in OBDThink tells you whether the dials are lit because of the coding or simply because the headlights are actually on. How do you revert it? Reverting means returning the same line to nicht_aktiv. Dial illumination is tied back to the headlights and the factory behaviour returns. Restoring a pre-coding backup gives the same result. Module: KOMBI Parameter: M_TAG_SKALENBELEUCHTUNG Revert value: nicht_aktiv Option 1: set the value to nicht_aktiv and write Option 2: restore the pre-coding backup Check: with the headlights off, the dials should be dark What does this coding really cost you? What you lose is not a comfort setting but a reminder. On lit roads and in town it becomes harder to notice that the headlights are off, and a car that looks fine from the front stays invisible from behind. That is a concrete risk at dusk and at the exit of a tunnel. After coding, leave the light switch in the automatic position or make a habit of switching the headlights on by hand. Driving at night without headlights is a traffic offence in many countries and directly affects how fault is assessed after a collision. What if the dials are still dark? First read the KOMBI data back and confirm the value really was written as aktiv. Second, check the instrument brightness setting; with the wheel beside the steering column at its lowest position the illumination is on but too dim to see. Third, if the line is absent from your car's KOMBI data, the function is not supported at that software level.