PCMFlash Dongle Manager – 67-in-1, 14-in-1 & 11-in-1 Profiles 0.1.0

PCMFlash Dongle Manager is a third-party Windows profile manager and launcher for three bundled legacy PCMFlash environments.

No physical Guardant USB dongle is connected in this workflow. The manager creates a local virtual Guardant device through USB/IP on the same computer, connects the selected profile and launches the matching PCMFlash build.

If anyone didn’t understand: you do not need to buy any USB dongles. Everything is already built into the manager, and it emulates all three versions that are normally sold together with Scanmatik.
All you need is a bare Scanmatik interface without any dongles.



The package includes:

• 67-in-1 profile — PCMFlash 1.2.0 — 67 enabled modules — 480 displayed ECU/TCU entries.
• 14-in-1 profile — PCMFlash 1.2.1 — 14 enabled modules — 124 displayed ECU/TCU entries.
• 11-in-1 profile — PCMFlash 1.2.1 — 11 enabled modules — 126 displayed ECU/TCU entries.

All three profiles were launched and checked by the uploader. The attached compatibility catalog was generated from the module lists shown by the running PCMFlash versions.

Important: This manager replaces only the local USB-dongle connection used by the bundled profile environment. It does not replace the vehicle communication hardware.

A compatible J2534 interface, such as an appropriate Scanmatik device, is still required for ECU/TCU communication. OBD, Bench or Boot work may also require the correct cable, breakout adapter, pinout and regulated power supply.

Main Features​#

• Three selectable profiles in one interface: 67-in-1, 14-in-1 and 11-in-1.
• Automatic launch of the PCMFlash build paired with the selected profile.
• Local virtual Guardant device over USB/IP localhost.
• Connected / Disconnected session status.
• Guardant and USB/IP prerequisite checks.
• Built-in buttons for installing missing driver components.
• Clean virtual-device connection and disconnection.
• Protection against changing profiles while PCMFlash is still open.
• Application log for driver, connection and launch events.
• Portable folder-based package after the required drivers are installed.

Profile Overview​#

67-in-1 — PCMFlash 1.2.0

The broadest profile in the package. Its displayed coverage includes Ford, Mazda, Honda/Acura, Nissan, Renault, Subaru, Kia/Hyundai, VAG, Mitsubishi, JLR, Mercedes-Benz, Jeep, Toyota, selected Chinese applications, generic Denso, Bosch MEDC17, Infineon/Tricore, Continental and additional commercial-vehicle entries.

14-in-1 — PCMFlash 1.2.1

A focused PCMFlash 1.2.1 profile built around Ford passenger vehicles, Ford USA, Ford PowerShift, selected Honda/Acura PGM-FI and transmission units, plus JLR SID208 entries.

11-in-1 — PCMFlash 1.2.1

A PCMFlash 1.2.1 profile focused on Kia/Hyundai engine and transmission controllers, VAG MED17/SIMOS/PCR2.1 and DSG/CVT units, Mercedes-Benz MED17/EDC17, selected Chinese Bosch/Delphi applications, generic Bosch MEDC17 and Infineon/Tricore service-mode entries.

Drivers and Local Virtual Session​#

PCMFlash Dongle Manager checks the prerequisite components before starting a profile session.



The tested package includes:

• Guardant driver package — the manager displays Guardant 7.0.206.
• USB/IP driver package — used to present the selected virtual device locally.
• Guardant kernel components such as grdusb.sys and grdkey.sys.
• USB/IP components such as usbip2_ude.sys and usbip2_filter.sys.

Administrator rights are required when installing system drivers. Restart Windows if an installer requests it.

System Requirements​#

• 64-bit Windows 10 or Windows 11.
• Administrator rights for initial driver installation.
• Approximately 90 MB of free storage for the package.
• A compatible J2534 vehicle interface.
• The correct OBD, Bench or Boot connection hardware for the selected PCMFlash module.
• A stable regulated ECU power supply when required by the selected operation.

Installation and First Start​#

1. Extract the complete ZIP into a dedicated folder. Do not run the program from inside the archive.
2. Launch DongleManager.exe.
3. Use Check drivers to verify Guardant and USB/IP components.
4. Install any missing prerequisite using the corresponding button.
5. Accept the administrator prompt and complete the driver installation.
6. Restart Windows if requested, then open Dongle Manager again.
7. Select the required 67-in-1, 14-in-1 or 11-in-1 profile.
8. Connect the selected virtual profile.
9. Click Launch PCMFlash.
10. Select the compatible J2534 interface inside PCMFlash before working with a control unit.

If Windows SmartScreen appears because the manager is unsigned, verify the file source and hash first. For a file you trust, choose More info and then Run anyway.

Important Operating Rules​#

• Do not update the bundled PCMFlash builds. The included versions are paired with the supplied profiles.
• Close PCMFlash before changing profiles.
• Do not disconnect the virtual profile while PCMFlash is identifying, reading or writing a control unit.
• Do not close Dongle Manager during an active ECU/TCU operation.
• Do not disconnect the J2534 interface or ECU power during programming.
• Confirm the exact ECU/TCU family, protocol and connection method before starting.
• Keep an original backup whenever the selected module supports reading.

Troubleshooting​#

Guardant or USB/IP is shown as missing

• Run the matching installer from Dongle Manager.
• Allow the administrator prompt.
• Use the recommended or compact installation option when offered.
• Restart Windows and run Check drivers again.

PCMFlash reports “Dongle not found”

• Close PCMFlash completely.
• Disconnect the current virtual session.
• Reconnect the required profile.
• Wait until Dongle Manager shows Connected.
• Launch PCMFlash again from the manager.

The PCMFlash module list appears empty

• Verify that the intended profile is connected.
• Close and reopen PCMFlash through Dongle Manager.
• Choose Retry if PCMFlash displays a reconnect prompt.
• If necessary, start a normal action such as Identification to refresh the interface.

The profile cannot be changed

Close PCMFlash first. The manager blocks profile switching while the application is running so that the virtual device is not removed unexpectedly.

PCMFlash offers an update

Cancel the update. Newer PCMFlash releases are not paired with the included legacy profiles.

Compatibility Notes​#

• Successful launch confirms the profile and bundled PCMFlash environment start correctly; it does not confirm every ECU/TCU operation.
• A module entry may cover only specific hardware, software, processor or connection variants.
• Read, Virtual Read, Write, EEPROM, Boot, BSL and checksum capabilities depend on the selected module entry.
• The manager does not provide J2534 communication by itself.
• The manager does not replace Bench/Boot cables, adapters or power equipment.
• Legacy PCMFlash 1.2.0/1.2.1 coverage must not be confused with the current official PCMFlash catalog.

---

Verified Profile and ECU/TCU Coverage​#

The compatibility data below was extracted directly from the module menus of the included PCMFlash 1.2.0 and 1.2.1 builds, then filtered by the modules enabled for each selected profile. The PCMFlash program files and profile data were not modified during extraction.

• 67-in-1 / PCMFlash 1.2.0: 67 enabled modules and 480 displayed ECU/TCU entries.
• 14-in-1 / PCMFlash 1.2.1: 14 enabled modules and 124 displayed ECU/TCU entries.
• 11-in-1 / PCMFlash 1.2.1: 11 enabled modules and 126 displayed ECU/TCU entries.

Important: The two PCMFlash 1.2.1 profiles are not merely shortened copies of the PCMFlash 1.2.0 profile. Their available entries reflect the module data present in their own bundled build.

Labels such as Test, Unlocked, Read-Only, BSL, Boot, MICRO, EEPROM and FLASH are reproduced from the displayed PCMFlash entries. They describe the menu item and must not be treated as a guarantee for every ECU hardware or software revision.

A listed family does not automatically mean every vehicle, ECU, TCU, hardware number or software number in that family is supported. Always verify the exact control-unit identification and the required connection method before reading or writing.

---

Final Note

Use ECU/TCU programming software only on vehicles and control units you own or are authorized to service. Always verify the selected module, interface, connection method and power conditions before starting a read or write operation.