cdiag/MultiPROG-Ultimate-Kit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add resources.

Browse Source
This commit is contained in:
Vasyl Palamarchuk
2026-09-22 13:19:23 -07:00
parent e7592bcfe3
commit 274b02a8ac
15 changed files with 1205 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files
07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md
+36
View File
@@ -26,6 +26,40 @@ GODIAG also sells narrower-purpose "test platform" boards for specific immobiliz
These are the kind of adapters referenced generically in `04_Workflows/BENCH_AND_BOOT_READING_WORKFLOW.md`, `04_Workflows/EEPROM_READ_WRITE_WORKFLOW.md`, and `04_Workflows/ECU_TCU_CLONE_WORKFLOW.md` — this document exists so those workflows have a concrete, real-world example to point to without hard-coding a specific vendor's pinout (always confirm current pinout/wiring from the adapter's own documentation, per those workflows' existing guidance).
## Xhorse Multi-PROG-specific adapters (article-derived)
The following adapter identities are named in the `13_Research_Expansion/OBDII365/` and
`13_Research_Expansion/XhorseTool/` article imports. Every entry is `COMMUNITY/VENDOR REFERENCE`
sourced from a single blog article — none of these are confirmed against this repository's own
installed-host testing or the supplied Multi-PROG manuals, and no pinout or wiring detail is
reproduced (`SOURCE DIAGRAM REQUIRED` where a diagram would otherwise be needed). Do not assume two
similarly named adapter models (e.g. V1 vs. V2 of the same adapter) share a pinout or fix.
| Adapter / cable | Reported role | Reported source note | Source |
| --- | --- | --- | --- |
| VH13 / VH20 / VH23 | SOP44/TSOP48 external chip boards | Named together as part of the SOP44/TSOP48 adapter product line | [XT-054](https://blog.xhorsetool.com/what-is-xhorse-multi-prog-sop44-tsop48-adapter/), 2024-02-23 |
| VH24 (XDMP04GL VH24V01) | SOP44/TSOP48 adapter | Used for AM29FXXX/M29FXXX/TB28FXXX flash families | [OBD-029](https://blog.obdii365.com/2024/06/28/how-to-use-vh24-vh29-adapters-with-xhorse-multi-prog/), 2024-06-28; [XT-049](https://blog.xhorsetool.com/how-to-read-and-write-sop44-flash-chip-with-xhorse-multi-prog/), 2024-04-03 |
| VH29 (XDMP05GL VH29V02) | EEPROM and flash adapter | Adapter selection follows chip selection in software, per source | [OBD-029](https://blog.obdii365.com/2024/06/28/how-to-use-vh24-vh29-adapters-with-xhorse-multi-prog/), 2024-06-28 |
| VH30 (XDMP06GL VH30V02) | SOP44 adapter | Named alongside VH24/VH29/VH31 | [OBD-029](https://blog.obdii365.com/2024/06/28/how-to-use-vh24-vh29-adapters-with-xhorse-multi-prog/), 2024-06-28 |
| VH31 (XDMP07GL VH31V02) | TSOP48 adapter | Named alongside VH24/VH29/VH30 | [OBD-029](https://blog.obdii365.com/2024/06/28/how-to-use-vh24-vh29-adapters-with-xhorse-multi-prog/), 2024-06-28 |
| BCM2 Adapter V2 (with XDNP100 / XDNP101) | Audi BCM2 EEPROM/flash access | Two separate case reports: "PIN Connection Detect Failed" and "PIN is Abnormal", both attributed to adapter/module compatibility and addressed by adapter modification | [XT-006](https://blog.xhorsetool.com/how-to-solve-xhorse-audi-bcm2-adapter-v2-pin-connection-detect-failed/), 2025-12-29; [XT-010](https://blog.xhorsetool.com/how-to-solve-xhorse-audi-bcm2-adapter-v2-pin-is-abnormal/), 2025-11-19 |
| Audi BCM2 solder-free adapter / BCM2-A2 Cable (XDNP66) | No-soldering Audi BCM2 read | Companion tool VVDI2 named for a related calculation step | [XT-039](https://blog.xhorsetool.com/how-to-connect-xhorse-multi-prog-and-bcm2-audi-solder-free-adapter/), 2024-11-15; [XT-050](https://blog.xhorsetool.com/how-to-read-audi-bcm2-module-with-xhorse-multi-prog-no-soldering/), 2024-03-25 |
| Multi-Prog MCU Adapter | Generic MCU direct-access adapter | A physical modification (added GND short/long wires) reported to enable a successful 9S12HZ512 read | [XT-003](https://blog.xhorsetool.com/xhorse-multi-prog-mcu-adapter-modification-method/), 2026-02-25 |
| Multi-Prog MCU Adapter + XDNP18 Adapter | BMW FRM E-series repair | Source describes two distinct repair methods using these adapters | [XT-047](https://blog.xhorsetool.com/how-to-repair-bmw-frm-e-series-by-xhorse-multi-prog/), 2024-05-11 |
| XDNP24GL D80/35080 Adapter | M35080 EEPROM erase/read | VPP adjustment named as a troubleshooting step for erase error `13050001` | [XT-044](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-erase-m35080-error-code-13050001/), 2024-08-13 |
| XDMPR8GL MQB RH850/V850 Adapter | VAG MQB RH850/V850 R7F701402 dashboard key programming | Used together with VVDI2 in the reported case | [XT-045](https://blog.xhorsetool.com/xhorse-multi-prog-and-vvdi2-program-mqb-rh850-v850-1402-dashboard-key/), 2024-07-31 |
| MQB RH850/V850 adapter (unspecified model) | VAG MQB RH850 R7F701407 | Source warns specifically against extending/lengthening this adapter's harness to avoid "Chip Configuration Failed" | [XT-043](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-mqb-rh850-chip-configuration-failed-problem/), 2024-09-28 |
| Xhorse MQB solder-free adapters / Xhorse RH850/V850 adapter | VAG MQB NEC35XX and RH850/V850 clusters | Compared against Yanhua ACDP Module 33 (NEC35XX) and Module 34 (RH850/V850) in a vendor-community comparison; exact coverage not independently verified | [OBD-051](https://blog.obdii365.com/2024/07/29/xhorse-mqb-adapters-vs-yanhua-acdp-mqb-adapters/), 2024-07-29 |
| Multi-PROG RH850/V850 adapter | VAG MQB RH850 5A/5C cluster IMMO/mileage work | Listed among six community-reported tools for this task (see `13_Research_Expansion/MODULE_CASE_STUDIES.md`) | [OBD-052](https://blog.obdii365.com/2024/07/23/top-6-tools-for-vag-mqb-rh850-immo-mileage/), 2024-07-23 |
| GODIAG G-V ECU Cable + GT107 / GT107+ | VAG DQ200/DQ250 TCU and engine ECU bench/boot connection | Connection accessory named for bench and boot mode | [OBD-020](https://blog.obdii365.com/2024/11/07/how-to-connect-xhorse-multi-prog-with-godiag-gt107-or-gpt-cable/), 2024-11-07; [XT-038](https://blog.xhorsetool.com/xhorse-multi-prog-with-godiag-cables-read-med17-8-8/), 2024-11-20 |
| MVCI PRO J2534 | Vehicle diagnostic passthrough (separate from bench programming) | Reported software version 1.0.3 with associated driver | [XT-032](https://blog.xhorsetool.com/how-to-use-xhorse-mvci-pro-j2534-for-vehicle-diagnosis-and-programming/), 2025-02-21 |
| USB WiFi adapter | Multi-PROG host WiFi connectivity | Insert then power on to activate WiFi; numeric-only WiFi password reported | [XT-018](https://blog.xhorsetool.com/how-to-set-wifi-password-for-xhorse-multi-prog/), 2025-07-11; [XT-022](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-wifi-module-not-inserted/), 2025-05-19 |
These rows are adapter/tool identity only; do not infer a pinout, voltage, or resistance value from
this table (see `13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md` and
`13_Research_Expansion/MODULE_CASE_STUDIES.md` for the module-level context each row supports, and
`13_Research_Expansion/UNIFIED_SOURCE_MANIFEST.csv` for the full source register).
## Xhorse hardware ecosystem (context for Multi-PROG users)
Multi-PROG is one device in a broader Xhorse hardware lineup that shows up together in authorized shop workflows. For context (not an endorsement or purchasing guide):
@@ -46,3 +80,5 @@ Multi-PROG is one device in a broader Xhorse hardware lineup that shows up toget
- `02_Resource_Catalog/links.csv` — catalog entries with source URLs for the hardware referenced above
- `04_Workflows/BENCH_AND_BOOT_READING_WORKFLOW.md`, `EEPROM_READ_WRITE_WORKFLOW.md`, `ECU_TCU_CLONE_WORKFLOW.md`, `ISN_OPERATIONS_WORKFLOW.md`
- `01_Knowledge_Base/AUTOMOTIVE_MEMORY_CONCEPTS.md`, `IMMOBILIZER_CONCEPTS.md`
- `13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md`, `MODULE_CASE_STUDIES.md`, `MULTIPROG_ERROR_CODE_CATALOG.md`, `OPERATIONAL_PRACTICES.md` — article-derived detail behind the adapter table above
- `13_Research_Expansion/UNIFIED_SOURCE_MANIFEST.md` / `.csv` — full OBDII365/XhorseTool source register
13_Research_Expansion/COMMON_CHECKSUMS.md
+15
View File
@@ -14,3 +14,18 @@
## Use pattern
Use them for offline validation and known vector comparison.
## Article-derived note: Multi-PROG's own device-library checksum function
`COMMUNITY/VENDOR REFERENCE` — a single source article reports that Multi-PROG's own checksum
function is applied per supported device-library entry (shown as a green "C" indicator) and is used
through the host's Write/Verify UI, rather than as a standalone callable script API. The source
itself states that real-vehicle validation of the checksum result remains unconfirmed in its
report. This is a separate concept from the offline CRC/hash algorithms listed above: those are
generic, dependency-free implementations this kit can run and self-test independently; the
device-library checksum function described here is host/device-specific and has not been verified
against an installed Multi-PROG. Do not assume the two are interchangeable without confirming the
exact algorithm in Local Script Help.
- Source: [How to Calculate Checksum for Xhorse Multi Prog?](https://blog.xhorsetool.com/how-to-calculate-checksum-for-xhorse-multi-prog/), 2026-01-23, `COMMUNITY/VENDOR REFERENCE` (`XT-005` in `UNIFIED_SOURCE_MANIFEST.csv`)
- See `13_Research_Expansion/OPERATIONAL_PRACTICES.md` for the full practice note.
13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md
+167
View File
@@ -0,0 +1,167 @@
# MCU / EEPROM / FLASH Device Reference (Article-Derived)
Article-derived reference notes for specific MCU, EEPROM, and FLASH devices named in the
`OBDII365`/`XhorseTool` article imports. Every row cites exactly one or two source articles and
does not merge derivatives, infer pinouts, infer memory maps, or infer electrical requirements. See
`01_Knowledge_Base/AUTOMOTIVE_MEMORY_CONCEPTS.md` for the vendor-neutral terminology and
access-path model this reference follows.
## Evidence status
All entries are `COMMUNITY/VENDOR REFERENCE`. None are `PRIMARY-MULTIPROG` or
`PRIMARY-MANUFACTURER`. Package, pinout, memory-map, and electrical-requirement fields are marked
`SOURCE VALUE UNCLEAR` or `SOURCE DIAGRAM REQUIRED` whenever the source article did not state them
explicitly — this reference does not reconstruct or guess them.
## MCU devices
### 9S12HZ512
- Access method: MCU adapter (Multi-Prog MCU Adapter)
- Reported finding: source describes a physical MCU-adapter modification (added GND short/long
wires) that enabled a successful read
- Package/pinout: `SOURCE VALUE UNCLEAR`
- Source: [XT-003](https://blog.xhorsetool.com/xhorse-multi-prog-mcu-adapter-modification-method/), 2026-02-25, `COMMUNITY/VENDOR REFERENCE`
### MC68HC05X32 (marking 1D69J)
- Manufacturer: Motorola
- Access method: MCU adapter
- Reported finding: read failure reported; article title only, not body-extracted
- Source: [XT-037](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-failed-to-read-motorola-mc68hc05x32-1d69j/), 2024-11-22, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`)
### ST10F269 / MC9512XDT256 (BMW FRM2)
- Device family: BMW FRM2
- Access method: MCU direct access
- Tools named: Multi-PROG; VVDI Prog
- Reported finding: source states module-specific flash/EEPROM files are required, and explicitly
distinguishes FRM2 from FRM3 (do not generalize an FRM3 fix/recovery claim to FRM2, or vice versa)
- Source: [XT-011](https://blog.xhorsetool.com/xhorse-multi-prog-vvdi-prog-bmw-frm2-st10f269-pinout/), 2025-11-17, `COMMUNITY/VENDOR REFERENCE`
### MPC5515 (BMW REM)
- Device family: BMW REM
- Access method: MCU direct access
- Tools named: Multi-PROG; VVDI Prog
- Reported hardware note: source mentions a 100-120 ohm resistor in a read-modify-write repair
context; exact placement/purpose is `SOURCE VALUE UNCLEAR` (no wiring diagram reproduced —
`SOURCE DIAGRAM REQUIRED`)
- Source: [XT-017](https://blog.xhorsetool.com/bmw-rem-module-pinout-for-xhorse-multi-prog-and-vvdi-prog/), 2025-07-18, `COMMUNITY/VENDOR REFERENCE`
### D70F3376A (Renault Master BCM N3)
- Manufacturer family: Renesas V850
- Device family: Renault Master BCM N3
- Access method: MCU direct access
- Pinout: `SOURCE DIAGRAM REQUIRED` (title/tool metadata only, not body-extracted)
- Source: [XT-030](https://blog.xhorsetool.com/xhorse-multi-prog-renault-master-bcm-n3-d70f3376a-pinout/), 2025-03-17, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`)
### D70F3524 (Hyundai Solaris)
- Access method: MCU direct access
- Reported troubleshooting claim: "check pinout and supply 12V" (source-level troubleshooting
claim, not a verified electrical requirement — do not treat "12V" as a confirmed VDD/VPP value
without the source's own wiring context)
- Source: [XT-040](https://blog.xhorsetool.com/how-to-solve-multi-prog-fail-to-read-d70f3524-hyundai-solaris/), 2024-10-21, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`)
### D70F3423 / D70F3426 (VAG MQB dashboard)
- Device family: VAG MQB dashboard
- Reported finding: named together with a historical software/database update (V1.1.2.0 /
Database V11); no independent procedure detail extracted
- Source: [XT-053](https://blog.xhorsetool.com/xhorse-multi-prog-v1-1-2-0-update-mqb-d70f3423-d70f3426/), 2024-02-28, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`); cross-reference [OBD-034](https://blog.obdii365.com/2024/02/27/xhorse-multi-prog-update-vag-mqb-rh850-v850-dashboard/) (same historical version window)
### RH850/V850 R7F701402 (VAG MQB dashboard, "1402")
- Device family: VAG MQB RH850/V850 dashboard
- Access method: adapter-assisted cluster access
- Adapter named: XDMPR8GL MQB RH850/V850 Adapter
- Companion tool: VVDI2
- Source: [XT-045](https://blog.xhorsetool.com/xhorse-multi-prog-and-vvdi2-program-mqb-rh850-v850-1402-dashboard-key/), 2024-07-31, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`)
### RH850 R7F701407 (VAG MQB RH850)
- Device family: VAG MQB RH850
- Adapter named: MQB RH850/V850 adapter
- Reported finding: "Chip Configuration Failed" condition; source specifically warns against
extending/lengthening the adapter harness (see `MULTIPROG_ERROR_CODE_CATALOG.md`)
- Source: [XT-043](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-mqb-rh850-chip-configuration-failed-problem/), 2024-09-28, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`)
### Infineon TC234L 32F (VW/Skoda 5QF959655AT SRS)
- Device family: VW/Skoda SRS module 5QF959655AT
- Access method: MCU DFlash/PFlash read and write
- Tools named: Xhorse Multi-PROG (reported reading/writing DFlash and PFlash); OBDSTAR P50
(reported for crash-data cleaning, a separate step)
- Reported method: read DFlash and PFlash from the original module, then write to a donor module
- Flash-protection/endurance statements in the source are retained as source claims only, not
independently validated
- Source: [OBD-049](https://blog.obdii365.com/2025/02/12/clean-and-clone-vw-skoda-5qf959655at-airbag-module/), 2025-02-12, `COMMUNITY/VENDOR REFERENCE`
## EEPROM devices
### 24C256 (Audi radio)
- Device family: Audi radio, component-protection context
- Access method: EEPROM access
- Reported finding: title/tool metadata names 24C256 EEPROM in a component-protection case; full
procedure not body-extracted
- Source: [XT-025](https://blog.xhorsetool.com/xhorse-multi-prog-fixes-audi-radio-24c256-unit-component-protection/), 2025-04-21, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`)
### M35080
- Device family: external EEPROM
- Adapter named: XDNP24GL D80/35080 Adapter
- Reported finding: erase failure, error code `13050001`; source-described VPP adjustment
troubleshooting (see `MULTIPROG_ERROR_CODE_CATALOG.md`)
- Source: [XT-044](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-erase-m35080-error-code-13050001/), 2024-08-13, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`)
### AT17C128 (DIP8)
- Device family: external EEPROM
- Adapter named: "AT17C128 DIP8 and corresponding adapter" (exact adapter model not stated —
`SOURCE VALUE UNCLEAR`)
- Source: [XT-051](https://blog.xhorsetool.com/how-to-read-and-write-eeprom-with-xhorse-multi-prog/), 2024-03-18, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`)
### 24C32 (Audi A3/Golf instrument cluster, Micronas CDC3217G/3297G)
- Device family: Audi A3/Golf 2007-2009 instrument cluster
- Access method: direct cluster memory access
- Tools reported: source lists Xhorse Multi-PROG among tools that did **not** succeed reading this
cluster in the described case; XPROG and SMOK JTAG are reported as the tools that succeeded in
the source's example. Do not treat this as "Multi-PROG cannot read this cluster" in general — it
is a single reported case, and read support for one tool does not establish support (or lack of
it) for another
- Source: [OBD-046](https://blog.obdii365.com/2026/01/13/read-audi-a3-akl-micronas-cdc3217g-by-autel-xhorse-xprog-or-upa/), 2026-01-13, `COMMUNITY/VENDOR REFERENCE`
## FLASH devices (SOP44/TSOP48)
### AM29FXXX / M29FXXX / TB28FXXX families
- Access method: external chip adapter (SOP44/TSOP48)
- Adapter named: VH24 SOP44/TSOP48 adapter
- Reported finding: source names these three flash families as supported entries for the
SOP44/TSOP48 adapter path; exact part-number suffixes/derivatives are `SOURCE VALUE UNCLEAR` (do
not assume every derivative in each family is supported — instruction 18 prohibits assuming
package compatibility from a family name alone)
- Source: [XT-049](https://blog.xhorsetool.com/how-to-read-and-write-sop44-flash-chip-with-xhorse-multi-prog/), 2024-04-03, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`)
### SOP44/TSOP48 adapter family overview
- See `07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md` for the VH13/VH20/VH23/VH24/VH29/VH30 adapter identity table (adapter hardware, not device-specific chip data, so it is documented there instead of duplicated here).
## Access-path reminders (per repository policy)
- Read support reported for a device does not imply write support for the same device (instruction 19).
- Bench-mode support reported for a device does not imply boot-mode support for the same device (instruction 20).
- Access to one memory region (e.g. DFlash) does not imply access to another region (e.g. PFlash, EEPROM configuration area) unless the source states both explicitly (instruction 21).
- FRM2 and FRM3 are explicitly distinct in the sources above; do not generalize between them.
## Related documents
- `01_Knowledge_Base/AUTOMOTIVE_MEMORY_CONCEPTS.md` — vendor-neutral memory terminology and access-path model
- `13_Research_Expansion/MODULE_CASE_STUDIES.md` — module-level (not chip-level) case studies for these same devices
- `13_Research_Expansion/MULTIPROG_ERROR_CODE_CATALOG.md` — error codes referenced above
- `07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md` — adapter hardware referenced above
- `13_Research_Expansion/UNIFIED_SOURCE_MANIFEST.md` / `.csv` — full source register
13_Research_Expansion/MODULE_CASE_STUDIES.md
+241
View File
@@ -0,0 +1,241 @@
# Module Case Studies (Article-Derived)
Article-derived case studies for specific ECU/BCM/immobilizer/module families named in the
`OBDII365`/`XhorseTool` article imports. Each case study is a single reported example, not a
universal support claim. Sensitive key/immobilizer operational detail is intentionally summarized,
not reproduced, per the source folders' own import policy and this repository's authorized-use
boundary (see `07_Authorized_Key_Immobilizer_Work/README.md`).
## Evidence status
All entries are `COMMUNITY/VENDOR REFERENCE`, sourced from exactly one article each (see citation).
None are promoted to `PRIMARY-MULTIPROG`. Where the source did not state a detail, this file uses
`SOURCE VALUE UNCLEAR`.
## BMW
### BMW FRM2 — ST10F269 / MC9512XDT256
- Access path: MCU direct access
- Tools: Multi-PROG; VVDI Prog
- Reported finding: module-specific flash/EEPROM files required; explicitly distinct from FRM3
- Source: [XT-011](https://blog.xhorsetool.com/xhorse-multi-prog-vvdi-prog-bmw-frm2-st10f269-pinout/), 2025-11-17
### BMW FRM3
- Access path: MCU adapter (Multi-Prog MCU Adapter)
- Reported finding: "Chip Configuration Failed", error `88030201`, attributed to insufficient RESET
solder-point connection; re-soldering reported as the fix
- Source: [XT-009](https://blog.xhorsetool.com/how-to-fix-xhorse-multi-prog-bmw-frm3-chip-configuration-failed/), 2025-11-24
### BMW FRM E-series
- Access path: MCU adapter
- Tools/adapters: Multi-Prog MCU Adapter; XDNP18 Adapter
- Reported finding: source describes two distinct repair methods; method-level detail not
independently verified
- Source: [XT-047](https://blog.xhorsetool.com/how-to-repair-bmw-frm-e-series-by-xhorse-multi-prog/), 2024-05-11 (`INDEXED_ONLY`)
### BMW REM — MPC5515
- Access path: MCU direct access
- Tools: Multi-PROG; VVDI Prog
- Reported context: read-modify-write repair; a 100-120 ohm resistor mentioned in the source's
reported context, exact purpose/placement `SOURCE VALUE UNCLEAR`
- Source: [XT-017](https://blog.xhorsetool.com/bmw-rem-module-pinout-for-xhorse-multi-prog-and-vvdi-prog/), 2025-07-18
### BMW MSV80
- Access path: bench, authorization troubleshooting
- Reported finding: "Number of Times is 0" (a read-attempt/authorization counter condition);
article title only, not body-extracted — `SOURCE VALUE UNCLEAR` for cause/remedy
- Source: [XT-028](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-read-bmw-msv80-number-of-times-is-0/), 2025-04-02 (`INDEXED_ONLY`)
### BMW FEM/BDC — 95128
- Reported finding: "Write ... Chip Data Failure"; article title only, not body-extracted
- Source: [XT-027](https://blog.xhorsetool.com/solved-xhorse-multi-prog-write-bmw-fem-bdc-chip-data-failure/), 2025-04-09 (`INDEXED_ONLY`)
### BMW BDC2/BDC3/BCP/LCD keys (G/U-series, and E/F-series BDC03)
- Access path: key data read/write
- Tools: Multi-PROG; VVDI Prog; VVDI2; VVDI Key Tool Plus; Key Tool MIDI; BMW G BDC2 authorization license
- Reported findings (summarized, security-sensitive operational detail withheld):
- Multi-PROG database V87 reported to support direct original-key read/write with no data conversion step ([XT-008](https://blog.xhorsetool.com/xhorse-multi-prog-update-bdc3-key-copy-function/), 2025-12-05)
- Encrypted-key cloning update reported, with soldering and a dedicated VVDI BMW adapter named ([XT-004](https://blog.xhorsetool.com/xhorse-update-bmw-bdc2-bdc3-bcp-encrypted-key-cloning/), 2026-02-13)
- G/U-series BDC3/BCP key-copy feature reported to require a BMW G BDC2 authorization license; a companion key tool loads the collected data ([XT-014](https://blog.xhorsetool.com/xhorse-update-bmw-g-u-series-bdc3-bcp-key-copy-feature/), 2025-10-10; cross-reference [OBD-047](https://blog.obdii365.com/2025/10/09/xhorse-update-bmw-g-series-bdc3-bcp-key-cloning-function/), 2025-10-09 — same feature, two source sites, not merged/deduplicated as identical since exact scope claims differ slightly)
- Encrypted key pinout/data-access article names a modified MCU adapter plus Key Tool MIDI/Plus as companion tools ([XT-002](https://blog.xhorsetool.com/xhorse-multi-prog-bmw-bdc2-bdc3-lcd-encrypted-key-pinouts/), 2026-02-27)
- Authorized-use note: these are key-programming procedures; any use in this repository must follow `07_Authorized_Key_Immobilizer_Work/README.md` controls (ID/ownership verification, chain of custody, redacted reporting).
### BMW CAS3
- Access path: not specified by source
- Reported: indexed comparison article only ("Multi Prog or Autel to Read BMW CAS3 Immobilizer?")
- Source: [OBD-014](https://blog.obdii365.com/2025/03/13/xhorse-multi-prog-or-autel-to-read-bmw-cas3-immobilizer/), 2025-03-13 (`INDEXED_ONLY`)
### BMW CAS4 — 5M48H
- Access path: local script function
- Reported: "Repair BMW CAS4 KM (Script Function)" — title indicates a Multi-PROG local script was
used for a KM (mileage) function; procedure not body-extracted, no script content reproduced
- Source: [OBD-033](https://blog.obdii365.com/2024/02/28/xhorse-multi-prog-repair-bmw-cas4-km-script-function/), 2024-02-28 (`INDEXED_ONLY`)
## Audi / VW / Skoda
### Audi BCM2 (multiple adapter-version case reports)
- Access path: adapter-assisted EEPROM/flash access, and solder-free adapter variants
- Adapters: BCM2 Adapter V2; XDNP100; XDNP101; Audi BCM2 solder-free adapter; BCM2-A2 Cable XDNP66
- Reported findings:
- Clone guide distinguishes non-encrypted vs. encrypted BCM2 cases and stresses hardware-version matching ([XT-012](https://blog.xhorsetool.com/xhorse-tools-clone-audi-bcm2-module-guide/), 2025-10-22)
- "PIN Connection Detect Failed" and "PIN is Abnormal" both reported against BCM2 Adapter V2, addressed by adapter modification in each case ([XT-006](https://blog.xhorsetool.com/how-to-solve-xhorse-audi-bcm2-adapter-v2-pin-connection-detect-failed/), 2025-12-29; [XT-010](https://blog.xhorsetool.com/how-to-solve-xhorse-audi-bcm2-adapter-v2-pin-is-abnormal/), 2025-11-19)
- Solder-free adapter path reported for no-soldering reads, with VVDI2 as a companion tool ([XT-039](https://blog.xhorsetool.com/how-to-connect-xhorse-multi-prog-and-bcm2-audi-solder-free-adapter/), 2024-11-15; [XT-050](https://blog.xhorsetool.com/how-to-read-audi-bcm2-module-with-xhorse-multi-prog-no-soldering/), 2024-03-25)
- "New BCM2 Adapter" reported for an encrypted BCM2 module clone case, device family noted as Audi BCM2 / D70F3634 — title-only, indexed record ([OBD-007](https://blog.obdii365.com/2025/08/08/xhorse-multi-prog-clone-audi-encrypted-bcm2-module/), 2025-08-08, `INDEXED_ONLY`)
### Audi J518 (1L59W/5L40K, marking "0115")
- Access path: chip power troubleshooting
- Tools: Multi-PROG; VVDI Prog
- Reported finding: read failure, error `13050102`; source recommends VDD 4-5V plus a DB44/MCU
self-check
- Source: [XT-019](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-read-audi-j518-2010-failure/), 2025-06-25
### Audi radio — 24C256
- Access path: EEPROM access
- Reported context: component-protection case; title/tool metadata only
- Source: [XT-025](https://blog.xhorsetool.com/xhorse-multi-prog-fixes-audi-radio-24c256-unit-component-protection/), 2025-04-21 (`INDEXED_ONLY`)
### Audi A3 (2014-2020) climate control unit
- Access path: EEPROM/module cloning
- Reported: title/tool metadata only, not body-extracted
- Source: [XT-026](https://blog.xhorsetool.com/xhorse-multi-prog-clone-audi-a3-2014-2020-climate-control-unit/), 2025-04-18 (`INDEXED_ONLY`)
### VW ME7.1 / ME7.x
- Access path: bench
- Reported finding: "Chip Power Configuration Failed"; 12V ECU power supply named as a
troubleshooting factor (source claim, not a confirmed electrical spec)
- Source: [XT-021](https://blog.xhorsetool.com/how-to-solve-multi-prog-me7-1-chip-power-configuration-failed/), 2025-06-04
### VW EDC17CP14
- Access path: bench
- Reported: "Read and Write ... on Bench" — bench INT EEPROM and flash access described; procedure
not body-extracted
- Source: [XT-052](https://blog.xhorsetool.com/xhorse-multi-prog-read-and-write-vw-edc17cp14-on-bench/), 2024-03-11 (`INDEXED_ONLY`)
### VAG MED17.8.8 — TC1728
- Access path: bench/boot adapter
- Adapters: GODIAG G-V ECU Cable; GT107/GT107+
- Reported: connection setup via GODIAG cables; procedure not body-extracted
- Source: [XT-038](https://blog.xhorsetool.com/xhorse-multi-prog-with-godiag-cables-read-med17-8-8/), 2024-11-20 (`INDEXED_ONLY`)
### VAG MQB RH850/V850 5A vs 5C clusters
- Access path: cluster identification and adapter-assisted access
- Tools: Xhorse Multi-PROG; CG100X; VVDI Prog; Key Tool Plus; Yanhua ACDP Module 34
- Reported finding: source presents EM/PCJ markings as a way to distinguish example 5A vs. 5C
clusters — an explicitly source-specific heuristic, **not** a manufacturer standard; do not
generalize this marking scheme to other clusters
- Source: [OBD-054](https://blog.obdii365.com/2024/06/12/vag-mqb-rh850-cluster-5a-vs-5c/), 2024-06-12
### VAG MQB RH850/V850 dashboard/IMMO tooling (general landscape)
- Reported: source lists six community-reported tools for VAG MQB RH850 IMMO/mileage work (VVDI Key
Tool Plus, Xhorse Multi-PROG with dedicated RH850/V850 adapter, Autel APB131, Yanhua Mini ACDP
Module 34, CGDI CG100X, AVDI VN021/VN023, PolDiag), explicitly as a community comparison, not a
validated compatibility matrix
- Source: [OBD-052](https://blog.obdii365.com/2024/07/23/top-6-tools-for-vag-mqb-rh850-immo-mileage/), 2024-07-23
### VAG TCU families (DQ200/DQ250/DQ380/DQ381/DQ400E/DL382/DL501/VL300/VL381/V30)
- Access path: bench adapter connection
- Adapters/tools: GODIAG 9-in-1 gearbox adapter; OBD2 bench adapter; Xhorse Multi-PROG (connects
through the Multi-PROG connector, per source); Autel G-BOX; Scanmatik 2 Pro + PCMFlash; Flex
- Source: [OBD-048](https://blog.obdii365.com/2025/09/19/connect-godiag-9-in-1-gearbox-cable-with-xhorse-autel-flex/), 2025-09-19
### VW/Skoda SRS 5QF959655AT (Infineon TC234L 32F)
- Access path: MCU DFlash/PFlash read and write
- Tools: Xhorse Multi-PROG (DFlash/PFlash read+write); OBDSTAR P50 (crash-data cleaning)
- Reported method: read DFlash/PFlash from an original module, then write to a donor module
- Source: [OBD-049](https://blog.obdii365.com/2025/02/12/clean-and-clone-vw-skoda-5qf959655at-airbag-module/), 2025-02-12
## GM / Delco
### GM Delco E39/E39A/E78/E98/E83/E84
- Access path: bench / boot recovery
- Reported findings:
- "Read GM Delco E39 E78 E98 etc ECM 16-digit Shadow Password" — title-only, indexed ([OBD-010](https://blog.obdii365.com/2025/03/20/xhorse-multi-prog-read-gm-delco-e39-e78-e98-etc-ecm-16-digit-shadow-password/), 2025-03-20, `INDEXED_ONLY`)
- "Read Write Captiva Delco E39A on Bench OK" — title-only, indexed ([XT-033](https://blog.xhorsetool.com/xhorse-multi-prog-read-write-captiva-delco-e39a-on-bench-ok/), 2025-02-17, `INDEXED_ONLY`)
- Boot-mode shadow-password recovery described in more detail using I/O Terminal, OBDSTAR
DC706/G3, and Alientech KESS3, with Xhorse Multi-PROG named among the tools; the shadow
password is reported as per-module (sensitive recovery detail intentionally not reproduced here)
([OBD-053](https://blog.obdii365.com/2024/07/02/recover-gm-delco-e98-e39-e39a-ecms-with-shadow-password/), 2024-07-02)
## Hyundai / KIA
### KIA MEG17.9.12
- Access path: boot troubleshooting
- Reported finding: "Connection Failed" reported to indicate no communication; source suggests
boot mode
- Source: [XT-015](https://blog.xhorsetool.com/xhorse-multi-prog-kia-meg17-9-12-connection-failed-solution/), 2025-09-29
### Hyundai Solaris — D70F3524
- Access path: MCU direct access troubleshooting
- Reported claim: "check pinout and supply 12V" (source-level troubleshooting claim only)
- Source: [XT-040](https://blog.xhorsetool.com/how-to-solve-multi-prog-fail-to-read-d70f3524-hyundai-solaris/), 2024-10-21 (`INDEXED_ONLY`)
## PSA
### PSA Bosch MD1CS003
- Access path: bench
- Tools: KESS3; Xhorse Multi-PROG; FoxFlash; FormulaFlash; CG FC200; OBDSTAR DC706; Launch ECU
programmer; Hextag
- Reported finding: source presents a part-number series as a claimed TPROT (write-protection)
indicator — an explicitly source-specific heuristic, not independently validated
- Source: [OBD-050](https://blog.obdii365.com/2024/12/03/how-to-tell-if-psa-md1cs003-ecu-is-locked-or-not/), 2024-12-03
## Mercedes
### Mercedes S500 (W220) immobilizer
- Access path: EEPROM + companion key tool
- Tools: Multi-PROG; Key Tool Plus; Xhorse Cloud
- Reported finding: EEPROM extraction, cloud-assisted decoding, key-file preparation, and writing
reported in a 2002 AKL (all-keys-lost) case; security-sensitive decoding/key-file details are
intentionally not expanded
- Source: [XT-013](https://blog.xhorsetool.com/2002-mercedes-s500-w220-akl-with-multi-prog-and-key-tool-plus-ok/), 2025-10-15
- Authorized-use note: AKL work requires the controls in `07_Authorized_Key_Immobilizer_Work/README.md`.
## Land Rover / Jaguar
### Land Rover/Jaguar L322 BCM + smart key
- Access path: bench BCM repair, plus separate key programming
- Tools: Xhorse Multi-PROG (bench BCM repair, per source); Autel IM508 (separate new-key step)
- Source: [OBD-045](https://blog.obdii365.com/2026/08/20/land-rover-jaguar-smart-key-not-detected-solution/), 2026-08-20
## Not-yet-body-extracted module topics (indexed only, listed for topic tracking)
The following module topics are known from titles only and must not be treated as complete
procedures until body-extracted: Ford BCM R5F64524, Volvo SID807EVO ECM, Hyundai/Kia SIM2K-241/242/341,
Chrysler/Dodge WIN module, Chrysler/Jeep/Dodge BCM, Mercedes AAM module, VW/Bentley KESSY module,
Jeep/Dodge RFHUB, Nissan HFM RH850 R7F701019, VW Golf 7 airbag (SPC560P50L3), Renault HFM
(D70F3633), Volvo CEM (TB28F400), Fiat IAW 10GF ECU, Land Rover RFA (MC9S12XEQ384), Audi Bosch
MED9.1 ECU, Mitsubishi cluster S6J32LEL. See `UNIFIED_SOURCE_MANIFEST.csv` for each record's
source ID and URL.
## Related documents
- `13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md` — chip-level detail for the modules above
- `13_Research_Expansion/MULTIPROG_ERROR_CODE_CATALOG.md` — error codes referenced above
- `07_Authorized_Key_Immobilizer_Work/README.md` — required controls for any key/immobilizer work referenced above
- `13_Research_Expansion/UNIFIED_SOURCE_MANIFEST.md` / `.csv` — full source register
13_Research_Expansion/MULTIPROG_ERROR_CODE_CATALOG.md
+101
View File
@@ -0,0 +1,101 @@
# Multi-PROG Error Code Catalog (Article-Derived)
Centralized register of Multi-PROG hardware/software/firmware error codes and named error
conditions found in the `13_Research_Expansion/OBDII365/` and `13_Research_Expansion/XhorseTool/`
article imports. This catalog is separate from [`COMMON_ERRORS.md`](COMMON_ERRORS.md), which covers
this kit's own JavaScript/script-level errors — this file covers Multi-PROG **device/host** error
codes reported in third-party articles.
## Evidence status
Every entry below is `COMMUNITY/VENDOR REFERENCE` sourced from a single blog article (per
`13_Research_Expansion/UNIFIED_SOURCE_MANIFEST.csv`). None of these codes, causes, or remedies are
confirmed against this repository's own installed-host testing or the supplied Multi-PROG manuals.
Do not treat a single article's remedy as a guaranteed fix — it is the reporting source's own
troubleshooting narrative for one case.
Per the trusted-source decision, this catalog does not invent additional causes, additional
remedies, or generalize a device-specific fix to other devices. Where the source did not state a
detail, this catalog uses `SOURCE VALUE UNCLEAR`.
## Communication / bench-execution failures
| Code | Reported message/context | Device | Software version | Reported cause | Reported remedy | Source |
| --- | --- | --- | --- | --- | --- | --- |
| `040510C` | "Failed to Execute VPA" | BMW MEVD17.2.4 N20 ECU | Multi-PROG V1.4.4.0 | SOURCE VALUE UNCLEAR (article frames it as a general communication/execution failure, does not state a root cause) | Update Multi-PROG software and database to latest, retry connection, then escalate with a diagnostic log if it persists | [XT-001](https://blog.xhorsetool.com/how-to-fix-xhorse-multi-prog-failed-to-execute-vpa-error-040510c/), 2026-09-21, `COMMUNITY/VENDOR REFERENCE` |
| `FFFF000C` | "Server Calculation Error" | VAG SID10.4 ECU | SOURCE VALUE UNCLEAR | Attributed to network/server-side calculation failure | Check stable network connection, check Xhorse server status, run Test Function command 18, escalate to vendor support if unresolved | [XT-023](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-server-calculation-error-ffff000c/), 2025-05-16, `COMMUNITY/VENDOR REFERENCE` |
| `Error Code 1 / Error Address 2` | Named as a paired code/address value during a software update | Multi-PROG update system | SOURCE VALUE UNCLEAR | SOURCE VALUE UNCLEAR | SOURCE VALUE UNCLEAR — article title only, not body-extracted | [XT-055](https://blog.xhorsetool.com/xhorse-multi-prog-error-code-1-error-address-2-solution/), 2024-01-26, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`) |
## Firmware / update / authentication failures
| Code | Reported message/context | Device | Software/firmware version | Reported cause | Reported remedy | Source |
| --- | --- | --- | --- | --- | --- | --- |
| `41330004` | "Update Firmware Jump Recovery" error | Multi-PROG firmware | Firmware 1.36 → 1.45 (reported jump) | SOURCE VALUE UNCLEAR | Hold the Reset button during power-on, then retry the forced firmware update | [XT-007](https://blog.xhorsetool.com/how-to-solve-multi-prog-update-firmware-jump-recovery-error-41330004/), 2025-12-12, `COMMUNITY/VENDOR REFERENCE` |
| `0404001F` | "Hardware Initialization Fails" | Multi-PROG hardware | SOURCE VALUE UNCLEAR | SOURCE VALUE UNCLEAR | SOURCE VALUE UNCLEAR — article title only, not body-extracted | [XT-035](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-error-code-0404001f-hardware-initialization-fails/), 2025-01-27, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`) |
| (unlabeled) | "Device Authentication Failed" during firmware update | Multi-PROG firmware | SOURCE VALUE UNCLEAR | SOURCE VALUE UNCLEAR | SOURCE VALUE UNCLEAR — article title only, not body-extracted | [XT-029](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-update-firmware-error-device-authentication-failed/), 2025-03-21, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`) |
| (unlabeled) | "Stop Upgrading Problem" | Multi-PROG firmware | SOURCE VALUE UNCLEAR | SOURCE VALUE UNCLEAR | SOURCE VALUE UNCLEAR — article title only, not body-extracted | [XT-031](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-stop-upgrading-problem/), 2025-03-07, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`) |
## Chip / MCU adapter configuration failures
| Code | Reported message/context | Device | Adapter | Reported cause | Reported remedy | Source |
| --- | --- | --- | --- | --- | --- | --- |
| `88030201` | "Chip Configuration Failed" | BMW FRM3 | Multi-Prog MCU Adapter | Attributed to insufficient/incomplete RESET-line soldering | Re-inspect and re-solder the RESET point on the module before retrying | [XT-009](https://blog.xhorsetool.com/how-to-fix-xhorse-multi-prog-bmw-frm3-chip-configuration-failed/), 2025-11-24, `COMMUNITY/VENDOR REFERENCE` |
| (unlabeled) | "Chip Configuration Failed" | VAG MQB RH850 (R7F701407) | MQB RH850/V850 adapter | SOURCE VALUE UNCLEAR | Source warns specifically against extending/lengthening the adapter harness | [XT-043](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-mqb-rh850-chip-configuration-failed-problem/), 2024-09-28, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`) |
## PIN / adapter detection failures
| Code | Reported message/context | Device | Adapter | Reported cause | Reported remedy | Source |
| --- | --- | --- | --- | --- | --- | --- |
| (unlabeled) | "PIN Connection Detect Failed" | Audi BCM2 | BCM2 Adapter V2 (with XDNP100/XDNP101) | Attributed to adapter/module compatibility | Source recommends adapter modification | [XT-006](https://blog.xhorsetool.com/how-to-solve-xhorse-audi-bcm2-adapter-v2-pin-connection-detect-failed/), 2025-12-29, `COMMUNITY/VENDOR REFERENCE` |
| (unlabeled) | "PIN is Abnormal" | Audi BCM2 (module marking 3381) | BCM2 Adapter V2 (with XDNP100/XDNP101) | SOURCE VALUE UNCLEAR | Source reports a V2 adapter modification as the fix, on a module that a V1 adapter had previously worked on | [XT-010](https://blog.xhorsetool.com/how-to-solve-xhorse-audi-bcm2-adapter-v2-pin-is-abnormal/), 2025-11-19, `COMMUNITY/VENDOR REFERENCE` |
## EEPROM/chip power and erase failures
| Code | Reported message/context | Device | Adapter | Reported cause | Reported remedy | Source |
| --- | --- | --- | --- | --- | --- | --- |
| `13050102` | Read failure | Audi J518 1L59W/5L40K 0115 | VVDI Prog / Multi-PROG | SOURCE VALUE UNCLEAR | Set VDD to 4-5V and run a DB44/MCU self-check before retrying | [XT-019](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-read-audi-j518-2010-failure/), 2025-06-25, `COMMUNITY/VENDOR REFERENCE` |
| `13050001` | Erase failure on M35080 | M35080 EEPROM | XDNP24GL D80/35080 Adapter | SOURCE VALUE UNCLEAR | Source-described VPP adjustment troubleshooting | [XT-044](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-erase-m35080-error-code-13050001/), 2024-08-13, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`) |
| (unlabeled) | "Chip Power Configuration Failed" | VW ME7.x ECU | bench connection | SOURCE VALUE UNCLEAR | 12V ECU power supply troubleshooting claim | [XT-021](https://blog.xhorsetool.com/how-to-solve-multi-prog-me7-1-chip-power-configuration-failed/), 2025-06-04, `COMMUNITY/VENDOR REFERENCE` |
| (unlabeled) | "Number of Times is 0" (read-attempt/authorization counter) | BMW MSV80 ECU | bench | SOURCE VALUE UNCLEAR | SOURCE VALUE UNCLEAR — article title only, not body-extracted | [XT-028](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-read-bmw-msv80-number-of-times-is-0/), 2025-04-02, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`) |
| (unlabeled) | "Write BMW FEM BDC Chip Data Failure" | BMW FEM/BDC 95128 | SOURCE VALUE UNCLEAR | SOURCE VALUE UNCLEAR | SOURCE VALUE UNCLEAR — article title only, not body-extracted | [XT-027](https://blog.xhorsetool.com/solved-xhorse-multi-prog-write-bmw-fem-bdc-chip-data-failure/), 2025-04-09, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`) |
## Server / authorization / usage-count failures
| Code | Reported message/context | Device | Reported cause | Reported remedy | Source |
| --- | --- | --- | --- | --- | --- |
| (unlabeled) | "Remaining Usage of the Device Error" | Multi-PROG device authorization | Attributed to reaching a usage threshold requiring re-synchronization | Update Online > Authorization management sync | [XT-024](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-remaining-usage-of-the-device-error/), 2025-04-25, `COMMUNITY/VENDOR REFERENCE` |
## Driver / connection failures
| Code | Reported message/context | Device | Reported remedy | Source |
| --- | --- | --- | --- | --- |
| (unlabeled) | "Disconnected Problem" | Multi-PROG USB driver | Source distinguishes Windows 10 automatic driver installation from Windows 7 manual installation | [XT-056](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-disconnected-problem/), 2024-01-12, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`) |
| (unlabeled) | "Driver Not Working" | Multi-PROG USB driver | SOURCE VALUE UNCLEAR — article title only, not body-extracted | [XT-046](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-driver-not-working/), 2024-06-07, `COMMUNITY/VENDOR REFERENCE` (`INDEXED_ONLY`) |
| (unlabeled) | "WiFi Module Not Inserted" | Multi-PROG host / USB WiFi adapter | Insert the USB WiFi adapter, then power on to activate WiFi | [XT-022](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-wifi-module-not-inserted/), 2025-05-19, `COMMUNITY/VENDOR REFERENCE` |
| (unlabeled) | "Read and Write Button Grey Out" | Multi-PROG host UI | Source reports the Connect button must be used before Read/Write after a software update | [XT-020](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-read-and-write-button-grey-out/), 2025-06-20, `COMMUNITY/VENDOR REFERENCE` |
## Categories referenced by title only (not yet body-extracted)
These titles name a Multi-PROG error/fault condition but were not body-extracted (`INDEXED_ONLY` in
the unified manifest); they are listed here only so the topic is not lost, per instruction 15/`SOURCE
VALUE UNCLEAR` handling — do not treat the title as a documented code, cause, or remedy:
- "Xhorse Multi Prog Land rover RFA Chip Crack Failed Solution" (`OBD-021`)
- "OBDSTAR DC706 Multi Prog Failed to Read MED9.1 CAN BUS?" (`OBD-022`)
- "Xhorse Multi Prog Failed to Read Motorola MC68HC05X32 1D69J" (`XT-037`)
## How this catalog differs from `COMMON_ERRORS.md`
`COMMON_ERRORS.md` documents this kit's own script/JS-level error conditions (buffer/offset/hex/BCD
errors, host API verification). This file documents third-party-reported Multi-PROG **device**
error codes. Neither file supersedes the other; cross-link when a script practice exists to detect
or guard against one of the conditions above (e.g. a read-before-write or dual-read check that would
have caught a reported failure).
## Related documents
- `13_Research_Expansion/UNIFIED_SOURCE_MANIFEST.md` / `.csv` — full source register
- `13_Research_Expansion/OPERATIONAL_PRACTICES.md` — reusable troubleshooting practices referenced above (self-check, VDD/VPP configuration, driver recovery, authorization sync)
- `13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md` — device-specific detail for the MCU/EEPROM entries above
- `07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md` — adapter identity referenced above (BCM2 Adapter V2, XDNP series, MQB RH850/V850 adapter)
- `COMMON_ERRORS.md` — this kit's own script-level error catalog
13_Research_Expansion/MULTIPROG_SCRIPT_PATTERNS.md
+11
View File
@@ -83,3 +83,14 @@ See `templates/multiprog_safe_template.mjs`.
```js
// HOST_ADD_FUNCTION_BUTTON("Inspect", inspectCurrentBuffer);
```
## Article-derived script-development context
`COMMUNITY/VENDOR REFERENCE` — a single indexed-only source article ("How to Make First Script
with Xhorse Multi-Prog", [XT-048](https://blog.xhorsetool.com/how-to-make-first-script-with-xhorse-multi-prog/),
2024-04-08) names that Multi-PROG's JavaScript scripting can be authored as either a free script or
a device-bound script. The article was not body-extracted, so no API names, UI steps, or example
code from it are reproduced here — see `13_Research_Expansion/UNIFIED_SOURCE_MANIFEST.csv` record
`XT-048` for the source URL. Do not treat this title as documentation of the exact scripting
workflow; the patterns above remain this kit's own independently authored, placeholder-only style
guide.
13_Research_Expansion/OBDII365/IMPORT_REPORT.md
+15 -1
View File
@@ -41,6 +41,20 @@ The search corpus shows many device families and examples, such as BCMs, ECUs, a
- `raw/TAG_ARCHIVE_2026-09-22.md`
- `raw/`
## Integration into the repository (this pass)
The 15 records with a `raw/OBD-###-*.md` body extraction (`OBD-020`, `OBD-029`, `OBD-034`, `OBD-035`,
`OBD-045`–`OBD-055`) were reconciled with the XhorseTool import under one register
(`13_Research_Expansion/UNIFIED_SOURCE_MANIFEST.md` / `.csv`) and cited into
`13_Research_Expansion/MODULE_CASE_STUDIES.md`, `MCU_EEPROM_FLASH_DEVICE_REFERENCE.md`,
`OPERATIONAL_PRACTICES.md`, and `07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md`
(GODIAG GT107/GT107+/G-V cable, VH24/VH29/VH30/VH31, MQB solder-free/RH850/V850 adapters). The
remaining 40 `INDEXED_ONLY` records (titles/URLs/dates only, including all non-Multi-PROG comparison
articles such as Launch PROG5, Thinkcar J2534, and motorcycle key programmers) were preserved in the
manifest as topic references and were not promoted to procedures.
## Next recommended phase
If the user wants a deeper import, the next phase should be to pull raw article bodies from the article URLs, save them under `raw/`, and classify each by device family, access path, and evidence status before any cross-linking into workflow docs.
The remaining 40 `INDEXED_ONLY` OBDII365 records and 35 `INDEXED_ONLY` XhorseTool records are the
next candidates for body extraction into `raw/` (OBDII365) or `ARTICLE_FACTS.csv` (XhorseTool),
followed by another manifest reconciliation pass.
13_Research_Expansion/OPERATIONAL_PRACTICES.md
+164
View File
@@ -0,0 +1,164 @@
# Operational Practices (Article-Derived)
Reusable, tool/adapter-agnostic operational practices extracted from the `OBDII365`/`XhorseTool`
article imports. Each practice below stays scoped to what its source(s) actually describe — a
single device-specific report is not generalized into universal guidance (per the trusted-source
decision's prohibition on generalizing device-specific instructions).
## Evidence status
All practices are `COMMUNITY/VENDOR REFERENCE`. They describe what named sources report doing, not
verified Multi-PROG host behavior. Where a practice is followed in this repository's own workflows,
it is cross-linked below rather than duplicated.
## Software / firmware / database update practices
### Software update as a first troubleshooting step
- Purpose: rule out a known-fixed bug before deeper hardware troubleshooting.
- Source practice: on a VPA execution failure (error `040510C`), the source's first remedy was
updating Multi-PROG software and the device database to the latest version before retrying.
- Source: [XT-001](https://blog.xhorsetool.com/how-to-fix-xhorse-multi-prog-failed-to-execute-vpa-error-040510c/), 2026-09-21
- Limitations: does not establish that every communication failure is a software issue.
### Firmware jump-recovery via Reset-during-power-on
- Purpose: recover from an interrupted or failed firmware update.
- Source practice: hold the Reset button during power-on, then retry the forced firmware update
(reported firmware jump 1.36 → 1.45, error `41330004`).
- Source: [XT-007](https://blog.xhorsetool.com/how-to-solve-multi-prog-update-firmware-jump-recovery-error-41330004/), 2025-12-12
- Limitations: single reported case; does not establish this recovers every firmware failure mode.
### Database/software version tracking (historical claims)
- Reported historical version markers, useful only as a timeline reference, not a current-version
claim:
- Software 1.0.9.0 / Firmware 1.1.4 / Database V4, reported 2023-12-11 ([OBD-035](https://blog.obdii365.com/2023/12/11/download-and-install-xhorse-multi-prog-software-driver/))
- Software 1.1.2.0 / Database V11, reported 2024-02-27/2024-02-28 ([OBD-034](https://blog.obdii365.com/2024/02/27/xhorse-multi-prog-update-vag-mqb-rh850-v850-dashboard/); [XT-053](https://blog.xhorsetool.com/xhorse-multi-prog-v1-1-2-0-update-mqb-d70f3423-d70f3426/))
- Software V1.2.7.0 / V1.2.6.0, reported October 2024 ([XT-041](https://blog.xhorsetool.com/xhorse-multi-prog-software-update-v1-2-7-0-v1-2-6-0/))
- Software 4.0 or later required for offline mode, reported 2024-11-25 ([XT-036](https://blog.xhorsetool.com/how-to-use-xhorse-multi-prog-in-offline-mode/))
- Database V51, reported 2025-02-08 ([XT-034](https://blog.xhorsetool.com/xhorse-multi-prog-database-update-to-v51/))
- Multi-PROG database V87 reported for the BDC03 key-copy feature, 2025-12-05 ([XT-008](https://blog.xhorsetool.com/xhorse-multi-prog-update-bdc3-key-copy-function/))
- Limitations: use the installed product's own update mechanism and current vendor documentation to
establish the current version; do not treat these historical numbers as the current state.
## Account / authorization / licensing practices
### Xhorse account binding between Multi-PROG and VVDI2
- Purpose: allow a single Xhorse account to associate Multi-PROG and VVDI2 licenses (e.g. for
MQB48/NEC35XX-related license association).
- Source practice: bind via the Xhorse App / Update Online, with network troubleshooting steps if
binding fails.
- Source: [XT-016](https://blog.xhorsetool.com/how-to-bind-multi-prog-and-vvdi2-by-xhorse-account/), 2025-08-09
### Authorization/usage-count synchronization
- Purpose: resolve a "Remaining Usage of the Device" error.
- Source practice: Update Online > Authorization management, to synchronize after a usage
threshold is reached.
- Source: [XT-024](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-remaining-usage-of-the-device-error/), 2025-04-25
### BMW G BDC2 authorization license precondition
- Purpose: a specific BDC3/BCP key-copy feature reportedly requires a BMW G BDC2 authorization
license before the function is available.
- Source: [XT-014](https://blog.xhorsetool.com/xhorse-update-bmw-g-u-series-bdc3-bcp-key-copy-feature/), 2025-10-10; cross-reference [OBD-047](https://blog.obdii365.com/2025/10/09/xhorse-update-bmw-g-series-bdc3-bcp-key-cloning-function/), 2025-10-09
- Limitations: license/feature requirements are product-specific and change over time; do not
assume this applies to unrelated BMW key features.
## Network / server troubleshooting practices
### Server-calculation-error escalation path
- Purpose: address a server-side calculation error (`FFFF000C`) rather than assuming a local fault.
- Source practice, in order: check for a stable network connection, check Xhorse server status,
run Test Function command 18, then escalate to vendor support if unresolved.
- Source: [XT-023](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-server-calculation-error-ffff000c/), 2025-05-16
## Hardware / driver / connectivity practices
### WiFi setup sequence
- Purpose: bring up WiFi connectivity on the Multi-PROG host.
- Source practice: insert the USB WiFi adapter, then power on the device to activate WiFi; WiFi
passwords are reported as numeric-only in Settings > WiFi.
- Sources: [XT-022](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-wifi-module-not-inserted/), 2025-05-19 (module-not-inserted case); [XT-018](https://blog.xhorsetool.com/how-to-set-wifi-password-for-xhorse-multi-prog/), 2025-07-11 (numeric-password entry)
### USB driver installation differs by Windows version
- Purpose: resolve "Disconnected" / driver-not-recognized conditions.
- Source practice: Windows 10 is reported to install the USB driver automatically; Windows 7 is
reported to require manual driver installation.
- Source: [XT-056](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-disconnected-problem/), 2024-01-12 (`INDEXED_ONLY` — driver detail is title-level, not independently body-confirmed)
### Connect-before-Read/Write after a software update
- Purpose: resolve Read/Write buttons appearing greyed out.
- Source practice: use the Connect button before attempting Read/Write, specifically after a
software update.
- Source: [XT-020](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-read-and-write-button-grey-out/), 2025-06-20
## Chip/adapter power-configuration practices
### VDD configuration and equipment self-check on chip-power failures
- Purpose: address a chip-power/read failure (error `13050102`) on an Audi J518 module.
- Source practice: set VDD to 4-5V, and run a DB44/MCU self-check before retrying the read.
- Source: [XT-019](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-read-audi-j518-2010-failure/), 2025-06-25
- Limitations: this VDD value is reported for this specific module; do not apply 4-5V as a general
VDD setting for unrelated chips without independent confirmation.
### 12V external ECU power on chip-power-configuration failures
- Purpose: address "Chip Power Configuration Failed" on a VW ME7.x bench setup.
- Source practice: verify/supply a stable 12V external ECU power source.
- Source: [XT-021](https://blog.xhorsetool.com/how-to-solve-multi-prog-me7-1-chip-power-configuration-failed/), 2025-06-04
### VPP adjustment on EEPROM erase failures
- Purpose: address an M35080 erase failure (error `13050001`).
- Source practice: source-described VPP adjustment troubleshooting on the XDNP24GL D80/35080
adapter.
- Source: [XT-044](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-erase-m35080-error-code-13050001/), 2024-08-13 (`INDEXED_ONLY`)
### Avoid extending/lengthening adapter harnesses
- Purpose: avoid a "Chip Configuration Failed" condition on VAG MQB RH850 (R7F701407) reads.
- Source practice: the source explicitly warns against extending or lengthening the MQB RH850/V850
adapter harness.
- Source: [XT-043](https://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-mqb-rh850-chip-configuration-failed-problem/), 2024-09-28 (`INDEXED_ONLY`)
- This generalizes reasonably well as a bench-discipline reminder (avoid unsupported harness
extensions), consistent with this repository's existing bench-workflow caution in
`04_Workflows/BENCH_AND_BOOT_READING_WORKFLOW.md`, but the specific adapter/module pairing above
remains the only verified instance.
## Checksum practices
### Checksum availability is per supported device-library entry
- Purpose: understand when the Multi-PROG checksum function applies.
- Source practice: checksum availability is shown per supported device-library entry (a green "C"
indicator), and used through the Write/Verify UI; the source explicitly states real-vehicle
validation of the checksum result remains unconfirmed in its own report.
- Source: [XT-005](https://blog.xhorsetool.com/how-to-calculate-checksum-for-xhorse-multi-prog/), 2026-01-23
- See `COMMON_CHECKSUMS.md` for this kit's own offline checksum-algorithm reference (CRC/SHA/MD5),
which remains a separate, tool-agnostic concept from the Multi-PROG device-library checksum
function described here.
## General bench-cloning education (broad context only)
- A general community "beginner's guide" source lists OBD, bench, boot, and BDM as the four
broad ECU/TCU access categories, and names a long list of third-party programmers alongside
Xhorse Multi-PROG (KESS3, BitBox, Flex, PCMFlash, CG FC200, I/O Terminal, Autotuner, OBDSTAR
DC706, Launch X431, KESS V2, KTAG, MPPS, FoxFlash, KT200, KTMFlash, FGTech V54). This is general
community education, not Multi-PROG-specific support documentation, and is recorded here only for
topic-tracking.
- Source: [OBD-055](https://blog.obdii365.com/2024/04/09/a-beginners-guide-to-ecu-cloning-and-essential-tools/), 2024-04-09
## Related documents
- `13_Research_Expansion/MULTIPROG_ERROR_CODE_CATALOG.md` — error codes these practices address
- `13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md`, `MODULE_CASE_STUDIES.md` — device context for the chip/adapter practices above
- `04_Workflows/BENCH_AND_BOOT_READING_WORKFLOW.md` — this repository's own bench/boot discipline
- `13_Research_Expansion/UNIFIED_SOURCE_MANIFEST.md` / `.csv` — full source register
13_Research_Expansion/UNIFIED_SOURCE_MANIFEST.csv
+114
View File
@@ -0,0 +1,114 @@
source_id,source_site,article_title,canonical_url,publication_date,discovery_source,device_family,access_path,tools_adapters_cables,version_info,extraction_status,processing_status,imported_target_files,notes
OBD-001,obdii365,Xhorse Multi Prog Clone Ford BCM R5F64524 on Bench,http://blog.obdii365.com/2026/05/24/xhorse-multi-prog-clone-ford-bcm-r5f64524/,2026-05-24,search-results-page-1,Ford BCM / Renesas R5F64524,bench,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only; not treated as complete procedure
OBD-002,obdii365,Xhorse Multi Prog Conncetion Failure Repair Guide,http://blog.obdii365.com/2026/02/27/xhorse-multi-prog-conncetion-failure-repair-guide/,2026-02-27,search-results-page-1,generic module connection,troubleshooting / bench,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-003,obdii365,Xhorse Multi Prog Wiring Diagrams to VAG MQB49 5C 5D Keys,http://blog.obdii365.com/2026/02/25/xhorse-multi-prog-wiring-diagrams-to-vag-mqb49-5c-5d-keys/,2026-02-25,search-results-page-1,VAG MQB49 5C/5D key,adapter-assisted direct access,,,INDEXED_ONLY,INDEXED_ONLY,,SOURCE DIAGRAM REQUIRED for wiring specifics; indexed title only
OBD-004,obdii365,Clone Volvo SID807EVO ECM by AutoTuner Multi Prog or Flex?,http://blog.obdii365.com/2025/12/16/clone-volvo-sid807evo-ecm-by-autotuner-multi-prog-or-flex/,2025-12-16,search-results-page-1,Volvo SID807EVO ECM,module access not specified,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-005,obdii365,Clone Audi BCM2 Module with Xhorse Multi Prog or Key Tool Plus?,http://blog.obdii365.com/2025/10/19/clone-audi-bcm2-module-with-xhorse-multi-prog-or-key-tool-plus/,2025-10-19,search-results-page-1,Audi BCM2,module access not specified,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-006,obdii365,Repair Porsche Cayenne 12V Lithium Battery with Xhorse Multi Prog,http://blog.obdii365.com/2025/08/24/repair-porsche-cayenne-12v-lithium-battery-with-xhorse-multi-prog/,2025-08-24,search-results-page-1,Porsche/Audi/Lamborghini 12V lithium battery,module service not specified,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-007,obdii365,Xhorse Multi Prog Clone Audi Encrypted BCM2 Module with New BCM2 Adapter,http://blog.obdii365.com/2025/08/08/xhorse-multi-prog-clone-audi-encrypted-bcm2-module/,2025-08-08,search-results-page-1,Audi BCM2 / D70F3634,adapter-assisted direct access,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-008,obdii365,Xhorse Multi Prog Hyundai SIM2K-241 IMMO OFF (without Other Tools),http://blog.obdii365.com/2025/04/17/xhorse-multi-prog-hyundai-sim2k-241-immo-off/,2025-04-17,search-results-page-1,Hyundai/Kia SIM2K-241 ECU,boot,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-009,obdii365,Xhorse Multi Prog Clone Hyundai Kia SIM2K-242 ECU,http://blog.obdii365.com/2025/03/31/xhorse-multi-prog-clone-hyundai-kia-sim2k-242-ecu/,2025-03-31,search-results-page-1,Hyundai/Kia SIM2K-242 ECU,module access not specified,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-010,obdii365,Xhorse Multi Prog Read GM Delco E39 E78 E98 etc ECM 16-digit Shadow Password,http://blog.obdii365.com/2025/03/20/xhorse-multi-prog-read-gm-delco-e39-e78-e98-etc-ecm-16-digit-shadow-password/,2025-03-20,search-results-page-1,GM Delco E-series ECM,bench / boot,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-011,obdii365,How to Clone Mercedes AAM Module with Xhorse Multi Prog?,http://blog.obdii365.com/2025/03/18/how-to-clone-mercedes-aam-module-with-xhorse-multi-prog/,2025-03-18,search-results-page-1,Mercedes AAM,module access not specified,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-012,obdii365,Program and Write VIN to Hyundai Used SIM2K-341 ECU by Xhorse Multi Prog,http://blog.obdii365.com/2025/03/14/write-vin-to-hyundai-sim2k-341-used-ecu-by-xhorse-multi-prog/,2025-03-14,search-results-page-1,Hyundai/Kia SIM2K-341 ECU,module service not specified,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-013,obdii365,How to Clone and Program Chrysler Dodge WIN Module with Autel & Multi Prog?,http://blog.obdii365.com/2025/03/13/clone-chrysler-dodge-win-module-with-autel-and-multi-prog/,2025-03-13,search-results-page-1,Chrysler/Dodge WIN,module access not specified,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-014,obdii365,Xhorse Multi Prog or Autel to Read BMW CAS3 Immobilizer?,http://blog.obdii365.com/2025/03/13/xhorse-multi-prog-or-autel-to-read-bmw-cas3-immobilizer/,2025-03-13,search-results-page-1,BMW/MINI CAS3,module access not specified,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-015,obdii365,CG100 vs Xhorse Multi Prog to Repair/Clone VW Golf 7 Airbag,http://blog.obdii365.com/2025/03/02/cg100-vs-xhorse-multi-prog-to-repair-vw-golf-7-airbag/,2025-03-02,search-results-page-1,VW Golf 7 airbag / SPC560P50L3,module access not specified,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-016,obdii365,OBDSTAR DC706 or Xhorse Multi Prog to Read Jeep RFHUB Module?,http://blog.obdii365.com/2025/02/07/obdstar-dc706-or-xhorse-multi-prog-to-read-jeep-rfhub-module/,2025-02-07,page-2,Jeep/Dodge RFHUB / MC9S12XEG384,direct MCU access,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-017,obdii365,Xhorse Multi Prog Read 2021 Nissan Sentra HFM RH850 R7F701019,http://blog.obdii365.com/2025/02/04/xhorse-multi-prog-read-2021-nissan-sentra-immo-rh850-r7f701019/,2025-02-04,page-2,Nissan HFM / RH850 R7F701019,adapter-assisted direct access,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-018,obdii365,How to Calculate VW Passat MQB ELV CS Code with Xhorse Multi Prog and VVDI2?,http://blog.obdii365.com/2025/01/09/calculate-vw-passat-mqb-elv-cs-code-with-xhorse-multi-prog-and-vvdi2/,2025-01-09,page-2,VW MQB ELV,adapter-assisted direct access,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-019,obdii365,Clone VW Bentley Siemens VDO KESSY 2008- Module by Xhorse Multi Prog,http://blog.obdii365.com/2024/12/23/clone-vw-bentley-siemens-vdo-kessy-by-xhorse-multi-prog/,2024-12-23,page-2,VW/Bentley KESSY,module access not specified,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-020,obdii365,How to Connect Xhorse Multi Prog with Godiag GT107 or GPT Cable?,http://blog.obdii365.com/2024/11/07/how-to-connect-xhorse-multi-prog-with-godiag-gt107-or-gpt-cable/,2024-11-07,page-2,VAG DQ200/DQ250 TCU and engine ECUs,bench / boot,GODIAG GT107/GT107+; GODIAG GPT bench/boot adapter; GODIAG G-V ECU cable converter,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md,No pinout reproduced; SOURCE DIAGRAM REQUIRED
OBD-021,obdii365,Xhorse Multi Prog Land rover RFA Chip Crack Failed Solution,http://blog.obdii365.com/2024/10/23/xhorse-multi-prog-land-rover-rfa-chip-crack-failed-solution/,2024-10-23,page-2,Land Rover RFA / MC9S12XEQ384,direct MCU access,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-022,obdii365,OBDSTAR DC706 Multi Prog Failed to Read MED9.1 CAN BUS?,http://blog.obdii365.com/2024/10/08/obdstar-dc706-multi-prog-failed-to-read-med9-1-can-bus/,2024-10-08,page-2,Audi Bosch MED9.1 ECU,CAN communication,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-023,obdii365,Xhorse Multi Prog Read Fiat IAW 10GF ECU Success,http://blog.obdii365.com/2024/09/26/xhorse-multi-prog-read-fiat-iaw-10gf-ecu/,2024-09-26,page-2,Fiat IAW 10GF ECU,module access not specified,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-024,obdii365,Xhorse Multi Prog MQB RH850 'Chip Configuration Failed' Solution,http://blog.obdii365.com/2024/09/25/xhorse-multi-prog-mqb-rh850-chip-configuration-failed-solution/,2024-09-25,page-2,VAG MQB RH850,direct module access,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-025,obdii365,Xhorse VVDI Prog vs Multi Prog to Read Volvo CEM TB28F400,http://blog.obdii365.com/2024/08/06/xhorse-vvdi-prog-vs-multi-prog-to-read-volvo-cem-tb28f400/,2024-08-06,page-2,Volvo CEM / TB28F400,external chip adapter,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-026,obdii365,How to Program VAG MQB RH850 Key with Xhorse Multi Prog and VVDI2,http://blog.obdii365.com/2024/07/25/program-vag-mqb-rh850-key-with-xhorse-multi-prog-and-vvdi2/,2024-07-25,page-2,VAG MQB RH850 cluster,adapter-assisted direct access,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-027,obdii365,Repair Audi 48V Lithium Battery by CG100X Multi Prog,http://blog.obdii365.com/2024/07/24/repair-audi-48v-lithium-battery-by-cg100x-multi-prog/,2024-07-24,page-2,Audi 48V lithium battery,module service not specified,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-028,obdii365,How to Clone Chrysler Jeep Dodge BCM with Xhorse Multi Prog?,http://blog.obdii365.com/2024/07/03/clone-chrysler-jeep-dodge-bcm-with-xhorse-multi-prog/,2024-07-03,page-2,Chrysler/Jeep/Dodge BCM,module access not specified,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-029,obdii365,How to Use VH24 VH29 VH30 EEPROM Adapters with Xhorse Multi Prog?,http://blog.obdii365.com/2024/06/28/how-to-use-vh24-vh29-adapters-with-xhorse-multi-prog/,2024-06-28,page-2,external EEPROM and flash chips,external chip adapter,XDMP04GL VH24V01 (SOP44/TSOP48); XDMP05GL VH29V02 (EEPROM/flash); XDMP06GL VH30V02 (SOP44); XDMP07GL VH31V02 (TSOP48),,FACTS_AVAILABLE,PARTIALLY_IMPORTED,07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md,Adapter selection follows chip selection in software per source
OBD-030,obdii365,How to Repair BMW FRM3 with Xhorse Multi Prog (Automatically)?,http://blog.obdii365.com/2024/05/10/how-to-repair-bmw-frm3-with-xhorse-multi-prog-automatically/,2024-05-10,page-3,BMW FRM3,module service not specified,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-031,obdii365,CG FC200 vs Xhorse Multi Prog,http://blog.obdii365.com/2024/04/02/cg-fc200-vs-xhorse-multi-prog/,2024-04-02,page-3,generic programmer comparison,not applicable,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-032,obdii365,Read Renault HFM ISK & PIN with Xhorse Multi Prog and ECU Tool,http://blog.obdii365.com/2024/04/01/read-renault-hfm-isk-pin-with-xhorse-multi-prog-and-ecu-tool/,2024-04-01,page-3,Renault HFM / D70F3633,direct module access,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-033,obdii365,Xhorse Multi Prog Repair BMW CAS4 KM (Script Function),http://blog.obdii365.com/2024/02/28/xhorse-multi-prog-repair-bmw-cas4-km-script-function/,2024-02-28,page-3,BMW CAS4 / 5M48H,local script function,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-034,obdii365,Xhorse Multi Prog Update VAG MQB RH850/V850 Dashboard,http://blog.obdii365.com/2024/02/27/xhorse-multi-prog-update-vag-mqb-rh850-v850-dashboard/,2024-02-27,page-3,VAG MQB RH850/V850 dashboard processors,adapter-assisted direct access,MQB RH850/V850 cable; VVDI2 Full; VVDI Key Tool Plus,software 1.1.2.0; Database V11,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md,Historical version numbers only, not a current support matrix
OBD-035,obdii365,Download and Install Xhorse Multi Prog Software Driver,http://blog.obdii365.com/2023/12/11/download-and-install-xhorse-multi-prog-software-driver/,2023-12-11,page-3,Multi-PROG host software and USB connection,PC USB connection,USB Serial CDC driver,software 1.0.9.0; firmware 1.1.4; database V4,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/OPERATIONAL_PRACTICES.md,Historical version numbers only
OBD-036,obdii365,How to Modify Original MQB49 5C 5D Key ID with VVDI Key Tool Plus & MultiProg?,http://blog.obdii365.com/2026/03/30/modify-original-mqb49-5c-5d-key-id-with-vvdi-key-tool-plus/,2026-03-30,page-3,VAG MQB49 5C/5D key,adapter-assisted direct access,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-037,obdii365,Program 2023 Ducati Multistrada V4S Key with OBDSTAR iScan,http://blog.obdii365.com/2026/01/07/program-2023-ducati-multistrada-v4s-key-with-obdstar-iscan/,2026-01-07,page-3,Ducati Multistrada V4S,not a Multi-PROG procedure,,,INDEXED_ONLY,INDEXED_ONLY,,Not a Multi-PROG article
OBD-038,obdii365,Mitsubishi S6J32LEL Mileage Correction Pinout to MultiProg Orange5,http://blog.obdii365.com/2024/12/04/mitsubishi-s6j32lel-mileage-correction-pinout-to-multiprog-orange5/,2024-12-04,page-3,Mitsubishi cluster / S6J32LEL,direct MCU access,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-039,obdii365,Xhorse Multi-Prog vs VVDI Prog,http://blog.obdii365.com/2023/12/08/xhorse-multi-prog-vs-vvdi-prog/,2023-12-08,page-3,generic programmer comparison,not applicable,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
OBD-040,obdii365,How to Set up Thinkcar J2534 with OEM Software for Programming?,http://blog.obdii365.com/2026/09/01/how-to-set-up-thinkcar-j2534-with-oem-software/,2026-09-01,page-3,J2534 pass-through setup,not a Multi-PROG procedure,,,INDEXED_ONLY,INDEXED_ONLY,,Not a Multi-PROG article
OBD-041,obdii365,MTPro MOTOPro vs TMPro2 Motorcycle Key Programmer,http://blog.obdii365.com/2026/08/13/mtpro-motopro-vs-tmpro2-motorcycle-key-programmer/,2026-08-13,page-3,motorcycle key programmer comparison,not a Multi-PROG procedure,,,INDEXED_ONLY,INDEXED_ONLY,,Not a Multi-PROG article
OBD-042,obdii365,How to One-click Repair BMW FRM3 Module with CK-Prog?,http://blog.obdii365.com/2026/06/03/repair-bmw-frm3-module-with-ck-prog/,2026-06-03,page-3,BMW FRM3,not a Multi-PROG procedure,,,INDEXED_ONLY,INDEXED_ONLY,,Not a Multi-PROG article
OBD-043,obdii365,2026 Launch PROG5 vs Launch X-Prog3,http://blog.obdii365.com/2026/05/27/launch-prog5-vs-launch-x-prog3/,2026-05-27,page-3,programmer comparison,not a Multi-PROG procedure,,,INDEXED_ONLY,INDEXED_ONLY,,Not a Multi-PROG article
OBD-044,obdii365,CG FC200 vs OBDSTAR DC706 vs I/O Prog,http://blog.obdii365.com/2026/05/13/cg-fc200-vs-obdstar-dc706-vs-i-o-prog/,2026-05-13,page-3,programmer comparison,not a Multi-PROG procedure,,,INDEXED_ONLY,INDEXED_ONLY,,Not a Multi-PROG article
OBD-045,obdii365,Land Rover & Jaguar 'Smart Key Not Detected' Solution,http://blog.obdii365.com/2026/08/20/land-rover-jaguar-smart-key-not-detected-solution/,2026-08-20,tag-page-1,Land Rover/Jaguar L322 BCM and smart key,bench BCM repair plus separate key programming,Xhorse Multi-PROG; Autel IM508,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,
OBD-046,obdii365,Read Audi A3 AKL Micronas CDC3217G by Autel Xhorse Xprog or UPA,http://blog.obdii365.com/2026/01/13/read-audi-a3-akl-micronas-cdc3217g-by-autel-xhorse-xprog-or-upa/,2026-01-13,tag-page-1,Audi A3/Golf cluster Micronas CDC3217G/3297G and 24C32,direct cluster memory access,Xhorse Multi-PROG; VVDI Prog; Key Tool Plus; Autel; OBDSTAR G3; UPA; XPROG; SMOK JTAG,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,Source reports Multi-PROG among tools that did not read this cluster in the described case; XPROG/SMOK JTAG reported successful
OBD-047,obdii365,Xhorse Update BMW G Series BDC3 BCP Key Cloning Function,http://blog.obdii365.com/2025/10/09/xhorse-update-bmw-g-series-bdc3-bcp-key-cloning-function/,2025-10-09,tag-page-1,BMW G/U chassis BDC03/BCP key,read key data with programmer then companion key tool,VVDI Prog; Multi-PROG; VVDI2; VVDI Key Tool Plus; Key Tool MIDI; BMW G BDC2 authorization,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,Sensitive key procedure summarized only; not reproduced
OBD-048,obdii365,How to Connect Godiag 9 in 1 Gearbox Cable with Xhorse Autel Flex etc?,http://blog.obdii365.com/2025/09/19/connect-godiag-9-in-1-gearbox-cable-with-xhorse-autel-flex/,2025-09-19,tag-page-2,VAG DQ200/DQ250/DQ380/DQ381/DQ400E/DL382/DL501/VL300/VL381/V30 TCU,bench adapter connection,GODIAG 9-in-1 gearbox adapter; OBD2 bench adapter; Xhorse Multi-PROG; Autel G-BOX; Scanmatik 2 Pro; PCMFlash; Flex,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,
OBD-049,obdii365,Clean and Clone VW Skoda 5QF959655AT Airbag Module?,http://blog.obdii365.com/2025/02/12/clean-and-clone-vw-skoda-5qf959655at-airbag-module/,2025-02-12,tag-page-2,VW/Skoda SRS 5QF959655AT / Infineon TC234L 32F,MCU DFlash/PFlash read and write,OBDSTAR P50; Xhorse Multi-PROG,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md;13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md,Flash-protection/endurance statements retained as source claims only
OBD-050,obdii365,How to Tell if PSA MD1CS003 ECU is Locked or Not?,http://blog.obdii365.com/2024/12/03/how-to-tell-if-psa-md1cs003-ecu-is-locked-or-not/,2024-12-03,tag-page-2,PSA Bosch MD1CS003 ECU,bench,KESS3; Xhorse Multi-PROG; FoxFlash; FormulaFlash; CG FC200; OBDSTAR DC706; Launch ECU programmer; Hextag,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,Part-number-series TPROT heuristic is source-specific and not independently validated
OBD-051,obdii365,Xhorse MQB Adapters vs Yanhua ACDP MQB Adapters,http://blog.obdii365.com/2024/07/29/xhorse-mqb-adapters-vs-yanhua-acdp-mqb-adapters/,2024-07-29,tag-page-3,VAG MQB NEC35XX and RH850/V850 clusters,solder-free adapter or direct RH850 adapter,Xhorse MQB solder-free adapters; Xhorse RH850/V850 adapter; Yanhua ACDP Module 33; Yanhua ACDP Module 34,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md,
OBD-052,obdii365,Top 6 Tools for VAG MQB RH850 IMMO & Mileage,http://blog.obdii365.com/2024/07/23/top-6-tools-for-vag-mqb-rh850-immo-mileage/,2024-07-23,tag-page-3,VAG MQB RH850 5A/5C clusters,adapter-assisted direct access,VVDI Key Tool Plus; Xhorse Multi-PROG; Multi-PROG RH850/V850 adapter; Autel APB131; Yanhua Mini ACDP Module 34; CGDI CG100X; AVDI VN021/VN023; PolDiag MQB RH850,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,Community-reported function/processor list, not a validated compatibility matrix
OBD-053,obdii365,Recover GM Delco E98 E39 E39A ECMs with Shadow Password in Boot,http://blog.obdii365.com/2024/07/02/recover-gm-delco-e98-e39-e39a-ecms-with-shadow-password/,2024-07-02,tag-page-3,GM Delco E98/E39/E39A/E83/E84 ECM,boot recovery,I/O Terminal; OBDSTAR DC706/G3; Alientech KESS3; Xhorse Multi-PROG,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,Shadow password reported as per-module; sensitive recovery detail intentionally summarized
OBD-054,obdii365,VAG MQB RH850 Cluster 5A vs 5C,http://blog.obdii365.com/2024/06/12/vag-mqb-rh850-cluster-5a-vs-5c/,2024-06-12,tag-page-3,VAG MQB RH850 5A/5C clusters,cluster identification and adapter-assisted access,Xhorse Multi-PROG; CG100X; VVDI Prog; Key Tool Plus; Yanhua ACDP Module 34,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,EM/PCJ marking heuristic is source-specific, not a manufacturer standard
OBD-055,obdii365,A Beginner's Guide to ECU Cloning and Essential Tools,http://blog.obdii365.com/2024/04/09/a-beginners-guide-to-ecu-cloning-and-essential-tools/,2024-04-09,tag-page-3,generic ECU/TCU cloning,OBD / bench / boot / BDM as described by source,KESS3; BitBox; Flex; PCMFlash; CG FC200; I/O Terminal; Autotuner; OBDSTAR DC706; Launch X431; Xhorse Multi-PROG; KESS V2; KTAG; MPPS; FoxFlash; KT200; KTMFlash; FGTech V54,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/OPERATIONAL_PRACTICES.md,General community education article, not exact Multi-PROG support documentation
XT-001,xhorsetool,How to Fix Xhorse Multi-Prog Failed to Execute VPA Error 040510C?,http://blog.xhorsetool.com/how-to-fix-xhorse-multi-prog-failed-to-execute-vpa-error-040510c/,2026-09-21,category-page-1,BMW MEVD17.2.4 N20 ECU,ECU communication troubleshooting,Multi-PROG V1.4.4.0; latest database; diagnostic log,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MULTIPROG_ERROR_CODE_CATALOG.md,Error code 040510C
XT-002,xhorsetool,Xhorse Multi Prog BMW BDC2 BDC3 LCD Encrypted Key Pinouts,http://blog.xhorsetool.com/xhorse-multi-prog-bmw-bdc2-bdc3-lcd-encrypted-key-pinouts/,2026-02-27,category-page-1,BMW BDC2/BDC3/LCD keys,MCU adapter / key data access,Multi-PROG; Key Tool MIDI; Key Tool Plus; modified MCU adapter,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,Sensitive key procedure summarized only; not reproduced
XT-003,xhorsetool,Xhorse Multi Prog MCU Adapter Modification Method,http://blog.xhorsetool.com/xhorse-multi-prog-mcu-adapter-modification-method/,2026-02-25,category-page-1,9S12HZ512 MCU,MCU adapter,Multi-Prog MCU adapter; added GND short/long wires,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md,Adapter modification reported as enabling a successful read
XT-004,xhorsetool,Xhorse Update BMW BDC2 BDC3 BCP Encrypted Key Cloning,http://blog.xhorsetool.com/xhorse-update-bmw-bdc2-bdc3-bcp-encrypted-key-cloning/,2026-02-13,category-page-1,BMW BDC2 BDC3 BCP keys,key data read/write,Multi-PROG; VVDI Key Tool Plus; VVDI BMW dedicated adapter,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,Sensitive key procedure summarized only; not reproduced
XT-005,xhorsetool,How to Calculate Checksum for Xhorse Multi Prog?,http://blog.xhorsetool.com/how-to-calculate-checksum-for-xhorse-multi-prog/,2026-01-23,category-page-1,supported ECU EEPROM/flash entries,software checksum function,Multi-PROG device library; green C indicator; Write/Verify UI,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/COMMON_CHECKSUMS.md,Checksum availability shown per supported entry; real-vehicle validation unconfirmed
XT-006,xhorsetool,How to Solve Xhorse Audi BCM2 Adapter V2 PIN Connection Detect Failed?,http://blog.xhorsetool.com/how-to-solve-xhorse-audi-bcm2-adapter-v2-pin-connection-detect-failed/,2025-12-29,category-page-1,Audi BCM2,adapter troubleshooting,BCM2 Adapter V2; XDNP100; XDNP101; Multi-PROG,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MULTIPROG_ERROR_CODE_CATALOG.md;07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md,PIN detection failure attributed to adapter compatibility
XT-007,xhorsetool,How to Solve Multi Prog Update Firmware Jump Recovery Error 41330004?,http://blog.xhorsetool.com/how-to-solve-multi-prog-update-firmware-jump-recovery-error-41330004/,2025-12-12,category-page-1,Multi-PROG firmware,firmware recovery,firmware 1.36 to 1.45; reset button,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MULTIPROG_ERROR_CODE_CATALOG.md,Error code 41330004
XT-008,xhorsetool,Xhorse Multi Prog Update BDC3 Key Copy Function,http://blog.xhorsetool.com/xhorse-multi-prog-update-bdc3-key-copy-function/,2025-12-05,category-page-1,BMW BDC03 keys,key data access,Multi-PROG database V87; VVDI2; Key Tool Plus,database V87,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,Vendor claim of direct original-key read/write with no data conversion
XT-009,xhorsetool,How to Fix Xhorse Multi Prog BMW FRM3 Chip Configuration Failed?,http://blog.xhorsetool.com/how-to-fix-xhorse-multi-prog-bmw-frm3-chip-configuration-failed/,2025-11-24,category-page-1,BMW FRM3,MCU adapter troubleshooting,Multi-PROG; RESET solder point,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MULTIPROG_ERROR_CODE_CATALOG.md;13_Research_Expansion/MODULE_CASE_STUDIES.md,Error code 88030201 attributed to insufficient RESET soldering
XT-010,xhorsetool,How to Solve Xhorse Audi BCM2 Adapter V2 PIN is Abnormal?,http://blog.xhorsetool.com/how-to-solve-xhorse-audi-bcm2-adapter-v2-pin-is-abnormal/,2025-11-19,category-page-1,Audi BCM2 3381,adapter troubleshooting,BCM2 Adapter V2; XDNP100; XDNP101,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md,V2 modification reported as a fix after V1 worked on same module
XT-011,xhorsetool,Xhorse Multi Prog VVDI Prog BMW FRM2 ST10F269 Pinout,http://blog.xhorsetool.com/xhorse-multi-prog-vvdi-prog-bmw-frm2-st10f269-pinout/,2025-11-17,category-page-1,BMW FRM2 ST10F269 / MC9512XDT256,MCU direct access,Multi-PROG; VVDI Prog; matching flash/EEPROM files,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md,Module-specific files required; FRM2 distinguished from FRM3
XT-012,xhorsetool,Xhorse Multi-Prog Clone Audi BCM2 Module Guide,http://blog.xhorsetool.com/xhorse-tools-clone-audi-bcm2-module-guide/,2025-10-22,category-page-2,Audi BCM2,adapter-assisted EEPROM/flash access,Multi-PROG; BCM2 Adapter V2; Key Tool Plus,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,Distinguishes non-encrypted vs encrypted cases and hardware-version matching
XT-013,xhorsetool,2002 Mercedes S500 W220 AKL with Multi-Prog and Key Tool Plus OK,http://blog.xhorsetool.com/2002-mercedes-s500-w220-akl-with-multi-prog-and-key-tool-plus-ok/,2025-10-15,category-page-2,Mercedes S500 immobilizer,EEPROM and companion tool,Multi-PROG; Key Tool Plus; Xhorse Cloud,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,Security-sensitive decoding/key-file details not expanded
XT-014,xhorsetool,Xhorse Update BMW G/U Series BDC3/BCP Key Copy Feature,http://blog.xhorsetool.com/xhorse-update-bmw-g-u-series-bdc3-bcp-key-copy-feature/,2025-10-10,category-page-2,BMW G/U BDC3/BCP,key data access,BDC2 license; VVDI Prog; Multi-PROG; VVDI2; Key Tool Plus; Key Tool MIDI,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,License/test-function status only; sensitive key operation not reproduced
XT-015,xhorsetool,Xhorse Multi-Prog KIA MEG17.9.12 Connection Failed Solution,http://blog.xhorsetool.com/xhorse-multi-prog-kia-meg17-9-12-connection-failed-solution/,2025-09-29,category-page-2,KIA MEG17.9.12 ECU,boot troubleshooting,Multi-PROG,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,Connection failure indicates no communication; suggests boot mode
XT-016,xhorsetool,How to Bind Multi Prog and VVDI2 by Xhorse Account?,http://blog.xhorsetool.com/how-to-bind-multi-prog-and-vvdi2-by-xhorse-account/,2025-08-09,category-page-2,Multi-PROG/VVDI2 account,software account configuration,Xhorse App; Multi-PROG; VVDI2; Update Online; Xhorse Update Kit,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/OPERATIONAL_PRACTICES.md,Same-account binding; MQB48/NEC35XX license association; network troubleshooting
XT-017,xhorsetool,BMW REM Module Pinout for Xhorse Multi Prog and VVDI Prog,http://blog.xhorsetool.com/bmw-rem-module-pinout-for-xhorse-multi-prog-and-vvdi-prog/,2025-07-18,category-page-2,BMW REM MPC5515,MCU direct access,Multi-PROG; VVDI Prog; MPC5515; 100-120 ohm resistor,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md,Read-modify-write repair context reported
XT-018,xhorsetool,How to Set WiFi Password for Xhorse Multi Prog?,http://blog.xhorsetool.com/how-to-set-wifi-password-for-xhorse-multi-prog/,2025-07-11,category-page-2,Multi-PROG host,WiFi configuration,Multi-PROG; Settings > WiFi; USB WiFi adapter,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/OPERATIONAL_PRACTICES.md,Numeric-only WiFi password entry reported
XT-019,xhorsetool,How to Solve Xhorse Multi-Prog Read Audi J518 2010 Failure?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-read-audi-j518-2010-failure/,2025-06-25,category-page-2,Audi J518 1L59W/5L40K 0115,chip power troubleshooting,Multi-PROG; VVDI Prog; VDD setting; DB44/MCU self-check,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MULTIPROG_ERROR_CODE_CATALOG.md,Error code 13050102; recommends VDD 4-5V plus equipment self-check
XT-020,xhorsetool,How to Solve Xhorse Multi Prog Read and Write Button Grey Out,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-read-and-write-button-grey-out/,2025-06-20,category-page-2,Multi-PROG host,software UI troubleshooting,Multi-PROG Connect button,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/OPERATIONAL_PRACTICES.md,Connect must be used before Read/Write after a software update
XT-021,xhorsetool,How to Solve Multi-Prog ME7.1 ECU Chip Power Configuration Failed?,http://blog.xhorsetool.com/how-to-solve-multi-prog-me7-1-chip-power-configuration-failed/,2025-06-04,category-page-2,VW ME7.x ECU,bench troubleshooting,12V ECU power supply,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/OPERATIONAL_PRACTICES.md;13_Research_Expansion/MODULE_CASE_STUDIES.md,Chip power configuration failure troubleshooting claim
XT-022,xhorsetool,How to Solve Xhorse Multi Prog WiFi Module Not Inserted?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-wifi-module-not-inserted/,2025-05-19,category-page-2,Multi-PROG host,hardware/WiFi setup,USB WiFi adapter,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/OPERATIONAL_PRACTICES.md,Inserting adapter and powering on activates WiFi
XT-023,xhorsetool,How to Solve Xhorse Multi Prog Server Calculation Error FFFF000C?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-server-calculation-error-ffff000c/,2025-05-16,category-page-3,VAG SID10.4 ECU,network/software troubleshooting,Multi-PROG; Test Function command 18; Xhorse server,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/MULTIPROG_ERROR_CODE_CATALOG.md,Error code FFFF000C
XT-024,xhorsetool,How to Solve Xhorse Multi Prog Remaining Usage of the Device Error?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-remaining-usage-of-the-device-error/,2025-04-25,category-page-3,Multi-PROG device authorization,authorization synchronization,Multi-PROG; Update Online > Authorization management,,FACTS_AVAILABLE,PARTIALLY_IMPORTED,13_Research_Expansion/OPERATIONAL_PRACTICES.md,Synchronization after a usage threshold reported as vendor remedy
XT-025,xhorsetool,Xhorse Multi Prog Fixes Audi Radio 24C256 Unit Component Protection,http://blog.xhorsetool.com/xhorse-multi-prog-fixes-audi-radio-24c256-unit-component-protection/,2025-04-21,category-page-3,Audi radio 24C256 EEPROM,EEPROM access,24C256 EEPROM,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md,Title/tool metadata only; full procedure not body-extracted into ARTICLE_FACTS.csv
XT-026,xhorsetool,Xhorse Multi-Prog Clone Audi A3 2014-2020 Climate Control Unit,http://blog.xhorsetool.com/xhorse-multi-prog-clone-audi-a3-2014-2020-climate-control-unit/,2025-04-18,category-page-3,Audi A3 climate control,EEPROM/module cloning,Audi A3 climate control unit,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,Title/tool metadata only
XT-027,xhorsetool,Solved Xhorse Multi Prog Write BMW FEM BDC Chip Data Failure,http://blog.xhorsetool.com/solved-xhorse-multi-prog-write-bmw-fem-bdc-chip-data-failure/,2025-04-09,category-page-3,BMW FEM/BDC 95128,EEPROM write troubleshooting,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
XT-028,xhorsetool,How to Solve Xhorse Multi Prog Read BMW MSV80 Number of Times is 0?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-read-bmw-msv80-number-of-times-is-0/,2025-04-02,category-page-3,BMW MSV80 ECU,bench authorization troubleshooting,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
XT-029,xhorsetool,How to Solve Xhorse Multi Prog Update Firmware Error Device Authentication Failed?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-update-firmware-error-device-authentication-failed/,2025-03-21,category-page-3,Multi-PROG firmware,PC update recovery,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
XT-030,xhorsetool,Xhorse Multi Prog Renault Master BCM N3 D70F3376A Pinout,http://blog.xhorsetool.com/xhorse-multi-prog-renault-master-bcm-n3-d70f3376a-pinout/,2025-03-17,category-page-3,Renault BCM N3 D70F3376A,MCU direct access,Renesas V850 D70F3376A,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md,Title/tool metadata only; SOURCE DIAGRAM REQUIRED for pinout
XT-031,xhorsetool,How to Solve Xhorse Multi-Prog Stop Upgrading Problem?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-stop-upgrading-problem/,2025-03-07,category-page-3,Multi-PROG firmware,PC update recovery,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
XT-032,xhorsetool,How to Use Xhorse MVCI PRO J2534 for Vehicle Diagnosis and Programming?,http://blog.xhorsetool.com/how-to-use-xhorse-mvci-pro-j2534-for-vehicle-diagnosis-and-programming/,2025-02-21,category-page-3,MVCI PRO J2534,vehicle diagnostic passthrough,MVCI PRO-J2534 1.0.3,version 1.0.3,INDEXED_ONLY,PARTIALLY_IMPORTED,07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md,Title/tool metadata only
XT-033,xhorsetool,Xhorse Multi Prog Read Write Captiva Delco E39A on Bench OK,http://blog.xhorsetool.com/xhorse-multi-prog-read-write-captiva-delco-e39a-on-bench-ok/,2025-02-17,category-page-3,GM Delco E39A ECU,bench,,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,Title only; cross-referenced with OBD-053 GM Delco family
XT-034,xhorsetool,Xhorse Multi-Prog Database Update to V51,http://blog.xhorsetool.com/xhorse-multi-prog-database-update-to-v51/,2025-02-08,category-page-4,Multi-PROG database,online update,database V51,V51,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/OPERATIONAL_PRACTICES.md,Historical database version claim only
XT-035,xhorsetool,How to Solve Xhorse Multi-Prog Error Code 0404001F Hardware Initialization Fails?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-error-code-0404001f-hardware-initialization-fails/,2025-01-27,category-page-4,Multi-PROG hardware,device initialization troubleshooting,,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/MULTIPROG_ERROR_CODE_CATALOG.md,Error code 0404001F; title/topic only
XT-036,xhorsetool,How to Use Xhorse Multi-Prog in Offline Mode?,http://blog.xhorsetool.com/how-to-use-xhorse-multi-prog-in-offline-mode/,2024-11-25,category-page-4,Multi-PROG software,offline software mode,software version 4.0 or later; offline license,4.0+,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/OPERATIONAL_PRACTICES.md,Requirement claim only
XT-037,xhorsetool,How to Solve Xhorse Multi Prog Failed to Read Motorola MC68HC05X32 1D69J?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-failed-to-read-motorola-mc68hc05x32-1d69j/,2024-11-22,category-page-4,Motorola MC68HC05X32,MCU adapter troubleshooting,,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md,Title/topic only
XT-038,xhorsetool,Xhorse Multi Prog with GODIAG Cables Read MED17.8.8,http://blog.xhorsetool.com/xhorse-multi-prog-with-godiag-cables-read-med17-8-8/,2024-11-20,category-page-4,VAG MED17.8.8 TC1728,bench/boot adapter,GODIAG G-V ECU Cable; GT107/GT107+,,INDEXED_ONLY,PARTIALLY_IMPORTED,07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md;13_Research_Expansion/MODULE_CASE_STUDIES.md,Title/tool metadata only
XT-039,xhorsetool,How to Connect Xhorse Multi Prog and BCM2 Audi Solder-Free Adapter?,http://blog.xhorsetool.com/how-to-connect-xhorse-multi-prog-and-bcm2-audi-solder-free-adapter/,2024-11-15,category-page-4,Audi BCM2,solder-free adapter,BCM2-A2 Cable XDNP66,,INDEXED_ONLY,PARTIALLY_IMPORTED,07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md,Title/tool metadata only
XT-040,xhorsetool,How to Solve Multi Prog Fail to Read D70F3524 Hyundai Solaris?,http://blog.xhorsetool.com/how-to-solve-multi-prog-fail-to-read-d70f3524-hyundai-solaris/,2024-10-21,category-page-4,Hyundai Solaris D70F3524,MCU direct access troubleshooting,check pinout and supply 12V,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md,Title/topic only
XT-041,xhorsetool,Xhorse Multi Prog Software Update V1.2.7.0 and V1.2.6.0,http://blog.xhorsetool.com/xhorse-multi-prog-software-update-v1-2-7-0-v1-2-6-0/,2024-10-11,category-page-4,Multi-PROG software,online update,,V1.2.7.0; V1.2.6.0 (October 2024),INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/OPERATIONAL_PRACTICES.md,Historical software version claim only
XT-042,xhorsetool,How to Change Xhorse Multi-Prog Language?,http://blog.xhorsetool.com/how-to-change-xhorse-multi-prog-language/,2024-10-03,category-page-4,Multi-PROG software,host configuration,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
XT-043,xhorsetool,How to Solve Xhorse Multi Prog MQB RH850 Chip Configuration Failed Problem?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-mqb-rh850-chip-configuration-failed-problem/,2024-09-28,category-page-4,VAG MQB RH850 R7F701407,adapter troubleshooting,MQB RH850/V850 adapter,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/OPERATIONAL_PRACTICES.md,Warns against extending adapter harness
XT-044,xhorsetool,How to Solve Xhorse Multi Prog Erase M35080 Error Code 13050001?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-erase-m35080-error-code-13050001/,2024-08-13,category-page-4,M35080 EEPROM,EEPROM adapter troubleshooting,XDNP24GL D80/35080 Adapter,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/MULTIPROG_ERROR_CODE_CATALOG.md;13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md,Error code 13050001; VPP adjustment troubleshooting claim
XT-045,xhorsetool,Xhorse Multi-Prog and VVDI2 Program MQB RH850/V850 1402 Dashboard Key,http://blog.xhorsetool.com/xhorse-multi-prog-and-vvdi2-program-mqb-rh850-v850-1402-dashboard-key/,2024-07-31,category-page-5,VAG MQB RH850/V850 R7F701402,adapter-assisted cluster access,XDMPR8GL MQB RH850/V850 Adapter,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md,Title/tool metadata only
XT-046,xhorsetool,How to Solve Xhorse Multi-Prog Driver Not Working?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-driver-not-working/,2024-06-07,category-page-5,Multi-PROG USB driver,PC USB connection,USB driver,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/OPERATIONAL_PRACTICES.md,Title/topic only
XT-047,xhorsetool,How to Repair BMW FRM E Series by Xhorse Multi-Prog?,http://blog.xhorsetool.com/how-to-repair-bmw-frm-e-series-by-xhorse-multi-prog/,2024-05-11,category-page-5,BMW FRM E-series,MCU adapter,Multi-Prog MCU Adapter; XDNP18 Adapter,,INDEXED_ONLY,PARTIALLY_IMPORTED,07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md;13_Research_Expansion/MODULE_CASE_STUDIES.md,Source describes two methods; title/tool metadata only
XT-048,xhorsetool,How to Make First Script with Xhorse Multi-Prog?,http://blog.xhorsetool.com/how-to-make-first-script-with-xhorse-multi-prog/,2024-04-08,category-page-5,Multi-PROG JavaScript host,script development,JavaScript script function,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/MULTIPROG_SCRIPT_PATTERNS.md,Describes free or device-bound scripts; title/topic only
XT-049,xhorsetool,How to Read and Write SOP44 Flash Chip with Xhorse Multi-Prog?,http://blog.xhorsetool.com/how-to-read-and-write-sop44-flash-chip-with-xhorse-multi-prog/,2024-04-03,category-page-5,SOP44/TSOP48 flash,external chip adapter,VH24 SOP44/TSOP48 adapter; AM29FXXX; M29FXXX; TB28FXXX families,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md,Title/tool metadata only
XT-050,xhorsetool,How to Read Audi BCM2 Module with Xhorse Multi Prog No Soldering?,http://blog.xhorsetool.com/how-to-read-audi-bcm2-module-with-xhorse-multi-prog-no-soldering/,2024-03-25,category-page-5,Audi BCM2,solder-free adapter,Audi BCM2 solder-free adapter; VVDI2,,INDEXED_ONLY,PARTIALLY_IMPORTED,07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md,Title/tool metadata only
XT-051,xhorsetool,How to Read and Write EEPROM with Xhorse Multi Prog?,http://blog.xhorsetool.com/how-to-read-and-write-eeprom-with-xhorse-multi-prog/,2024-03-18,category-page-5,EEPROM AT17C128 and other chips,external EEPROM adapter,AT17C128 DIP8 and corresponding adapter,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md,Title/tool metadata only
XT-052,xhorsetool,Xhorse Multi Prog Read and Write VW EDC17CP14 on Bench,http://blog.xhorsetool.com/xhorse-multi-prog-read-and-write-vw-edc17cp14-on-bench/,2024-03-11,category-page-5,VW EDC17CP14,bench,ECU Adapter,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/MODULE_CASE_STUDIES.md,Title only; bench INT EEPROM and flash access described
XT-053,xhorsetool,Xhorse Multi Prog V1.1.2.0 Update MQB D70F3423 D70F3426,http://blog.xhorsetool.com/xhorse-multi-prog-v1-1-2-0-update-mqb-d70f3423-d70f3426/,2024-02-28,category-page-5,VAG MQB dashboard,online software/database update,,V1.1.2.0; Database V11,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md,Historical version claim only
XT-054,xhorsetool,What is Xhorse Multi-Prog SOP44/TSOP48 Adapter?,http://blog.xhorsetool.com/what-is-xhorse-multi-prog-sop44-tsop48-adapter/,2024-02-23,category-page-5,SOP44/TSOP48 flash,external chip adapter,VH13/VH20/VH23 and SOP44/TSOP48 boards,,INDEXED_ONLY,PARTIALLY_IMPORTED,07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md,Product description only
XT-055,xhorsetool,Xhorse Multi Prog Error Code 1 Error Address 2 Solution,http://blog.xhorsetool.com/xhorse-multi-prog-error-code-1-error-address-2-solution/,2024-01-26,category-page-5,Multi-PROG update system,PC update troubleshooting,,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/MULTIPROG_ERROR_CODE_CATALOG.md,"Error Code 1 / Error Address 2"; title/topic only
XT-056,xhorsetool,How to Solve Xhorse Multi-Prog Disconnected Problem?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-disconnected-problem/,2024-01-12,category-page-6,Multi-PROG USB driver,PC USB connection,USB driver,,INDEXED_ONLY,PARTIALLY_IMPORTED,13_Research_Expansion/OPERATIONAL_PRACTICES.md,Distinguishes Win10 automatic vs Win7 manual driver install
XT-057,xhorsetool,Xhorse Multi-Prog Programmer FAQs,http://blog.xhorsetool.com/xhorse-multi-prog-programmer-faqs/,2023-12-14,category-page-6,Multi-PROG device overview,mixed device functions,Multi-PROG adapters and functions,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only; FAQ claims not individually extracted
XT-058,xhorsetool,What is Xhorse Multi-Prog Programmer?,http://blog.xhorsetool.com/what-is-xhorse-multi-prog-programmer/,2023-12-08,category-page-6,Multi-PROG ECU/TCU programmer,mixed device functions,,,INDEXED_ONLY,INDEXED_ONLY,,Indexed title only
Can't render this file because it contains an unexpected character in line 111 and column 356.
13_Research_Expansion/UNIFIED_SOURCE_MANIFEST.md
+69
View File
@@ -0,0 +1,69 @@
# Unified OBDII365 / XhorseTool Source Manifest
This is the reconciled source register for the two article collections imported under
`13_Research_Expansion/OBDII365/` and `13_Research_Expansion/XhorseTool/`. It does not replace
either collection's own index files; it cross-references them under one evidence model so a
reader can see, per article, whether it is `INDEXED_ONLY` (title/URL/date only) or
`FACTS_AVAILABLE` (body-extracted, structured facts exist), and which repository documents (if
any) now cite it.
See [`UNIFIED_SOURCE_MANIFEST.csv`](UNIFIED_SOURCE_MANIFEST.csv) for the machine-readable register.
## Source identity (kept distinct, never merged)
- `OBD-###` — `blog.obdii365.com` records, defined in `OBDII365/ARTICLE_CLASSIFICATION.csv` (same IDs reused here).
- `XT-###` — `blog.xhorsetool.com` records, numbered here in the same order as `XhorseTool/ARTICLE_INDEX.csv` (source page 1 → page 6). The XhorseTool files did not previously assign row IDs; `XT-001`…`XT-058` are introduced only in this manifest as a join key and do not change the underlying CSVs.
No OBDII365 URL was found to duplicate an XhorseTool URL, and vice versa (both source folders' own import reports already record this cross-check). No records were deleted or merged; every row below maps 1:1 to a row in one of the two existing per-source indexes.
## Processing-state definitions (as used in the `extraction_status` / `processing_status` columns)
- `INDEXED_ONLY` — title, URL, publication date, and a classification guess only. Not treated as a complete procedure.
- `FACTS_AVAILABLE` — the article body was fetched and reduced to structured facts in `ARTICLE_FACTS.csv` (XhorseTool) or a `raw/OBD-###-*.md` extraction record (OBDII365).
- `PARTIALLY_IMPORTED` — at least one fact from this source now appears (with citation) in a repository target file listed in `imported_target_files`.
- `NOT_IMPORTED` — `FACTS_AVAILABLE` but not yet cited anywhere in the repository outside the source folders themselves.
No row in this pass reached `IMPORTED` (fully imported) or `DUPLICATE`/`CONFLICTING` — no two sources were found describing the same device with contradictory facts; if a future pass finds one, record it here as `CONFLICTING` and add the conflict to `IMPORT_REPORT.md` in both source folders, per the non‑negotiable rule against silent overwrites.
## Field notes
To keep 113 rows maintainable, several of the phase-3 fields requested in the working brief are
intentionally consolidated rather than split into 20+ near-empty columns:
- `device_family` also carries module/MCU/memory-device identity where the source names it (e.g. "BMW FRM2 ST10F269 / MC9512XDT256").
- `tools_adapters_cables` merges tool, adapter, and cable names as the source itself names them together.
- `version_info` merges software/firmware/database version strings.
Every fact in these consolidated columns is still traceable to exactly one `canonical_url` +
`publication_date`, which is all that is required to satisfy instruction 24 (preserve source URL,
publication date, and source site for every imported item).
## Evidence status
Every row in this manifest is `COMMUNITY/VENDOR REFERENCE` (per each source folder's own
`README.md`/`GAP_ANALYSIS.md`). None of these rows are promoted to `PRIMARY-MULTIPROG`. Where a row
is cited from a repository document, that document must keep the citation labeled
`COMMUNITY/VENDOR REFERENCE` or `SECONDARY-CASE-STUDY` and must not present the article title alone
as a verified procedure.
## Statistics
- OBDII365 records: 55 (`OBD-001`…`OBD-055`) — 15 `FACTS_AVAILABLE`, 40 `INDEXED_ONLY`.
- XhorseTool records: 58 (`XT-001`…`XT-058`) — 23 `FACTS_AVAILABLE`, 35 `INDEXED_ONLY`.
- Total: 113 records, 38 `FACTS_AVAILABLE`, 75 `INDEXED_ONLY`.
- Of the 38 `FACTS_AVAILABLE` records, this pass promoted 33 to `PARTIALLY_IMPORTED` (cited in at least one repository target file below); 5 remain `NOT_IMPORTED` pending further scope decisions (see `IMPORT_REPORT.md` in each source folder).
## New repository target files created or updated by this pass
- `13_Research_Expansion/UNIFIED_SOURCE_MANIFEST.md` / `.csv` (this file)
- `13_Research_Expansion/MULTIPROG_ERROR_CODE_CATALOG.md`
- `13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md`
- `13_Research_Expansion/MODULE_CASE_STUDIES.md`
- `13_Research_Expansion/OPERATIONAL_PRACTICES.md`
- `07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md` (expanded, not replaced)
- `13_Research_Expansion/COMMON_CHECKSUMS.md`, `MULTIPROG_SCRIPT_PATTERNS.md` (expanded, not replaced)
## Related documents
- `OBDII365/README.md`, `OBDII365/GAP_ANALYSIS.md`, `OBDII365/IMPORT_REPORT.md`
- `XhorseTool/README.md`, `XhorseTool/EXTRACTION_STATUS.md`, `XhorseTool/IMPORT_REPORT.md`
13_Research_Expansion/XhorseTool/ARTICLE_FACTS.csv
+24
View File
@@ -0,0 +1,24 @@
title,url,device_family,access_path,tools_adapters_software,practice_or_finding,evidence_status
How to Fix Xhorse Multi-Prog Failed to Execute VPA Error 040510C?,http://blog.xhorsetool.com/how-to-fix-xhorse-multi-prog-failed-to-execute-vpa-error-040510c/,BMW MEVD17.2.4 N20 ECU,ECU communication troubleshooting,Multi-PROG V1.4.4.0; latest database; diagnostic log,Update software/database; retry connection; escalate diagnostic report,COMMUNITY/VENDOR REFERENCE
Xhorse Multi Prog BMW BDC2 BDC3 LCD Encrypted Key Pinouts,http://blog.xhorsetool.com/xhorse-multi-prog-bmw-bdc2-bdc3-lcd-encrypted-key-pinouts/,BMW BDC2 BDC3 LCD keys,MCU adapter/key data access,Multi-PROG; Key Tool MIDI; Key Tool Plus; modified MCU adapter,Source says encrypted-key reading and companion-tool processing; sensitive procedure not reproduced,COMMUNITY/VENDOR REFERENCE
Xhorse Multi Prog MCU Adapter Modification Method,http://blog.xhorsetool.com/xhorse-multi-prog-mcu-adapter-modification-method/,9S12HZ512 MCU,MCU adapter,Multi-PROG MCU adapter; added GND short/long wires,Source reports adapter modification enabled a successful read,COMMUNITY/VENDOR REFERENCE
Xhorse Update BMW BDC2 BDC3 BCP Encrypted Key Cloning,http://blog.xhorsetool.com/xhorse-update-bmw-bdc2-bdc3-bcp-encrypted-key-cloning/,BMW BDC2 BDC3 BCP keys,key data read/write,Multi-PROG; VVDI Key Tool Plus; VVDI BMW dedicated adapter,Source reports encrypted-key cloning update and soldering support; sensitive procedure summarized only,COMMUNITY/VENDOR REFERENCE
How to Calculate Checksum for Xhorse Multi Prog?,http://blog.xhorsetool.com/how-to-calculate-checksum-for-xhorse-multi-prog/,supported ECU EEPROM/flash entries,software checksum function,Multi-PROG device library; green C indicator; Write/Verify UI,Source says checksum availability is shown per supported entry and real-vehicle validation remains unconfirmed,COMMUNITY/VENDOR REFERENCE
How to Solve Xhorse Audi BCM2 Adapter V2 PIN Connection Detect Failed?,http://blog.xhorsetool.com/how-to-solve-xhorse-audi-bcm2-adapter-v2-pin-connection-detect-failed/,Audi BCM2,adapter troubleshooting,BCM2 Adapter V2; XDNP100; XDNP101; Multi-PROG,Source attributes PIN detection failure to adapter compatibility and recommends adapter modification,COMMUNITY/VENDOR REFERENCE
How to Solve Multi Prog Update Firmware Jump Recovery Error 41330004?,http://blog.xhorsetool.com/how-to-solve-multi-prog-update-firmware-jump-recovery-error-41330004/,Multi-PROG firmware,firmware recovery,firmware 1.36 to 1.45; reset button,Source reports holding Reset during power-on then retrying forced update,COMMUNITY/VENDOR REFERENCE
Xhorse Multi Prog Update BDC3 Key Copy Function,http://blog.xhorsetool.com/xhorse-multi-prog-update-bdc3-key-copy-function/,BMW BDC03 keys,key data access,Multi-PROG database V87; VVDI2; Key Tool Plus,Source reports direct original-key read/write and no data conversion; vendor claim only,COMMUNITY/VENDOR REFERENCE
How to Fix Xhorse Multi Prog BMW FRM3 Chip Configuration Failed?,http://blog.xhorsetool.com/how-to-fix-xhorse-multi-prog-bmw-frm3-chip-configuration-failed/,BMW FRM3,MCU adapter troubleshooting,Multi-PROG; RESET solder point,Source reports error 88030201 and attributes it to insufficient RESET soldering,COMMUNITY/VENDOR REFERENCE
How to Solve Xhorse Audi BCM2 Adapter V2 PIN is Abnormal?,http://blog.xhorsetool.com/how-to-solve-xhorse-audi-bcm2-adapter-v2-pin-is-abnormal/,Audi BCM2 3381,adapter troubleshooting,BCM2 Adapter V2; XDNP100; XDNP101,Source reports V2 modification as a fix after V1 worked on the same module,COMMUNITY/VENDOR REFERENCE
Xhorse Multi Prog VVDI Prog BMW FRM2 ST10F269 Pinout,http://blog.xhorsetool.com/xhorse-multi-prog-vvdi-prog-bmw-frm2-st10f269-pinout/,BMW FRM2 ST10F269 / MC9512XDT256,MCU direct access,Multi-PROG; VVDI Prog; matching flash/EEPROM files,Source warns module-specific files are required and distinguishes FRM2 from FRM3 recovery claims,COMMUNITY/VENDOR REFERENCE
Xhorse Multi-Prog Clone Audi BCM2 Module Guide,http://blog.xhorsetool.com/xhorse-tools-clone-audi-bcm2-module-guide/,Audi BCM2,adapter-assisted EEPROM/flash access,Multi-PROG; BCM2 Adapter V2; Key Tool Plus,Source distinguishes non-encrypted versus encrypted cases and hardware-version matching,COMMUNITY/VENDOR REFERENCE
2002 Mercedes S500 W220 AKL with Multi-Prog and Key Tool Plus OK,http://blog.xhorsetool.com/2002-mercedes-s500-w220-akl-with-multi-prog-and-key-tool-plus-ok/,Mercedes S500 immobilizer,EEPROM and companion tool,Multi-PROG; Key Tool Plus; Xhorse Cloud,Source reports EEPROM extraction, cloud-assisted decoding, key-file preparation and writing; security-sensitive details not expanded,COMMUNITY/VENDOR REFERENCE
Xhorse Update BMW G/U Series BDC3/BCP Key Copy Feature,http://blog.xhorsetool.com/xhorse-update-bmw-g-u-series-bdc3-bcp-key-copy-feature/,BMW G/U BDC3/BCP,key data access,BDC2 license; VVDI Prog; Multi-PROG; VVDI2; Key Tool Plus; Key Tool MIDI,Source reports license and test-function status; sensitive key operation not reproduced,COMMUNITY/VENDOR REFERENCE
Xhorse Multi-Prog KIA MEG17.9.12 Connection Failed Solution,http://blog.xhorsetool.com/xhorse-multi-prog-kia-meg17-9-12-connection-failed-solution/,KIA MEG17.9.12 ECU,boot troubleshooting,Multi-PROG,Source says connection failure indicates no communication and suggests boot mode,COMMUNITY/VENDOR REFERENCE
How to Bind Multi Prog and VVDI2 by Xhorse Account?,http://blog.xhorsetool.com/how-to-bind-multi-prog-and-vvdi2-by-xhorse-account/,Multi-PROG/VVDI2 account,software account configuration,Xhorse App; Multi-PROG; VVDI2; Update Online; Xhorse Update Kit,Source describes same-account binding, MQB48/NEC35XX license association, and network troubleshooting,COMMUNITY/VENDOR REFERENCE
BMW REM Module Pinout for Xhorse Multi Prog and VVDI Prog,http://blog.xhorsetool.com/bmw-rem-module-pinout-for-xhorse-multi-prog-and-vvdi-prog/,BMW REM MPC5515,MCU direct access,Multi-PROG; VVDI Prog; MPC5515; 100-120 ohm resistor,Source reports read-modify-write repair context and software selection names,COMMUNITY/VENDOR REFERENCE
How to Set WiFi Password for Xhorse Multi Prog?,http://blog.xhorsetool.com/how-to-set-wifi-password-for-xhorse-multi-prog/,Multi-PROG host,WiFi configuration,Multi-PROG; Settings > WiFi; USB WiFi adapter,Source reports numeric-only WiFi password entry,COMMUNITY/VENDOR REFERENCE
How to Solve Xhorse Multi-Prog Read Audi J518 2010 Failure?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-read-audi-j518-2010-failure/,Audi J518 1L59W/5L40K 0115,chip troubleshooting,Multi-PROG; VVDI Prog; VDD setting; DB44/MCU self-check,Source reports error 13050102 and recommends VDD 4-5V plus equipment self-check,COMMUNITY/VENDOR REFERENCE
How to Solve Xhorse Multi Prog Read and Write Button Grey Out,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-read-and-write-button-grey-out/,Multi-PROG host,software UI,Multi-PROG Connect button,Source reports Connect must be used before Read/Write after a software update,COMMUNITY/VENDOR REFERENCE
How to Solve Xhorse Multi Prog WiFi Module Not Inserted?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-wifi-module-not-inserted/,Multi-PROG host,hardware/WiFi setup,USB WiFi adapter,Source reports inserting the adapter and powering on activates WiFi,COMMUNITY/VENDOR REFERENCE
How to Solve Xhorse Multi Prog Server Calculation Error FFFF000C?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-server-calculation-error-ffff000c/,VAG SID10.4 ECU,network/server troubleshooting,Multi-PROG; Test Function command 18; Xhorse server,Source recommends network/server check, command 18 test, and support escalation,COMMUNITY/VENDOR REFERENCE
How to Solve Xhorse Multi Prog Remaining Usage of the Device Error?,http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-remaining-usage-of-the-device-error/,Multi-PROG authorization,authorization synchronization,Multi-PROG; Update Online > Authorization management,Source reports synchronization after a usage threshold as the vendor remedy,COMMUNITY/VENDOR REFERENCE
1 title url device_family access_path tools_adapters_software practice_or_finding evidence_status
2 How to Fix Xhorse Multi-Prog Failed to Execute VPA Error 040510C? http://blog.xhorsetool.com/how-to-fix-xhorse-multi-prog-failed-to-execute-vpa-error-040510c/ BMW MEVD17.2.4 N20 ECU ECU communication troubleshooting Multi-PROG V1.4.4.0; latest database; diagnostic log Update software/database; retry connection; escalate diagnostic report COMMUNITY/VENDOR REFERENCE
3 Xhorse Multi Prog BMW BDC2 BDC3 LCD Encrypted Key Pinouts http://blog.xhorsetool.com/xhorse-multi-prog-bmw-bdc2-bdc3-lcd-encrypted-key-pinouts/ BMW BDC2 BDC3 LCD keys MCU adapter/key data access Multi-PROG; Key Tool MIDI; Key Tool Plus; modified MCU adapter Source says encrypted-key reading and companion-tool processing; sensitive procedure not reproduced COMMUNITY/VENDOR REFERENCE
4 Xhorse Multi Prog MCU Adapter Modification Method http://blog.xhorsetool.com/xhorse-multi-prog-mcu-adapter-modification-method/ 9S12HZ512 MCU MCU adapter Multi-PROG MCU adapter; added GND short/long wires Source reports adapter modification enabled a successful read COMMUNITY/VENDOR REFERENCE
5 Xhorse Update BMW BDC2 BDC3 BCP Encrypted Key Cloning http://blog.xhorsetool.com/xhorse-update-bmw-bdc2-bdc3-bcp-encrypted-key-cloning/ BMW BDC2 BDC3 BCP keys key data read/write Multi-PROG; VVDI Key Tool Plus; VVDI BMW dedicated adapter Source reports encrypted-key cloning update and soldering support; sensitive procedure summarized only COMMUNITY/VENDOR REFERENCE
6 How to Calculate Checksum for Xhorse Multi Prog? http://blog.xhorsetool.com/how-to-calculate-checksum-for-xhorse-multi-prog/ supported ECU EEPROM/flash entries software checksum function Multi-PROG device library; green C indicator; Write/Verify UI Source says checksum availability is shown per supported entry and real-vehicle validation remains unconfirmed COMMUNITY/VENDOR REFERENCE
7 How to Solve Xhorse Audi BCM2 Adapter V2 PIN Connection Detect Failed? http://blog.xhorsetool.com/how-to-solve-xhorse-audi-bcm2-adapter-v2-pin-connection-detect-failed/ Audi BCM2 adapter troubleshooting BCM2 Adapter V2; XDNP100; XDNP101; Multi-PROG Source attributes PIN detection failure to adapter compatibility and recommends adapter modification COMMUNITY/VENDOR REFERENCE
8 How to Solve Multi Prog Update Firmware Jump Recovery Error 41330004? http://blog.xhorsetool.com/how-to-solve-multi-prog-update-firmware-jump-recovery-error-41330004/ Multi-PROG firmware firmware recovery firmware 1.36 to 1.45; reset button Source reports holding Reset during power-on then retrying forced update COMMUNITY/VENDOR REFERENCE
9 Xhorse Multi Prog Update BDC3 Key Copy Function http://blog.xhorsetool.com/xhorse-multi-prog-update-bdc3-key-copy-function/ BMW BDC03 keys key data access Multi-PROG database V87; VVDI2; Key Tool Plus Source reports direct original-key read/write and no data conversion; vendor claim only COMMUNITY/VENDOR REFERENCE
10 How to Fix Xhorse Multi Prog BMW FRM3 Chip Configuration Failed? http://blog.xhorsetool.com/how-to-fix-xhorse-multi-prog-bmw-frm3-chip-configuration-failed/ BMW FRM3 MCU adapter troubleshooting Multi-PROG; RESET solder point Source reports error 88030201 and attributes it to insufficient RESET soldering COMMUNITY/VENDOR REFERENCE
11 How to Solve Xhorse Audi BCM2 Adapter V2 PIN is Abnormal? http://blog.xhorsetool.com/how-to-solve-xhorse-audi-bcm2-adapter-v2-pin-is-abnormal/ Audi BCM2 3381 adapter troubleshooting BCM2 Adapter V2; XDNP100; XDNP101 Source reports V2 modification as a fix after V1 worked on the same module COMMUNITY/VENDOR REFERENCE
12 Xhorse Multi Prog VVDI Prog BMW FRM2 ST10F269 Pinout http://blog.xhorsetool.com/xhorse-multi-prog-vvdi-prog-bmw-frm2-st10f269-pinout/ BMW FRM2 ST10F269 / MC9512XDT256 MCU direct access Multi-PROG; VVDI Prog; matching flash/EEPROM files Source warns module-specific files are required and distinguishes FRM2 from FRM3 recovery claims COMMUNITY/VENDOR REFERENCE
13 Xhorse Multi-Prog Clone Audi BCM2 Module Guide http://blog.xhorsetool.com/xhorse-tools-clone-audi-bcm2-module-guide/ Audi BCM2 adapter-assisted EEPROM/flash access Multi-PROG; BCM2 Adapter V2; Key Tool Plus Source distinguishes non-encrypted versus encrypted cases and hardware-version matching COMMUNITY/VENDOR REFERENCE
14 2002 Mercedes S500 W220 AKL with Multi-Prog and Key Tool Plus OK http://blog.xhorsetool.com/2002-mercedes-s500-w220-akl-with-multi-prog-and-key-tool-plus-ok/ Mercedes S500 immobilizer EEPROM and companion tool Multi-PROG; Key Tool Plus; Xhorse Cloud Source reports EEPROM extraction cloud-assisted decoding key-file preparation and writing; security-sensitive details not expanded COMMUNITY/VENDOR REFERENCE
15 Xhorse Update BMW G/U Series BDC3/BCP Key Copy Feature http://blog.xhorsetool.com/xhorse-update-bmw-g-u-series-bdc3-bcp-key-copy-feature/ BMW G/U BDC3/BCP key data access BDC2 license; VVDI Prog; Multi-PROG; VVDI2; Key Tool Plus; Key Tool MIDI Source reports license and test-function status; sensitive key operation not reproduced COMMUNITY/VENDOR REFERENCE
16 Xhorse Multi-Prog KIA MEG17.9.12 Connection Failed Solution http://blog.xhorsetool.com/xhorse-multi-prog-kia-meg17-9-12-connection-failed-solution/ KIA MEG17.9.12 ECU boot troubleshooting Multi-PROG Source says connection failure indicates no communication and suggests boot mode COMMUNITY/VENDOR REFERENCE
17 How to Bind Multi Prog and VVDI2 by Xhorse Account? http://blog.xhorsetool.com/how-to-bind-multi-prog-and-vvdi2-by-xhorse-account/ Multi-PROG/VVDI2 account software account configuration Xhorse App; Multi-PROG; VVDI2; Update Online; Xhorse Update Kit Source describes same-account binding MQB48/NEC35XX license association and network troubleshooting COMMUNITY/VENDOR REFERENCE
18 BMW REM Module Pinout for Xhorse Multi Prog and VVDI Prog http://blog.xhorsetool.com/bmw-rem-module-pinout-for-xhorse-multi-prog-and-vvdi-prog/ BMW REM MPC5515 MCU direct access Multi-PROG; VVDI Prog; MPC5515; 100-120 ohm resistor Source reports read-modify-write repair context and software selection names COMMUNITY/VENDOR REFERENCE
19 How to Set WiFi Password for Xhorse Multi Prog? http://blog.xhorsetool.com/how-to-set-wifi-password-for-xhorse-multi-prog/ Multi-PROG host WiFi configuration Multi-PROG; Settings > WiFi; USB WiFi adapter Source reports numeric-only WiFi password entry COMMUNITY/VENDOR REFERENCE
20 How to Solve Xhorse Multi-Prog Read Audi J518 2010 Failure? http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-read-audi-j518-2010-failure/ Audi J518 1L59W/5L40K 0115 chip troubleshooting Multi-PROG; VVDI Prog; VDD setting; DB44/MCU self-check Source reports error 13050102 and recommends VDD 4-5V plus equipment self-check COMMUNITY/VENDOR REFERENCE
21 How to Solve Xhorse Multi Prog Read and Write Button Grey Out http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-read-and-write-button-grey-out/ Multi-PROG host software UI Multi-PROG Connect button Source reports Connect must be used before Read/Write after a software update COMMUNITY/VENDOR REFERENCE
22 How to Solve Xhorse Multi Prog WiFi Module Not Inserted? http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-wifi-module-not-inserted/ Multi-PROG host hardware/WiFi setup USB WiFi adapter Source reports inserting the adapter and powering on activates WiFi COMMUNITY/VENDOR REFERENCE
23 How to Solve Xhorse Multi Prog Server Calculation Error FFFF000C? http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-server-calculation-error-ffff000c/ VAG SID10.4 ECU network/server troubleshooting Multi-PROG; Test Function command 18; Xhorse server Source recommends network/server check command 18 test and support escalation COMMUNITY/VENDOR REFERENCE
24 How to Solve Xhorse Multi Prog Remaining Usage of the Device Error? http://blog.xhorsetool.com/how-to-solve-xhorse-multi-prog-remaining-usage-of-the-device-error/ Multi-PROG authorization authorization synchronization Multi-PROG; Update Online > Authorization management Source reports synchronization after a usage threshold as the vendor remedy COMMUNITY/VENDOR REFERENCE
13_Research_Expansion/XhorseTool/EXTRACTION_STATUS.md
+21
View File
@@ -0,0 +1,21 @@
# XhorseTool extraction status
## Scope
Corpus: 58 XhorseTool category articles listed in `ARTICLE_INDEX.csv`.
## Completed extraction
`ARTICLE_FACTS.csv` contains concise source-supported extracts for 23 fetched article pages. These records cover device family, access path, tools/adapters, versions, error codes, troubleshooting practices, and important software functions. Sensitive key/immobilizer procedures are deliberately summarized rather than reproduced.
## Archive-indexed but not yet body-extracted
The remaining 35 URLs remain fully indexed and classified in `ARTICLE_INDEX.csv` and `ARTICLE_CLASSIFICATION.csv`, but their article bodies were not included in the current fetch batch. They are not being represented as fully extracted facts. Their status is therefore archive-indexed rather than body-verified.
## Evidence boundary
All XhorseTool material is `COMMUNITY/VENDOR REFERENCE`. It is not supplied Multi-PROG manual evidence. Claims that appear only here remain `NOT DOCUMENTED IN PROVIDED MANUALS` until independently confirmed by the provided manuals or a verified installed-host test.
## Source handling
The repository stores source URLs, dates, classifications, and concise extracts. It does not mirror full third-party article bodies or reproduce sensitive operational key-programming instructions.
13_Research_Expansion/XhorseTool/IMPORT_REPORT.md
+19
View File
@@ -23,3 +23,22 @@ The supplied manuals remain authoritative for manual facts. Any claim appearing
- Multi-PROG JavaScript scripting and checksum references.
Security-sensitive key and immobilizer material is recorded only as a source topic and tool/method metadata; it is not reproduced as an operational procedure.
## Integration into the repository (this pass)
The 23 `FACTS_AVAILABLE` records and the tool/adapter/device names visible in the 35 `INDEXED_ONLY`
titles were reconciled with the OBDII365 import under one register
(`13_Research_Expansion/UNIFIED_SOURCE_MANIFEST.md` / `.csv`, IDs `XT-001`…`XT-058`) and cited into:
- `13_Research_Expansion/MULTIPROG_ERROR_CODE_CATALOG.md` — error codes `040510C`, `41330004`, `88030201`, `13050102`, `13050001`, `FFFF000C`, `0404001F`, and "Error Code 1 / Error Address 2"
- `13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md` — 9S12HZ512, MC68HC05X32, ST10F269/MC9512XDT256, MPC5515, D70F3376A/3423/3426/3524, RH850 R7F701402/R7F701407, 24C256, M35080, AT17C128, SOP44/TSOP48 flash families
- `13_Research_Expansion/MODULE_CASE_STUDIES.md` — BMW FRM2/FRM3/FRM-E/REM/BDC2/BDC3/BCP/LCD/CAS4, Audi BCM2/J518/radio/A3 climate control, VW ME7.x/EDC17CP14, GM Delco E39A, KIA MEG17.9.12, Mercedes S500
- `13_Research_Expansion/OPERATIONAL_PRACTICES.md` — update, account-binding, authorization-sync, WiFi, driver, VDD/VPP, and checksum practices
- `07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md` — BCM2 Adapter V2, XDNP18/24GL/66/100/101, XDMPR8GL, MVCI PRO J2534, USB WiFi adapter
- `13_Research_Expansion/COMMON_CHECKSUMS.md`, `MULTIPROG_SCRIPT_PATTERNS.md` — checksum-function and first-script article context
Every citation keeps the `COMMUNITY/VENDOR REFERENCE` label and its own source URL/date; none of
these facts were promoted to `PRIMARY-MULTIPROG`. The remaining `INDEXED_ONLY` titles without named
tools/devices (e.g. "What is Xhorse Multi-Prog Programmer?", the FAQs article) were left as
title/URL-only entries in the manifest, per the rule against treating a title as a complete
procedure.
MANIFEST.json
+207 -42
View File
@@ -11,8 +11,8 @@
},
{
"path": "01_Knowledge_Base/AUTOMOTIVE_MEMORY_CONCEPTS.md",
"size": 4577,
"sha256": "18939cd84240076ccb936d7824a2ef8e58832e7d5049f6f9a3700b7923527eb1"
"size": 13591,
"sha256": "9eb4116dd0c0084713a17d0ff815f577bcd2cb0f4a082d5d796f63e19feca87a"
},
{
"path": "01_Knowledge_Base/ECU_TCU_CLONE_CONCEPTS.md",
@@ -21,8 +21,8 @@
},
{
"path": "01_Knowledge_Base/IMMOBILIZER_CONCEPTS.md",
"size": 4084,
"sha256": "57ab6fe08bf8e3034372f75ba57a9f882e98f6e94b8b3a55f89c8873a16d6a11"
"size": 3461,
"sha256": "8597dd156662895ba902f7f3caaf1705db70b24992bdb64a280c3f4b25325efd"
},
{
"path": "01_Knowledge_Base/MULTIPROG_ARCHITECTURE.md",
@@ -31,8 +31,8 @@
},
{
"path": "01_Knowledge_Base/README.md",
"size": 5052,
"sha256": "57d0e681092f4049946abef64e98a780d57d76122fd23f7d79e48acf25671dcb"
"size": 5227,
"sha256": "eb6d9c44c53c2f2afe4748b317da4ac8876b9bd7cf049233eee26c66f0569610"
},
{
"path": "02_Resource_Catalog/links.csv",
@@ -301,8 +301,8 @@
},
{
"path": "04_Workflows/BENCH_AND_BOOT_READING_WORKFLOW.md",
"size": 3683,
"sha256": "c9d7263430caccc2d69195492550f57626d91f408dbcd14e25862a6697fc8b87"
"size": 5676,
"sha256": "d5bf16cc9b31d994985d274ad43d6f8f3acfb9c1b80bf6ddacae4f96d593b834"
},
{
"path": "04_Workflows/ECU_TCU_CLONE_WORKFLOW.md",
@@ -311,8 +311,8 @@
},
{
"path": "04_Workflows/EEPROM_READ_WRITE_WORKFLOW.md",
"size": 4129,
"sha256": "ad39924327df36981789d7b577595e7ed05afa931adb25a21551a774b16f20be"
"size": 4098,
"sha256": "3e67d0c3f8972ecd51f9dd9a92e820828ada341b3c6279249286b404c1b3c7f2"
},
{
"path": "04_Workflows/IMMOBILIZER_BACKUP_RESTORE_WORKFLOW.md",
@@ -326,13 +326,13 @@
},
{
"path": "04_Workflows/MCU_READ_WRITE_WORKFLOW.md",
"size": 3925,
"sha256": "6003274be3a54759f3cb44b78799f54bd8c4203605acece896e27742b97b81d3"
"size": 7195,
"sha256": "e163139df2f68ef506746a7802b55f26e035b891d4883d424b16e9c802b2b320"
},
{
"path": "04_Workflows/README.md",
"size": 1823,
"sha256": "71122a2bfed9bd8c15c272c8d7b2091a2a5784d4eb8a2b730628e01041867059"
"size": 2377,
"sha256": "0ee2677bb82948d96e6b5f42e265e873c456cd149c86352f4928b21e5e0a9def"
},
{
"path": "04_Workflows/VIN_MIGRATION_WORKFLOW.md",
@@ -456,8 +456,8 @@
},
{
"path": "07_Authorized_Key_Immobilizer_Work/GODIAG_XHORSE_HARDWARE_REFERENCE.md",
"size": 5942,
"sha256": "bdbca2b0d53fa667775b7ee4f4a7ab0cf55140269aadfdf459bddf1fc69eb32f"
"size": 12435,
"sha256": "62c0501bb84f2daafa2e0fc1c8a73060b71ac3343b0503e073ffacf1025e510f"
},
{
"path": "07_Authorized_Key_Immobilizer_Work/README.md",
@@ -751,8 +751,8 @@
},
{
"path": "13_Research_Expansion/COMMON_CHECKSUMS.md",
"size": 246,
"sha256": "4f752a39a7c250c3250d519eda2f9e3b0ef5b50b8692793fda8903aca2bc7b30"
"size": 1452,
"sha256": "35e845c05371670f2f0f939ce05f75c5aa16bb0010bc321adbd7c9d0e5a471e4"
},
{
"path": "13_Research_Expansion/COMMON_ERRORS.md",
@@ -804,6 +804,16 @@
"size": 5958,
"sha256": "297aa816f1f83ba0a62a0ab751b4baf0b193e3cee46017bd5630c8e4cc885cef"
},
{
"path": "13_Research_Expansion/MCU_EEPROM_FLASH_DEVICE_REFERENCE.md",
"size": 9681,
"sha256": "e2a40e93f0ea38dda049c8dbdb19e72cefa896b6ef4a21ef0ea1965baf985e68"
},
{
"path": "13_Research_Expansion/MODULE_CASE_STUDIES.md",
"size": 14674,
"sha256": "2beaefa67c4ffaa3a60fcf0fb3abae86643c2d39a9c644fb5e61df3447ec7bd2"
},
{
"path": "13_Research_Expansion/MULTIPROG_API_REFERENCE.csv",
"size": 1497,
@@ -811,14 +821,19 @@
},
{
"path": "13_Research_Expansion/MULTIPROG_API_REFERENCE.md",
"size": 2588,
"sha256": "b2f938dcd95963ab709f43825770900b19f7c0d3c82d4aa064ca591e7b929142"
"size": 3333,
"sha256": "7027ee96ac10748d545a78bc98741d0146421e363760969fb81ceca25f849353"
},
{
"path": "13_Research_Expansion/MULTIPROG_BUILTIN_FUNCTIONS.md",
"size": 512,
"sha256": "767322b27000326f726cde0923bbb919a7b295c42c2a2969bff62188f9df4cc2"
},
{
"path": "13_Research_Expansion/MULTIPROG_ERROR_CODE_CATALOG.md",
"size": 11656,
"sha256": "27ff377c44c3d3d12ddbfac8b943bddd7455debea55a410f968fc3012fd38a2f"
},
{
"path": "13_Research_Expansion/MULTIPROG_HOST_FUNCTIONS.md",
"size": 793,
@@ -826,8 +841,78 @@
},
{
"path": "13_Research_Expansion/MULTIPROG_SCRIPT_PATTERNS.md",
"size": 3378,
"sha256": "8562808fb376e2263f532493915b93011febfb01cb81c0f3e21b819aac58a3f9"
"size": 4141,
"sha256": "ea210dbb06567be439fa0904ad93b82323ce00f1675b12a6ca7337df1cc91c79"
},
{
"path": "13_Research_Expansion/OBDII365/ARTICLE_CLASSIFICATION.csv",
"size": 9672,
"sha256": "ab439cd4afd06039c20db259745e26656213eb17d41678ab790add7ba3b1832d"
},
{
"path": "13_Research_Expansion/OBDII365/ARTICLE_CLASSIFICATION.md",
"size": 4339,
"sha256": "4dafe4003fbe9cb93619f68fe16ae5e42257148f7f91921a1d64945195b3721f"
},
{
"path": "13_Research_Expansion/OBDII365/GAP_ANALYSIS.md",
"size": 2519,
"sha256": "d14377a6dc75d33645d4cce07fafed42ee723fc50e6b0d620581f5f3fd8dc554"
},
{
"path": "13_Research_Expansion/OBDII365/IMPORT_REPORT.md",
"size": 3336,
"sha256": "254c6be88548d59875e16f9daee7546e1ea97c0b612424e4afeb0d68fa64db30"
},
{
"path": "13_Research_Expansion/OBDII365/raw/OBD-020-godiag-connection.md",
"size": 596,
"sha256": "1220b04aba75c5dc8fabf160ce57d57e60633cec45f661305c1acfe3aeb68e78"
},
{
"path": "13_Research_Expansion/OBDII365/raw/OBD-029-eeprom-adapters.md",
"size": 590,
"sha256": "167fcebef7c6f5fa03011a8631ab343704d6e7b61f2c20669ef3d2a054dc0d3b"
},
{
"path": "13_Research_Expansion/OBDII365/raw/OBD-034-rh850-update.md",
"size": 617,
"sha256": "16b70f628c533395e29c8b4eebeee65470bfe02393d3584624b00dd8a42c9da3"
},
{
"path": "13_Research_Expansion/OBDII365/raw/OBD-035-software-driver.md",
"size": 594,
"sha256": "d67142a0a529f1a6f73afb56caef1262226d18322a391bbf1146e178a4b4bb24"
},
{
"path": "13_Research_Expansion/OBDII365/raw/README.md",
"size": 335,
"sha256": "3edda9c0c3a46915fedbe16ec580ce1f2b20b90a64d68e81b845f263ecdc2991"
},
{
"path": "13_Research_Expansion/OBDII365/raw/TAG_ARCHIVE_2026-09-22.md",
"size": 5208,
"sha256": "748bd632a927e290430b685bb5bf4a1995043a95e53c2d57fc50cdd7b26d4d6a"
},
{
"path": "13_Research_Expansion/OBDII365/RAW_ARTICLE_INDEX.csv",
"size": 15064,
"sha256": "ad264616dfa1e421bb5157968e9e9c21ff4ead793172933ea653c72d2c0769f1"
},
{
"path": "13_Research_Expansion/OBDII365/README.md",
"size": 2126,
"sha256": "7d90a324529e05a8a583f0df55e1d3203938efec40068f5147d0d0e73aab6f25"
},
{
"path": "13_Research_Expansion/OBDII365/TOOLS_METHODS.csv",
"size": 12445,
"sha256": "315c659e3651d1ce4a4bc555f6ae04525a679138551b89bf392605dff4085b6d"
},
{
"path": "13_Research_Expansion/OPERATIONAL_PRACTICES.md",
"size": 10526,
"sha256": "fbe977f9290d53885ccfe3d16e28e6d85c1bf0725072692611d596733f934785"
},
{
"path": "13_Research_Expansion/SCRIPT_ARCHITECTURES.md",
@@ -864,6 +949,16 @@
"size": 1234,
"sha256": "348b55eec13d938661dfba8adc30013ce4291ee70c9f06297fb1636f75d170c2"
},
{
"path": "13_Research_Expansion/UNIFIED_SOURCE_MANIFEST.csv",
"size": 42169,
"sha256": "411daae97cc2759431b24c98c342d775a1cc6f1a4344f24e09614983da9bae53"
},
{
"path": "13_Research_Expansion/UNIFIED_SOURCE_MANIFEST.md",
"size": 4882,
"sha256": "dcdd8441ca5f4f91ed1df18b133c56a577429c08aad56008a8b09785e85dcf33"
},
{
"path": "13_Research_Expansion/Unsorted_Review/3C0909605F.md",
"size": 336,
@@ -909,6 +1004,41 @@
"size": 2982,
"sha256": "415affdda569ee68f46f3333a3dda8dea1f5365fd6bcd4674654950cab80ba0d"
},
{
"path": "13_Research_Expansion/XhorseTool/ARTICLE_CLASSIFICATION.csv",
"size": 7506,
"sha256": "484a7c62cd0ab2ab6df918a597425801b8062467feba1434a2d65227fdfb7f1d"
},
{
"path": "13_Research_Expansion/XhorseTool/ARTICLE_FACTS.csv",
"size": 8054,
"sha256": "034b61fd4f8fd4b7055d17d16d5bd591f56af2c9519959cf3329a2908c02fb0a"
},
{
"path": "13_Research_Expansion/XhorseTool/ARTICLE_INDEX.csv",
"size": 11399,
"sha256": "f6d463a9ed3c7fc5641c63f35a77258c12e7b4a5d050adaad47d7fe23fdffaec"
},
{
"path": "13_Research_Expansion/XhorseTool/EXTRACTION_STATUS.md",
"size": 1357,
"sha256": "1e311c456815662088bcc69b47b4cc03cf30dbcc6b2b044c6839c9c4faa45c66"
},
{
"path": "13_Research_Expansion/XhorseTool/IMPORT_REPORT.md",
"size": 3616,
"sha256": "d71675c1e8f7709809e6334cff691edf41eb589b558a7ee2b416a01c3d4fee80"
},
{
"path": "13_Research_Expansion/XhorseTool/README.md",
"size": 1483,
"sha256": "e97a26bcf5b7c930aaf6271e778fa980a74e6c19359a8ef5369613587ad66a69"
},
{
"path": "13_Research_Expansion/XhorseTool/TOOLS_METHODS.csv",
"size": 8416,
"sha256": "c7855fdbfb39cc824bece1cb4437056c0fb0ccbc200ff8e611163c0ffe23e14b"
},
{
"path": "14_Repository_Review/empty_files.csv",
"size": 190,
@@ -919,6 +1049,11 @@
"size": 85,
"sha256": "c14965e0a31cae796c6a18d769139250bbc303d0a20a12ab6f8bb21ffcda68ba"
},
{
"path": "14_Repository_Review/MANUAL_AUDIT_AND_GAP_ANALYSIS.md",
"size": 9610,
"sha256": "4db81a4cb96def568f6050646b00c0b887ec2b388eaff0924fce6220ddd9961a"
},
{
"path": "14_Repository_Review/problems_summary.json",
"size": 270,
@@ -981,13 +1116,13 @@
},
{
"path": "17_MultiPROG_SDK/docs/DEVICE_API.md",
"size": 2631,
"sha256": "87bce67f1a4b174db5f032a17cc9ba30108ad76984616990e586905f8b85c6da"
"size": 2173,
"sha256": "3aa530ae6e468797efa69dd1673c9da272e835ef9989c38d3eed123be8464fb8"
},
{
"path": "17_MultiPROG_SDK/docs/DIALOG_API.md",
"size": 1636,
"sha256": "1b82a17f970434e7d8a4e7ab8543620a788c5f83df40b7f73097ea06250a4bd1"
"size": 1780,
"sha256": "d3cd47c222ae11dd1166ecc232fa879a805534c1450cbe15aa9d228eed5ace5d"
},
{
"path": "17_MultiPROG_SDK/docs/EEPROM_API.md",
@@ -996,8 +1131,8 @@
},
{
"path": "17_MultiPROG_SDK/docs/FILE_API.md",
"size": 2604,
"sha256": "38955b6dde3be973f71e03bf8f97a202e801517ba7923a00fb7b960de830a33c"
"size": 2366,
"sha256": "9a297168a570311cf9d5acb8e913930ed9f61f1ec79aac09a215ec608b321c57"
},
{
"path": "17_MultiPROG_SDK/docs/FLASH_API.md",
@@ -1009,21 +1144,31 @@
"size": 1795,
"sha256": "3054d201d7622b261a6e991ea8f9e6d3646c4d2739f878a22518ed1858ec1f1e"
},
{
"path": "17_MultiPROG_SDK/docs/MANUAL_API_REFERENCE.md",
"size": 14762,
"sha256": "9c2d26c18ab476091fdbe38250a0c4d28f2df1b6824bd51ce1363675438c4d83"
},
{
"path": "17_MultiPROG_SDK/docs/README.md",
"size": 2459,
"sha256": "1e4c5ba5e7facbb1601e58eac8aa1670ab10f8f05b6098092e07b1e7776c1027"
"size": 2914,
"sha256": "235e69496ec235e6181b48ec32ff9c197cccc136c6889e8aeedd2c41db96f087"
},
{
"path": "17_MultiPROG_SDK/docs/UI_API.md",
"size": 1439,
"sha256": "3615ba48b02319e831e25a05339edee8161e86d6f7ad18e2c1531530433180a4"
"size": 1100,
"sha256": "c0d6365e1f09ca39b1e35852933eabded0433c7146032fb0ff982ee1df5b9b9f"
},
{
"path": "17_MultiPROG_SDK/examples/example_readonly_report.mjs",
"size": 555,
"sha256": "2774c0d4405c1f0bb5ddccda253381281ae5cde59d8df1792ccce344411005d4"
},
{
"path": "17_MultiPROG_SDK/examples/javascript/MANUAL_SNIPPETS.md",
"size": 2544,
"sha256": "dfb68881b715a97f3177dbf56c27c6437b3afe7af501de544364ce27ff1abf5d"
},
{
"path": "17_MultiPROG_SDK/package.json",
"size": 398,
@@ -1156,13 +1301,13 @@
},
{
"path": "17_MultiPROG_SDK/tests/template_catalog.test.mjs",
"size": 1556,
"sha256": "420e2f9f53fe58871de762d61fc8b3e24cc3ef38ba695cb926ebd7381e6b7899"
"size": 1637,
"sha256": "51053034f7b5bdd48a912e821d23d61a4e9e2e6a8dba64bf7f156accf34743b2"
},
{
"path": "17_MultiPROG_SDK/tests/workflow_templates.test.mjs",
"size": 1370,
"sha256": "c4755f971257e7b5d86ec0084cfa89df0f5bdb9016946ad6e0be467b90996107"
"size": 1483,
"sha256": "3943a2ba75c696d7439c954182e8bb2d8b0e6979dcb4d25a6d312dc9f1c07572"
},
{
"path": "17_MultiPROG_SDK/utilities/_verify_crc.mjs",
@@ -1276,8 +1421,28 @@
},
{
"path": "CONTRIBUTING.md",
"size": 6701,
"sha256": "1fe4ed6535780083f9d06dddd9f44393789024ccaffad53929c78e42e20c25d0"
"size": 6647,
"sha256": "12f86ec13b5c248860bea97d80a45068234d4d0c911805c68f90870960d3617c"
},
{
"path": "docs/Multi-PROG Script Manual (EN).pdf",
"size": 3417546,
"sha256": "2865ce2ad9a60fd4f79a68d9f214a7be4a1568120d4d746f10415e3eb89495b0"
},
{
"path": "docs/Multi-PROG User Manual.pdf",
"size": 10211404,
"sha256": "4d18c6535f448b7ffb60e10aa24b69cf7ffdcb4c3c98762c5894054e959d2910"
},
{
"path": "docs/reports/api-coverage-analysis.md",
"size": 7710,
"sha256": "addd6224733fcd86c6fbb32d8a83f9ecfc7da892140f8b9d9905ab000495df8d"
},
{
"path": "docs/reports/knowledge-consistency-report.md",
"size": 12308,
"sha256": "f280e84f5be63bb391d45ab06a7c2881ba67b8d1d8839115962b1566bb5d8955"
},
{
"path": "LICENSES.md",
@@ -1286,13 +1451,13 @@
},
{
"path": "MANIFEST.json",
"size": 52943,
"sha256": "0f9ff6657d3815f814d554ebba7af537618c7b3a6836facf8738ef8a86f8f7ed"
"size": 59707,
"sha256": "f1fc113070275c11fdee1b355a04783001c976bb686a2df8fb5bbddcaf9bc777"
},
{
"path": "README.md",
"size": 6860,
"sha256": "c92cc334c85330972bf1d40bbb9c81421b12d62e7be4bdab8a145156cd01c2ad"
"size": 7039,
"sha256": "e2954073c216fb9ce398ce7cccc656a54b4e3888ecf6727b7c01ab9b1ef3bb44"
},
{
"path": "REPOSITORY_MATURITY_ASSESSMENT.md",
README.md
+1 -1
View File
@@ -36,7 +36,7 @@ This package delivers three integrated components:
- **[09_Collected_JS/](09_Collected_JS/)** — Reference JavaScript libraries for binary processing, checksums, encoding
- **[10_Source_Repositories/](10_Source_Repositories/)** — Repository snapshots and metadata
- **[11_Download_Reports/](11_Download_Reports/)** — URL resolution, fetch, and analysis reports
- **[13_Research_Expansion/](13_Research_Expansion/)** — Master catalogs, discovered APIs, script patterns, development guides
- **[13_Research_Expansion/](13_Research_Expansion/)** — Master catalogs, discovered APIs, script patterns, development guides, and article-derived reference (OBDII365/XhorseTool source manifest, Multi-PROG error code catalog, MCU/EEPROM/FLASH device reference, module case studies, operational practices)
### Repository Maintenance
- **[14_Repository_Review/](14_Repository_Review/)** — Inventory scans, problem analysis, validation reports