This is why every e46 owner needs a working copy of dealer level software. Good examples are Brake Module replacements, or Steering Angle Sensor calibrations. Good news is that there is plenty of information in the web.Now tools like OBD Fusion and PA Soft might all be part of your arsenal for an e46 but there are times when neither of these will do the job. Its best if you do your own research as this topic is very extensive. I’m sure I missed a bunch of things but hope this gives you some idea. it also allows you to flash modules.Īll these softwares use the same root directories (ediabas and daten files) it also allows you to read/erase codes, activate different components, perform maintenance operations such as vanos bleed, SMG adaptation, etc. It contains the maintenance manual with instructions, torque values etc. Its a newer version of what used to be BMW DIS.
BMW ISTA CABLE UPDATE
Winkfp - engineering software to flash and update module firmware. NCS - engineering software to perform coding and customize lights, displays etc. INPA - engineering software to get real time information from modules, read codes and erase codes, you can also activate modules to check functionality. Good news is that there is plenty of information in the web.Ī good baseline explanation would be the following: Let me know if you need more details - I will get that laptop and give you exact folders, filenames, etc.Ĭlick to expand.Its best if you do your own research as this topic is very extensive. This was the last step that made everything work correctly - I reverted back to COM3 (I had followed instructions and made it COM9) and I also reverted back the latency to the default value (I think it I left it at 16 when everything worked - don't have that machine around right now). Just update your odb config file(s) to that value and don't touch Windows.
BMW ISTA CABLE DRIVERS
If your drivers installed correctly, keep the port that was assigned by the install.
BMW ISTA CABLE INSTALL
Here are all the deviations from published instructions that made the difference in my case: After confirming the installation and the correct position of the cable switch (my cable has that pins7/8 bridge switch), after locating and installing the USB drivers for the two devices that the cable chip adds to Windows (one was the USB "serial emulator" and the other was the "serial port"), I suspected, and that proved to be a correct assumption, that the prevalent instruction to use COM9 and latency of 1 to be the culprit.
I struggled for hours just the other day on a 2008 M5 (USA/SMG).