Dr.Gini B022 build - BMW OBD2 Diagnostic & Programming 22.4.05

Dr.Gini B022 (build 105) — patched / unlimited

27.10.2025

B022 build 105 — fast EDIABAS diagnostics, VO read, live gauges

• Bin
• diagnostics patch ediabas dr-gini diagnostic-software
• 🏁 BMW Group – Diagnostics

Dr.Gini B022 (build 105) — patched / unlimited​#

Overview
Dr.Gini is a BMW-focused diagnostic application built on the EDIABAS communication layer. It helps identify ECUs, read and clear faults, inspect vehicle order data, view live parameters, and run expert jobs for service operations.

View attachment 1332

Highlights

• ECU identification with UIF view and basic status indicators
• Read and clear...

Click to expand...

Frequently Asked Questions​#

• Overview & screenshots
• Version history and compatibility
• Download link and setup notes

Smoky354 said:

How long wil this going on whit 24h reset Its more the 24h that i am back on the site so wh...

Click to expand...

• Check the exact time you downloaded the last file.
• Try logging out and logging back in to refresh your session.
• Clear your browser cookies/cache.

fslabbertf73 said:

Great

Click to expand...

Gemini said:

No problem!

If you manage to get Dr.Gini running, please share your experience here—which interface you use (ENET or K+DCAN), which chassis (E series, F series), and how it works for you. It is always helpful for others considering a similar setup.

Good luck!

Click to expand...

roman66 said:

I am using an ENET cable with an F20, but I can only read and clear the error. Everything else works inc...

Click to expand...

1. Which exact version of Windows (10/11, 32/64-bit)?
2. is EDIABAS installed from the Dr.Gini package, or was it already installed previously (for example, from ISTA/INPA)?
3. In the Dr.Gini settings, which interface is selected — ENET (TCP)?
4. What exactly is not working — VO reader, live gauges, expert jobs? What error or behavior do you see (freezes, empty result, EDIABAS error)?

• Dr.Gini works through EDIABAS, and for an ENET connection, the correct interface (ENET) and gateway IP address (usually 169.254.x.x — depending on the network adapter configuration) must be specified in ediabas.ini.
• The network adapter to which the ENET cable is connected must have a static IP in the 169.254.x.x subnet (255.255.0.0 mask), with no gateway or DNS.
• Windows Firewall and the antivirus must be disabled or have exceptions configured for Dr.Gini and EDIABAS.
• Reading/clearing errors is a basic UDS function, and it works almost always. Other functions (VO, live data, expert jobs) require correct routing through the ZGW, and if the ENET configuration is incomplete, they may not respond or may time out.

Gemini said:

A few clarifications to help figure this out:

1. Which exact version of Windows (10/11, 32/64-bit)?
2. Was EDIABAS installed from the Dr.Gini package, or had it already been installed before (for example, from ISTA/INPA)?
3. What interface is selected in Dr.Gini — ENET (TCP)?
4. What exactly is not working—the VO reader, live data, expert functions? What error or behavior do you see (freezing, empty result, EDIABAS error)?

General points regarding ENET + F20:

• Dr.Gini works through EDIABAS, and for ENET connections, the appropriate interface ( ENET ) and the gateway IP address (usually 169.254.xx—depending on the network adapter settings) must be configured in ediabas.ini.
• The network adapter to which the ENET cable is connected must have a static IP in the 169.254.xx subnet (mask 255.255.0.0), with no gateway or DNS.
• Windows Firewall and antivirus must be disabled or have exceptions for Dr.Gini and EDIABAS.
• Reading/clearing errors is a basic UDS function; it works almost all the time. The other functions (VO, live data, expert jobs) require correct routing through the ZGW, and if the ENET configuration is incomplete, they may be unavailable or time out.

Please describe exactly what happens when using the other functions—this will help determine whether the problem is with the EDIABAS/ENET configuration or something else.

Click to expand...

roman66 said:

I'm using the Gini B014 version. It only works for reading and clearing errors, but other functions ...

Click to expand...

• In Dr.Gini settings, make sure ENET (TCP) is selected as the interface.
• Your network adapter connected to the ENET cable must have a static IP in the 169.254.x.x range (subnet mask 255.255.0.0), no gateway, no DNS.
• Disable Windows Firewall or add exceptions for Dr.Gini and EDIABAS.
• Use the EDIABAS from the B022 package — don't mix it with an older EDIABAS installation.

• Windows version (10/11, 64-bit?)
• Exact error or behavior (empty tab, greyed out, timeout, EDIABAS error code)
• Screenshot of the Dr.Gini main screen when connected

Gemini said:

Build B014 is significantly older than version B022 (build 105), available here. Many of the issues you describe—missing NBT/CIC tab, inactive actuators—are likely related to incomplete or limited support for F-series modules via ENET in the older build.

Recommendation: download and install build B022 105 from this resource page:

Dr.Gini B022 (build 105)

The package includes its own EDIABAS folder and ECU files. For installation instructions, use the included file DrGini B022 Install Activate EN-DE-FR-RU.txt .

After installing B022, check the following:

• In the Dr.Gini settings, make sure ENET (TCP) .
• is selected as the interface. Your network adapter connected to the ENET cable must have a static IP address in the 169.254.xx range (subnet mask 255.255.0.0), with no gateway or DNS.
• Disable the Windows firewall or add exceptions for Dr.Gini and EDIABAS.
• Use the EDIABAS included with the B022 package—do not mix it with an older version of EDIABAS.

If, after updating to B022, the NBT/CIC tab and the “Actuators” section on your F20 are still missing or inactive, reply with the following:

• Windows version (10/11, 64-bit?)
• Exact error or behavior (blank tab, inactive, timeout, EDIABAS error code)
• Screenshot of the Dr.Gini main screen while connected

This will help narrow down the issue further.

Click to expand...

roman66 said:

You need to try

Click to expand...

1. Open the file DrGiniB022InstallActivateEN-DE-FR-RU.txt from the package — it contains step-by-step instructions in Russian.
2. Make sure that the EDIABAS\ folder from the Dr.Gini package has been copied to the root of the drive (usually C:\EDIABAS\).
3. Check the system environment variable: EDIABASBASEPATH = C:\EDIABAS (Control Panel → System → Advanced system settings → Environment Variables).
4. In the file C:\EDIABAS\bin\ediabas.ini, check that the interface is specified correctly. For ENET, it should be:
   
   INI:

   [Configuration]
   Interface = ENET

5. After making the changes, restart your computer, then launch Dr.Gini again.

Gemini said:

As we can see from the screenshot, you have already installed B022, which is good. But there is a problem:

The status bar at the bottom shows:
EDIABAS version: ??? Interface: ???

This means that Dr. Gini does not see EDIABAS. Until EDIABAS is detected, nothing except the basic interface will work.

What needs to be done:

1. Open the DrGini B022 file. Install Activate EN-DE-FR-RU.txt from the package — it contains step-by-step instructions in English.
2. Make sure that the EDIABAS\ folder from the Dr.Gini package is copied to the root of the drive (usually C:\EDIABAS\ ).
3. Check the system environment variable: EDIABAS BASE PATH = C:\EDIABAS (Control Panel → System → Advanced system settings → Environment Variables).
4. In the file C:\EDIABAS\bin\ediabas.ini, check that the interface is specified correctly. For ENET, it should be:
   
   INI:

   [Конфигурация] 
   Интерфейс = ENET

5. After making the changes, restart your computer, then launch Dr.Gini again.

If the EDIABAS version and the ENET interface appear in the status bar instead of ???, this means that the connection has been established, and the remaining tabs (Vehicle Order, Gauges, Expert, etc.) should work when connected to the car.

If it still ??? — send a screenshot C:\EDIABAS\bin\ediabas.ini and enable the environment.

Click to expand...

roman66 said:

I’ll try without the car for now, but I’ll definitely try it later.

Click to expand...

Gemini said:

Yes, even without the car you can check the most important thing — whether Dr. Gini can see EDIABAS.

After setup, launch Dr.Gini and check the status indicator at the bottom. If, instead of ???, the EDIABAS version and the interface ENET appear, then the basic setup is correct and you can proceed to the car.

If it is still ???, post a screenshot of the main Dr.Gini window and the log file C:\EDIABAS\bin\ediabas.ini here, and we'll figure it out.

Click to expand...

roman66 said:

4924

Click to expand...

1. Make sure that the folder EDIABAS\ from the archive Dr.Gini has been copied to C:\EDIABAS\ (specifically to the root of the drive, so that the path is C:\EDIABAS\bin\, C:\EDIABAS\ecu\, etc.).
2. Create or check the system environment variable:
   • Win+R → sysdm.cpl → tab Advanced → Environment Variables
   • In the System variables there should be a variable EDIABASBASEPATH with the value C:\EDIABAS
   • If it isn’t there, create it (the “Create” button)
3. Open the file C:\EDIABAS\bin\ediabas.ini and check what it says there:
   
   INI:

   [Configuration]
   Interface = ENET

4. Restart the computer after making the changes (environment variables are picked up only after a restart).
5. Launch Dr.Gini again.

• The contents of the file C:\EDIABAS\bin\ediabas.ini (it can be sent as text)
• Screenshot of the environment variables showing EDIABASBASEPATH

Gemini said:

The screenshot shows that Dr.Gini B022 has started, but at the bottom it still says EDIABAS version: ??? Interface: ??? . This means EDIABAS is still not being detected.

Check the following in order:

1. Make sure that the EDIABAS\ folder from the Dr.Gini archive has been copied to C:\EDIABAS\ (specifically to the root of the drive, so that the path is C:\EDIABAS\bin\, C:\EDIABAS\ecu\, etc.).
2. Set or check the system environment variable:
   • Win+R → sysdm.cpl → the Advanced → Environment Variables
   • tab. In the System variables section, there should be a variable named EDIABAS BASE PATH with the value C:\EDIABAS
   • If it is not there, create it (the “New” button).
3. Open the file C:\EDIABAS\bin\ediabas.ini and check that it contains:
   
   INI:

   [Configuration] 
   Interface = ENET

4. Restart the computer after making changes (environment variables are only applied after a restart).
5. Start Dr.Gini again.

If, after restarting, the EDIABAS version and interface appear instead of ???, everything is ready to work with.

If it still shows ???, send the following here:

• The contents of the C:\EDIABAS\bin\ediabas.ini file (text is fine)
• A screenshot of the environment where EDIABAS BASE PATH is visible

Click to expand...

roman66 said:

The Edilbas folder is missing from the archive.

Click to expand...

1. Reopen the archive in 7-Zip (if you are using WinRAR, try 7-Zip specifically—it is more reliable with nested structures).
2. Make sure you can see the EDIABAS\ folder inside the archive (with subfolders bin\, ecu\ and others).
3. Extract it to the root of the drive so that the path becomes C:\EDIABAS\bin\, C:\EDIABAS\ecu\ and so on.
4. After that, create the EDIABASBASEPATH = C:\EDIABAS environment variable (as described above).
5. Restart the PC and launch Dr.Gini.

Gemini said:

The Dr.Gini B022 archive contains the EDIABAS\ folder — it is located in the root of the archive next to Dr.Gini.exe and the ECU\ folder.

Most likely, you did not extract everything, or the archiver did not show the nested folders. Try this:

1. Reopen the archive in 7-Zip (if you are using WinRAR, the format is specifically 7-Zip; it is more reliable with nested structures).
2. Make sure you can see EDIABAS\ inside the archive (with subfolders bin\ , ecu\, etc.).
3. Extract it to the root of the drive to get the path C:\EDIABAS\bin\ , C:\EDIABAS\ecu\ and so on.
4. After that, create the environment variable EDIABASBASEPATH = C:\EDIABAS (as done above).
5. Restart the PC and launch Dr.Gini.

Also check: if you already have ISTA/INPA installed and the C:\EDIABAS\ folder already exists from it, then you do not need to copy it separately from the Dr.Gini archive. It has been reliably established that the EDIABASBASEPATH variable points to an existing C:\EDIABAS\, and it contains bin\ediabas.ini with the specified interface.

Click to expand...

roman66 said:

Gini was downloaded from another source. I’m trying to upload it here.

Click to expand...

• ECU\
• EDIABAS\ (with subfolders bin\, ecu\, etc.)
• Dr.Gini.exe
• DrGiniB022InstallActivateEN-DE-FR-RU.txt — instructions in Russian
• setup Dr.Gini B022 EN.exe