Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 39

Thread: Autoscan hangs and 14.2.3 won't connect

  1. #11
    Verified VCDS User
    Join Date
    Feb 2014
    Location
    USA
    Posts
    53
    Post Thanks / Like
    It's the same. This time the car was in the list first time, so that may have been user failure.
    On the autoscan, it appears to miss the ABS controller altogether, it goes straight from the transmission (02) to the Kessy (05), and fails to communicate with the Kessy. If I manually look at controller 05, the initial interrogation appears successful, it knows what the controller is, but it can't get any further. The comm status shows IC=1 TE=0 RE=0.

  2. #12
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    24,688
    Post Thanks / Like
    Blog Entries
    1
    OK, sounds like something either in the ABS controller or the Kessy is messing up that scan. It would be nice know which one. With the PC-based VCDS you can edit the AutoScan.txt file and create a custom entry for your car. Copy the line for the Phaeton, and try removing 03 and/or 05 from it. If eliminating one module form the list of modules to be scanned gets you through the rest of the car, then we'd know which module to try to get in here, and getting one module is usually a lot easier than getting a whole car, especially when the car is kinda rare.

    -Uwe-

  3. #13
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    24,688
    Post Thanks / Like
    Blog Entries
    1
    Quote Originally Posted by invisiblewave View Post
    Still only works in infrastructure mode with my Acer Aspire.
    Interestingly enough, the eeePC that won't find any HEX-NETs in AP mode also has an older Atheros card in it. There seems to be something about the way the way the WiFi module in the HEX-NET does AP mode that's incompatible with the Windows drivers for those old Atheros cards.

  4. #14
    Verified VCDS User
    Join Date
    Feb 2014
    Location
    USA
    Posts
    53
    Post Thanks / Like
    It's not just those two controllers, it's everything I've tried after controller 02. It's strange, love.

  5. #15
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    24,688
    Post Thanks / Like
    Blog Entries
    1
    Understood, but our thought is that something happening with one of those modules is crashing one of the threads in the HEX-NET. Verifying that and being able to identify with certainty which module it is would be a big help.

    -Uwe-

  6. #16
    Verified VCDS User
    Join Date
    Feb 2014
    Location
    USA
    Posts
    53
    Post Thanks / Like
    Ok, that doesn't seem to be the case. It successfully reads the first two controllers, then won't read any others. On the third controller, it runs quickly but then doesn't write anything to the log for that controller. On the next one, it takes much longer, fails to communicate, but writes the header part to the log. I tried deleting the ABS (03) controller first and it stopped working on the Kessy (05). I then removed the Kessy and it stopped working on the seat memory (06).

    In summary: After the first two controllers, the log skips one controller altogether, then for the following controllers displays the Address, VCID, then lists "no faults found or DTCs not supported by controller or a communication error occurred".
    Last edited by invisiblewave; 04-15-2014 at 02:28 PM.

  7. #17
    Verified VCDS User
    Join Date
    Feb 2014
    Location
    USA
    Posts
    53
    Post Thanks / Like
    The only three controllers I can find that I can access at all are 01, 02 and 03. If I run autoscan on just those three, it does 1 & 2 fine but doesn't write 03 to the log, nor does it display the main controller page for 03 just before the log pops up.

    I tried changing the sequence to 01,03,02 and that did the full (abbreviated) scan. If I then put 05 in there before 02, it runs the full (abbreviated) scan but logs the communications error on 05.

    If I run 01,02,05,03, it runs to the end of the scan but doesn't log 05 at all.

  8. #18
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    24,688
    Post Thanks / Like
    Blog Entries
    1
    Quote Originally Posted by invisiblewave View Post
    If I run 01,02,05,03, it runs to the end of the scan but doesn't log 05 at all.
    Did you save that scan? If so, would you mind posting it?

    -Uwe-

  9. #19
    Verified VCDS User
    Join Date
    Feb 2014
    Location
    USA
    Posts
    53
    Post Thanks / Like
    I didn't, but it was pretty straightforward. It looked just like it would if 05 wasn't in the list. Do you want me to run it again?

  10. #20
    Verified VCDS User
    Join Date
    Feb 2014
    Location
    USA
    Posts
    53
    Post Thanks / Like
    Here it is:

    Tuesday,15,April,2014,15:21:47:58155
    VCDS -- Windows Based VAG/VAS Emulator
    VCDS Version: 14.4.0.3
    Data version: 20140411


    VIN: License Plate:



    --------------------------------------------------------------------------------
    --------------------------------------------------------------------------------


    Chassis Type: 3D (3D - VW Phaeton Test (2002 > 2006))
    Scan: 01 02 05 03

    VIN:
    -------------------------------------------------------------------------------
    Address 01: Engine Labels: 4D0-907-560-BGH.lbl
    Part No SW: 4D0 907 560 CS HW: 8E0 907 560
    Component: 4.2L V8/5V G 0040
    Coding: 0007873
    Shop #: WSC 25019 444 00532
    VCID: F9BAACB5B33AF9F387-5184

    No fault code found.
    Readiness: 0000 0000

    -------------------------------------------------------------------------------
    Address 02: Auto Trans Labels: 09L-927-760.lbl
    Part No SW: 09L 927 760 C HW: GS1 9.0 4.1
    Component: AG6 09L 4,2L V8 1003
    Coding: 0000102
    Shop #: WSC 01065 000 00000
    VCID: B73E6A8DC5AE2F8331-5184

    No fault code found.

    -------------------------------------------------------------------------------
    Address 03: ABS Brakes Labels: 3D0-614-517.lbl
    Part No: 3D0 614 517 AK
    Component: ESP 5.7 allrad H35 0047
    Coding: 0008376
    Shop #: WSC 25019 000 00000
    VCID: EB9686FDC9665B6305-5184

    No fault code found.

    End ---------------------------------------------------------------------

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •