The OBDStar X300 Classic G3 programmer has unveiled a groundbreaking new feature: MQB All Keys Lost (AKL) Sync Data Calculation, eliminating the need for third-party software. This innovation simplifies immobilizer synchronization for VW, Audi, SEAT, and Škoda (MQB platform) vehicles, offering a faster and more cost-effective solution for locksmiths and automotive technicians.
In this article, we’ll explore:
- How the new Sync Data Calculation feature works
- Supported modules and procedures
- Compatibility with other tools
- Step-by-step execution
How the OBDStar G3 MQB AKL Sync Calculation Works
Requires VW/Audi/Skoda/Seat software version 45.48 and onwards. New software version is available to download on April 22nd, 2025.
Also need to use with the OBDSTAR RH850/V850 kit.
Previously, generating sync data for MQB-platform vehicles required:
- Extracting data from multiple modules (Instrument Cluster, ECU, Transmission, ELV). Data is usually required from all 4 modules/locations in order to calculate sync data.
- Using third-party tools (e.g., VVDI, AVDI, or manual calculation)
- Manual file transfers and decryption
Now, the OBDStar G3 can:
✅ Read data directly from the vehicle’s modules.
✅ Calculate sync codes automatically (no manual hex editing).
✅ Program dealer keys without external software.
Key Features:
- Free service (no token system)
- Three sync calculations per day (limits abuse)
- Supports multiple modules (Cluster, ECU, Transmission, ELV)
- Works with other diagnostic tools (e.g., ACDP, DC76 for data extraction)
Process for MQB AKL Sync Calculation
1. Accessing the MQB AKL Function
- Navigate to:
VW/Audi/SEAT/Škoda (MQB) – MQB Meter- All Keys Lost - Ensure the device is connected to stable network (required for sync calculation on OBDSTAR’s server).
2. Reading Required Module Data
The system needs data from four critical modules:
1). Instrument Cluster (Dashboard IMO Data)
-
- Supported versions are listed (expanding regularly).
- Can be read via:
- OBDStar G3 directly
- Other tools (e.g., ACDP) if files are unencrypted
2). ECU (Engine Control Unit)
-
- Supported ECUs (e.g., EDC17, Simos series)
- Pinout diagrams are provided for direct reading
3). Transmission Module
-
- Some models (e.g., DQ200 G2) require immobilizer data.
- OBDStar offers 7-in-1 or other gearbox connector kits for easier access.
4). ELV (Steering Column Lock)
-
- Can be read via:
- New C4-06 adapter (upcoming release)
- The collection cable method
- Can be read via:
Method 1: Read immo data by RH850/V850 kit.
Method 2: Collect ELV authentication data and calculate immo data
3. Calculating the Sync Code
Once all data is collected:
- Select “Calculate Sync Code”
- The system processes the data and generates the immobilizer sync.
4. Programming a New Key
- Use “Make Dealer Key” to program a new key via OBD.
- No need for external key programmers.
Compatibility with Other Tools
A major advantage of this feature is flexibility in data sourcing:
- Instrument Cluster Data can be read using:
- OBDStar G3
- ACDP, VVDI, or other tools (if unencrypted)
- ECU Data can be extracted via:
- OBDStar DC76 or G3 itself
- Direct ECU bench reading (pinout guides provided)
This means technicians aren’t locked into OBDStar’s ecosystem—existing tools can still be used.
Limitations & Considerations
- Three sync calculations per day (prevents misuse).
- Server connection required (no offline mode).
- Some modules may still need adapters (e.g., C4-06 for ELV).
- Not all MQB variants supported yet (but expanding).
Keep an eye on OBDSTAR’s upcoming updates.