License MQB Locked Nec 35xx for programmer Poldiag (for example Poldiag MB) interface.
POLDIAG MQB - the world's first solution for adding keys (including in cases of complete AKL loss) and odometer correction for VAG (Audi, VW, Skoda, Seat) vehicles on the MQB platform (2012+).
- Compatible with white panels Polo (6RF 920 861), Octavia A7 (5E0 920 851)
- No tokens required for instrument clusters with ID48 keys
- No token required for adding MQB48 keys
- No tokens required for odometer correction
Main Features of Poldiag MQB:
- Full read and write of Renesas and NEC35xx processors (in-circuit)
- Decoding of IMMO data (CS, VIN, MAK, keys)
- Odometer reading correction
- Instrument cluster cloning
- Creation of VVDI2 file for dealer key preparation
- Key programming (requires POLDIAG OBD2 interface, not included in the kit)
- Block synchronization with one click
- Reading of NEC 35XX processors (including encrypted ones) in other vehicles (e.g., Mercedes, Opel, Toyota, etc.)
Supported Instrument Clusters by Poldiag MQB (list is not exhaustive, constantly expanding, up-to-date as of the release date):
- VDO
- JCI (JOHNSON CONTROL)
- VISTEON
Download the full list of supported Poldiag MQB instrument clusters
Unsupported Instrument Clusters by Poldiag MQB:
- Instrument clusters with RH850 processor, for example R7F7
- Instrument clusters with NEC D70F3426A + external EEPROM
For enhanced functionality and convenience, we recommend purchasing the Poldiag OBD2 interface.
ATTENTION!
IOBD Store is not responsible for the functionality of the POLDIAG programmer. The programmer is non-returnable.
An activated module or license cannot be returned.
If you have entered the wrong key or device number, the return is not valid. It is not possible to modify the license for another device.
After status update to "Waiting for activation", the data has already been sent to the developer for activation. The order cannot be canceled or corrected starting from this status update.
Pay attention to all information specified in the description of modules and scripts taken from the manufacturer. We are not responsible if the information is not correct or there are some differences from the reality. In the disputed situation, it is necessary to look for a solution to the issue to the manufacturer.
Our store is not responsible for the functionality of the software module. We cannot guarantee the declared functions since we are not the developer.