Here is a solution to BMW DASH v2.02 (which now updated to V2.1.0)interface diagnostic tool "vehicle not ready” error.

Here take a user real case…

O/S: windowsxp32bit

Model: E87andE83 (pre-200

Solutions from obd365.com technicians:

Tips:BMW DAS 

v2.1.0only works ok on most cars before 2008, but not all. And cars post-2008 hardly works with BMW DASH, but BMW ICOM A2/BMW Creator C310 ok.

– make sure com port setup on your PC is the same as that in the software

BMW Dash interfacereference:

1- Models tested ok:

1 Series: E81/E82/E87/E88

3 Series: E30/E36/E46/E90/E91/E92/E93

5 Series: E28/E34/E39/E60/E61

6 Series: E24/E63/E64

7 Series: E23/E32/E38/E65

8 Series: E31

X Series: X3-E83, X5-E53, X5-E70, X5-E71

Z Series: Z1-E30, Z3-E36, Z4-E85/E86, Z5-E52

MINI Series: MINI-R50/R52/R53/R55/R56/R57

2- systems tested no issues:

Engine system

Auto Transmission

SRS

ABS

Cruise system

Air-condition system

EWS

LKE

BUS etc.

3- functions without issues:

Connecting with all electronic control modules in the vehicle.

For all electronic control units reading identification data, sw/hw versions, user information fields.

For all electronic control units read and clear error (DTCs) memories – standart, shadow, history memory.

Possibility to read/program memory of electronic control units (including CAS modules).

Synchronization DME/DDE and CAS.

Posted by: jean at 02:05 AM | No Comments | Add Comment
Post contains 203 words, total size 4 kb.

Posted by: jean at 02:04 AM | No Comments | Add Comment
Post contains 168 words, total size 5 kb.

Here are someworking solutions onBMW Creator C110OBD2 code scanner "Communication error”.

1) Communication failed when access Z3 2000 ABS

I’ve just purchased a Creator C110 code reader to try and diagnose an abs fault on my 2000 Z3, but for anything I try and scan (not just the abs) the reader just shows ‘Communication Error’. The OBD port should be fine since it powers up the C110 and the software version says April 2014.Can anyone help me get get them talking?

Update: Now fixed
I have resolved this problem. If anyone in a similar situation is searching for solutions – the C110 scanner cannot read [at least my particular car] error codes from the OBD port below the steering column. It required a16 pin to 20 pin adapter(cheap $4.99) so that it could be plugged into the circular port located in the engine bay.

2) Communication error when diagnose 3 series E90 ABS

Notice how the ABS system only starts up when the start/stop button is pressed (turn 2) this is when the ABS connection should be tried.

Then select 3-series>DSC, this time C110 will show device and vehicle info, it works.

3) Creator C110 Communication failed on525i BMW 2009

Reference theCreator C110 scanner, when I use to test my 525i BMW 2009it shows communication Error with a number of the codes.
In particular I wish to use the PDC fault diagnosis which fails to communicate ”

Solved!

Updated to the latest V4.4 , the problem would solved !

How to Operation would help you :

Posted by: jean at 03:20 AM | No Comments | Add Comment
Post contains 342 words, total size 6 kb.

This is a customer solution onhow to use BMWcoding software NCS Expert & WinKFP to read/backup bmw cas and frm, how to write win and vo to frm, how to reset frm default and how to update frm. Try atyour on risk!

Tools to use:

Xprog-m v5.55

BMW ICOM A2

PC to run Xprog v5.5.5 software, NCS Expert and WinKFP

FRM fix list:

NCS expert read/backup cas and frm

NCS expert write VIN and VO to FRM

NCS expert reset frm default according to VO

WINKFP update frm

WINKFP trying to locate the zb or zusb

NCS expertread/backup cas and frm

goto work folder delete nettodat.trc and fsw_psw.trc

file

load profile

expert

f1 fg/zcs/fa

f3 zcs/fa f. ecu

r56

cas

f6 back

f4 process ecu

cas

f2 change job

codierdaten_lesen (reads coding from ecu)

f4 reading ecu

goto work folder move nettodat.trc and fsw_psw.trc to a new folder CAS Original make files read only

f1 change ecu

frm

f4 reading ecu

goto work folder move nettodat.trc and fsw_psw.trc to a new folder FRM Original make files read only

NCS expertwrite VIN and VO to FRM

file

load profile

expert

f1 fg/zcs/fa

f3 zcs/fa f. ecu

r56

cas

f6 back

f4 process ecu

frm

f2 change job

fa_write (writes FA aka VO to ecu)

f3 execute job

f2 change job

fgnr_schreiben (writes FG aka VIN to ecu)

f3 execute job

NCS expert reset frm default according to VO

goto work folder delete nettodat.trc and fsw_psw.trc

file

load profile

expert

file

edit profile

click FSW/PSW

uncheck FSW-/PSW-Manipulate with FSW_PSW.MAN

OK

OK

f1 fg/zcs/fa

f3 zcs/fa f. ecu

r56

cas

f6 back

f4 process ecu

frm

f2 change job

sg_codierren (writes coding to ecu)

f3 execute job

WINKFPupdate frm

f1 Comfort mode

f3 update ZUSB pick FRMR3

f4 enter vin

f8 done

f3 prog. zb-update

I don’t remember the rest from here but it updates the FRM. It takes 5-10 minutes and there is a progress bar.

If WINKFP update frm doesn’t work.

Updating WINKFP using BMW Coding Tool

extract the datens for your chasis into a folder

open BMW coding tool

select sp-source

choose the folder with the extracted datens

update WinKFP

WINKFP trying to locate the zb or zusb

(I don’t know)

f1 Comfort mode

f3 update ZUSB pick FRMR3

f4 enter vin

f8 done

f5 diagnosis

f1 ecu status

f2 ecu ident

http://blog.obd365.com/2016/10/14/ncs-expert-winkfp-read-write-reset-update-frm/

Posted by: jean at 01:57 AM | No Comments | Add Comment
Post contains 401 words, total size 4 kb.

Successfully repaired my dead FRM3 model on my BMW R56, with the MINIMUM cost (xprog and BMW ICOM Winkfp)! Here, i wanna share something useful with you all.xprog

Note: The setup below did work for me, but i’m not sure of yours. You are at your risk.

My model:

2011 BMWR56

Reason for FRM repair:

I disconnected the battery and the DME to change the thermostat and when I put it back together the FRM was dead.

Tool i used:
Except the BMW ICOM A2 emulator plus ISTA+ I had, i also was shopping for xprog v5.55 boxes from

http://www.obd365.com/wholesale/xprog-m-programmer-dongle-cas-decryption.html

Before this whole ordeal of the junk BMW/MINI FRM dying the only software I used was playing with was Carly for iOS and Dashcommand. But cannot solve issues.

BKGD location:

BKGD is on the HC(S)12 BDM adapter in the attached photo.

Vdd(+5V) = Vcc
RESET = B5
BKGD = B3
GND = GND (do not use the GND that is B0)

I think since we are not using the XCLKS and EXTAL flashing works with or without the BDM adapter.

Xprog m software installation:

I was not able to get this software to work with windows 7 64-bit. I was lucky enough to have an old HDD with windows 7 32-bit.
Before plugging in the xprog hardware go to system properties and change the device installation settings to never install driver software from windows update.
Xprogand FRM fix using Xprog:
Once the software was setup I hooked up the frm to the xprog and tried to make a backup of the existing EPROM via the MCU/MPU -> Freescale 9S12XE -> MC9s12XEQ384_EEE profile. Error partition corrupted. Set the sector to 16. I also made a backup of the existing P-FLASH via the MCU/MPU -> Freescale 9S12XE -> MC9s12XEQ384_P-FLASH profile. I think I got errors the first few times I tried to do this but restarting the program resolved the error.
In the MCU/MPU -> Freescale 9S12XE -> MC9s12XEQ384_EEE profile: erase, blank, open good EEE dump, write, verify, close, new, read.
This took several tries because the read back was still showing as blank.
I removed the BDM adapter and went direct into the xprog box. I also closed the program and reopened it when it kept giving me errors. After I was able to get a good write to the FRM I installed it back into the car and it was working again with a couple of errors (xenon high beam failure and fog light failure).

NCS expert& WINKFP setup for FRM:
In NCS expert I backed up the FRM, changed the VO and VIN, reset the FRM to factory and still had the high beam and fog errors. I proceeded to WINKFP to update the FRM and none of the ZB-numbers for my ECU worked. I updated WINKFP with BMW coding tool and the list of available ZB-numbers changed. After WINKFP was able to update the FRM I went back to NCS Expert and copied the VO from the CAS to the FRM and then set the FRM back to defaults. Everything was fixed. Fired up ISTA+ and cleared fault memory.

SOLVED!
Afterwards I hooked the frm back to the xprog and made a backup of the EEE and pflash.

My FRM:
R56 HIGH EKS 35 frm3r pl3 6135 3456395 01 23994322 sw141030 hw07 5324828c5
mc9s12xeq384mag
3m25j
Internet file:
R56 HIGH EKS 35 frm3r pl3 6135 3456987 01 23994322 sw156033 hw11 5324828r5

According to realoem parts 61353456395 and 61353456987 are Bilaterally exchangeable.
http://www.realoem.com/bmw/enUS/partsearch?id=SV33-USA-08-2010-R56N-Mini-Cooper_S&diagId=61_2102&q=61353456395

Hopefully this demonstrates to people it’s possible to repair these modules with the minimum cost.

Posted by: jean at 02:02 AM | No Comments | Add Comment
Post contains 608 words, total size 6 kb.

ISTA-P software 3.59 can be downloaded free here.ISTA-P is multilingual, so software is EN.



ISTA-P En version .exe



version 3.59.0.600



paste the 2 files in a directory and run the .exe


a phone and loader


Access to ista-P file



More features



BMW_ISPI_ISTA-P_SYS_3.59.0.600



the executable file
BMW_ISPI_ISTA-P_SYS_3.59.0.600.exe
https://mega.nz/#!Op1yTBiQ!_CW3hVON378zRRmE2Nq-6z-dwZXM3SyF0ZKO8RgA9FY

Posted by: jean at 06:55 AM | No Comments | Add Comment
Post contains 72 words, total size 4 kb.

Posted by: jean at 01:37 AM | No Comments | Add Comment
Post contains 363 words, total size 3 kb.

Here is a DIY guide onsetting up BMW ICOM ISTA+ BMW v4.01.22 Voltage Control tool. Simulates voltage of connected interface.

Posted by: jean at 03:21 AM | No Comments | Add Comment
Post contains 103 words, total size 3 kb.