[tinkerman]

ISTA-P installation package includes an installation of EDIABAS (e.g. ISTA-P\BMW\Environment\EDIABAS), but this doesn't have an Ecu folder (as it would with a regular EDIABAS 7.3.0 install). Instead the ".PRG" files seem to be assigned to 2 folders elsewhere:
- ISTA-P\BMW\Services\data\ecudata\BASE\ecu
- ISTA-P\BMW\Services\templates\AmphionTemplate\ecu

The Loader 6.1 notifies during initial boot that EDIABAS 7.3.0(patched) needs to be installed (if not already installed by itself or through a BMW Standard Tools installation). When EDIABAS 7.3.0 is installed(by itself) the Ecu folder(C:\EDIABAS\Ecu) is initially empty(no ".PRG" files).

I've seen some ISTA-P setup guides that install the patched EDIABAS 7.3.0, without any mention of updating the empty Ecu folder with say BMW Coding Tool and SP-daten(".PRG" files), making it seem that such update is not necessary.

1. Can this "separate installation" of EDIABAS and its empty Ecu folder affect ISTA-P's functions directly?

2. Or is this "separate installation" of EDIABAS "independent" of the installed ISTA-P's operation, and solely for the Loader's use, to access mainly the interface handler/related ".dll" files and ".ini" files(EDIABAS/OBD) for the interface, hence the empty Ecu folder is not an issue?

[szilagyilajos]

ISTA-P does not uses ECU folder from Ediabas. So it's normal.
ISTA-P have own folders for ecus, depends of model series.
Like this:
\ISTA-P\BMW\Services\data\ecudata\E36\ecu\

[tinkerman]

ISTA-P does not uses ECU folder from Ediabas. So it's normal.
ISTA-P have own folders for ecus, depends of model series.
Like this:
\ISTA-P\BMW\Services\data\ecudata\E36\ecu\

That's what I thought... Thanks for the confirmation.

I did not mention the individual model related ecu folders as they are not installed in the EDIABAS folder(in Standard Tools installations), but you are right that ISTA-P installs them in their respective "ecu" folders.

Cheers...