PSA TPROT Remover MD1CS003 and EDC17C60 File Utility

PSA TPROT Remover is an offline Windows utility with separate processing pages for Bosch MD1CS003 and Bosch EDC17C60 engine-controller files in supported Peugeot and Citroën service workflows.

Each page exposes Open File, TPROT OFF and Save File controls while keeping the selected ECU family visible. The two family labels describe the supplied interface's scope; vehicle model, engine code, software revision and read format must still be verified against the ECU label and original binary.

MD1CS003 page selected, EDC17C60 and INFO tabs visible, with no file loaded and processing/save controls disabled.

What This Resource Is For

Local-file work for a qualified calibrator or ECU technician with a recognized PSA binary and a documented need to process its tuning-protection data. The application must be paired with the correct read/write method, stable power and a recoverable untouched original.

Confirmed Functions

• Select the MD1CS003 processing page.
• Select the EDC17C60 processing page.
• Open an existing ECU binary.
• Apply the available controller-family TPROT operation.
• Save the result as a separate working file.
• Keep the selected ECU family visible throughout processing.

Supported Vehicles, Controllers and Files

• Bosch MD1CS003: recognized files from selected PSA diesel applications.
• Bosch EDC17C60: recognized files from selected Peugeot and Citroën applications.
• Support is restricted to binaries accepted by the packaged algorithms.
• The family name alone does not establish support for every hardware or software revision.
• Do not substitute a virtual read for a full physical read, or vice versa, without proving that the format is appropriate.

Package Contents

• One portable 64-bit Windows executable.
• An interface preview showing both ECU-family tabs.
• No map packs, DAMOS, firmware collection, drivers or vehicle interface.
• The package notes report no embedded product-version metadata and static inspection without launch. The software version remains Unspecified; this is not an independent ECUDB executable test.

System, Hardware and Interface Requirements

• 64-bit Windows workstation or isolated virtual machine; exact supported Windows editions are unspecified.
• Exact original read from the target MD1CS003 or EDC17C60 ECU.
• Programmer compatible with the controller and selected read/file type.
• Hex/binary comparison software and controller-appropriate checksum validation.
• Regulated bench or vehicle support power for any later write operation.

Recommended Workshop Workflow

1. Record the vehicle, ECU label, hardware/software numbers and communication method.
2. Where practical, obtain two original reads, compare their hashes and store an untouched copy outside the working directory.
3. Match the file type, segment, exact byte length and ECU family to the intended operation.
4. Perform one documented operation on a working copy and inspect every changed region before saving.
5. Reopen or recheck the output, then validate it with the intended programmer or diagnostic platform before writing.
6. Use regulated power for subsequent bench/vehicle work and finish with identification and a full fault scan.

Compatibility Limits and Responsible Use

• Opening a binary successfully does not prove compatibility with the target controller, vehicle or hardware revision.
• Keep a verified original and compare byte lengths, identifiers and modified regions before any write.
• Security, identity, emissions and anti-theft functions require authority to service the property and a lawful intended change.
• The application does not replace OEM service information, stable power, a compatible interface or a tested recovery route.
• Isolate and independently check unsigned legacy executables; no malware-free claim is made.
• Emissions-related changes may be unlawful for road use and are not validated by this utility.

Troubleshooting

• File rejected: check full-read versus calibration-read format, byte length, ECU family and software revision.
• Unchanged output: confirm that the expected signature or supported data structure is present.
• Unexpectedly large changes: stop and compare against the untouched read; do not flash an unexplained result.
• Vehicle communication fails: check power, grounds, ignition state, interface driver and bus wiring separately from local-file processing.
• No recovery after writing: restore the exact original through the documented bench or boot recovery procedure.

File Integrity and Safety Notes

The package-preparation notes describe archive testing/extraction and static enumeration of executables, libraries and nested containers without running the automotive application. These are attributed preparation claims, not tests performed by ECUDB.

Preserve original hashes and backups, work on copies, independently check legacy or unsigned binaries and maintain a verified recovery route before controller writes or live-equipment changes.