I could not make the keys to the BMW F15 with Xhorse VVDI2. I must say that there was no access to the car, since it was far away and available only the BDC and the ISN with ECU.
BDC SWFL 00002419_052_010_030
This version of the SWFL is not supported in the VVDI2 and asks to upgrade the BDC.
However, I was unable to perform a BDC upgrade using E-SYS on a table without a car, error: error ID:9 – Vehicle not in state Pruefen_Analyse_Diagnose / ignition not activated (clamp 15 off). The test platform has an ignition contact in the dashboard connector, closing the contacts in the dashboard connector did nothing (I don’t have a dashboard and access to the car)
Has anyone done BDC/FEM programming with E-SYS on a table without a car? What I need for programming BDC/FEM with E-SYS on the table? Connecting the dashboard will allow performing programming?
And the Xhorse makes support for this old version of SWFL, I am silent about the SWFL version after the ISTA 4.28.32 update.
Had one FEM from F20 with the exact problem. Usually error: error ID:9 – Vehicle not in state Pruefen_Analyse_Diagnose / ignition not activated (clamp 15 off) means that you need to connect Xhorse ELV to get ignition on for programming with ESYS.
Option 2: Esys require “ignition on” to proceed through programming – this is nothing to do with the ELV. It won’t start the process otherwise. Things like CGDI or Yanuhua or something, they are bypassing the requirements going through anyway. When it fails then maybe a problem to recover.
Esys is much more reliable and never fails but won’t help you sometimes when AKL.
Option 3: When using ISTA it forces ignition on, and then you can plug in enet cable and flash using e-sys.
This is how I did it a long time ago when playing around with some spare FEMs.
->>> And someone feedback: I have tried this one couple of FEM modules – Does not work!!!
Please try one by one according to your situation, any question, please contact at www.xhorse.co.uk.