ISTA+ DME Blue Block - MEV1746 MV1746 Bmw E Series LCI

Post #1

N Online now

nogeren

Stock Member

Russia
Joined
06.07.2026
Messages
11
Reactions
0
Location
Russia
Hello, please help. BMW e87 lci 2008 n46b20
I have:
  • original DME
  • donor DME
both marked 7 585 247 and 0 261 s04 289
The original one broke at the service center!
They said the unit wasn't communicating, but I saved it.
We bought a donor kit - (CAS + DME + key) - installed it, and the car started. (The donor VIN, ISN, etc., was preserved.)

The donor DME was flooded.
I extracted the entire donor backup using ktag.
1) 973 KB file
2) 128 KB eeprom file
3) 4 MB flash file
4) 2 MB MPC
I decided to read the ORIGINAL DME.
1) 284 KB file
2) 128 KB eeprom file
3) 30 KB flash file (garbage)
4) 2 MB MPC

I decided to upload the donor's flash to the ORIGINAL DME
and read the ktag again.

1) 627 KB file
2) 128 KB eeprom file
3) 4 MB flash file (inside the donor's flash)
4) 2 MB MPC

The car now recognizes the original DME.
The DME is now blue in ISTA+, previously, it wasn't detected at all.

Available
ISTA+ 4.50.12 ISTA-P 3.72 WINKFP
VCX SE BMW
KTAG KESS R207+
ISTA+ 4.50.12 - doesn't program, says go to ISTA-P 3.72 - it's been working for us for a very long time....

WINKFP gives this error
switching programming mode failed 03ME17, DIAGNOSE_MODE (ECUPM) ERROR_ECU_SECURITY_ACCESS_DENIED_ SECURITY_ACCESS_REQUESTED
Flash download failed 03ME17, FLASH_SCHREIBEN (..): IFH-0009: No response from controlunit
Flash download failed 03ME17, FLASH_SCHREIBEN (..)
Flash download failed SG_PROGRAMMIEREN
Flash download failed
Tell me where I made a mistake?
 
Ratings and Reviews
Total ratings: 0

Post #21

2B79 была ошибка всегда еще до запуска мотора, еще когда я восстанавливал dme
 

Post #22

That's an important detail — it changes the priority.

What it means
A fault that was already there before the engine ever ran, during the DME restore work, is most likely a legacy entry from that period. With ignition on and the unit in the broken/mixed state, the DME runs its output-stage checks anyway, so an activation fault on the inlet VANOS output would set without a single revolution. That is not evidence of a real electrical defect now that the block is restored, programmed and coded.

How to prove it
The only thing that matters is whether 2B79 is current or just stored after a clean cycle on the restored DME:

  • Plug the MAF back in (this also removes 2EF2).
  • Clear the full fault memory.
  • Ignition off, wait for bus sleep (~1 min), then start, idle to warm, short rev to ~3000 rpm, a few load changes so VANOS actually gets commanded.
  • Re-read and look at the fault details, not just the code: the "fault present / fault not present" flag and the frequency counter. If the counter stays at the old value and the flag says not present, the entry is history — ignore it.

If it comes back as current after that, then do the checks from my last post: coil resistance on both VANOS solenoids compared against each other, continuity to the DME pins, then ISTA component activation on the inlet valve.

Separate issue — the noise
Still unresolved, and that one I would not drop. Same at cold and hot, unaffected by new idlers and belt, PS pump quiet but steering feels weak on pressure — that combination still points at the brake vacuum pump (rear of the head, driven off the exhaust cam) or, given the weak steering assist, the PS pump itself even if it isn't the noise source. A stethoscope on the rear of the head versus the PS pump will separate them in minutes.

If you can, post a short video with the sound and the fault detail screen for 2B79 (with counter and present/not-present), plus your current I-level after the update. That's enough to close both items.
 
Activity
So far there's no one here