logo elektroda
logo elektroda
X
logo elektroda

I am looking for a driver for the VAG KKL 409.1 cable

daniel95 121896 35
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 14867649
    daniel95
    Level 9  
    Hello, I'm looking for a Usb2.0-Serial driver for the VAG KKL 409.1 win 7 64bit cable, I was looking for different str and lip: /, the system will not install itself. If anyone has it, please send me a link on a private message.
  • ADVERTISEMENT
  • #3 14867755
    daniel95
    Level 9  
    Yes. I looked but I can't install it: / because I don't know what file format it is. And where to upload this file / files?
  • #4 14868069
    grala1
    VAG group specialist
    After inserting the cable into the USB, if the system does not find the driver, it will ask you to indicate the location of the driver and then you will point it to it.
    You can put it in the SYSTEM32 / DRIVERS folder in WINDOWS.
  • #5 14868309
    daniel95
    Level 9  
    I did girla1 as you write and it still does not see the system driver: / I also tried to point it to the target and automatically. Any other suggestions on how to start it?
  • #6 14868446
    tzok
    Moderator of Cars
    There were a lot of cables on the counterfeit FT232 chips, which were blocked by the driver provided by Windows Update. Provide the hardware identifier (PID, VID) from the device manager.
  • #7 14869991
    daniel95
    Level 9  
    I don't know if that's what you meant.
    USB \ VID_1A86 & PID_7523 & REV_0254
    USB \ VID_1A86 & PID_7523
  • Helpful post
    #8 14870266
    PiotrT
    Level 19  
    USB \ VID_1A86 & PID_7523 is CH340 / CH341 chip identification not FT232.
    Drivers for CH340 / CH341 attached.
  • #9 14870509
    daniel95
    Level 9  
    Many thanks are the drivers!

    Added after 54 [minutes]:

    I have one more problem, the cable / program does not always read the computer from the car, what is it? I use Vag gives on Engine and it doesn't read anything until after a few tries
  • ADVERTISEMENT
  • #11 16026723
    Pioter.K
    Level 14  
    Hello
    I'll reheat the cutlet because I don't want to create a new thread.
    What is the reason why the advanced properties of the USB port cannot be changed after installing the drivers for the Facebook? In my case, when I enter the advanced settings, I have "Use FIFO buffers" and two sliders for the receive buffer and the transmit buffer. Lack of possibility to select transmission buffers (sliders and settings from 4096 to 1024).
    Thanks in advance for the info.
  • #12 16026738
    PiotrT
    Level 19  
    You probably have an interface with a CH340 / 341 chip. In this case, these settings cannot be changed.
  • #13 16026769
    Pioter.K
    Level 14  
    Hello
    PiotrT wrote:
    You probably have an interface with a CH340 / 341 chip. In this case, these settings cannot be changed.

    Is it good or bad?
  • #14 16026856
    tzok
    Moderator of Cars
    Pioter.K wrote:
    is it good or bad? Yes, it's like a Chip 340T
    Badly. Cables based on different variants of the FT232 chip work much more stable and connect to a larger number of modules.
  • #15 16027070
    Pioter.K
    Level 14  
    tzok wrote:
    Pioter.K wrote:
    is it good or bad? Yes, it's like a Chip 340T
    Badly. Cables based on different variants of the FT232 chip work much more stable and connect to a larger number of modules.


    Hello, you cheered me up.

    One more question about this Chip 340T.
    After installing the drivers, I only have a mention in the device manager in the port (COM, LPT) with the content USB-Serial CH340 (COM2). There is no mention of an interface in Universal Serial Bus Controllers. Is that good or is there something else missing from the system? WinXP system.
  • ADVERTISEMENT
  • #16 16441455
    malqsch
    Level 2  
    Hello, maybe someone will be able to help me explain why I do not want to detect the KKL VAG-COM for 409.1 cable. The drivers are supposed to be, in the device manager it shows CH340 in the USB-SERIAL ports, but after starting the VAG-COM program, it shows the message Port status: ok Interface: not found.
  • #17 16441473
    PiotrT
    Level 19  
    Interface power supply connected and appropriate COM port selected on VAG-COM?
  • ADVERTISEMENT
  • #18 16442909
    malqsch
    Level 2  
    PiotrT wrote:
    Interface power supply connected and appropriate COM port selected on VAG-COM?


    COM3 port selected both in the program and in the device manager, anyway, the game because the program shows "Port: ok", and when I change the name of the port, it does not even detect it.
    The power supply probably works because after connecting the cable, the LED on the other end of the cable lights up.
  • #19 16443142
    tzok
    Moderator of Cars
    For the test, the cable must be connected to the 12V power supply from the side of the OBD-II plug, i.e. plugged into the car.
  • #20 16443428
    malqsch
    Level 2  
    People on the forum previously wrote that it does not have to be connected, i.e. that without connecting it to the car, it should show that the interface is there, but no connection to the car. For me it shows "no interface".
  • #21 16443449
    tzok
    Moderator of Cars
    And I write to you that it must be connected ... plug in, you will see.
  • #22 16446874
    PiotrT
    Level 19  
    malqsch wrote:

    The power supply probably works because after connecting the cable, the LED on the other end of the cable lights up.


    This LED often indicates that the interface is powered from the USB port
    Therefore, during the test, the interface is to be connected to the power supply from the installation, i.e. + 12V.
  • #23 16483141
    xmariomx
    Level 9  
    I will join the topic. I have the same problem as my colleagues above. CH341SER driver installed, lots of different programs and none of them want to detect interface Continuous message Port status: ok Interface: not found and so on. Tried other random drivers but no changes. The port in the manager is the same as in the program. I checked, including as an administrator, on two different laptops with win7 and win xp, connecting to the car and not. I have no idea what to do now. Anyone help me connect to the car?
  • #24 16483750
    pepe150
    Level 36  
    CH341, I only think of a programmer for I2C memory. So this driver won't get it.
    Look for FTDI or Profilic. Because they are popular RS232 controllers.
  • #25 16483870
    xmariomx
    Level 9  
    pepe150 wrote:
    CH341, I only think of a programmer for I2C memory. So this driver won't get it.
    Look for FTDI or Profilic. Because they are popular RS232 controllers.

    I did with FTDI but I don't know if it's good. I first installed it as a "serial bus controller" - nothing found and had no port. Then I installed it like a port (I installed different versions) and then interface: Not Found error. Of course, I check now without a car, but it should be up to the vaga anyway.
    I have no idea how to make a Profilic.
  • #26 16483914
    tzok
    Moderator of Cars
    You only have to install the drivers for the system your cable is on - based on the hardware ID. After installing the correct driver, a virtual COM port (USB Serial Port) will appear in the system and that's it. The program will not detect any interface that does not have a 12V power supply from the OBD-II plug.
  • #27 16483973
    xmariomx
    Level 9  
    Now i do not understand. Device ID: USB \ VID_1A86 & PID_7523 & REV_0254 USB \ VID_1A86 & PID_7523. After connecting the device, I have USB2.0- Serial without a driver, I install the driver on it as a universal serial bus controller (installs twice on the same device) and the second time I install I have a blue screen - the driver is not installed. Only installs "digitally assigned" drivers. It is enough to install the COm and LPT port once, but I do not have how to check now if it will actually see the vag only when I connect to the car.
  • #28 16484013
    tzok
    Moderator of Cars
    xmariomx wrote:
    VID_1A86 & PID_7523
    So you have a cable on the CH340 chip and you have to install such a driver, not some "universal serial bus controller".

    The driver is here: https://www.elektroda.pl/rtvforum/topic2612980.html
    ... or directly from the manufacturer's website: http://www.wch.cn/download/CH341SER_ZIP.html
    Description of the installation here: https://www.elektroda.pl/rtvforum/topic2324818.html
  • #30 16484049
    tzok
    Moderator of Cars
    pepe150 wrote:
    After VID and PID it finds CH340 - not CH341.
    There is the same driver for CH340 and CH341 ...

Topic summary

The discussion revolves around finding and installing a USB to Serial driver for the VAG KKL 409.1 cable on a Windows 7 64-bit system. Users share links to drivers, specifically for the CH340/CH341 chip, and provide troubleshooting advice for installation issues. Common problems include the system not recognizing the driver, the need for a 12V power supply from the OBD-II plug for proper operation, and the distinction between different chipsets (FT232 vs. CH340). Users also discuss the limitations of the KKL cable in modern vehicles that primarily use CAN protocols, leading to connectivity issues with VAG-COM software.
Summary generated by the language model.
ADVERTISEMENT