Published on
Image description

Using Tool32 on a BMW is much easier when you know which .PRG file belongs to the control unit you want to diagnose. Choosing the wrong file can lead to missing functions, communication errors, or confusing results.

The good news is that INPA can help you find the correct file. Its Identification function displays the control units installed in the vehicle, along with the related SGBD names. These names are often connected to the .PRG files used by Tool32.

This guide explains the basic process for BMW F-series vehicles and also covers why encoder specifications matter before opening a file in Tool32.


What Is a PRG File?

A .PRG file is a diagnostic program file used by Tool32. It contains the communication data and available jobs for a particular BMW electronic control unit.

Depending on the module, a PRG file may allow you to:

  • Read identification information
  • Check live data
  • Read and clear fault memory
  • Activate components
  • Run system tests
  • Reset adaptations
  • Carry out service functions
  • Monitor control-unit status

Every control unit does not use the same PRG file. For example, the file required for a body control module may be completely different from the file used for an engine ECU or transmission module.

That is why identifying the installed control unit first is an important step.


Why the SGBD Name Matters

Inside INPA, the SGBD column shows the name associated with a diagnostic control-unit description. In many cases, this name corresponds to a PRG file stored in the EDIABAS ECU folder.

The usual location is:


C:\EDIABAS\ECU

For example, if INPA displays an SGBD entry such as:


Example_Module.PRG

you can check whether the matching file is available in:


C:\EDIABAS\ECU\Example_Module.PRG

The exact name depends on the BMW model, control unit version, EDIABAS installation, and diagnostic software package.

Do not assume that a similar-looking file is automatically correct. BMW modules can have different hardware versions, software versions, and communication requirements.


How to Find PRG Files with INPA

1. Start INPA

Connect your compatible BMW diagnostic interface and switch on the ignition. It is usually best to connect a stable battery charger before carrying out longer diagnostic procedures.

Open INPA and wait for the vehicle connection indicators to appear.

If the vehicle is not detected, check the following:

  • Diagnostic cable connection
  • Ignition position
  • USB or COM port settings
  • EDIABAS configuration
  • Vehicle communication interface
  • Battery voltage

A communication problem should be solved before searching for PRG files.


2. Select the Correct Chassis

For an F-series BMW, select the appropriate Fxx model group in INPA.

The exact menu name may vary depending on the INPA version and installation. Older BMW E-series vehicles use different model selections, so make sure the selected chassis matches the vehicle being tested.

Selecting the wrong chassis may show incomplete menus or control-unit entries that do not match the actual car.


3. Open Functional Jobs

After selecting the correct model group, double-click:


Functional Jobs

This section contains general diagnostic functions that can communicate with multiple control units.

4. Select Identification

Choose:


Identification

INPA will scan the vehicle and display information about the control units it can identify.

The results may include:

  • Control-unit name
  • Hardware information
  • Software information
  • Identification number
  • Version data
  • SGBD name
  • Communication details

The layout can vary slightly between INPA versions, but the SGBD information is usually visible in the identification results.


5. Check the SGBD Column

Look for the column named:


SGBD

This column contains the names of the diagnostic descriptions used by the vehicle software.

Write down the relevant SGBD name or take a clear screenshot. You can then compare it with the files installed in:


C:\EDIABAS\ECU

The matching .PRG file is normally the first file to investigate in Tool32.


Checking the File in the EDIABAS ECU Folder

Open Windows File Explorer and navigate to:


C:\EDIABAS\ECU

Use the search field to find the SGBD name shown by INPA.

Check that:

  • The file exists
  • The file has the .PRG extension
  • The spelling matches the SGBD name
  • The file is not located in an unrelated backup folder
  • The EDIABAS installation is using the same ECU folder

Some installations contain multiple software versions or duplicate files. This can make the folder look more complicated than expected.

It is a good idea to make a backup of the original ECU folder before changing or replacing any files.


Why Encoder Specifications Are Important

Finding a PRG file is only part of the process. You should also consider the encoder specification before running jobs in Tool32.

The encoder describes how Tool32 communicates with the control unit. Different modules may require different communication methods, protocols, or interface settings.

The encoder specification can affect:

  • Whether Tool32 connects successfully
  • Which jobs are available
  • How data is transmitted
  • Whether responses are displayed correctly
  • Whether a job can be safely executed

A PRG file may appear to match the module name, but the communication encoder may still be unsuitable for that specific control unit.

This is especially important with BMW F-series vehicles because they may use newer communication systems compared with older E-series models. Depending on the module, communication can involve different vehicle networks and diagnostic interfaces.

Before running any job, confirm that the PRG file and encoder are intended for the same control-unit family.


Avoid Choosing a PRG File by Name Alone

A common mistake is choosing a file simply because its name looks similar to the module being tested.

For example, two files may share part of the same module name but represent different:

  • Hardware generations
  • Software versions
  • Vehicle platforms
  • Communication protocols
  • Regional configurations
  • ECU suppliers

The safest approach is to compare the information from INPA with the available file names and then confirm the module documentation or known diagnostic data.

If the file does not clearly match, avoid running active jobs until the correct information has been verified.


Tool32 Safety Tips

Tool32 is a powerful BMW engineering and diagnostic application. Some jobs only read information, while others can change settings, reset values, activate components, or write data to a control unit.

Before executing a job:

  1. Confirm the correct vehicle and control unit.
  2. Check the PRG file name carefully.
  3. Read the job description before running it.
  4. Use a stable battery charger.
  5. Avoid interrupting communication during an active procedure.
  6. Record the original values where possible.
  7. Do not run unfamiliar jobs on a customer vehicle without testing first.
  8. Keep a backup of important configuration data.

A diagnostic laptop losing power or the vehicle voltage dropping during a programming-related procedure can create unnecessary problems.


Common Problems and Their Causes

The SGBD File Is Not in the ECU Folder

This may happen when:

  • The EDIABAS installation is incomplete
  • The file belongs to another software version
  • The file was deleted or moved
  • INPA is using a different installation path
  • The vehicle requires a newer diagnostic package

Check the EDIABAS configuration and confirm which installation folder is active.


Tool32 Opens the File but Cannot Connect

Possible causes include:

  • Incorrect interface configuration
  • Wrong encoder
  • Ignition switched off
  • Low vehicle battery voltage
  • Incorrect PRG file
  • Communication cable problem
  • Unsupported control unit

Start with basic checks before assuming the ECU itself is faulty.


The Required Job Is Missing

Not every PRG file contains the same jobs. Available functions may depend on the control unit version and the software data installed on the computer.

A missing job does not always mean the module is damaged. It may simply mean that the selected PRG file is not the correct version.


INPA Shows Limited Information

Limited identification data can result from communication issues, an incorrect model selection, or an incomplete software setup.

Make sure the correct F-series chassis menu is selected and that the interface is communicating properly with the car.


A Practical Workflow

A reliable workflow looks like this:

  1. Connect the diagnostic interface.
  2. Switch on the ignition.
  3. Start INPA.
  4. Select the correct F-series chassis.
  5. Open Functional Jobs.
  6. Select Identification.
  7. Find the control unit and record the SGBD name.
  8. Check the matching .PRG file in C:\EDIABAS\ECU.
  9. Confirm the encoder specification.
  10. Open the file in Tool32.
  11. Read available jobs carefully.
  12. Test with an identification or read-only function first.

Starting with a read-only job is a sensible way to confirm that the selected file communicates correctly.

0 Comments