PSA IMMO PIN Code Calculator is an offline Windows utility that derives the four-character immobilizer security code from a compatible ECU or BSI memory dump. It is intended for authorized key replacement, ECU/BSI matching and module-repair work on supported Peugeot and Citroën systems, with a smaller set of Volkswagen and Opel decoder profiles also present in the application.
The program does not connect to the vehicle and it does not read an EEPROM through OBD. The operator first acquires the correct EEPROM, flash or MCU region with suitable bench, boot, BDM, JTAG or chip-programmer hardware, then selects the exact controller profile and opens that file locally. The result is only as trustworthy as the dump identity and read quality.
The package includes the calculator plus two known-format PSA sample dumps for learning the file-selection workflow. The preview below is the real interface and shows the controller families exposed by its profile list.
It is a decoder, not a universal key-programming suite. It does not cut keys, program transponders, synchronize modules, reset a BSI, virginize an ECU or correct checksums after unrelated editing. Those are separate operations that require the correct diagnostic or programming workflow.
The name in the list must match the actual ECU family and the memory region read from it. For example, an EDC17 EEPROM-area file is not interchangeable with a full internal flash, and a DCM3.4 profile expects the serial EEPROM layout used by that decoder. Confirm the Bosch/Continental/Delphi part number, PSA number, processor and memory device before loading a file.
SID807 accepts several documented dump sizes depending on the chosen memory region and application. SID801, SID802 and SID806 use much smaller data blocks in this calculator. Never pad or truncate a dump simply to satisfy the size check; obtain the correct EEPROM or internal data area instead.
These profiles are useful only when the file comes from the matching controller generation. Similar model names can conceal different ECUs across engine, fuel, market and production-year variants. Read the ECU label and identify the memory component rather than selecting by vehicle model alone.
BSI data can contain VIN, configuration, mileage, key and security information in addition to the PIN. Treat every dump as sensitive customer data. Do not post an unredacted BSI file publicly.
For those non-PSA profiles, verify results independently before any adaptation. A plausible four-character output is not proof that the wrong controller definition was selected correctly.
File size is a first gate, not complete authentication. Two unrelated ECUs can produce files of the same length. Always pair size with controller number, processor, memory device and a visual review of the data.
That list is orientation only. The same model may use Bosch, Siemens/Continental, Delphi, Sagem or Magneti Marelli management, and the BSI design can change during a model run. Compatibility must be decided from the module label and dump structure, not from the badge or year alone.
If two reads differ, stop. A calculator cannot repair an unstable hardware read.
This resource is for lawful repair and recovery. A security code must never be used to bypass ownership checks.
The executable is an unsigned managed x86 application. Use it on an isolated workshop PC or virtual machine and verify its pinned hash before launch.
The original encrypted RAR passed a complete test and extraction. The executable and both sample files are byte-pinned; the application was inspected statically and was not launched during packaging because a genuine multi-panel interface screenshot was supplied. The publication archive uses encrypted headers and is independently tested after creation.
The program does not connect to the vehicle and it does not read an EEPROM through OBD. The operator first acquires the correct EEPROM, flash or MCU region with suitable bench, boot, BDM, JTAG or chip-programmer hardware, then selects the exact controller profile and opens that file locally. The result is only as trustworthy as the dump identity and read quality.
The package includes the calculator plus two known-format PSA sample dumps for learning the file-selection workflow. The preview below is the real interface and shows the controller families exposed by its profile list.
What the calculator does#
- Loads a local binary dump from a supported engine ECU or BSI
- Checks the selected profile against one or more expected file sizes
- Extracts the stored immobilizer PIN/security code when the layout is recognized
- Displays the calculated code in the application window
- Works offline after the required dump has been acquired
- Includes two sample files that demonstrate valid PSA EDC dump sizes
It is a decoder, not a universal key-programming suite. It does not cut keys, program transponders, synchronize modules, reset a BSI, virginize an ECU or correct checksums after unrelated editing. Those are separate operations that require the correct diagnostic or programming workflow.
PSA Bosch ECU profiles#
The interface contains profiles for the following Bosch controller families:- EDC15C2 and EDC15C7 diesel ECUs
- EDC16C3/C4 diesel ECUs
- EDC17C10 and EDC17C60 diesel ECUs
- MED17.4 and MEV17.4 petrol ECUs
- DCM3.4 and DCM3.5 diesel controllers
The name in the list must match the actual ECU family and the memory region read from it. For example, an EDC17 EEPROM-area file is not interchangeable with a full internal flash, and a DCM3.4 profile expects the serial EEPROM layout used by that decoder. Confirm the Bosch/Continental/Delphi part number, PSA number, processor and memory device before loading a file.
PSA Siemens and Continental SID profiles#
Supported selections visible in the program include SID201, SID801, SID802, SID803, SID803A, SID806 and SID807. These families span different generations, engines and memory devices, so the same file size is not valid for every SID controller.SID807 accepts several documented dump sizes depending on the chosen memory region and application. SID801, SID802 and SID806 use much smaller data blocks in this calculator. Never pad or truncate a dump simply to satisfy the size check; obtain the correct EEPROM or internal data area instead.
Magneti Marelli, Sagem and Lucas profiles#
The PSA list also includes:- IAW 4MP2 and IAW 48P2
- IAW 6LP
- ME7.4.4 and ME7.4.5
- J34P
- S2000 and S2000PM
- Lucas DCN2
These profiles are useful only when the file comes from the matching controller generation. Similar model names can conceal different ECUs across engine, fuel, market and production-year variants. Read the ECU label and identify the memory component rather than selecting by vehicle model alone.
Supported BSI layouts#
The interface includes dedicated BSI decoders for several older PSA body-control architectures:- Peugeot 206 non-multiplexed BSI with Motorola HC05 MCU data
- Valeo BSI with NEC MCU data
- Peugeot 406 Siemens BSI using 93C66 EEPROM
- Peugeot 406 and Citroën Xsara II Valeo BSI using 95040 EEPROM
- Peugeot 607 Z8 BSI using 93C66 EEPROM
- PSA UDS BSI using 95256 EEPROM
BSI data can contain VIN, configuration, mileage, key and security information in addition to the PIN. Treat every dump as sensitive customer data. Do not post an unredacted BSI file publicly.
Additional non-PSA profiles#
The application exposes Volkswagen EDC15V and EDC16U1 profiles plus an Opel MJD602 profile. Fiat/Ducato immobilizer entries appear in the interface as future or incomplete functions and should not be treated as working coverage.For those non-PSA profiles, verify results independently before any adaptation. A plausible four-character output is not proof that the wrong controller definition was selected correctly.
Exact input-size checks found in the application#
The built-in validation messages document these accepted sizes for several profiles:- EDC16C3/C4: 2,048, 4,096 or 8,192 bytes
- MEV17.4: 32,768 bytes
- EDC17C10: 65,536 or 131,072 bytes
- EDC17C60: 196,608 or 262,144 bytes, depending on profile path
- DCM3.4 / 95320: 4,096 bytes
- DCM3.5 / 95640: 8,192 bytes
- SID201: 4,096 bytes
- SID801, SID802 and SID806: 256 bytes
- SID807: 32,768, 65,536 or 131,072 bytes; another internal path expects 4,096 bytes
- IAW 4MP2: 262,144 bytes
- IAW 48P2 and IAW 6LP paths: 524,288 bytes
- ME7.4.4: 2,048 bytes
- ME7.4.5: 4,096 bytes
- J34P: 2,048 bytes
- Lucas DCN2, S2000 and S2000PM: 1,024 bytes
- BSI HC05 or NEC data: 256 bytes
- BSI 93C66 or 95040: 512 bytes
- BSI UDS / 95256: 32,768 bytes
- VAG EDC15V / 24C04: 512 bytes
- VAG EDC16U1 and Opel MJD602: 4,096 bytes
File size is a first gate, not complete authentication. Two unrelated ECUs can produce files of the same length. Always pair size with controller number, processor, memory device and a visual review of the data.
Typical Peugeot and Citroën applications#
These controller families appear across many PSA vehicles, including period Peugeot 206, 207, 208, 306, 307, 308, 406, 407, 607, Partner and Expert applications, and Citroën C2, C3, C4, C5, Xsara, Berlingo and Jumpy applications.That list is orientation only. The same model may use Bosch, Siemens/Continental, Delphi, Sagem or Magneti Marelli management, and the BSI design can change during a model run. Compatibility must be decided from the module label and dump structure, not from the badge or year alone.
Recommended acquisition workflow#
- Record the vehicle VIN, module part numbers and visible memory-device markings privately.
- Choose a programmer and pinout proven for that exact ECU or BSI.
- Use stable bench power and observe the required boot/BDM/JTAG/EEPROM voltage.
- Read the target region at least twice.
- Compare both files byte-for-byte and calculate a SHA-256 hash.
- Keep one immutable original before opening a working copy in the calculator.
- Select the exact controller profile and confirm that the file-size check passes naturally.
- Compare the displayed PIN with authorized service records or a second trusted method whenever possible.
If two reads differ, stop. A calculator cannot repair an unstable hardware read.
Authorized module-matching workflow#
The recovered PIN is commonly needed when adding keys or matching a replacement ECU/BSI through an approved diagnostic procedure. Before using it:- Verify ownership and technician authorization
- Confirm that the VIN and module identity correspond to the same vehicle
- Back up every involved module before adaptation
- Use the manufacturer's diagnostic sequence or a tool documented for the exact platform
- Maintain battery support throughout key or module programming
- Do not repeatedly guess a PIN; some systems impose delays or lockouts
- After completion, scan all modules and verify starting, central locking and remote functions
This resource is for lawful repair and recovery. A security code must never be used to bypass ownership checks.
System requirements#
- Windows PC with 32-bit x86 application support
- Microsoft .NET Framework 4.x; enabling the legacy .NET components may help on a clean modern Windows installation
- 1 GHz CPU, 1 GB RAM and less than 100 MB free storage
- A suitable EEPROM/flash programmer, ECU bench tool or BSI programmer for acquiring the source dump
- A hex viewer and hashing tool for verifying repeated reads
- No internet connection is required for calculation
The executable is an unsigned managed x86 application. Use it on an isolated workshop PC or virtual machine and verify its pinned hash before launch.
Package contents and integrity#
The cleaned package contains the Windows calculator and two PSA sample dumps: one larger EDC17C10 example and one small EDC16C3/C4 example. Their public filenames are normalized so demo security codes are not exposed in the archive listing.The original encrypted RAR passed a complete test and extraction. The executable and both sample files are byte-pinned; the application was inspected statically and was not launched during packaging because a genuine multi-panel interface screenshot was supplied. The publication archive uses encrypted headers and is independently tested after creation.
Limitations and troubleshooting#
- Unsupported file size: re-check whether you read EEPROM, internal flash, external flash or MCU data; do not resize the file.
- PIN remains blank or implausible: confirm the exact controller profile and compare with another verified dump.
- The sample works but the vehicle file does not: your module may use a different hardware/software revision despite the same vehicle model.
- The application does not start: enable the required .NET Framework components and 32-bit application support.
- A BSI dump contains personal data: keep it private and redact VIN, PIN, keys, mileage and customer identifiers before asking for help.
- A Fiat/Ducato entry is visible but unavailable: the interface labels it as a future function; do not claim it as supported.
- A calculated code is rejected by diagnostics: stop before repeated attempts and verify module identity, byte order, dump integrity and the diagnostic procedure.
- Security software flags the executable: quarantine it, compare the pinned hash and obtain an independent scan before use.
