An E90 or E87 that loses its interior lamps straight after a battery change usually has a problem in the footwell module. The unit holds the coding for those lamps and counts short circuits until it locks an output. A short set of measurements separates a dead unit from a supply fault.
The lamps go dead and the wipers park wherever they like, while the engine still starts and the cluster behaves. That pattern tells you the supply to the rest of the car is sound and the fault sits inside one unit. Ask what else stopped working on the same day, because owners mention the lamps and forget the wipers that no longer park.
Ask when the battery was changed and whether the ignition was on during the reconnect. A spike from a jump start or from a loose terminal can leave an output locked inside the unit, and the car then behaves as though a fuse had blown. Ask also whether the wipers were left in the service position, because a motor held against its stop draws current the unit counts as a short.
Connect the tester and open the footwell module address before you touch a lamp. A unit that answers gives you a fault memory and a set of live values, while a silent unit sends you to the supply pins first. Write down whether the address opens at all, since that one result decides the rest of the job and the order of the tests that follow.
When the address opens, read the entries and note the order they appear in. An entry that repeats many times describes an output switched off after a short, and a single entry describes a momentary event during the battery work. Then read the counters for each output group in the live values, because a group at its limit stays switched off until that counter is cleared. Clear the memory and watch what returns within a minute.
Unplug the unit and measure the permanent supply pins against the battery negative post with the ignition off. Each feed should show battery voltage, and a reading well below that points at the distribution box in the engine bay. Then repeat the measurement with the plug fitted, using fine probes pushed through the seal so the reading is taken with the load connected.
Load the feed with a bulb while you read the voltage, because a supply that collapses under a small load has resistance in it that a voltmeter cannot see on its own. Measure the ground pins against the battery post on the millivolt range. A drop above about fifty millivolts means the ground stud needs cleaning before any unit is condemned, and that cleaning is often the whole repair.
A module that answers, has no counters set and still does nothing on any output may be sitting there uncoded. Read the coding status in the identification screen and compare it with the vehicle order held by the car. A unit that was never coded answers on the tester and behaves like a dead one once the lamps are switched on.
This happens after a failed write, after a unit is swapped from another car, and after a spike during programming. The coding is written from the vehicle order, then the unit is cycled off and on, then each function is tested on its own. Do not code a unit that still shows a live short, because the write will not settle while an output is in protection.
Back probe the lamp output at the module connector with a bulb fitted in place of the lamp. A pin that shows twelve volts with no load and drops to two volts with the bulb connected is a driver that has failed inside the unit. The loom plays no part in that result, so the reading is worth more than a resistance check along the wire.
Repeat the test on the pin for the other side of the same function, because the unit often drives the left and the right lamps from separate drivers. One side that holds its voltage while the other collapses narrows the fault to a single driver on the board. Write both readings down before the unit comes out, with the lamp type noted beside them.
The module sits low in the car and takes water from a blocked drain under the screen or from a leaking door seal. Open the connector and look at the pins for green deposit, then look at the board through the slot for tide marks. Water damage shows up as faults that move between outputs from one week to the next.
Clean the pins and repeat the same measurements so the change is visible in your notes. If the same outputs fail after cleaning, the damage is inside the housing and the repair is on the board. If different lamps fail, water is still arriving and the leak becomes the first job on the sheet, ahead of any work on the unit itself.
The fault is inside the module when the supplies hold under load, the ground drop is low, the counters are clear, the coding is present, and an output collapses with a bulb on it. All five results have to agree before the unit leaves the car. Each one of them rules out a cheaper repair on the way, and each one is written on the sheet.
On the bench the unit is fed at thirteen and a half volts and each output is loaded in turn while the current is watched. A driver that gives no current with a load attached confirms the internal fault. A driver that gives current and no voltage at the pin points at the solder joint behind the connector, which is repaired with the board out of the housing.
Test every function the unit controls, including the ones the owner never mentioned, with the engine off and then with it running. Cycle the wipers through their full travel and watch them park. A wiper that stops in the wrong place shows a coding value that was not taken, which a lamp test cannot see and a fault code does not report.
Write the supply values and the counter readings on the sheet so a return visit starts from your numbers. Add the output voltage you measured on the dead lamp while the bulb was connected. Tell the owner that a battery change with the ignition on is what caused the spike, and that a charger left on the terminals with the key in the lock can do exactly the same thing.
Keep the battery on a stabilised supply during any coding work on the footwell module, because a write takes long enough for a weak battery to fall away in the middle of it. Photograph the part number on the housing and note the coding index before you start. Read the counters a second time after the repair so the sheet carries a clean set of values. A lamp that works on the bench and fails in the car sends you back to the ground stud.
| Symptom | Likely cause | What is measured |
|---|---|---|
| All interior lamps dead | Output group locked after a short | Counter value for that group in live data |
| One side dead, other side works | One driver failed on the board | Output voltage with a bulb on each side |
| Unit answers but nothing works | Coding missing after a failed write | Coding status against the vehicle order |
| Faults move between lamps | Water on the connector pins | Pin condition and tide marks on the board |
The reconnect or the jump start sends a spike through the module while its outputs are live, and the unit records it as a short and locks the group. The counter then holds the lamps off long after the spike is gone.
Yes, when the counter is the only problem. Clear the counters, cycle the ignition and test the lamps at once. A counter that climbs again means a wire is still shorting, and the loom is opened before the unit.
No, because the unit carries the coding for the lamps and for the wiper park position. It answers on the tester and misbehaves in the car until it is coded to the vehicle order and each function is tested.
Yes. Cycle the wipers through their full travel after the coding is written and watch where they stop. A wiper that parks late shows a coding value that was not taken, or a park switch inside the motor.