The Simos PCR 2.1 ECU is widely used in Volkswagen Group’s 1.6 TDI engines, and its built‑in immobiliser (often called “IMMO”) can sometimes cause headaches during ECU swaps or repairs. This guide is written for car professionals and hobbyists, explaining SIMOC VAG PCR 2.1 ECU IMMO OFF in depth. We’ll cover what the SIMOS PCR 2.1 ECU is, how the VAG immobiliser system works, and why and how you might need to disaBle (IMMO OFF) the imobiliser. You’ll learn about the required tools (hardware and software), step‑by‑step procedures, troubleshooting tips, and even unique insights from experts. By the end, you’ll understand how to confidently disable the immobiliser on a Simos PCR 2.1 ECU for legal and practical purposes,using techniques like bench‑mode reading and specialized software patches. Let’s dive in into this critical process for VW/Audi/Seat/Skoda technicians and enthusiasts.

Understanding the Simos PCR 2.1 ECU
The Simos PCR 2.1 (often just called SIMOS 2.1) is an engine control unit (ECU) developed by Siemens/Continental for Volkswagen Group vehicles. It’s found in many VW, Audi, Seat and Skoda models equipped with 1.6 TDI engines. In fact, Simos PCR 2.1 belongs to the fourth-generation immobiliser family (WFS4/IMMO4) used by VAG. The ECU uses a TriCore TC1796 microcontroller and includes both flash memory (for the engine software) and an EEPROM (for data like key codes). Because SIMOS is a Continental (Siemens) OEM unit, it replaced older Siemens Med17 or VDO ECUs in many diesel cars around 2009–2014. For example, cars like the VW Golf VI, Passat B7, Polo 6R, Audi A1/A3 8P (1.6 TDI) and Skoda Octavia II commonly use SIMOS PCR2.1.
Simos PCR 2.1 handles engine management functions (fueling, boost, etc.) but also tightly integrates VAG’s immobiliser (“Wegfahrsperre”) system. The immobiliser data – including the vehicle identification number (VIN), PIN code and security bytes (Component Security, or CS) – are stored on the ECU (typically in the EEPROM). When the car starts, the system checks that the key’s transponder code matches the ECU’s stored PIN and CS. If they don’t match, the ECU locks the engine (no start) as a security measure.
Key Point: The SIMOS PCR 2.1 ECU is a WFS4/IMMO4 unit used in VW 1.6 TDI cars. It contains both the engine map and the immobiliser data (VIN, PIN, CS) on-board.
Understanding the hardware is helpful. A typical PCR 2.1 unit has a green circuit board inside a metal housing, with connectors to the car’s wiring harness. The heart of the board is the Infineon TriCore TC1796 microcontroller (the brain). For many operations, technicians connect to it via the round 176-pin connector (often labeled C167) or via solder points if opened. This microcontroller contains the bootloader, which is used for reading/writing the ECU’s full data. To modify the immobiliser, we ultimately unlock and access this TC1796 controller.
Simos PCR 2.1 is different from some earlier PCR series like PCR 2.0 or 2.5, and from older Siemens VDO/Med17 units. Its locking mechanism (IMMO4) is more secure: you cannot simply “clone” the data from one PCR2.1 ECU to another without addressing the immobiliser. Simply transferring the EEPROM isn’t enough, because the TC1796 keeps a security lock. In practice, even if two PCR2.1 ECUs have the same part number (e.g. 03L 906 023), you usually need to disable (turn off) the immobiliser function if you swap ECUs between cars or use a donor ECU.
Image of a simos ECU (Figure above). The PCR 2.1 ECU uses a TriCore TC1796 CPU and contains both engine software and immobiliser data. Disabling the immobiliser requires special boot‑mode access to this unit.
How the VAG Immobiliser (IMMO) System Works
Before performing IMMO OFF, it helps to understand how VAG’s immobiliser system operates on PCR 2.1. Volkswagen/Audi immobilisers (called Wegfahrsperre or WFS) tie the car’s ignition system to the transponder-equipped keys. With a SIMOS PCR 2.1 (WFS4) system, key data is stored on the ECU and the dashboard (cluster), and proper matching is required for engine start. Key information includes the 4-digit PIN and a 4-byte component security (CS) value. These values are programmed into the ECU’s EEPROM when the car is first coded. Every time the ignition is turned on, the ECU checks that the coded PIN/CS match what’s in the cluster (and the transponder key). If the data does not match (for example, if the ECU has been replaced without reprogramming), the engine is disabled.
Technically, the PCR2.1 ECU’s firmware contains an IMMO routine that will prevent injection or starter engagement if the immobiliser is active. The ECU’s flash typically includes an immo disable block or flag. Disabling IMMO (IMMO OFF) involves either erasing or patching this block so the ECU no longer checks for the matching key code. In other words, an IMMO OFF patch effectively removes the security check code from the software.
An important point: PCR 2.1 uses CAN bus for communication (to verify keys and PIN). It has separate memory areas for the engine tune (flash) and for coding information (EEPROM). Key details are normally stored in the EEPROM at specific addresses. Many tools (like the WebOctopus IMMO Editor) allow reading the VIN/PIN/CS/Powerclass from these files and editing them. However, simply editing these values won’t allow engine start unless the ECU itself is unlocked for writing and the immobiliser check is bypassed.
Did you know? The term “Power Class” on VAG ECUs is the numeric identifier of the car model/engine the ECU is coded to. PCR2.1 units include the Power Class in their coding data. IMMO OFF tools often let you transfer the power class along with VIN/PIN data when cloning an ECU.
In summary, performing IMMO OFF means we either remove the requirement for the original PIN/CS or override that logic entirely. This is usually done by: (a) reading out the ECU’s binary data (flash and/or EEPROM) via boot mode, (b) running a special software patch that clears or neutralizes the immobiliser section, and (c) writing the modified data back. After doing so, the ECU will accept any key (or effectively have no key lock), and the engine can start without immobiliser matching.
Why Perform an IMMO OFF on PCR 2.1?
Disabling the immobiliser on a PCR2.1 ECU is rarely for convenience alone – it’s typically done for practical reasons. Here are common scenarios where a PCR 2.1 IMMO OFF is needed:
- ECU Replacement or Swapping: If a PCR2.1 ECU has failed (water damage, chip error, etc.), replacing it with a used or new unit will trigger an immobiliser mismatch unless IMMO OFF is done. For example, swapping in a donor ECU from a similar car (e.g. a 2012 VW Golf 1.6 TDI) will fail to start unless the immobiliser lock is disabled.
- Data Corruption or Cloning: In some cases, an ECU might lose its coding (VIN/PIN) due to a write error or corruption. If a tech tries to “clone” the EEPROM from a damaged ECU into a fresh unit, the SIMOS PCR2.1 often still detects a mismatch because it ties the pin to the ECU’s unique identifiers. Performing IMMO OFF allows cloning the ECU without worrying about the VIN/PIN mismatch.
- Engine Swaps and Tuning: Enthusiasts sometimes swap a 1.6 TDI engine (with PCR2.1) into a different VW body or do heavy tuning. Disabling the immobiliser ensures that an ECU from any donor car will run the engine without immobiliser intervention. This can simplify engine swaps where key adaptation might be tricky.
- Service Failures: Occasionally, cars come with immobiliser faults (blown transponder, etc.). A quick diagnostic might be an IMMO OFF to rule out ECU/key mismatches. Professional services may offer a temporary or permanent IMMO OFF as a quick fix for no-start issues.
It’s worth noting that performing IMMO OFF is generally intended for legitimate repairs – such as fixing a dead ECU – rather than for illegal use. Dealers or trusted workshops will often charge for this procedure. For example, IAS Automotive offers a PCR2.1 IMMO OFF service, requiring the ECU’s boot-mode dump (TC1796 file) and then applying a custom patch. They highlight that they do not use generic, mismatched files; each ECU is handled individually so other vehicle configurations remain untouched. This ensures the ECU still behaves correctly except for the removed immo lock.
Expert Tip: If you try to simply clone a PCR2.1 ECU (e.g. copy eeprom from car A to car B) without disabling immo, you will often encounter “locked” status or start-up failure. A successful IMMO OFF effectively makes the ECU accept any key data, avoiding this issue.
By disabling the immobiliser, you regain full control: the car will start normally even if the ECU’s VIN/PIN don’t match the keys. After IMMO OFF, technically the ECU is “immobiliser‑free,” meaning it won’t check keys at all. Keep in mind that after this operation, if the car is ever sold or re-serviced, it’s good practice to document that the ECU no longer has an active immobiliser.
Essential Tools & Software
Disabling a SIMOS PCR 2.1 immobiliser requires specialized equipment. Below is an overview of the hardware and software tools commonly used:
- Hardware Programmers: You’ll need a flash tool capable of working with PCR2.1’s TriCore TC1796 microcontroller. Common choices include KESS V2 (Alientech Ksuite), K-TAG (Alientech), MPPS, Autotuner, FGTech Galletto (V54), Magic X-17, OBDSTAR DC706, XDJs, etc. All of these can read/write PCR2.1 data, but note that most require bench mode to unlock the ECU for reading or writing. The Magic X-17 is notable because it reportedly supports direct OBD (no bench) communication with PCR2.1 (as of recent versions).
- Boot/SSM Cables: Because PCR2.1 ECUs often need a boot mode connection, you will require a TriCore boot cable. The Infineon cable model SSM 144300T111 is standard for PCR2.1 bench mode. This 12‑pin cable (also called TriCore cable) connects between the ECU and the programmer, providing power, ground, CAN lines, and debug (SSM) signals. Without this cable (and sometimes an external 12 V supply), you cannot communicate with the locked microcontroller.
Figure: An Infineon SSM cable (144300T111) used for PCR2.1 ECU bench-mode connection. This specialized cable interfaces the ECU’s TC1796 controller to the programmer for reading/writing. - Immo-OFF Software/Services: There are sofware tools specificaly designed to disable the immobiliser in a PCR2.1 ECU. For example, CK Decode is an online service where you upload the full ECU dump and it patches the immobiliser section. Robaizkine sells a “PCR 2.1 Immo Remover 2.4” tool (software) that automatically edits the flash/dump file for IMMO OFF. Other aftermarket solutions include NeuroSuite (DTC Disabler) or AutoDelphi, as well as hardware emulators (below).
- ECU Emulators (ECU Cloning Tools): Devices like the Julie Universal Emulator . For example, the Julie Emulator can disable the immo by emulating a correct transponder code inside the ECU. These emulators often require the ECU to be connected in the car with ignition on. CarLabImmo’s technical channel shows a Julie emulator performing IMMO OFF on a Simos PCR2.1 via OBD – a convenient alternative to bench flashing.
- Backup & Editing Tools: Always have a reliable EEPROM/flash file editor. Programs like WinOLS, ECUtool, or Cartool can open PCR2.1 dumps for manual inspection. Additionally, WebOctopus provides an online editor/cloning tool specifically for PCR2.1 immo data. These allow reading VIN, PIN, power class, etc., and even editing them if needed. The WebOctopus IMMO Editor lets you extract or change the VIN/PIN/CS values and clone them to a donor ECU. It also warns that file compatibility is critical (mixing mismatched files can fail).
To summarize, you typically need: a bench-mode flasher (KESS/Ktag etc., the SSM boot cable (144300T111) with stable 12 V supply,and IMMO OFF software. Optionally, an emulator like Julie can do it without bench mode. When gathering tools, ensure your software versions support PCR2.1 and the TC1796 chip.
Preparing the ECU for IMMO Removal
Proper preparation is key before disabling the immobiliser. This involves physically accessing and reading the ECU, then safely making a backup.
First, locate the PCR2.1 ECU in the vehicle. In many VWs/Skodas with a 1.6 TDI, the ECU is under the dashboard or behind a kick panel. Carefully remove any panels to reach the ECU casing. Unbolt and extract the ECU.
Next, open the ECU case if bench mode is needed. (Some vendors offer to disable immo via OBD without opening; but often a full read requires bench mode access to the TriCore chip.) Release the metal clips or screws to open the housing. The green PCB of the PCR2.1 will be visible, with a large round connector and possibly an SMD section for the microcontroller.
Figure: A Siemens/Continental Simos PCR2.1 ECU opened on the bench. The green circuit board (with the microcontroller under metal shields) is exposed. For IMMO OFF, a boot cable is connected to specific pins on this board.
With the ECU open, prepare to connect the TriCore cable. The SSM cable (Pin-header cable) must mate with the ECU’s JTAG/DBG connector. According to Alientech’s KESS instructions, the cable pinouts are: +12 V to ECU pins 5, 87, 92 (red/orange wires), ground to pin 1 (black wire), CAN High to pin 68 (yellow), CAN Low to pin 67 (green). The KESS cable (part #14P600KT02) plugs into the 176-pin ECU connector, while the TriCore cable (144300T111) plugs into the KESS OBD port and provides the I/O to the ECU. A schematic from KESS is shown:


Figure: KESS boot-mode pinout for SIMOS PCR2.1. Red/orange wires supply +12 V to pins 5, 87, 92; black is ground (pin 1); yellow is CAN-H (pin 68); green is CAN-L (pin 67). This wiring is needed to unlock the ECU (TriCore TC1796) for reading.
Ensure a stable power supply before proceeding. Many technicians use a bench power unit set to 13.5 V to avoid dips during communication. Connect the SSM cable and cables to the ECU as shown. Double-check ground and voltage connections (wrong polarity can brick the ECU).
Now, backup the ECU data. Using your flasher tool (e.g. KESS or KTAG) in boot mode, perform a full read of the ECU’s memory. This typically means reading both the ECU’s flash (the engine map/code) and its EEPROM (where VIN/PIN data reside). For example, in KESS you’d select “PCR2.1” under VAG and perform a “Read ECU”. The TriCore should unlock and dump the data. Save this dump file carefully – this is your stock backup. If anything goes wrong, you will need this file to restore the ECU.
Pro Tip: Label the backup file clearly and verify its integrity (check file size typically ~2–3 MB for PCR2.1). Some tools let you immediately save separate ECU.bin (flash) and eeprom.bin (coding data) files. Keep the backup on a safe computer
With a successful full read in hnd, you’re ready to apply the IMMO OFF patch. As a final check, ensure the ECU was fully unlocked. Some software will indicate if the TC1796 was still locked (read errors). If so, you may need to unlock it (e.g. “Unlock” option in Ktag) before retrying the read. The goal is to have an uncompromised dump to working on.
Step-by-Step IMMO OFF Procedure
With the ECU data backed up, the immobiliser-off process typically involves modifying this data and writing it back. The exact steps vary depending on the software, but a general workflow is:
- Upload or Load the ECU Dump: Open your IMMO OFF software (online service or local program) and load the full dump (flash + EEPROM) you read from the ECU.
- Select IMMO OFF Option: Choose the Simos PCR2.1 ECU in the software. For CK Decode, this means going to VAG → Siemens → SIMOS PCR2.1 → Immo Off. For GTAAuto’s tool, it means selecting “Immo Off” from the menu.
- Process/Patch the File: Click the process or start button. The software will automatically remove or blank the immobiliser data. For example, CK Decode will adjust the security bytes and code so the ECU no longer checks the PIN. GTAAuto’s Immo Remover will produce new files with IMMO disabled, correcting checksums in the process.
- Save the Modified File: Once processing completes, save the new (patched) dump to your computer. Double-check the file name to distinguish it from the backup. These tools often produce separate files (flash.bin and eeprom.bin) or a combined file – follow the tool’s instructions.
- Write the Modified Data Back to the ECU: Using the same hardware tool (KESS/Ktag/etc.), write the patched file back into the ECU. Usually this is done in the same mode you read it: boot mode for KTAG or appropriate mode for KESS. Begin by writing the new flash (if changed) and then the EEPROM. The software should automatically handle checksum correction.
- Verify the Write: After writing, some programmers will verify the written data. If not automatic, do a readback compare against the patched file to ensure it was written correctly. This step catches any communication issues.
- Power Cycle and Test: Disconnect the ECU from the bench, reassemble, and reinstall it in the car (or keep it bench-mounted if using a test bench). Reconnect all wires, then turn the ignition on. The car should start with any original key now. If the engine cranks and fires, the IMMO OFF was successful.
Figure: Example IMMO OFF software steps. (Left) CK Decode Online – select “Simos PCR2.1 – Immo off”, read ID, upload dump, click Process, then write the output file. (Right) GTAAuto PCR2.1 Immo Remover – load the dump, select “Immo Off”, and save the patched file.
Throughout this process, backup and caution are essential. Always have the original dump saved before any editing. The GTAAuto tool specifically warns:
❗ Backup the Original File – Always make a full backup before making modifications.
After writing, be aware of error or warning messages. If the ECU reports “Locked” or an error after flashing, it likely means the unlock or patching step failed. In that case, restore your original backup and try again, ensuring proper cable connections and tool settings. If writing was interrupted (power glitch, cable slip), do not attempt a second write before restoring the original state – that could brick the ECU.
Once successfully written and tested on the bench, you can reinstall the ECU in the vehicle. Turn on the ignition – the immobiliser light on the dash should go out immediately and the engine should start normally (without requiring the key to be reprogrammed).
Important: If you are using a diagnostic scanner after IMMO OFF, clear any fault codes. Initially the ECU might have thrown a Immobiliser/DTC error, which should be erased once the immo check is removed.
Aftercare: Testing and ECU Reinstallation
After the IMMO OFF process, follow these steps to finish up:
- Reinstall the ECU: Place the PCR2.1 unit back into its car bracket or housing and reconnect all wiring harnesses securely. Ensure grounds are tight and connectors click fully.
- Key Test: Insert a valid key (or an ignition simulator) and attempt to start the car. A properly IMMO-disabled ECU will crank and start regardless of VIN/PIN mismatch. The immobiliser warning light (WFS lamp) should turn off as soon as ignition is on.
- Clear DTCs: Use an OBD2 scanner (like VCDS or a generic OBD tool) to clear any error codes. Particularly clear any locked-ecu or immobiliser-related codes. If you see codes like “P059F Immobiliser Failure”, clearing them should allow normal operation after immo is off.
- Check Engine and Security: Verify that the engine runs smoothly and that no unexpected security alerts appear (e.g. EML or engine warning). Some cars may show a “Security” warning until adaptation is complete. If so, follow normal VAG procedures to sync keys/ECU via the scanning tool (even though it’s no longer needed to start, this can clear residual warnings).
- Test Drive: Perform a brief test drive to ensure everything functions. If the car runs correctly with no hesitation or limp mode, the procedure is successful.
For many technicians, the final check is simply ensuring the car starts and drives after the IMMO OFF. In some modern VW cars, any replaced ECU must be coded or adapted via the official software (ODIS) to match the vehicle’s chassis in terms of immobiliser config. However, if the ECU is immo-disabled, this coding step is unnecessary for key recognition. You may still code basic settings (if replacing ECU for hardware reasons) like instrument cluster alignment, but engine-wise the car should run fine.
Troubleshooting Common Issues
Even with all precautions, issues can arise. Here are common problems and fixes during PCR 2.1 IMMO OFF:
- ECU Still “Locked” or Won’t Start: This usually means the Immobiliser check wasn’t fully disabled. Check that you processed the correct dump file. Ensure you used the boot-mode dump (from TC1796) and that both flash and EEPROM were patched. Some tools require that you upload the entire memory image. If the problem persists, try repeating the process, and make sure the correct PCB area was patched.
- Write Errors or Verification Fail: If your flasher reports verify errors when writing the new file, first double-check cable connections and power supply. A weak ground or power drop can corrupt writes. Using a strong external PSU often fixes this. In one tip, removing the TriCore module on KESS V2 and using a very stable bench cable + PSU gave a 100% success for PCR2.1 writes.
- Blown ECU (Bricked): Worst case, improper flashing can brick the ECU. If this happens, use your original backup and try again. Some advanced tools (like UNLOCK options in K-TAG) can recover a “dead” TriCore if supported. Otherwise, professional ECU repair may be needed. This is why backups are essential.
- Incorrect File Format: PCR2.1 comes in different hardware versions; some dumps may have different checksums or structures. Make sure your IMMO software supports your exact ECU boot ID or part number. WebOctopus warns that incompatible files (mixing flash and eeprom from different units) will not work. Only clone between truly identical ECUs, or use IMMO OFF to avoid cloning entirely.
- CAN or Communication Problems: If the ECU won’t communicate in boot mode, verify CAN wiring (pins 67/68) and ground. If needed, try OBD mode reading (some tools like Magic X-17 can read through OBD now). However, OBD often won’t allow full write of immo sections on PCR2.1, so bench is recommended.
- Dashboard Sync Issues: On reinstallation, if the dash cluster still complains about immobliser even after a successful start, performing a diagnostics session (like “sync immo” in VAG software) can help. Alternatively, set the DIP switch on the ECU (if present) to match the cluster. But usually, clearing codes and restarting is enough after IMMO OFF.
Overall, patience and careful checking at each step will avoid most problems. If something fails, restore your backup and double-check each prior step (connection, cable orientation, correct dump, etc.) before trying again.
Case in Point: A technician reported a PCR2.1 ECU that wouldn’t write via OBD after unlocking. The fix was to remove the KESS TriCore module and use a bench cable with a robust 13.8 V PSU, which yielded a perfect write success. Such details matter for trouble‑shooting.
Legal and Ethical Considerations
Before disabling any immobiliser, it’s crucial to understand the legal context. In many jurisdictions, tampering with a vehicle’s security system may be illegal or strictly regulated. The IMMO OFF procedure should only be performed for legitimate reasons such as ECU repairs, tuning, or engine swaps – not for theft or unauthorized use.
Several IMMO OFF tools and services include disclaimers. For example, the GTAAuto IMMO Remover explicitly warns: “⚠️ Legal Disclaimer – Disabling the immobilizer may not be legal in some countries. Always check local regulations before using this tool.”. This highlights that removing the immobiliser could violate road safety or anti-theft laws where you live.
For professionals, it’s wise to:
- Inform the Vehicle Owner: Clearly document that the immobiliser has been disabled. Advise them on any implications (insurance, resale, etc.).
- Maintain Legitimacy: Only apply IMMO OFF on vehicles you have the right to service. If in doubt, obtain written authorization.
- Consider Alternatives: Sometimes a proper key coding or dealer programming might be the lawful solution. Use IMMO OFF when it’s the only practical fix (e.g. flooded ECU, no dealer support for an older car).
Remember: Safety and ethics come first. The goal of IMMO OFF is to restore or modify a vehicle you own or are repairing, not to help criminals. As a technician, always stay on the right side of the law.
Quick Takeaways
- Simos PCR2.1 Overview: A Continental/Siemens ECU used in VW Group 1.6 TDI cars (WFS4/IMMO4 system). Contains engine map and immobiliser data (VIN, PIN, CS).
- Reason for IMMO OFF: Needed when replacing or cloning ECUs, or for specific tuning/repair scenarios. Prevents immobiliser mismatch lockout.
- Key Tools: Bench-mode flasher (KESS, K-TAG, MPPS, etc.), TriCore boot cable (SSM 144300T111), and IMMO-OFF software (CK Decode, GTAauto, NeuroSuite). Emulators (Julie, FoxFlash) can also disable immo via OBD.
- Procedure Steps: Read full ECU (flash + EEPROM) in bench mode. Use IMMO-OFF software to patch out immobiliser code. Write back the modified file. Verify start.
- Backup First: Always save the original ECU dump before editing. The IMMO tool should fix checksums automatically. Keep a backup to restore if needed.
- Aftercare: Reinstall ECU, clear fault codes, and ensure the engine starts normally. No special key programming is needed once immo is off.
- Troubleshooting: Use a stable power supply to avoid read/write errors. Check compatibility of files. If ECU refuses to start, restore backup and retry steps.
- Legality: Check local laws before disabling an immobiliser. Perform IMMO OFF only for lawful repair or modification purposes.
Conclusion
Disabling the immobiliser on a SIMOS PCR 2.1 ECU is a specialized but essential skill for VW/Audi/Skoda technicians and enthusiasts working on 1.6 TDI engines. By understanding the ECU’s hardware (TriCore TC1796) and the VAG security system, you can safely remove the immobiliser lock when swapping or cloning an ECU. The key is preparation: use the proper boot-mode cable (SSM144300T111) and flasher tool, make a complete backup, then apply a tested IMMO OFF patch using software or an emulator. While the process sounds complex, following a step-by-step approach ensures success. Remember to troubleshoot carefully (stable power, correct dumps) and always save your original files.
The effort pays off in practical benefits: a once-dead or mismatched ECU can be revived, engine swaps become simpler, and the vehicle runs normally. For professional repairs, offering an IMMO OFF service (using custom methods like IAS does) can save time compared to dealer programming. Just be mindful of the legal side – only disable the immobiliser for legitimate, documented reasons.
With this guide, car professionals and hobbyists should feel confident tackling a SIMOS PCR2.1 IMMO OFF job. The car will start, the engine will run, and the immobiliser lamp will stay off. If you found these tips helpful, give them a try in your next ECU swap or repair. Safe tuning!
FAQs
Q: What vehicles use the Simos PCR 2.1 ECU?
A: The PCR 2.1 ECU appears in many VW Group 1.6 TDI models. Examples include VW Golf 6, Passat B7, Polo 6R, Jetta, Audi A1 (8X), A3 (8P), Skoda Octavia II, Fabia II, and Seat Leon/Toldeo with 1.6 TDI engines. It is identified by ECU part numbers like 03L 906 023 or 03L 907 425. In short, if your VW/Audi/Seat/Skoda 1.6 TDI has a digital engine ECU with an immobiliser (WFS4), it’s likely a SIMOS PCR2.1.
Q: Is it legal to disable (IMMO OFF) the immobiliser on my VW?
A: Laws vary by country. In many places, permanently disabling an immobiliser without a valid reason may violate anti-theft regulations. Always use IMMO OFF for legitimate purposes (e.g. repairing a broken ECU) and ensure the vehicle isn’t stolen. Some software tools explicitly warn that disabling the immobiliser “may not be legal in some countries”. When in doubt, consult local vehicle code or an experienced MOT tester.
Q: Do I need to open the ECU, or can I do IMMO OFF via OBD?
A: For SIMOS PCR2.1, a bench-mode connection is typically needed. That means removing the ECU and connecting via the boot cable to access the TC1796 micro. Some devices (like the Magic X-17 or a Julie emulator) claim to do PCR2.1 tricks over OBD, but most reliable methods require bench access and a cable (SSM 144300T111). In short, be prepared to open the ECU unless you have an ECU emulator specifically proven to work on PCR2.1.
Q: What tools do I need for PCR2.1 immobiliser removal?
A: You will need a programmer that supports Simos PCR2.1 (for example KESS v2, K-TAG, MPPS, or FGTech) plus the TriCore boot cable (Infineon SSM 144300T111). You also need immo‑off software: e.g., CK Decode online service, or a PCR2.1 Immo OFF tool (like GTAAuto’s), or an emulator like Julie Universal. In practice, one common setup is: use KESS/KTAG to read the ECU dump, then upload that dump to the CK Decode website, process it, and write back the patched file with the programmer.
Q: My ECU is water damaged. I only have the microcontroller flash dump (bin file). Can I still do IMMO OFF?
A: The PCR2.1 immobiliser relies partly on EEPROM data (VIN/PIN/CS) and partly on code in the main flash. If your EEPROM is unreadable, simply disabling IMMO via the flash (removing code) might let the engine run without keys. Some advanced tools allow “IMMO OFF using flash only” by patching the necessary code. However, without the EEPROM (where PIN/CS live), you lose all key data, so the car will start but no keys will be recognized. In these cases, it’s best to consult a professional who can extract or rewrite the EEPROM portion. Some immo removal services require the full dump (like IAS did), so a water-damaged micro might need more advanced recovery.
We Value Your Feedback!
Was this article helpful? If you’ve performed SIMOC PCR 2.1 IMMO OFF, let us know your experience in the comments! Share this guide with fellow car enthusiasts or technicias who might need to disable a VW/Audi/Skoda immobiliser. What tools or tips do you find indispensable when working on Simos PCR2.1 ECUs? Tweet or post this on social and tag us – we’d love to hear your feedback. How has IMMO OFF on PCR 2.1 helped in your project?