Register
Page 578 of 854 FirstFirst ... 78478528568573574575576577578579580581582583588628678 ... LastLast
Results 8,656 to 8,670 of 12803
  1. #8656
    DK Veteran
    Join Date
    Feb 2013
    Posts
    392
    Thanks Thanks Given 
    73
    Thanks Thanks Received 
    94
    Thanked in
    77 Posts

    Default

    It think You missed the part in the Info or Read ME pdf file about STC.
    You have there on pcb IC8 - STC, so you need to cut the trace to R50 and after try again

  2. #8657
    Newbie
    Join Date
    Mar 2010
    Posts
    5
    Thanks Thanks Given 
    0
    Thanks Thanks Received 
    1
    Thanked in
    1 Post

    Default

    Quote Originally Posted by alexm1 View Post
    It think You missed the part in the Info or Read ME pdf file about STC.
    You have there on pcb IC8 - STC, so you need to cut the trace to R50 and after try again
    ah, okay. i looked for an STC label on a chip, but the sucker is not labeled. ok first mistake solved. do i have to resolder the connection after flashing?

    my problem is now, that i flashed die v2.ept and the cable wont be detected correctly (see attached screenshot of Mprog and windows device manager). cutting the r50 trace did not help here.
    Mprog and ft_prog do not detect this device and i cannot reflash it.
    is there a way to reflash it and which file is the right one (ftdi_mprog_BMBL.ept or ftdi_mprog_RLRQ.ept)?
    Attached Images Attached Images

  3. #8658
    DK Veteran
    Join Date
    Feb 2013
    Posts
    392
    Thanks Thanks Given 
    73
    Thanks Thanks Received 
    94
    Thanked in
    77 Posts

    Default

    1. After cutting trace to R50 no need to restore that line.
    2. Your FTDI (near usb wires) is FT232RL ,so you need RLRQ ept file.

    Now, go to Dev. Manager
    select your usb device Hex V2...(first time when I see that name for a cable) Properties- dropdown menu Hard. IDs and write here what you see there.

    In order to reflash ftdi you should do something with that yelow warning sign on your device hex v2... maybe forcing to instal driver again.

  4. #8659
    Newbie
    Join Date
    Mar 2010
    Posts
    5
    Thanks Thanks Given 
    0
    Thanks Thanks Received 
    1
    Thanked in
    1 Post

    Default

    Quote Originally Posted by alexm1 View Post
    1. After cutting trace to R50 no need to restore that line.
    2. Your FTDI (near usb wires) is FT232RL ,so you need RLRQ ept file.

    Now, go to Dev. Manager
    select your usb device Hex V2...(first time when I see that name for a cable) Properties- dropdown menu Hard. IDs and write here what you see there.

    In order to reflash ftdi you should do something with that yelow warning sign on your device hex v2... maybe forcing to instal driver again.
    VID: 0483
    PID: A0CB
    Rev: 0600

    i will search for an driver and try to get rid of the warning sign.
    Thanks so far!!

  5. #8660
    Newbie
    Join Date
    Mar 2010
    Posts
    5
    Thanks Thanks Given 
    0
    Thanks Thanks Received 
    1
    Thanked in
    1 Post

    Default

    Quote Originally Posted by x-trac View Post
    VID: 0483
    PID: A0CB
    Rev: 0600

    i will search for an driver and try to get rid of the warning sign.
    Thanks so far!!
    yeah!!!!!!


    newest info:
    i could reflash the FTDI chip and with the broken R50 Trace HWType.exe can read all data!!
    To recover from the previous state i installed the ftdi USB Converter Driver (selected in the device list of windows driver installation wizard). this allows Mprog to find the device and reprogram it with the correct settings! --> Big thanks to alexm1! the STC hint did the magic!!

    I used VAGCOM_EEWriteLang.exe to write the german Version. Everything works just fine with the v8 Loader and 18.9 DRV (v7 is not working).

    Interface is found and license is valid!!

    i already tested it in the car!!

    Thanks for the help!

  6. #8661
    Newbie
    Join Date
    Oct 2018
    Posts
    3
    Thanks Thanks Given 
    4
    Thanks Thanks Received 
    0
    Thanked in
    0 Posts

    Default

    Thanks to all who managed to inform me the vcds cable is of no use. Will look at getting another cable with the atmega 162 chips etc.

    Many thanks!

  7. #8662
    Member
    Join Date
    May 2018
    Posts
    84
    Thanks Thanks Given 
    29
    Thanks Thanks Received 
    16
    Thanked in
    13 Posts

    Default

    Guys

    need little help about mileage check

    When i have VCDS 15.7 the function "EDC 15 16 Mileage" works normaly.
    However, at this newest versions (17.8-18.9) it isnt working anymore

    Does anyone know something about it ?
    Is something related to clone cable PCB or only software version ?
    67419702_322475231804386_820124812625051648_n.jpg

  8. #8663
    DK Veteran
    Join Date
    Feb 2013
    Posts
    392
    Thanks Thanks Given 
    73
    Thanks Thanks Received 
    94
    Thanked in
    77 Posts

    Default

    Did you tested on the same car with both versions and with one is ok and the other not?
    Because not al ECU's supports this function.

  9. #8664
    DK Veteran

    Join Date
    Jul 2016
    Location
    Vilnius
    Posts
    1,188
    Thanks Thanks Given 
    58
    Thanks Thanks Received 
    566
    Thanked in
    380 Posts

    Default

    TBH, this never worked for me and I considered this as crappy RT implementation (because other tools were able to retrieve this on same car).
    Can you check with 17.1.3?
    I can calculate ABS module codings for:
    * Continental/Teves MK60EC1 and MK60;
    * TRW systems in Passat B6 / B7 / CC /Tiguan;
    * MK100
    ;
    * Bosch ABS8.2, ABS9.0 and ESP8.2, ESP9.0;
    * EBC 460 (UP!, Mii, Rapid, CitiGo, Fabia, Toledo, etc) New!
    *
    ... and other VW/Audi/Seat/Skoda modules.I can assist with repairing \/CDS interfaces.

  10. #8665
    Newbie kurekpit's Avatar
    Join Date
    Sep 2018
    Location
    Kaczogrod
    Posts
    1
    Thanks Thanks Given 
    10
    Thanks Thanks Received 
    0
    Thanked in
    0 Posts

    Default

    Hello Guys.
    I have older interface 9.081.
    Is any chance to upgrade it to newer version?
    VCDS-AKP-9081_front.jpgVCDS-AKP-9081_back.jpg

  11. #8666
    Top Poster

    Join Date
    Mar 2018
    Posts
    174
    Thanks Thanks Given 
    42
    Thanks Thanks Received 
    140
    Thanked in
    64 Posts

    Default

    Quote Originally Posted by kurekpit View Post
    Hello Guys.
    I have older interface 9.081.
    Is any chance to upgrade it to newer version?
    VCDS-AKP-9081_front.jpgVCDS-AKP-9081_back.jpg
    Yes, if the bootloader is locked you have pins for the programmer, version 0x44.

  12. The Following User Says Thank You to Roma77 For This Useful Post:

    kurekpit (30th July, 2019)

  13. #8667
    DK Veteran

    Join Date
    Jul 2016
    Location
    Vilnius
    Posts
    1,188
    Thanks Thanks Given 
    58
    Thanks Thanks Received 
    566
    Thanked in
    380 Posts

    Default

    oops, remove.

  14. #8668
    Newbie
    Join Date
    Jul 2019
    Posts
    8
    Thanks Thanks Given 
    1
    Thanks Thanks Received 
    6
    Thanked in
    4 Posts

    Default

    Quote Originally Posted by fantomel View Post
    A little history lesson maybe some of you need it

    EN - DE - FR - IT - ES - PT - PL - HU - RO - NL - RU - SWE - CZ
    Hello my friend. Is there any Chinese(ZHS) old version for download?

  15. #8669
    Newbie
    Join Date
    Jul 2019
    Posts
    19
    Thanks Thanks Given 
    10
    Thanks Thanks Received 
    1
    Thanked in
    1 Post

    Default

    Hi guys,
    As always, if something is not working anymore go to the world wide web. My VCDS 11.11 cable is not recognised by the Windows 7. I was working on my IQ in adaptation and of a sudden the program not responded, I tried closing it and it didn't even from task manager, then I shut down my laptop. After restart, the cable is not seen as a ross tech device, is unknown device- in VCDS interface is not found.
    I red trough some pages here and I downloaded the contents and when I tried running the ..HWType.exe it says Interface not found! Is it dead for good? Or I am doing something wrong?
    Thanks a bunch! EDIT : Pictures attached! The v regulator has been changed in the past and the version updated(by the vendor). Thanks!
    IMG_20190731_160852.jpgIMG_20190731_160910.jpg
    Last edited by ely862me; 31st July, 2019 at 02:14 PM.

  16. #8670
    DK Veteran

    Join Date
    Jul 2016
    Location
    Vilnius
    Posts
    1,188
    Thanks Thanks Given 
    58
    Thanks Thanks Received 
    566
    Thanked in
    380 Posts

    Default

    Most likely FTDI died. If you really have read through some pages back, you most likely know that you must post pics to keep the discussion constructive, haven't you?
    I can calculate ABS module codings for:
    * Continental/Teves MK60EC1 and MK60;
    * TRW systems in Passat B6 / B7 / CC /Tiguan;
    * MK100
    ;
    * Bosch ABS8.2, ABS9.0 and ESP8.2, ESP9.0;
    * EBC 460 (UP!, Mii, Rapid, CitiGo, Fabia, Toledo, etc) New!
    *
    ... and other VW/Audi/Seat/Skoda modules.I can assist with repairing \/CDS interfaces.

  17. The Following User Says Thank You to hid3 For This Useful Post:

    ely862me (31st July, 2019)

 

 

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.