Starts with the prior read-only adapter/BCM audit. All imported data is handled only on this device, in this tab. This page has no Bluetooth, OBD, cloud upload, As-Built write or programming capability.
1 · Load read-only evidence
Open a transport-audit JSON or compatible combined snapshot from Edge Config Lab. You can also keep the included November 6 reference snapshot.
2 · Add a FORScan network reference
Optional CSV with headers module,network, or JSON with modules. This is a topology cross-check; network placement is not proof of access.
Module evidence matrix
“Verified” means an attributed identifier response—not configuration compatibility or safe programming.
| Module | Reported / ref bus | Audit outcome | Evidence gate | Next read-only step |
|---|
Compare two audit snapshots
Import another audit to identify differences in module visibility and sender-verification status. No raw identifiers are kept or exported.
No second snapshot loaded.
Read-only testing sequence
Adapter presets 33/53 were confirmed; prior BCM identifier response was attributed and measured at 229 ms.
Validate MS-CAN address, sender and route from trustworthy material before testing. No guessed commands.
Research HS-CAN3 gateway diagnostic paths, possible session limitations and response attribution.
Keep disabled until schema, transport, backup and recovery are tested. No write operation here.
Do not run new diagnostic scans while driving. Use a parked vehicle and a healthy electrical system. An unanswered request does not mean a module is absent. All feature recipes remain research-only; model-year and firmware matching is still required.