SID310 and SID307 Virgin, Immo Off and Original Files: Duster, Kadjar, Qashqai, A180 CDI

A Dacia Duster 1.5 dCi comes in on a truck. The owner bought a used engine ECU online after the original flooded, the label says 237107137R, and after fitting it the car cranks with the immobiliser lamp flashing. The scan tool reads the new ECU fine, but CLIP refuses the pairing because the unit still holds the previous car’s code. This is the everyday SID310 case, and it is what a virgin file is for.

Where SID310 and SID307 are fitted

Continental SID310 runs the 1.5 dCi K9K in its Euro 6 form: Dacia Duster, Dokker and Logan, Renault Kadjar, Kangoo, Megane IV and Clio IV, Nissan Qashqai J11 and Juke, and Mercedes CLA 180 CDI W117 and A180 CDI W176 with the OM607 (the same K9K engine with a Mercedes badge). SID307 is the earlier Euro 5 unit on the Mercedes W176 A180 CDI, W246 B180 CDI and the Renault Kangoo and Megane 1.5 dCi. They look alike and both use a Tricore processor, but the files are not interchangeable.

Part numbers you’ll meet

Renault prints two or three numbers on the label: the hardware reference ending in R (237107137R is by far the most common on SID310), the software reference ending in R or S, and a Continental internal number such as 10361622AA. Mercedes uses A607 numbers. Samples from our catalogue, written exactly as the product titles:

• DACIA DUSTER SID310 237107137R 237619923R
• RENAULT KADJAR SID310 237107137R 237610681S 10361622AA
• RENAULT KANGOO SID310 237106680R 237610556S 10317242AA
• NISSAN QASHQAI SID310 237107137R 23710HX43C 23701HX63D
• MERCEDES CLA180 W117 SID310 A6079002300 6079031903 10371711AA
• MERCEDES W176 SID307 S180170003A 6079020300 6079035200
• RENAULT KANGOO SID307 4558R 4559R 8375R 10336009AA VIRGIN
• RENAULT MEGANE SID307 S180153104 A 237102426R 237101908R 3052R

The Nissan version of the same hardware carries 23710 numbers instead of Renault 2376 software codes, and the Qashqai calibration differs from the Kadjar one even where the R number matches. Send the whole label, not just the first line.

Virgin on a Renault or Dacia, step by step

1. Read the replacement ECU on the bench. SID310 and SID307 need a bench or boot connection for the full read; OBD tools get the flash on many versions but not the area that holds the immobiliser data. Flex, New Trasdata and KTAG all cover them, and KESS3 handles SID310 in bench mode.
2. Keep the full read as a backup. Check the ID in the read against the label so you know the ECU is what the seller claimed.
3. Write the virgin file for that exact hardware and software. A virgin SID310 is in the state it left the factory: no immobiliser code, no VIN, no injector codes.
4. Refit it, connect CLIP, and run the ECU replacement routine. The UCH sends the code, the ECU stores it, and the immobiliser lamp stops flashing. Enter the injector correction codes afterwards; they are not carried over.
5. On a Nissan the same job ends in Consult with the NATS registration instead of CLIP.

The logic is the same as in our SID305 virgin guide, only the hardware is newer. If the UCH itself is faulty or the car has a mixed set of used modules, the pairing can fail even with a clean virgin ECU. That is when an immo off file is the practical answer: the engine runs without the UCH handshake. It is a workshop decision, and not one a later owner will thank you for if they are not told.

Mercedes A180 and CLA 180 CDI

The Mercedes cars use the same Continental hardware, but the immobiliser is FBS3 through the EZS, not a Renault UCH. A virgin SID307 or SID310 for a W176 needs Xentry to personalise and activate it, and that step is online at dealer level on most cars. Independent shops without Xentry online access usually go the immo off route on these, or clone the original ECU if it still reads. Original files for the W176 and W117 are useful mostly for recovering a failed flash or reverting a tune, and the software number (6079031100, 6079039903 and so on) has to match.

When you just need the stock file

A SID310 that dropped into limp mode after a chip tune, or one that will not identify after an interrupted OBD write, does not need immo work. Write the original for the matching software reference and the ECU is back to standard, with the immobiliser data untouched because that lives outside the flash area. If the unit no longer answers at all, the recovery guide covers boot mode on Tricore units.

For a file, send the label photo and, if you have it, the bench read through the request page. Stock listings are on the SID310 and SID307 model pages, with the rest of the range under the Dacia brand page.