Windows & drivers
Use a Windows installation compatible with the supplied CORE build. Install the adapter manufacturer’s official drivers separately.
The right connection.
The right expectations.
Compatibility is specific to the adapter, protocol, module and software version. A manufacturer name alone is not a support guarantee.
| Engine family | Diagnostic coverage | Active routines / writes |
|---|---|---|
| Detroit | Verify against exact ECU and build | Not validated for release here |
| Cummins | Verify against exact ECU and build | Not validated for release here |
| PACCAR | Verify against exact ECU and build | Not validated for release here |
| Volvo / Mack | Verify against exact ECU and build | Not validated for release here |
| International / Navistar | Verify against exact ECU and build | Not validated for release here |
| Legacy Caterpillar | Verify against exact ECU and build | Not validated for release here |
These are development target families, not a certified supported-vehicle list.
Adapter & protocol
CORE’s existing connection work uses RP1210 interfaces. Identify the installed adapter and supported protocol before beginning a diagnostic session.
Exact module identity
Capture ECU name, hardware number, software version and engine details. These are required to evaluate coverage beyond basic connectivity.
Need a compatibility review?
Send your vehicle model/year, engine, ECU identity, adapter model and CORE version. Exclude passwords, private keys and customer information that is not needed.
Prepare a support request ↗