formskvm.blogg.se - Inpa kdcan

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.

If your drivers installed correctly, keep the port that was assigned by the install.

The bundle (and many other sources on the net) instructs to change port settings through Windows Device Manager to COM9.I copied the one that I found under the INPA/root EDIABAS. The ISTA EDIABAS did not have obd configuration file at all.Just copy the configuration from the one that is documented to the other one The bundle came with instructions to configure only one of them (the one used by INPA), but that left the one used by ISTA incorrectly configured. The bundle installs two separate EDIBAS installations.Since I was installing on Win 7 (not on 10), I had to source USB drivers myself (the ones that were bundled in the install weren't complete - missing Win 7 DLLs).

I chose to install Microsoft dependencies from Microsoft site and not the ones provided in the bundle (that is.

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).