Fiat Body Computer Dump on Grande Punto, Doblo and Panda: Code Card and Proxi Alignment

Grande Punto 1.3 Multijet, 2008. Dash lights up, no crank, immobiliser light on. The engine ECU has already been swapped by a previous garage for a used one and now nothing talks to anything. On the body computer behind the glovebox the label says 00518690940, Delphi. And the Code Card? Lost years ago. This is the everyday Fiat job, and it’s mostly about getting three modules to agree with each other again.

What the Body Computer holds

Fiat calls it the Body Computer (Nodo Body). Marelli built it for the old Punto (188), Panda (169) and Doblo I; Delphi took over for the Grande Punto, Punto Evo, Doblo II, 500 and the later Panda. Either way the memory inside carries:

• The vehicle configuration (proxi data: engine, gearbox, market, options, tyre size).
• The immobiliser secret and the learned keys. On these cars the Body Computer is the immo master.
• The VIN and mileage (shared with the cluster).

The engine ECU holds a copy of the proxi and its own immobiliser link. When the two disagree you get proxi alignment warnings or no start. Multiecuscan calls the fix ‘Proxy alignment procedure’ and on most versions it copies the configuration from the Body Computer out to every other node.

Part numbers you’ll meet on the bench

• 00518690940: Delphi Body Computer, Grande Punto / Punto Evo. In our catalogue as a full dump.
• 52152607 / F083D707: Doblo II Marelli MJD 9DF-D7 engine ECU. Not a body computer, but it’s the other half of the immo pairing and the dump is listed on the 9DF-D7 page.
• Older Punto 188 and Panda 169 Marelli bodies: same idea, different memory, usually read in-circuit with UPA or Orange5.

Replacing a Body Computer, step by step

1. Read the original unit. Delphi bodies use an external EEPROM on most versions; Marelli bodies often need an in-circuit read. Save the dump twice.
2. Find a donor with the same 005 number. Fiat re-issues the part with small suffix changes, and a wrong suffix means missing functions (rear fog, one-touch windows, follow-me-home lights).
3. Write the original dump into the donor. The keys, VIN, mileage and proxi come with it and nothing needs pairing.
4. If the original is unreadable, use a matching dump from us and be ready to program keys. Multiecuscan does key learning on most Delphi bodies, but you need the electronic code that used to be on the Code Card. Zed-Full or AVDI can pull it from the dump on most versions.
5. Run the proxi alignment in Multiecuscan, clear codes in every node, cycle the ignition, test.

What went wrong on the bench

The Grande Punto from the opening had two problems, not one. The used engine ECU still carried its previous car’s immo link, so even after the Body Computer was sorted the car cranked but didn’t fire. A virgin file for the engine ECU (see the virgin category) let the Body Computer pair it at the first key-on. Lesson: when a Fiat has had a used engine ECU fitted, the ECU side needs to be virgin before you blame the body.

Another one: a Doblo II where someone had swapped the Body Computer for a used one and ‘it worked’. It did, until the customer noticed the dash showing 40,000 km more than before and a service light. A used body brings its own mileage and proxi. The customer had also lost the second key without knowing it, because the donor’s keys don’t match.

Does proxi alignment fix a wrong VIN?

No. Proxi alignment copies the configuration, not the identity. If the VIN in the Body Computer is wrong (donor unit), the only clean fix is writing the correct dump.

Can I do this with a generic OBD tool?

Key learning and proxi need Multiecuscan with the right adapter cable, or the dealer’s Examiner/WiTech. Generic scanners read the codes; they don’t fix them.

Fiat, Alfa and Lancia body and engine dumps sit on the Fiat brand page, and the Delphi bodies are grouped under Delphi. If your 005 number isn’t there, use the request form with a label photo and tell us whether you need a plain dump or one with the immo area cleared.