How To Use Ediabas Tool32

There must be a check-mark by Use FIFO buffers and the highest possible setting must be selected for the receive buffer.The reason for this is that only one programme can access EDIABAS at a time.Solution: Therefore, before you start the ToolSet, you must exit INPA.

  • Error IFH-0038 is generated when loading the utility file into the Tool Set.
  • Reason 1: The error was caused by another programme that accessed the COM1 interface.
  • This programme could be HotSync for Palm or ActiveSync for lpack.

Use Ediabas Tool32 Driver With The

who like this article also viewed:

Solution 1: Check the programmes that are started automatically when Windows is started (see Chapter 4.1). Reason 2: The COM1 interface is taken by a serial printer. Reason 4: There is no COM1 interface (COM3 instead, for example) Solution 4a): Install the COM1 interface. Solution 4b): Create a file with the name OBD.ini and make the following entry to set the existing serial interface (COM3, for example).

Related posts:

  • The current version of the Ediabas Package can be seen in the files C:EDIABASversion.txt or C:EDIABASpackage.pdf.
  • Reason 5: Only for IBM notebooks: The COM1 interface is reserved for the docking station; the COM3 interface is installed instead.
  • Then use the right mouse button Properties Port Settings Advanced to reach the Advanced Settings for COM3.
  • The message that COM1 is already taken can be ignored in this case.
  • Solution 6: Please uninstall the old OMITEC driver with the instructions InstructionforOMITECInstallation.pdf via the GIS server.
  • Reason 1: ODB has actually been set as the interface in Ediabas.ini, but the Tool Set uses the multi-instance with another interface, e.g.

The setting for the multiinstance and the interfaces used here is made in the file Tool32.ini in the directory C:Windows (for Windows XP) or alternatively C:Winnt (for Windows NT).


Then, the entries in Tool32.ini, or alternatively the interface apply and not the ones in Ediabas.ini. The use of multi-instance in the Tool Set is identified in the title bar, for example with Tool32:1, for single multi-instance.

Tool32 (EDIABAS ToolSet 32)

Solution 2: Enter the interface that is being used in Tool32.ini or disable multi-instance with the entry No. Reason 2: A SGBD is loaded in the Tool Set when the diagnosis protocol UDS is being used. For UDS-SGBDs You have to use the interface OMITEC but in the EDIABAS.ini the setting fort he interface ist STD:OBD.

The OMITEC connector has to be stressed by the voltage (blue blinking). If the connector cant be stressed by the voltage and You want to load the SGBD yet, You will use the simulation mode.

NCS Expert

You can activate the simulation mode e.g. Notice, if you want to use the simulation mode, a simulation file for the interface will have to exist in the simulation path.

NCS Dummy

Reason 3: The device manager has been used to disable the FIFO buffer for COM1.

Solution 3: In the device manager (Windows XP: Enter Start Control Panel System Hardware Device Manager Ports (COM LPT)), and select COM1 from the ports and under the Port Settings tab, select Advanced.


So, you’ve just purchased a second hand DME / ECU and you want your own VIN coded to it right? Well, luckily for you this is a very simple process using the rather awesome ‘Tool32’ program, which is provided as part of the BMW Standard Toolset.


First things first, you’ll need the following:. A laptop with a working installation of INPA and Tool32. An OBD2 cable that works with INPA and your E46 or E39. An E46 M3 or an E39 M5.

Now you have the prerequisites in order plug your OBD2 cable into the car and fire up your laptop.

Load up Tool32 (ToolSet 32). Click ‘File’ > ‘Load SGBD, Group File’ and browse to the ‘C:\Ediabas\ECU\12MSS54.PRG’ file and click ‘Open’. In the ‘Jobs’ list double click ‘aif_lesen’.

Classic way (F-/G-Models)


The results window should return a ‘Job_Status’ of ‘OKAY’ and the first VIN programmed into the DME will be displayed along with other AIF data. In the ‘Arguments’ box type ‘2’ and double click ‘aif_lesen’ again. The results window should update, repeat the process of incrementing the number in the ‘Arguments’ box until you reach a number with a blank ‘AIF_FG_NR’ field.


  • Make a note of the ‘AIF_ADRESSE_LOW’ number, you’ll need that shortly.
  • In my case, slot ‘3’ was free and had an ‘AIF_ADRESSE_LOW’ of ‘7596’.
  • Using the Windows ‘Notepad’ construct the following string, replacing the values etc with your own:.
  • The string is constructed in the following order:.
  • AIF_ADRESS_LOW; VIN; Today Date; Software Number ; Authority Number; Assembly Number; Serial Number; Handler Number; AIF Programmed KM; AIF Program Number.


So, you’ll have something like this:. The software number, authority number and assembly numbers should be labeled on the outside case of the DME, the fields after those are fairly unimportant so can be left as detailed in my string.


Copy the constructed string into your clipboard by highlighting it and clicking the ‘Edit’ Menu and selecting ‘Copy’. Go back to Tool32 and scroll down the ‘Jobs’ list until you see ‘seed_key’, double click ‘seed_key’ and then paste your newly constructed string into the ‘Arguments’ box.

Modern way


Double click ‘aif_schreiben’ and ensure the ‘JOB_STATUS’ returns ‘OKAY’. If the status returns ‘Error’ or ‘Rejected’ double click ‘seed_key’ and retry ensuring you don’t click anything other than ‘aif_schreiben’. Once the report has responded ‘OKAY’ then close Tool32, you’re done!

Carly für BMW

If you want to confirm the coding has worked, load up INPA, select ‘E46’ or ‘E39’ then ‘Engine’ then ‘MS S54 for S54 M3’ then select ‘Coding’.

Your newly coded data should be displayed here! Well after a lot of tinkering with this and that I’ve finaly done it. I’ve reactivated BMW Online and Internet.



Comments are closed.