A Golf 7 that cranks and refuses to fire with a black cluster has one fault and two symptoms, because the immobiliser data lives inside the instrument cluster on this platform. The reader coil for the key sits in the same housing, so a dead cluster cannot pass the key on to the engine unit. The plug is measured before the cluster is condemned.
The customer reports a car that turns over and does not start, and mentions the dark dashboard second, because the engine is what worries them. On the tester the engine unit often stores an entry about the immobiliser, and the cluster is the address that does not answer at all. That combination is the signature of a cluster that has lost its feed.
Ask whether the car was jump started and whether the dashboard dimmed before it went out. A car that cranked normally until one morning and now spins without firing points at the cluster, and the battery is the first thing you rule out. Ask about a recent windscreen replacement as well, since water that runs down behind the dash reaches the cluster connector on these cars.
Read the installation list from the gateway and look for the cluster on it. A cluster that is listed as fitted and does not answer has a feed or a data fault, and a cluster that has dropped off the list has been absent for long enough for the gateway to forget it. Both are worth writing down.
Save the fault memory from every address that answers before anything is unplugged, because the engine entry and the gateway entry together describe what the car thinks happened. Then read the cluster address once more after a full ignition cycle, since a unit that answers cold and fails hot is a different repair from one that never answers at all.
The cluster is fed by a permanent supply and by an ignition supply, and it needs both to wake. Measure them at the cluster connector with the plug fitted, using fine probes through the seal at the back of the housing. Each should read at battery level with the ignition on, and a pin that sits at zero sends you to the fuse panel.
Load the permanent feed with a bulb before you accept the reading, because a pin that holds twelve volts on an open circuit and collapses under a small load has a corroded terminal behind it. A cluster that boots for one second on a feed like that looks dead to the driver and healthy on the meter. Read the same pin again with the engine cranking and note the lowest number the meter shows.
Measure the ground pins to the battery negative post on the millivolt range with the ignition on. A drop above about fifty millivolts upsets the cluster and produces a unit that resets in the middle of a key cycle. Clean the earth stud, repeat the reading and then repeat the feed values on the same pins.
Put the scope on the data pair at the cluster plug and compare the trace with a car that lights. A flat pair with the ignition on names the wiring, and a live pair under a black screen puts the fault inside the unit. Note the state of the pair at key on, since the cluster needs a message before it will light. Compare the two wires to each other as well, because a pair that sits at the same level on both lines has lost its bias somewhere in the car.
On this platform the cluster holds the immobiliser data and the key reader sits in the same housing, so a dead cluster takes the start with it. That is why a car with a healthy engine unit will spin and not fire, and why a used cluster from another car will not start this one until the data is written.
Write the vehicle identification and the key count from the identification page of any unit that still answers, because those two items are needed when the data is transferred. A cluster that is fitted without that work leaves the car cranking, and the customer reads it as a second fault on top of the first. Ask for the second key with the car, since both keys are matched in the same session and a key left at home comes back as a complaint later.
A replacement is prepared with the immobiliser data from the car and the coding that matches the equipment level, then the keys are matched to it. The odometer and the service data are carried over in the same session. Do that work before the unit goes into the car, since a cluster fitted with the wrong data locks the start again.
Check the part number and the software level against the unit that came out, because two clusters that look identical can carry different software and the coding will not take. Photograph both labels and keep the picture with the job, since the second unit is often ordered from that photograph.
On the bench the cluster is fed at thirteen and a half volts and the current is watched at switch on. A unit that pulls a small steady current has a live board and a display fault, and one that pulls nothing has an open path on its supply side. A unit that pulls hard has a short that warms the board within a minute.
Give the unit a wake message on the bench, because a cluster with a feed and no message stays dark and looks faulty. Then flex the board gently while it is lit, since the connector joints at the pin row open with the plug being loaded every time the cluster comes out. Warm the board with a heat gun on low and watch the current, because a unit that fails when warm will pass every cold test you run.
Fit the cluster, connect the battery and cycle the ignition several times, watching the display at each key on and letting it settle before the next one. Then start the engine and confirm that it fires on the first turn, because a cluster with the wrong immobiliser data cranks and never catches.
Write the feed and ground values from the plug on the sheet along with the coding result. That record is what makes a return visit short, since these cars come back after a flat battery and the numbers from the first visit show whether the cluster or the car has moved. Note the software level of the unit that went in, because a later owner will ask for it when the car changes hands.
Before the cluster comes out, confirm that the ignition switch is really switching, because a car with a tired ignition contact gives a dead cluster and a crank at the same time. Measure the ignition feed at the plug while an assistant turns the key, and keep your eyes on the meter. A feed that appears and falls away as the starter engages explains the whole complaint and leaves the cluster untouched in the car.
| Symptom | Likely cause | What is measured |
|---|---|---|
| Cranks, will not fire, cluster dark | Feed missing at the cluster | Terminal 30 and terminal 15 at the plug |
| Cluster absent from the gateway list | Data pair open or shorted | Trace on the data pins at the plug |
| Display resets during a key cycle | Ground drop at the housing | Millivolt drop to the battery negative post |
| Cluster lights on the bench, dark in the car | Wiring in the car | Feeds and ground at the plug under load |
The immobiliser data and the key reader sit inside the cluster on this platform, so the engine unit never receives the key. The car cranks and does not fire until the cluster answers again.
Only after the immobiliser data from this car is written into it and the keys are matched. A unit fitted with the data from the car it came from leaves this car cranking.
The feeds and the ground are measured at the plug with it fitted, and then the unit is fed on the bench. A cluster that lights on the bench sends you back to the car wiring.
The coding that matches the equipment level is written, then the keys are matched and the display is cycled several times. The odometer and the service data are carried over in the same session.