logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

VAG012 Cable Connection Issues with VCDS 17.3.1: Lights On but Not Connecting to Car

kotaphone 11550 16
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
Reply | New topic
  • #1 17387532
    kotaphone
    Level 9  
    Hello

    I have browsed a lot of forums and no one has had symptoms like mine.

    I have a VAG012 cable and it was working normally for me, but a few days it stopped.
    The computer was connected to the internet all the time and it's possible that it started to update and got off the cable software, or I don't know.

    Symptoms:
    Cable connected to the car, the green light and red light comes on, after a second the red light goes off, VCDS on and after pressing TEST everything is OK, only at the end there is a message: Not connected to the car.

    Would anyone advise what exactly I need to do to get everything working again?

    Data from USB View:
    Spoiler:

    Device Descriptor:
    bcdUSB: 0x0200
    bDeviceClass: 0x00
    bDeviceSubClass: 0x00
    bDeviceProtocol: 0x00
    bMaxPacketSize0: 0x08 (8)
    idVendor: 0x0403 (Future Technology Devices International Limited)
    idProduct: 0xFA24
    bcdDevice: 0x0600
    iManufacturer: 0x01
    0x0409: "Ross-Tech"
    iProduct: 0x02
    0x0409: "Ross-Tech HEX-USB"
    0x0409: "Ross-Tech HEX-USB"
    iSerialNumber: 0x03
    0x0409: "RT000001"
    bNumConfigurations: 0x01

    ConnectionStatus: DeviceConnected
    Current Config Value: 0x01
    Device Bus Speed: Full
    Device Address: 0x01
    Open Pipes: 2

    Endpoint Descriptor:
    bEndpointAddress: 0x81 IN
    Transfer Type: Bulk
    wMaxPacketSize: 0x0040 (64)
    bInterval: 0x00

    Endpoint Descriptor:
    bEndpointAddress: 0x02 OUT
    Transfer Type: Bulk
    wMaxPacketSize: 0x0040 (64)
    bInterval: 0x00

    Configuration Descriptor:
    wTotalLength: 0x0020
    bNumInterfaces: 0x01
    bConfigurationValue: 0x01
    iConfiguration: 0x00
    bmAttributes: 0x80 (Bus Powered )
    MaxPower: 0x19 (50 Ma)

    Interface Descriptor:
    bInterfaceNumber: 0x00
    bAlternateSetting: 0x00
    bNumEndpoints: 0x02
    bInterfaceClass: 0xFF
    bInterfaceSubClass: 0xFF
    bInterfaceProtocol: 0xFF
    iInterface: 0x02
    0x0409: "Ross-Tech HEX-USB"
    0x0409: "Ross-Tech HEX-USB"

    Endpoint Descriptor:
    bEndpointAddress: 0x81 IN
    Transfer Type: Bulk
    wMaxPacketSize: 0x0040 (64)
    bInterval: 0x00

    Endpoint Descriptor:
    bEndpointAddress: 0x02 OUT
    Transfer Type: Bulk
    wMaxPacketSize: 0x0040 (64)
    bInterval: 0x00



    Screens:
    Spoiler:

    VAG012 Cable Connection Issues with VCDS 17.3.1: Lights On but Not Connecting to Car VAG012 Cable Connection Issues with VCDS 17.3.1: Lights On but Not Connecting to Car VAG012 Cable Connection Issues with VCDS 17.3.1: Lights On but Not Connecting to Car
    .
  • ADVERTISEMENT
  • #2 17387626
    KapitanSTS
    Level 30  
    You have not installed anything else for the same USB?
  • ADVERTISEMENT
  • #3 17387844
    kotaphone
    Level 9  
    No. It stopped working during diagnostics.
  • #4 17565084
    Danon14119
    Level 10  
    Hello. Did the colleague who assumed the topic or someone else managed to solve the problem?
    I have the same and after installing the PL ADAKO 18.9 version it stopped working
  • #5 17565296
    dizba
    Level 33  
    And before downloading, did you read what is written on the adako website?
    "NOTE the software available on this website is intended only for cooperation with original devices from ADAKO, i.e. with HEX-NET, HEX-V2 interfaces. The program will not work with interfaces of other manufacturers. Original devices offered by ADAKO act as a hardware key to the VCDS program, and only they allow for legal and trouble-free use of the VCDS software we offer. "
  • ADVERTISEMENT
  • #6 17566304
    Danon14119
    Level 10  
    I know what it said, and I know it probably broke. The question is whether someone has worked through this problem and whether it can be resuscitated, and how.
  • ADVERTISEMENT
  • #7 17604529
    kotaphone
    Level 9  
    I'm sorry I was silent for so long.
    Unfortunately, I did not manage to solve this problem, because the topic turned out to be "too heavy" for me and the cable is lying and waiting for better times.
    I wrote to the company from which I bought the cable and got the answer that by trying to update the software, the cable was "damaged" and it should be reprogrammed and they can do it for a fee of PLN 50, so I gave up, because it will come out with shipments around PLN 80.
    If I ever find a way to program this cable, I will try to share the solution. But for now, I don't know where to start.
    Best regards.
  • #8 17646036
    zed1011
    Level 11  
    In such a situation, uploading a new batch helps.
  • #9 17647885
    bodzio012
    Level 33  
    kotaphone wrote:
    I'm sorry I was silent for so long.
    Unfortunately, I did not manage to solve this problem, because the topic turned out to be "too heavy" for me and the cable is lying and waiting for better times.
    I wrote to the company from which I bought the cable and got the answer that by trying to update the software, the cable was "damaged" and it should be reprogrammed and they can do it for a fee of PLN 50, so I gave up, because it will come out with shipments around PLN 80.
    If I ever find a way to program this cable, I will try to share the solution. But for now, I don't know where to start.
    Best regards.



    If it's a pity to spend on a cable that can be done / viewed a lot and with which you can repair a lot, it's better to go to the workshop and pay 50 for the connection immediately.
    You should be glad that your brand has such cheap diagnostic sites because you can't afford a Mercedes.
  • #10 17648092
    kotaphone
    Level 9  
    It's hard for me to comment on what you wrote ... because it does not contribute NOTHING to the topic. I can afford the cable. Even to F16 .... but that's not the point here.
    I paid 230 zlotys for this cable and I am not going to pay another 50 zlotys + 30 zlotys shipment for uploading the input to the cable. I bought a "New VCI" interface and that cable is lying around. And I just want it to be operational ...

    You are not able to help me and you do not know how to upload the input to the cable, just do not write ...
  • #11 17648162
    strucel
    Level 35  
    If you are counting on getting fix_kabel.exe, you had to write to Saint Nicholas, today is a magical day ...
    The cable to repair should be dismantled and see what processor it is built on - these better / more expensive versions have golpins on the board to which you connect the interface and program the processor
    http://www.eobdtool.com/blog/2017/08/how-to-repair-vcds-interface-for-any-language/
  • #12 17702664
    czester50
    Level 11  
    Dear colleagues.
    I greeted my friend "Chinczyk" with HEX + CAN VCDS 17,3 to scan my Audi A4 B7 car
    for possible errors, but as it turned out, the cable both on Xp and on win 7 checks individual measuring blocks, but stops at number 70 - the phone and does not want to move in order to completely scan the car.
    Did anyone have such a problem and how to solve it
  • #13 17714365
    freetz_master
    Level 31  
    czester50 wrote:
    Dear colleagues.
    Did anyone have such a problem and how to solve it

    Yes, buy / borrow original VCDS cable.
    It's not just a matter of stolen software. This is a question of a chip that likes to hang and when it blows up the gateway, you will understand that you should buy a cable for PLN 1200.
    http://www.eevblog.com/forum/reviews/ftdi-driver-kills-fake-ftdi-ft232/msg537012/#msg537012
  • #14 17725769
    czester50
    Level 11  
    freetz_master wrote:
    czester50 wrote:
    Dear colleagues.
    Did anyone have such a problem and how to solve it

    Yes, buy / borrow original VCDS cable.
    It's not just a matter of stolen software. This is a question of a chip that likes to hang and when it blows up the gateway, you will understand that you should buy a cable for PLN 1200.
    http://www.eevblog.com/forum/reviews/ftdi-driver-kills-fake-ftdi-ft232/msg537012/#msg537012

    Dear colleague
    Thank you for the suggestions. But as I wrote, the cable is not mine and I am not going to spend PLN 1,200 on a cable that I want to use to scan any errors in the car once.
    greeting
  • #15 17729966
    freetz_master
    Level 31  
    Well, then a visit to a professional workshop will solve the problem.
    You can't scan everything well with these Chinese cables. Even Russians on forums with stolen software know this.
  • #16 18360602
    ertes232
    Level 18  
    And this has to be written to quinola, let them make better cables
Reply | New topic
Report a violation of the law

Topic summary

The discussion revolves around issues with the VAG012 cable, which has stopped connecting to the car while using VCDS 17.3.1. Users report that the cable shows lights indicating power but fails to establish a connection. Several participants suggest potential causes, including software updates that may have damaged the cable. Some users mention that the cable may need reprogramming, which can incur additional costs. Others recommend using original VCDS cables for better reliability and suggest visiting a professional workshop for diagnostics. There are also discussions about the limitations of cheaper, non-original cables and the potential need for hardware repairs or replacements.
Summary generated by the language model.
ADVERTISEMENT