VBID (Vehicle Binary Identifier) is a NEUROSUITE tool designed to quickly identify ECU binary files. It reads hardware numbers, software versions, MCU IDs, calibration codes, and other key identifiers directly from the binary, without requiring any diagnostic hardware. Useful when you receive a file without any context and need to know exactly what ECU it came from.

VBID is free to run, but you must have a minimum balance of 10 tokens in your account to use it. No tokens are deducted when using VBID. The 10-token balance acts as a verification requirement to prevent abuse of the free service.

VBID supports most modern Tricore and Aurix ECUs, including:
• Bosch: MED17, EDC17, ME17, MG1, MD1, MEVD17
• Continental: SIMOS 8 through 18, PPD, SID series, EMS series
• Delphi: DCM3.5, DCM3.7, DCM6.1, DCM6.2, DCM7.1
• Siemens/VDO: SDI4 through SDI21
• Valeo: VD56 series
Full ECU reads (FLASH + EEPROM) provide the most complete identification.

First, make sure you are loading a COMPLETE FLASH read and not a virtual read (calibration only) or a partial file. If the file is a full read and still not recognized, it may be a newer ECU variant that we have not yet mapped. Email the file to support@neurosuite.ca and we will add support, usually within a few business days.

No. VBID requires an active internet connection to access the identification database. All identification logic runs server-side to ensure the database is always up to date with the latest ECU variants.

Absolutely, this is one of the most common uses. Before writing, run VBID on the file to confirm the hardware number, software version, and MCU ID match your target ECU exactly. This simple check prevents most bricking incidents caused by writing the wrong file to the wrong ECU.

VBID works directly on BIN files. For encrypted FRF or ODX-F containers, you must first extract the BIN using your flash tool or a dedicated FRF extractor, then run VBID on the extracted BIN.

Our system automatically sends the token key to the email used for the PayPal purchase. Allow 15 to 20 minutes to receive the email. If you do not receive it after 30 minutes, check your spam folder before contacting support@neurosuite.ca with your PayPal transaction ID.

The price of the tokens can be found in the “BUY TOKENS” section. Volume discounts are automatically applied: 5% off at 100 tokens, 10% off at 160 tokens, and 15% off at 320 tokens.

Your tokens expire one year after the date of your last purchase. Example: if you have 100 tokens remaining and leave them unused for more than 365 days, the system will lock your token key. As soon as you make a new purchase, say 20 tokens, your key is unlocked and your balance becomes 120 tokens. This way you never lose your tokens as long as you recharge at least once a year.

Simply make a new PayPal purchase using the same email address you used for your previous purchase. Your existing token key will be topped up automatically, no new account or new key is created. If you pay with a different email by mistake, contact support@neurosuite.ca so we can merge the balances.

No. Tokens are only subtracted when the file operation is fully completed. You can open and analyze a file to check compatibility without any token subtraction. A confirmation message always appears with your total remaining balance and the operation cost before any token is debited.

Yes, the software is not PC locked. You can run NEUROSUITE software on as many computers as you want with the same token key. An active internet connection is required for the software to work.

Unlimited access is not viable considering the level of support and the ongoing algorithmic development we provide.

Take PCR2.1 as an example: introduced in 2020, it was exclusive at the time, and has benefited from four years of continuous algorithmic refinement unmatched by any other software available today. If you frequently perform PCR2.1 immo off procedures and prioritize reliability for your customers, a limited but refined immo off software is more prudent than any “unlimited” alternative.

IMMOFF17 also remains the only software capable of accurately correcting checksums across all relevant sectors. Most competing tools only correct the calibration sector checksum, while the immo bytes are located in a separate sector. This causes widespread issues for users of other tools. IMMOFF17 ensures comprehensive checksum correction, addressing a problem that affects the majority of users in the industry.

Tokens are digital goods delivered instantly and are non-refundable once the token key has been issued. If you encounter a technical problem that prevents you from using the software, contact support@neurosuite.ca before requesting a refund, we will resolve the issue in most cases.

Yes. Every completed operation is saved on our server for 1 year. You can re-process the exact same file at no additional token cost during this period. Tokens are only deducted once per unique file.

NEUROSUITE software downloaded from our download section is encrypted and packed to prevent cracking and reverse engineering. This protection also blocks antivirus engines from analyzing the executable, which sometimes triggers false positives. We recommend adding the NEUROSUITE folder and all its executables to your antivirus exclusion list.

Follow these steps in order:
1) Disable antivirus, firewall and Windows Defender.
2) Try a different internet connection (mobile hotspot works well for testing).
3) Synchronize your PC clock: enable Windows automatic time synchronization.
4) Reinstall OpenSSL: https://slproweb.com/download/Win32OpenSSL_Light-3_6_2.exe

Tricore ECUs such as BOSCH MED17, EDC17 and CONTINENTAL SIMOS 8 through 18 can be fully read with many different tools. We recommend AUTOTUNER, ALIENTECH KTAG, CMD FLASH and BFLASH. For OBD operations on supported platforms, PCMFLASH is the most reliable choice.

A virtual read (V-Read) only contains the calibration (MAP) area of the ECU. It is typically enough for basic tuning but does NOT contain the immo bytes, bootloader, or other critical areas. A full read contains the complete FLASH memory including all sectors and is required for IMMO OFF, cloning, and most NEUROSUITE operations. Always provide a full read when possible.

NEUROSUITE software runs on Windows 7, 8, 10 and 11 (32-bit and 64-bit). Linux and macOS are not supported natively. You can run the software inside a Windows virtual machine (VMware, VirtualBox, Parallels) if you are on another OS, as long as internet connectivity is available to the VM.

Email support@neurosuite.ca during support hours (Monday to Friday, 10h00 to 16h00 GMT-5). To speed up resolution, always include:
• Your token key
• Which NEUROSUITE software you are using
• ECU make, model and software version
• The complete files, zipped (original read, modified file, re-read after write)
• Exact error message or screenshot
• The tool used to read and write the ECU
• What you have already tried

U-codes are mapped to P-codes using two simple patterns:
U0XXX = PCXXX
U1XXX = PDXXX
U2XXX = PDXXX
Just use the equivalent P-code in DTC DISABLER.

The full list of tested files is available here: https://www.neurosuite.ca/immoff17_medc17_filelist.html

Yes. Always load an unmodified original file first and provide a full read whenever possible. Modified or virtual files reduce the reliability of DTC removal.

If your file is not in the database, DTC DISABLER will prompt you to upload it to our server. Within a few seconds you should be able to process your file. The algorithm works best with a complete (full) file read, not a virtual read.

If your file cannot be processed for any reason, DTC DISABLER will prompt you to FLAG the file. Flagging alerts us to manually add it to the server. We usually process flagged files the same day. You will be notified by email as soon as your file is ready.

Between 15 minutes and 48 hours, depending on the complexity of the file and our current workload. Most flagged files are processed within the same business day.

DTC DISABLER can disable virtually any P, C, U or B code stored in the ECU calibration. It patches the DTC table so the code cannot be triggered or stored. Some critical codes tied to hardware safety (airbag, immobilizer authentication) are not recommended for removal.

Yes. Checksum is automatically corrected after DTC modifications, on all relevant sectors of supported ECUs. No manual correction is required.

Run through this checklist:
1) Is ESP OFF?
2) Is the clutch signal working? (Verify with VCDS, engine cruise switch, or by searching online for your specific model)
3) If the car is AUTOMATIC or DSG, did you select the DSG option in LAUNCH17?
4) Did the engine rev hit a soft limiter? If the car has NO ESP button, you need to RAISE the “standby nmax” map in the calibration. If you cannot modify that map, set launch control RPM below the soft limiter RPM.

We recommend starting with the default settings. Optimal values depend on your setup (turbo size, exhaust, engine displacement).

Reference video: https://www.youtube.com/watch?v=T3Gub4-WnTQ

Presets:

VW/AUDI 2.0T MANUAL, stock turbo
SPEED: 5 km/h
RPM ATDC: 4000
TIMING ATDC: 15
RPM IGN CUT: 4200
RPM NLS: 5800

VW/AUDI 2.0T DSG, stock turbo
SPEED: 5 km/h
RPM ATDC: 3950
TIMING ATDC: 15
RPM IGN CUT: 4010
TCU DSG LAUNCH RPM: 4000 (TCU must be reflashed)

VW/AUDI 2.5 TFSI
SPEED: 5 km/h
RPM ATDC: 4400
TIMING ATDC: 16
RPM IGN CUT: 4600
RPM NLS: 6300

VW/AUDI 3.6 VR6
SPEED: 5 km/h
RPM ATDC: 4300
TIMING ATDC: 12
RPM IGN CUT: 4500
RPM NLS: 6300

Warning: more aggressive settings mean more mechanical and thermal stress on the engine.
More ATDC timing degrees = louder bang.

Aggressive example:
TIMING ATDC: 18
RPM IGN CUT: 4800
This combination produces a very hard cut and loud pops, but should only be used on well-built engines.

The TCU DSG launch RPM must be set 50 RPM higher than the ECU launch maximum RPM.
Example: TCU DSG Launch at 3500 RPM, LAUNCH17 timing at 3350 RPM, ignition cut at 3450 RPM.

Yes. You can re-edit your launch settings at no additional token cost, but you must start from the exact same original file that was used the first time.

Yes, for both MED9 and MED17. For MED17 we have specifically tested and validated PCMFLASH for OBD writing. Other tools may also work depending on the platform.

Errors like “Can't locate freespace offset” or “Can't locate variable” usually occur when the file is a virtual read (calibration only). LAUNCH17 requires a complete file obtained via boot or bench mode using tools such as MPPS, BFLASH, AUTOTUNER, KTAG, TRASDATA, KESS and others. Only PCMFLASH can currently obtain a complete file by OBD.

The initial file saved by AUTOTUNER is named “BENCH_NR.BIN”. This is a virtual file containing only the MAP calibration area. It can be flashed through OBD or BENCH but is NOT suitable for applying LAUNCH.

1) After the read is complete, locate and copy the Bench-backup.zip file, typically found in “Documents\Autotuner ECU backups”, to your Desktop.

2) Extract Bench-backup.zip to a new folder. The files represent the full ECU read: DFLASH = EEPROM, IFLASH = FLASH.

*If AUTOTUNER saved the FLASH as two files (iflash0 and iflash1), you may need to merge them before patching.

3) Run LAUNCH17, select the FLASH file, and save as iflash0_LAUNCH.bin.

*Unlike other tools, AUTOTUNER does NOT automatically correct the checksum on backup file writes. If you modify any binary inside the zip, checksum correction is mandatory.

4) Perform iflash checksum correction.

5) Delete the original IFLASH0.bin and rename your new iflash0_LAUNCH.bin to IFLASH0.bin.

6) Zip the entire folder again, for example LAUNCH_BACKUP.zip. You can use the extension .zip_noread to skip the full ECU re-read.

7) In AUTOTUNER, click WRITE and select the .ZIP file.

Done.

Mandatory first step
After installing the ECU, always perform a full fault code clear. Old immobilizer-related DTCs remaining in memory can prevent the vehicle from starting.

Verification checklist

1) ECU and MCU ID specificity
An IMMO OFF file is generated for one specific and unique MCU ID, and cannot be cloned. The IMMO OFF file will only work on the exact ECU for which it was generated. Never mix files between different ECUs, even if hardware and software appear identical.

2) Software compatibility
Confirm that the ECU software version matches the exact engine type and model revision of the vehicle.

3) Diagnostic Trouble Codes
Scan the vehicle for all DTCs. When replacing an ECU, verify that no other vehicle-side issue is blocking start authorization.

4) Write and checksum verification
After writing the IMMO OFF file, immediately perform a re-read of the ECU. Compare the re-read against the generated IMMO OFF file to confirm write integrity and checksum validity.

If the issue persists
If all checks above pass and the vehicle still does not start, provide the data listed below to support.

Required files (zipped)
A) Original ECU full backup, if available
B) Replacement ECU full backup
C) Generated IMMO OFF file
D) ECU re-read performed immediately after writing the IMMO OFF file (confirms correct writing and checksum integrity)

Please answer the following questions:
• What tool was used to read and write the ECU?
• If an MCU ID was requested, which MCU ID was provided, and does it match the ECU that was written?
• Does the starter motor crank?
• Is this only an ECU replacement?
• Is this a total key loss situation?
• Are the keys still paired with the BCM?
• Can you provide a full vehicle scan including all DTCs?
• Why was the ECU replaced? Please describe the situation in detail.

1) Identify the original car software version (example: “03L906023DM / 03L906023DL”).
2) Obtain a replacement ECU with the exact same software version, or update your existing ECU (see instructions below).
3) Perform a full read of the replacement ECU and apply IMMOFF17 to deactivate the immobilizer in the FLASH or MPC.
4) Write the saved flash file to your replacement ECU.

Why avoid a different software version?
SIMOS and PCR2.1 ECUs include a distinctive “POWERKLASS” protection. This deliberately prevents installing a more powerful software on a lower-rated vehicle (for example installing 180hp software on a 150hp car). When the ignition is turned on, the ECU transmits its powerklass ID to the BCM and other CAN components. All components must share the same powerklass ID. If the ECU has a different one, the other components reject it and the vehicle will not start.
To work around this, follow the instructions in the next question: How to Flash IMMO OFF and Update ECM to a Newer or Compatible Software Version.

1) Perform a boot or bench mode read to obtain the complete ECU read.
2) Apply the IMMO OFF patch with IMMOFF17 to the flash/mpc.
3) Write the IMMO OFF file to the ECU.
4) Connect the ECU for standard programming over OBD or BENCH (CAN LOW/HIGH).
5) Write the newer correction version (FRF/ODX/BIN) as you normally would with your OBD writer tool.
6) After the update, the ECU is updated but IMMO is reactivated.
7) Perform another boot or bench mode read.
8) Apply IMMO OFF again to the updated flash/mpc (this second application is FREE).
9) Write the new IMMO OFF file to the ECU again.
10) Result: ECU is updated and IMMO is permanently disabled.

STEP SUMMARY: BACKUP ECU -> APPLY IMMO OFF -> FLASH UPDATE (FRF/ODX/BIN) -> RE-READ ECU -> RE-APPLY IMMO OFF.

1) Perform a boot or bench mode read to obtain the complete ECU read.
2) Apply the IMMO OFF patch with IMMOFF17.
3) Write the IMMO OFF file to the ECU.
4) Connect the ECU for standard programming over OBD or BENCH (CAN LOW/HIGH).
5) Use your tuning tool's V-Read option and flash the ECU.
6) After this step, the ECU is unlocked but IMMO is reactivated.
7) Perform another boot or bench mode read.
8) Apply IMMO OFF again to the unlocked flash/mpc (this second application is FREE).
9) Write the new OBD-unlocked IMMO OFF file.
10) Result: the ECU is unlocked and IMMO OFF is preserved, ready for OBD tuning without any IMMO constraint.

Yes. In our software suite:
• IMMO5 = WFS5
• IMMO6 = WFS6
• IMMO4 = WFS4
IMMOFF17 supports WFS4, WFS5 and WFS6 depending on the ECU platform.

For ECU immo version WFS4 and less:
Plug your VCDS interface to the ECU (OBD OR BENCH)
Open VCDS,
Go to 01 – Engine
Click [Measuring Blocks] or [Advanced Measuring Values]
Read Channel 91
1 = OFF
4 = ON

Every time you apply the IMMO OFF feature to any FLASH, the MCUID of that ECU is registered in our database and linked to your account. This guarantees you are never charged twice if you need to update the ECU with a newer FRF and subsequently reapply the IMMO OFF patch. The second patch on the same MCUID is always FREE. This design eliminates any redundant charges during ECU updates.

ADDITIONAL NOTES: In cases where all keys are lost on more recent vehicles (model year 2009 and newer), the engine may still start, but several issues can occur. The most common issues on VAG platforms are inoperative window up/down functions caused by the BCM (Body Control Module), and an immobilizer warning displayed in the instrument cluster such as “key not found”. Please note that we do not provide BCM immobilizer deactivation services. Some users have reported partial success by placing a new or virgin ID48 transponder chip near the key antenna, however this method is not guaranteed and may not work on all vehicle models.

It is important to understand how the immobilizer system operates. Depending on the vehicle brand, even if the ECU allows the engine to run, BCM-related functions may remain locked if the immobilizer status is not fully satisfied:

KEY -> CLUSTER -> NO KEY? -> DISPLAY MESSAGE
KEY -> CLUSTER -> ECU -> ENGINE RUNNING
KEY -> CLUSTER -> BCM -> WINDOWS CONTROL
KEY -> CLUSTER -> BCM -> STARTER
KEY -> CLUSTER -> BCM -> FUEL PUMP

For this reason, IMMO OFF is suitable for ECU REPLACEMENT or complete engine SWAP purposes, NOT as a substitute for key programming in a total key loss scenario.

The initial file saved by AUTOTUNER is named “BENCH_NR.BIN”. This is a virtual file containing only the MAP calibration area. It can be flashed through OBD or BENCH but cannot be used for IMMO OFF.

1) After the read is complete, locate and copy the Bench-backup.zip file, typically found in “Documents\Autotuner ECU backups”, to your Desktop.

2) Extract Bench-backup.zip into a new folder. The files represent the full ECU read: DFLASH = EEPROM, IFLASH = FLASH.

*If AUTOTUNER saved the FLASH as two files (iflash0 and iflash1), IMMOFF17 will prompt you to MERGE them. Merging is mandatory before IMMO OFF. After patching, IMMOFF17 automatically re-splits the merged file back into iflash0 and iflash1. Checksum is applied.

3) Run IMMOFF17, select the FLASH file, and save to the same folder.

4) Delete the original IFLASH0.bin and rename your new IFLASH0_IMMOOFF.bin to IFLASH0.bin. Do the same for IFLASH1.bin if present.

5) Zip the entire folder, for example IMMO_OFF_BACKUP.zip. You can use the extension .zip_noread to skip the full ECU re-read.

6) In AUTOTUNER, click WRITE and select the .ZIP file.

Quick tip: rename .zip to .bak_noread to skip the post-write re-read. Make sure your ECU backup is already secured before doing this.

Done.

No. IMMO OFF requires a full ECU read containing all sectors, because the immo bytes are often located outside the calibration area. A virtual read (V-Read) only contains the MAP calibration and cannot be used. You must perform a full read via boot mode or bench mode using tools such as AUTOTUNER, KTAG, CMD FLASH or BFLASH.

Yes. IMMOFF17 supports modern Bosch MG1 and MD1 ECUs across VAG, PORSCHE, BMW, FORD and other brands. Token cost varies by platform, see the token cost table on the BUY TOKENS page for the exact pricing per ECU family.

If the ECU accepts the file (no communication error on write) but the engine cranks without starting, check in this order:
1) Full DTC scan of ALL modules (not just the ECU).
2) Fuel pump activation at key-on (listen for the pump priming).
3) CAN communication between ECU, BCM and cluster (some BCMs block starter or fuel pump until immo handshake is complete).
4) Verify the MCU ID in the IMMO OFF file matches the target ECU exactly.
5) Re-read the ECU after writing, compare against the IMMO OFF file you generated, and send both to support if they differ.

Simply open the FLASH file in EEPROM EDITOR. The software automatically detects and displays the WFS generation (WFS4, WFS5 or WFS6) along with the decrypted immo data.

1) Full read the original ECU. Save as “ORI_FLASH.bin” and “ORI_EEPROM.bin”.
2) Full read the replacement ECU. Save as “REP_FLASH.bin” and “REP_EEPROM.bin”.
3) In EEPROM EDITOR, select CLONE, then Next, then select your files and click NEXT.
4) Save the new eeprom as “REP_EEPROM_CLONE.bin”.
5) Write “REP_EEPROM_CLONE.bin” and “ORI_FLASH.bin” to your replacement ECU.
6) Change SOFT CODING via OBD using VCDS, VCP, or any equivalent tool.

1) Full read the original ECU. Save as “ORI_FLASH.bin” and “ORI_EEPROM.bin”.
2) Run EEPROM EDITOR and EXPORT the decrypted original info to a file, for example “ORI_INFO.txt”.
3) Full read the replacement ECU. Save as “REP_FLASH.bin” and “REP_EEPROM.bin”.
4) Run EEPROM EDITOR again and IMPORT “ORI_INFO.txt” into the replacement eeprom.
5) Save as “REP_EEPROM_CLONE.bin”.
6) Write “REP_EEPROM_CLONE.bin” and “ORI_FLASH.bin” to your replacement ECU.
7) Change SOFT CODING via OBD using VCDS, VCP, or any equivalent tool.

1) Full read the original ECU. Save as “ORI_FLASH.bin” and “ORI_EEPROM.bin”.
2) Run EEPROM EDITOR and EXPORT the decrypted original info, for example “ORI_INFO.txt”.
3) Full read the replacement ECU. Save as “REP_FLASH.bin” and “REP_EEPROM.bin”.
4) Run EEPROM EDITOR again and IMPORT “ORI_INFO.txt” into the replacement eeprom.
5) Save the new eeprom as “REP_EEPROM_CLONE.bin”.
6) Write “REP_EEPROM_CLONE.bin” and “ORI_FLASH.bin” to your replacement ECU.
7) Change SOFT CODING via OBD using VCDS, VCP, or any equivalent tool.

Cloning requires the source and target ECUs to share the same hardware number and the same software/calibration version. Different versions store data at different addresses, have different POWERKLASS identifiers (on SIMOS/PCR2.1), and use different encryption keys on newer generations. Attempting to clone across different versions will result in a non-starting vehicle or CAN bus communication errors with the BCM and cluster.

POWERKLASS is a protection mechanism used by VAG SIMOS and PCR2.1 ECUs that links the ECU power rating to the rest of the vehicle's CAN network (BCM, cluster, gateway). When the ignition is turned on, the ECU broadcasts its POWERKLASS ID. If this ID does not match what the BCM expects (for example, after installing a 180hp ECU on a 150hp vehicle), the other modules will reject the ECU and the car will not start. When cloning, you must either source an ECU with the same POWERKLASS or update all related modules, which is usually impractical.

Yes. EEPROM EDITOR can open and decrypt the eeprom data of supported ECUs for inspection purposes only. Each decryption/save operation consumes 5 tokens. Cloning (full data transfer to a replacement ECU) consumes 10 tokens on MEDC17 platforms.