<![CDATA[Bimmer Scene - Latest BMW Coding / Retrofits / Maps

<![CDATA[Bimmer Scene - Latest BMW Coding / Retrofits / Maps - All Forums]]> https://www.bimmerscene.com/ Fri, 24 Apr 2026 12:24:22 +0000 MyBB <![CDATA[How to remove ECU from tree in ISTA]]> https://www.bimmerscene.com/showthread.php?tid=9566 Fri, 24 Apr 2026 11:37:25 +0000 bavees]]> https://www.bimmerscene.com/showthread.php?tid=9566
I am looking at how to remove an ECU from the ISTA control unit tree so that the car no longer looks for it.

I have a Canadian G30 but fitted some EU seats in it. My passenger seat no longer has a control unit but only the seat heating module. But the car is still looking for the ecu "SMBF". It shows in red in the ISTA unit tree and BDC registers an error because it cannot talk to it.

What I tried to do is:

TAL Calculation:
1 - Read SVT IST from car (the ECU is not listed there since its not connected)
2 - Calculate SVT SOLL (the ecu re-apears, in red)
3 - Edit SVT SOLL to delete that ECU and save

VCM:
1 - load the modified SVT SOLL in both SVT Current and SVT target
2 - write SVT target to VCM

But when I read the car with ISTA the ecu show up in red again.

The only thing that comes to mind is that because my typekey is still the Canadian/US one the car expects a passenger seat control unit. So wondering if I also need to write a modified FA with European typekey then re-do the SVT steps in VCM.

If anyone can comment I'd appreciate your input.

Thanks!

EDIT:

I forgot to mention I also tried to enable VCM update after TAL processing in options and run a TAL processing without checking any of the ECU's.
Likewise also tried to load the SVT target in VCM then just code any ECU to force VCM update.

Neither of these make the ECU go away either.]]>
I am looking at how to remove an ECU from the ISTA control unit tree so that the car no longer looks for it.

I have a Canadian G30 but fitted some EU seats in it. My passenger seat no longer has a control unit but only the seat heating module. But the car is still looking for the ecu "SMBF". It shows in red in the ISTA unit tree and BDC registers an error because it cannot talk to it.

What I tried to do is:

TAL Calculation:
1 - Read SVT IST from car (the ECU is not listed there since its not connected)
2 - Calculate SVT SOLL (the ecu re-apears, in red)
3 - Edit SVT SOLL to delete that ECU and save

VCM:
1 - load the modified SVT SOLL in both SVT Current and SVT target
2 - write SVT target to VCM

But when I read the car with ISTA the ecu show up in red again.

The only thing that comes to mind is that because my typekey is still the Canadian/US one the car expects a passenger seat control unit. So wondering if I also need to write a modified FA with European typekey then re-do the SVT steps in VCM.

If anyone can comment I'd appreciate your input.

Thanks!

EDIT:

I forgot to mention I also tried to enable VCM update after TAL processing in options and run a TAL processing without checking any of the ECU's.
Likewise also tried to load the SVT target in VCM then just code any ECU to force VCM update.

Neither of these make the ECU go away either.]]> <![CDATA[PSdZData 4.59.10 LITE *LATEST*]]> https://www.bimmerscene.com/showthread.php?tid=9565 Fri, 24 Apr 2026 05:53:55 +0000 dzooky]]> https://www.bimmerscene.com/showthread.php?tid=9565 To keep enjoying your privileges, Please always read the Forum's Updated Rules:CLICK HERE

-------------------------------------------------------

PSdZData 4.59.10 LITE on MEGA

[HIDE]https://mega.nz/file/sZUETaYJ#4e8PA1zEj7YnLMmBodvB0z6BWo7SZ0nDIoVVpFy3QhU[/HIDE]]]> To keep enjoying your privileges, Please always read the Forum's Updated Rules:CLICK HERE

-------------------------------------------------------

PSdZData 4.59.10 LITE on MEGA

[HIDE]https://mega.nz/file/sZUETaYJ#4e8PA1zEj7YnLMmBodvB0z6BWo7SZ0nDIoVVpFy3QhU[/HIDE]]]> <![CDATA[BMW E-Sys 3.27 VMware for BMW coding: E-Sys + Premium Launcher + PSdZdata Lite]]> https://www.bimmerscene.com/showthread.php?tid=9564 Thu, 23 Apr 2026 11:46:14 +0000 Alex-MS]]> https://www.bimmerscene.com/showthread.php?tid=9564 Files inside:
BMW E-Sys 3.27
Premium Launcher
PSdZdata 63 Lite
Windows 7 x64 English VMware

1. BMW E-Sys 3.27
This is a stable "engineering" version of the software for BMW F, G, and I-series vehicles. It is used for:
- Function coding (activating hidden options);
- Editing trim levels (FA/VO);
- Programming (flashing) electronic control units.

2. E-Sys Launcher Premium (by TokenMaster)
E-Sys itself is closed for editing critical data.

The launcher performs two main tasks:

- Token generation (.EST): Allows the "FDL Coding" function
(changing individual parameters within the unit). Without this, you can only
change the entire trim level, not individual settings.

- Un-trimming (Mapping): In newer databases, BMW removes function names,
leaving periods or empty strings. The launcher replaces this data,
returning human-readable names (for example, instead of "3001 > .."
you see "3001 > Speed_Limit").

3. Differences in PSdZdata Databases
PSdZdata contains firmware and module descriptions that are "inserted"
into E-Sys for vehicle operation.

PSdZdata LITE:
- Purpose: Exclusively CODING (hidden functions, settings).
- SWFL files: None (cut to save space).
- Disk space: ~5-15 GB.
- Pros: Takes up little space, downloads and installs quickly.

PSdZdata FULL:
- Purpose: PROGRAMMING (firmware) + coding.
- SWFL files: Included in full.
- Disk space: ~150-350 GB.
- Pros: Allows you to fully update your vehicle's software and restore control units.

* SWFL (Software Files) are large firmware files required for updating control unit software.

4. Which one to choose?
- If you're a beginner and just want to activate functions (start-stop, logos, videos): download the LITE version.
- If you plan to update your vehicle's firmware or replace the hardware with used equipment: you need the FULL version.
[Image: bmw-e-sys-vmware.jpg]

Need it? Push button Thanks, PM for pass | or by email right now.

.txt

BMW E-Sys VMware new.txt (Size: 34 bytes / Downloads: 8) ]]> Files inside:
BMW E-Sys 3.27
Premium Launcher
PSdZdata 63 Lite
Windows 7 x64 English VMware

1. BMW E-Sys 3.27
This is a stable "engineering" version of the software for BMW F, G, and I-series vehicles. It is used for:
- Function coding (activating hidden options);
- Editing trim levels (FA/VO);
- Programming (flashing) electronic control units.

2. E-Sys Launcher Premium (by TokenMaster)
E-Sys itself is closed for editing critical data.

The launcher performs two main tasks:

- Token generation (.EST): Allows the "FDL Coding" function
(changing individual parameters within the unit). Without this, you can only
change the entire trim level, not individual settings.

- Un-trimming (Mapping): In newer databases, BMW removes function names,
leaving periods or empty strings. The launcher replaces this data,
returning human-readable names (for example, instead of "3001 > .."
you see "3001 > Speed_Limit").

3. Differences in PSdZdata Databases
PSdZdata contains firmware and module descriptions that are "inserted"
into E-Sys for vehicle operation.

PSdZdata LITE:
- Purpose: Exclusively CODING (hidden functions, settings).
- SWFL files: None (cut to save space).
- Disk space: ~5-15 GB.
- Pros: Takes up little space, downloads and installs quickly.

PSdZdata FULL:
- Purpose: PROGRAMMING (firmware) + coding.
- SWFL files: Included in full.
- Disk space: ~150-350 GB.
- Pros: Allows you to fully update your vehicle's software and restore control units.

* SWFL (Software Files) are large firmware files required for updating control unit software.

4. Which one to choose?
- If you're a beginner and just want to activate functions (start-stop, logos, videos): download the LITE version.
- If you plan to update your vehicle's firmware or replace the hardware with used equipment: you need the FULL version.
[Image: bmw-e-sys-vmware.jpg]

Need it? Push button Thanks, PM for pass | or by email right now.

.txt

BMW E-Sys VMware new.txt (Size: 34 bytes / Downloads: 8) ]]> <![CDATA[B57S (2020 X5 M50d G05) Swirl Flap Delete. FDL Parameters for DDE via E-SYS/BimmerUt]]> https://www.bimmerscene.com/showthread.php?tid=9563 Wed, 22 Apr 2026 19:28:54 +0000 Gassz16]]> https://www.bimmerscene.com/showthread.php?tid=9563 Hi everyone,

I’m currently dealing with a persistent swirl flap issue on my 2020 BMW X5 M50d (B57S Quad-Turbo) with 170k km. I am planning a full physical delete, but want to handle the software side myself using BimmerUtility and E-SYS. I'm afraid of the flaps and snapping ruining engine.

The Problem:
I am getting fault code 2F8500 (Swirl-flap controller, position sensor, signal: Too low).
Live data under WOT confirms the severity — at 2930 RPM boost reads 3280 hPa against a nominal of 3859 hPa. At 4234 RPM it's 3431 hPa vs 4037 hPa nominal. Consistently ~600 hPa under target at full throttle. At partial load the actuator tracks fine (30° commanded = 30.21° actual, no fault). Failure only at the full-open extreme

The Hardware Plan:
Full removal of the rod and plastic flaps from the aluminum intake manifold.
Plugging the manifold hole.

The Software Questions:
I am looking for the specific FDL parameters in the DDE (DDE8) to permanently suppress these monitoring functions via OBD without a bench unlock.
After the physical delete I plan to do the ISTA adaptation reset (Vehicle Management → Service Functions → Powertrain → DDE → Adaptations → ABL) followed by FDL coding via E-SYS + BimmerUtility to permanently suppress the 2F8500 monitoring.

BimmerUtility Experience: Has anyone successfully used BimmerUtility to code out these specific checks on a 2020 G05? Is this DDE usually write-protected for FDL changes via OBD?

What I need specifically:
Confirmed FDL parameter names inside the B57S DDE CAFD to disable swirl flap fault monitoring — the master enable switch and any position plausibility checks
Whether anyone has done this successfully on a 2020 G05 via OBD without a bench unlock
Whether there are any secondary parameters I need to address to avoid blocking DPF regeneration after the delete
Has anyone done this on a G05 M50d or similar B57 platform? Any confirmed parameter list would be hugely appreciated — happy to post full results back here once complete.

Thanks in advance!]]> Hi everyone,

I’m currently dealing with a persistent swirl flap issue on my 2020 BMW X5 M50d (B57S Quad-Turbo) with 170k km. I am planning a full physical delete, but want to handle the software side myself using BimmerUtility and E-SYS. I'm afraid of the flaps and snapping ruining engine.

The Problem:
I am getting fault code 2F8500 (Swirl-flap controller, position sensor, signal: Too low).
Live data under WOT confirms the severity — at 2930 RPM boost reads 3280 hPa against a nominal of 3859 hPa. At 4234 RPM it's 3431 hPa vs 4037 hPa nominal. Consistently ~600 hPa under target at full throttle. At partial load the actuator tracks fine (30° commanded = 30.21° actual, no fault). Failure only at the full-open extreme

The Hardware Plan:
Full removal of the rod and plastic flaps from the aluminum intake manifold.
Plugging the manifold hole.

The Software Questions:
I am looking for the specific FDL parameters in the DDE (DDE8) to permanently suppress these monitoring functions via OBD without a bench unlock.
After the physical delete I plan to do the ISTA adaptation reset (Vehicle Management → Service Functions → Powertrain → DDE → Adaptations → ABL) followed by FDL coding via E-SYS + BimmerUtility to permanently suppress the 2F8500 monitoring.

BimmerUtility Experience: Has anyone successfully used BimmerUtility to code out these specific checks on a 2020 G05? Is this DDE usually write-protected for FDL changes via OBD?

What I need specifically:
Confirmed FDL parameter names inside the B57S DDE CAFD to disable swirl flap fault monitoring — the master enable switch and any position plausibility checks
Whether anyone has done this successfully on a 2020 G05 via OBD without a bench unlock
Whether there are any secondary parameters I need to address to avoid blocking DPF regeneration after the delete
Has anyone done this on a G05 M50d or similar B57 platform? Any confirmed parameter list would be hugely appreciated — happy to post full results back here once complete.

Thanks in advance!]]> <![CDATA[Service history editor]]> https://www.bimmerscene.com/showthread.php?tid=9562 Tue, 21 Apr 2026 16:59:16 +0000 rxp2007]]> https://www.bimmerscene.com/showthread.php?tid=9562
The method I used was:

1. Set my laptop's wired connection IP to 192.168.0.1; subnet mask as 255.255.255.0 and default gateway 192.168.0.1. Left DNS blank.
2. Opened Tftpd64 application and did the following:

* Went to DCHP tab
* Set IP pool start address to: 192.168.0.2
* Set size of pool to: 10
* Set default router to: 192.168.0.1
* Set mask to: 255.255.255.0
* Pressed "OK" button
* Selected 192.168.0.1 (ethernet connection) from the "Server interfaces" dropdown

3. I then connected the ethernet to ODB2 cable to the car and started the car engine.
4. I pressed and held down the radio power/volume button for 30 seconds
5. The iDrive screen restarted
6. I then noticed that the tftp32 application indicated that it had assigned 192.168.0.2 and 192.168.0.3
7. I visited ftp://192.168.0.2/ in my web browser and was promoted for a username and password
8. I entered "root" and "Hm83stN)" and logged in successfully for testing.
9. open filezilla and connect with ip 192.168.0.2, user root and password Hm83stN)
10. navigate to \HBpersistence\Hmi\data\rw
11. transfer file servicehistorie.bin
12. open SHMLITE
13. open file, select *.* and open servicehistorie.bin

Now, with SHMLITE i can see all service history, but in reverse mode.

If I add a new service, it will be placed at the beginning, not the end, in chronological order.

Is that possible to developers create an application for edit that bin file, like SHMLITE with more options , like to reverse order, etc.. etc.. ?

Via ftp we can replace a saved file with all service history with filename servicehistorie.bin .]]>
The method I used was:

1. Set my laptop's wired connection IP to 192.168.0.1; subnet mask as 255.255.255.0 and default gateway 192.168.0.1. Left DNS blank.
2. Opened Tftpd64 application and did the following:

* Went to DCHP tab
* Set IP pool start address to: 192.168.0.2
* Set size of pool to: 10
* Set default router to: 192.168.0.1
* Set mask to: 255.255.255.0
* Pressed "OK" button
* Selected 192.168.0.1 (ethernet connection) from the "Server interfaces" dropdown

3. I then connected the ethernet to ODB2 cable to the car and started the car engine.
4. I pressed and held down the radio power/volume button for 30 seconds
5. The iDrive screen restarted
6. I then noticed that the tftp32 application indicated that it had assigned 192.168.0.2 and 192.168.0.3
7. I visited ftp://192.168.0.2/ in my web browser and was promoted for a username and password
8. I entered "root" and "Hm83stN)" and logged in successfully for testing.
9. open filezilla and connect with ip 192.168.0.2, user root and password Hm83stN)
10. navigate to \HBpersistence\Hmi\data\rw
11. transfer file servicehistorie.bin
12. open SHMLITE
13. open file, select *.* and open servicehistorie.bin

Now, with SHMLITE i can see all service history, but in reverse mode.

If I add a new service, it will be placed at the beginning, not the end, in chronological order.

Is that possible to developers create an application for edit that bin file, like SHMLITE with more options , like to reverse order, etc.. etc.. ?

Via ftp we can replace a saved file with all service history with filename servicehistorie.bin .]]> <![CDATA[[MEGA] Live 2026-1]]> https://www.bimmerscene.com/showthread.php?tid=9561 Tue, 21 Apr 2026 14:11:08 +0000 dzooky]]> https://www.bimmerscene.com/showthread.php?tid=9561 First of all , Please read the UPDATED Forum Rules :CLICK HERE

-------------------------------------------

New Europe maps
[HIDE]https://mega.nz/file/dUcHlbbC#FLhnJXija0TFgPvA4z0vWbyexyxP5XAP9vzg19lwTWI[/HIDE]]]> First of all , Please read the UPDATED Forum Rules :CLICK HERE

-------------------------------------------

New Europe maps
[HIDE]https://mega.nz/file/dUcHlbbC#FLhnJXija0TFgPvA4z0vWbyexyxP5XAP9vzg19lwTWI[/HIDE]]]> <![CDATA[BMW ETK Offline: Parts Catalog + Prices]]> https://www.bimmerscene.com/showthread.php?tid=9560 Tue, 21 Apr 2026 12:21:16 +0000 Alex-MS]]> https://www.bimmerscene.com/showthread.php?tid=9560
Files inside:
BMW ETK 01.2020
ETK Price 04.2026
How to install ETK
Pass for Rolls-Royce, Zinoro

Catalog Coverage

Brands:
BMW, MINI, Rolls-Royce.

Vehicle types:
Passenger cars and motorcycles. Includes classic and retro models.

Why you need the price file
The BMW ETK program provides only diagrams, technical specifications, and original part numbers (part codes), but does not display their cost.

Installing the additional price file provides the following capabilities:
Price display: The cost of each part appears in the interface in the selected currency (current as of the date this price file was created).
Quotation generation: The ability to add parts to a “cart” and generate a preliminary estimate for repairs or parts orders.
Localization: Price files are typically released for specific markets (e.g., dealer prices in Europe or the U.S.), allowing the program to be adapted to local pricing structures.
[Image: bmw-etk-prices.jpg]

Need it? Push button Thanks, PM for pass | or by email right now.

.txt

BMW ETK + Prices new.txt (Size: 34 bytes / Downloads: 6) ]]>
Files inside:
BMW ETK 01.2020
ETK Price 04.2026
How to install ETK
Pass for Rolls-Royce, Zinoro

Catalog Coverage

Brands:
BMW, MINI, Rolls-Royce.

Vehicle types:
Passenger cars and motorcycles. Includes classic and retro models.

Why you need the price file
The BMW ETK program provides only diagrams, technical specifications, and original part numbers (part codes), but does not display their cost.

Installing the additional price file provides the following capabilities:
Price display: The cost of each part appears in the interface in the selected currency (current as of the date this price file was created).
Quotation generation: The ability to add parts to a “cart” and generate a preliminary estimate for repairs or parts orders.
Localization: Price files are typically released for specific markets (e.g., dealer prices in Europe or the U.S.), allowing the program to be adapted to local pricing structures.
[Image: bmw-etk-prices.jpg]

Need it? Push button Thanks, PM for pass | or by email right now.

.txt

BMW ETK + Prices new.txt (Size: 34 bytes / Downloads: 6) ]]> <![CDATA[Hello from Southwest Germany!]]> https://www.bimmerscene.com/showthread.php?tid=9559 Mon, 20 Apr 2026 09:06:01 +0000 Dee Luxe]]> https://www.bimmerscene.com/showthread.php?tid=9559
My name is Dario, I´m a german engineer and driving 6-cylinder BMWs only since 20 years. Fun fact: I´v never driven anything other than a six‑cylinder BMW, even my driving school car was a 320i :-)
On my E46, I started doing some coding with a Maxdiag 2 and would love to expand my knowledge on the F06.

Happy coding! Swerve

]]>
My name is Dario, I´m a german engineer and driving 6-cylinder BMWs only since 20 years. Fun fact: I´v never driven anything other than a six‑cylinder BMW, even my driving school car was a 320i :-)
On my E46, I started doing some coding with a Maxdiag 2 and would love to expand my knowledge on the F06.

Happy coding! Swerve

]]> <![CDATA[ISTA for Motorcycles]]> https://www.bimmerscene.com/showthread.php?tid=9558 Sun, 19 Apr 2026 18:44:04 +0000 Hibermanni]]> https://www.bimmerscene.com/showthread.php?tid=9558 Does anyone use ISTA for their motorcycle? I can enter the VIN and everything is recognized, but the “Product Structure” field is grayed out for me. Does anyone know how to fix this? I'm using version 4.57.21.

Is there a separate ISTA version just for Motorcycles?]]> Does anyone use ISTA for their motorcycle? I can enter the VIN and everything is recognized, but the “Product Structure” field is grayed out for me. Does anyone know how to fix this? I'm using version 4.57.21.

Is there a separate ISTA version just for Motorcycles?]]> <![CDATA[Troubleshooting a KAFAS camera issue on a BMW E70]]> https://www.bimmerscene.com/showthread.php?tid=9556 Sat, 18 Apr 2026 11:04:03 +0000 rikerud]]> https://www.bimmerscene.com/showthread.php?tid=9556
The original problem was multiple KAFAS-related faults in ISTA, including no communication with headunit, lane departure warning, and all-round view camera, along with a general KAFAS malfunction.

I first tested the original camera module. In ISTA it showed an internal hardware fault and calibration failed. In INPA the module responds normally and all voltages (1.8V, 3.3V, 5V, vehicle voltage) are within range, so power supply and wiring appear OK. However, the VIN from the camera shows as “yyyyyyyy” and VIN status says no access, which is not normal.

Based on that, I replaced the camera with a used unit (Continental KAFAS, similar part number). After installation, the replacement module behaves almost exactly the same. It communicates fine, shows proper hardware/software information, and all voltages and current are normal. But again in INPA the VIN camera shows as “yyyyyyyy” and VIN status says no access.

I then attempted calibration in ISTA with both the original and the replacement module. In both cases calibration fails with the same message (camera dirty/covered, no movement in front of camera, or camera defective). There is no difference in behavior between the two units.

So currently:

Power supply to KAFAS is OK
Communication with the module is OK
Calibration fails on both units
Both show invalid VIN (“yyyyyyyy”) in INPA

This suggests the issue is not wiring or vehicle-side, but related to the camera modules themselves. Either both modules are defective, not properly initialized, or have corrupted internal data (EEPROM/flash). Another possibility is compatibility or coding, but I would expect the VIN to be readable if the module was healthy.

Main question:
Is it normal on E-series KAFAS for the camera VIN to show as “yyyyyyyy” in INPA if it is uncoded, or does this indicate a defective or corrupted camera module?]]>
The original problem was multiple KAFAS-related faults in ISTA, including no communication with headunit, lane departure warning, and all-round view camera, along with a general KAFAS malfunction.

I first tested the original camera module. In ISTA it showed an internal hardware fault and calibration failed. In INPA the module responds normally and all voltages (1.8V, 3.3V, 5V, vehicle voltage) are within range, so power supply and wiring appear OK. However, the VIN from the camera shows as “yyyyyyyy” and VIN status says no access, which is not normal.

Based on that, I replaced the camera with a used unit (Continental KAFAS, similar part number). After installation, the replacement module behaves almost exactly the same. It communicates fine, shows proper hardware/software information, and all voltages and current are normal. But again in INPA the VIN camera shows as “yyyyyyyy” and VIN status says no access.

I then attempted calibration in ISTA with both the original and the replacement module. In both cases calibration fails with the same message (camera dirty/covered, no movement in front of camera, or camera defective). There is no difference in behavior between the two units.

So currently:

Power supply to KAFAS is OK
Communication with the module is OK
Calibration fails on both units
Both show invalid VIN (“yyyyyyyy”) in INPA

This suggests the issue is not wiring or vehicle-side, but related to the camera modules themselves. Either both modules are defective, not properly initialized, or have corrupted internal data (EEPROM/flash). Another possibility is compatibility or coding, but I would expect the VIN to be readable if the module was healthy.

Main question:
Is it normal on E-series KAFAS for the camera VIN to show as “yyyyyyyy” in INPA if it is uncoded, or does this indicate a defective or corrupted camera module?]]> <![CDATA[v.4.58.42_PSdZData_LITE]]> https://www.bimmerscene.com/showthread.php?tid=9554 Fri, 17 Apr 2026 02:16:29 +0000 Rob]]> https://www.bimmerscene.com/showthread.php?tid=9554 <![CDATA[F25 esys coding]]> https://www.bimmerscene.com/showthread.php?tid=9553 Wed, 15 Apr 2026 09:57:12 +0000 Arnoldas]]> https://www.bimmerscene.com/showthread.php?tid=9553
Dme encoding….]]>
Dme encoding….]]> <![CDATA[valid ICOM unit]]> https://www.bimmerscene.com/showthread.php?tid=9552 Wed, 15 Apr 2026 03:18:55 +0000 m2mostly]]> https://www.bimmerscene.com/showthread.php?tid=9552 <![CDATA[Hello from Ukraine]]> https://www.bimmerscene.com/showthread.php?tid=9551 Tue, 14 Apr 2026 22:40:44 +0000 Romzes84]]> https://www.bimmerscene.com/showthread.php?tid=9551 I drive a G30 540 LCI
Хотел бы присоединиться к сообществу.]]> I drive a G30 540 LCI
Хотел бы присоединиться к сообществу.]]> <![CDATA[Change Startup Video on NBT (non evo) HUs]]> https://www.bimmerscene.com/showthread.php?tid=9549 Tue, 14 Apr 2026 02:19:43 +0000 andreluizpd]]> https://www.bimmerscene.com/showthread.php?tid=9549

Video of it working:

https://youtu.be/cBRI5WnvA5M?si=ygT2Q-J7On_DSalU

[HIDE]
Ok, like on NBT Evo, you are going to need SSH access to the headunit, this can be done using hu tools and a usb drive or the way I did it:

Followed this guide and soldered two wires on the pcb and used a usb to serial TTL adapter, after that, just ran the commands and connected to ssh.

Code:
ip: 169.254.199.99

User: root

Password: ts&SK412

As a freebie I'll throw SCP, you can follow this guide, it's pretty similar, just use the file I linked here.

ok, now you need to find you current animation, they are not saved as avi but as PDDS files, you can search for eva_ani_0x00_07.pdds, changing the params for the ones on your HU.

this are weird files, so I had to reverse engineer (using AI of course) and then created a script to encode .mp4 videos to it.

You can check my script here. and the github if you want to check how it works.

With a compiled video you can just replace the file on the folder and check if the video is working.

I think this is it, any questions just LMK.

[/HIDE]]]>

Video of it working:

https://youtu.be/cBRI5WnvA5M?si=ygT2Q-J7On_DSalU

[HIDE]
Ok, like on NBT Evo, you are going to need SSH access to the headunit, this can be done using hu tools and a usb drive or the way I did it:

Followed this guide and soldered two wires on the pcb and used a usb to serial TTL adapter, after that, just ran the commands and connected to ssh.

Code:
ip: 169.254.199.99

User: root

Password: ts&SK412