This can be fixed by going to the c:\windows\system32\drivers folder and deleting ftser2k.sys and then un-installing the driver, plug the cable back in, and reinstalling if requested, using the FTDI driver that comes with EvoScan or ECUFlash in the drivers folder.
On some strange situations, when plugging in the "FTDI USB to Serial COM" cable it pops up a message informing you that the driver was not digitally signed correctly and will be disabled. Remember x86 means 32bit windows, and 圆4 means 64bit version of windows. Then reinstall from the evoscan drivers folder or ecuflash installer, then it will work. On my pc I found oem10.inf oem11.inf oem12.inf oem14.inf.
This happens 1% of the time, and to fix this you need to go into the c:\windows\inf\ folder and do a windows search "in file contents" for the word FTDI and delete just those specific inf files.
Sometimes the driver just won't work no matter how much you install/uninstall ecuflash or evoscan. Openport 1.3D/1.3R/1.3U FT232R and FT232RQ are faster at datalogging pre 2007 vehicles than the OpenPort2.0 NXP chipset. Should do, ask support for further instruction. * ask support for instructions to change USB pid and descriptor to CC4A you will find that for all features of EvoScan such as actuators and datalogging, they are 100% identical cables.Įcuflash is not licensed for use with 1.3R cables.īut you can use EvoScan for reflashing under the Reflash menu.
a special serial number is loaded into each 1.3U cable that allows Ecuflash software to recognise it as a licensed cable, but this is a software check thing, not a physical cable thing. IMPORTANT NOTE: For Mitsubishi DSM/3000GT use EvoScan v2.5, and here are some additional instructionsġ.3R and 1.3U are the exact physical same cable. IMPORTANT NOTE: OpenPort 2.0 is required for Reflashing 1998-2000 H8 Mitsubishi Evo5/6/6.5 TME/DSM ECUs. IMPORTANT NOTE: OpenPort 1.3D/1.3R/1.3U is twice as fast at datalogging than OpenPort 2.0 EF = EcuFlash Fuel and Timing Reprogramming Support Included) (ES = EvoScan Reflashing/Reprogramming Support included. That’s all about how to set up BMW ENET cable with BMW ISTA.EvoScan v2.9 Supported Vehicles and Best USB Cable for your vehicle: Or here is another alternative way after you click the Setting button and select “VCI Config” tab:Ĭhoose “HO-ICOM ENET direct connection” option and set ENET mode with empty IP-Address. Select your ENET connection from the list and click “Set up connection”.Īnd just wait the vehicle identification process complete! Select “Read out Vehicle Data” tab and click “Complete Identification”. Select “VCI Config” tab and “HO-ICOM ENET local and ISIS network” option, click the OK button.īack to main menu and click the Operations button. Turn on car ignition and run BMW ISTA Rheingold. Uncheck the box “Connect a host virtual adapter to this network”. Open Virtual Network Editor and disconnect form the host all adapters with Subnet Address 169.254.0.0.
Or if you install ISTA in VMWare, try this way: Select Internet Protocol Version 4 (TCP / IP) and click the Properties button.Įnter 169.254.1.1 for the IP address and 255.255.0.0 for the subnet mask then press the OK button. Select the Ethernet that is connected to the vehicle and open the Properties screen. Newest BMW Rheingold ISTA-D 4.12.12 ISTA-P 3.65.0.500 DownloadĪnd here is a collection about BMW Coding/Programming,check it here: BMW Coding/ProgrammingĬonnect your laptop/PC with vehicle using the ENET cable.Īfter that, go to Control Panel→ Network and Internet→ Network Connections. Here is a guide to show you how correctly connect and set up BMW ENET Cable with BMW ISTA Rheingold software! It is the first step to use this cheap BMW F Series coding cable instead of ICOM!īMW ENET (Ethernet to OBD) Interface Cable