There seems to be a lot of confusion regarding how to configure

There seems to be a lot of confusion regarding how to configure things for NSCEXPERT and various
cables. Not all cables use the same device drivers and that is where most of this confusion stems from.
If this helps anyone at all, great, if not, putting this together helped me understand things a little better.
My setup:
Vista 32-bit, cable from Patryk’s group buy.
I ran C:\EDIABAS\hardware\OBDSETUP.exe and got a warning, so I used regedit to manually edit the
registry. I am not sure OBDSETUP does anything else than to create these registry keys/values.
I don’t think my cable and its associated drivers use these registry keys/values since the list of drivers
associated with my cable do not include ‘serial.sys’. One of my other COM ports, COM6, uses serial.sys,
which is a Microsoft serial device driver.
My cable uses device drivers from FTDI Ltd. These drivers have different input windows and do not have
FIFO Receive and Transmit buffer settings. I think these settings and the serial.sys device driver are used
if the cable requires it. One of the device drivers used ‘FTSER2K’ has registry keys/values like the ones
used by ‘serial.sys’.
I am not really sure if I needed to have an OBD.ini file, but I created one manually and put it in
C:\windows. My obd.ini file has the following contents.
[OBD]
Port = Com1
;Einstellen der seriellen Schnittstelle
;erlaubte Werte: COM1, .., COM99
TRACELEVEL = 0
;nur für interne Fehlersuche
;erlaubte Werte: 0=aus, ansonsten 0x00000000 .. 0xFFFFFFFF
RETRY = OFF
;Wiederholung im Fehlerfall, wird von EDIABAS bereits gemacht, sollte deshalb aus sein.
;erlaubte Werte: OFF, ON
MODE=NORMAL
;Bei KBUS werden DS2-Telegramme in K-Bus-Telegramme umgewandelt.
;Kommunikation nur am einzelnen DS2-Steuergerät am K-Bus zulässig.
;erlaubte Werte: NORMAL, KBUS
HARDWARE=OBD
;OBD-Stecker OBD
;OBD-Stecker am USB->Seriell-Adapter USB
;alte ADS-Hardware ADS
UBATT=ON
;Bei UBATT=OFF wird der Batteriestatus nicht über die Hardware ermittelt
;sondern fest auf „Batteriespannung vorhanden“ gesetzt.
;Workaround für den Hardwarefehler des LAPTOP DELL LATITUDE D600.
;Dieser ist nicht in der Lage den Batteriestatus richtig zu erkennen.
Initially when I ran NCSEXPERT I was getting an COAPI-1000 error when I tried to load a profile. I then
deleted everything, C:\NCSEXPERT, C:\INPA, and C:\EDIABAS, then recreated them using the latest ones.
After doing this I got it to work and my car now chirps when I lock/unlock my car. I had previously
installed the alarm system.
The following screenshot shows my device manager. Under Ports (COM & LPT), USB Serial Port (COM1)
is listed. COM1 is used by my OBD cable. I have a Bavarian Technic tool as well…it is listed under the
Universal Serial Bus controllers as “Durametric Diagnostic USB”. The BT tool also uses drivers from FTDI
Ltd., although they are different drivers than the ones used by the OBD cable I use with NCSEXPERT.
After selecting Properties on USB Serial Port (COM1) the following windows can be displayed. These
show which drivers are being used .
Here are the advanced settings for COM1. Note no mention of FIFO buffers.
Shown next are property windows associated with my BT tool. Note that drivers from FTDI Ltd. Are also
used, but they are different ones. The BT tool uses DLLs and public key encryption to allow it to work
rather than COM ports.
Finally, the next images show the property windows associated with my COM6. Note the serial.sys
device driver is used, which used the registry keys/values mentioned earlier.
The advanced settings specify FIFO Receive and Transmit Buffers.