[andyburm]

Using ISTA/P 3.62.4.001, the DME notified me of an available update but then the measures plan would always skip it (see picture before flash)

I decided to manually override it (7508916 -> 7539336), only to find out after that the variant is different (before ME72KWP0, now ME72KWP1). The flash was successful but the DME now has a different mileage than the EWS, making it driveable for only a short time. EWS-DME synch obviously doesn't work as it only aligns the immobilizer.

I cannot reverse it with ISTA/P and would like to, either adjust the mileage in the DME or flash it back. What software can I use and what are the basic steps....WinKFP ?

Thanks guys

[lynxbmw]

You can try to flash with Winkfp. The DME is ME 7.2 in group EK726.
So, in winkfp chose EK726 and then take 7539342.

[willisodhiambo]

Coming to think of it. Is it possible to connect the old tools via ICOM? I.e Inpa and the like? What settings does one need to make? I may need to work on an E39. I have Icom ABC.

[SweetBMW]

You need to use easyconnect program to allocate the icom. Then you can use icom with old tools.

[bohozoku]

You do not need any kind of software to allocate. Just open web gui and allocate through it.

[lynxbmw]

Guys, that's not what the author asked for.

You do not need any kind of software to allocate. Just open web gui and allocate through it.

True, but to make it work with "old tools" also there should be correct settings in EDIABAS, where all that(allocation and settings) are set easily by tool as easyconnect.

[DNK76]

ItoolRadar /easyconnect ICOM Reserve (easyconnect Icom lock)
Ediabas 7.3.0 Standard tools 2.12
(Do not use the Ediabas_730.msi installer
There is no REMOTE.ini file)

ICOM IP 169.254.92.38
EDIABAS.ini config

;#################
;# EDIABAS 7.3.0 #
;#################

;=============================================================================
[Configuration]
;=============================================================================
Interface =REMOTE
Simulation = 0

EcuPath =C:\EDIABAS\ECU
SimulationPath =C:\EDIABAS\SIM
TracePath =C:\EDIABAS\TRACE
TraceSize = 1024

ApiTrace =0
IfhTrace =0
; IfhnTrace = 0

; SystemTraceSys = 0
; SystemTraceBip = 0
; SystemTraceIfh = 0
; SystemTraceNet = 0

; BipDebugLevel = 0
; BipErrorLevel = 0

UbattHandling = 0
IgnitionHandling = 0
ClampHandling = 0

RetryComm =1
SystemResults = 1
TaskPriority = 0

; CodeMapping = C:\EC-Apps\EDIABAS\BIN\ansi2oem.tab
; LoadWin32 = 0

NetworkProtocol = TCP

; --- neu ab EDIABAS 7.2.0 ---------------------------------------------------
ShowIcon = 1
LogLevel = 0
TraceBuffering = 0
TraceHistory = 0
TraceSync = 1
SystemTraceSys=0
SystemTraceBip=0
SystemTraceIfh=0
SystemTraceNet=0
BipDebugLevel=0
BipErrorLevel=0
; TraceWriter = <FilePathName>

;=============================================================================
[TCP]
;=============================================================================
RemoteHost = 169.254.92.38
Port = 6801
TimeoutConnect = 2000
TimeoutReceive = 2000
TimeoutFunction = 10000
; TimeResponsePending = 5000
; DisconnectOnApiEnd = 1
; InitCmd0 = FE,04,00,03,01
; InitCmd1 = FD,05,00,03,01

;=============================================================================
[XEthernet]
;=============================================================================
RemoteHost = Autodetect
HeaderFormat = 0
TesterAddress = F4,F5
ControlPort = 6811
DiagnosticPort = 6801
TimeoutConnect = 20000

;=============================================================================
[IfhProxy]
;=============================================================================
Port = 6700


;#############################################################################
;#############################################################################
;## ausf?hrliche Variante von EDIABAS.ini (mit Kurz-Info und Default) ##

[hojo29]

The whole thing is quite easy with EasyConnect.
Set EasyConnect correctly and then go to check.
In Itool Radar the Icom is red and is reserved.
Then you can use Inpa or synonymous Winkfp

[willisodhiambo]

Thank you all. I did not expect that much guidance. So much to choose from!

So it seems one needs to reserve the ICOM the same way we do for Esys. If so it is damn easy. Will try it out. Thank you all.

---

Thank you all. I did not expect that much guidance. So much to choose from!

So it seems one needs to reserve the ICOM the same way we do for Esys. If so it is damn easy. Will try it out. Thank you all.

Oh, and I have easy connect and ediabas configurator. Just one more question.

With Easy connect, Type REMOTE, we have IP field and Mode field. What should be in the mode field? I see strange options like
Base
DiagBus
MOSTOBD_ab625 e.t.c

What are all these? Id like to understand. I ask because when using ISTA+ sometimes the connection with ICOM (when selecting the connection) shows DCAN and ETH but many times only DCAN. Must be some setting in the Ediabas, I think it shows both if interface is left as ENET. My understanding is that an ICOM has both Ethernet and K+DCAN capability and uses both?

Sorry for deviating the post from the original authors question but since I expect to work an E39 I would better get things right. A bricked pre Esys era car would be a pain for me.

---

;=============================================================================
[TCP]
;=============================================================================
RemoteHost = 169.254.92.38
Port = 6801


I changed mine to read the same as the ICOM IP. Mine reads

Remotehost = 192.168.68.40.

Is that correct or should it be left as default? It seems not to cause much issue but I may be wrong!

[jaramillo]

Use this tool, it is reeally esay to configure ediabas settings.