Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Trouble with pop up's/baloons

  1. #1
    Verified VCDS User
    Join Date
    Aug 2019
    Location
    USA
    Posts
    19
    Post Thanks / Like

    Trouble with pop up's/baloons

    pretty sure it's a settings issue on my end. running windows 10 fwiw.

    went to replace a G200 and had to do the log in. enter the log in code and never got the "log in accepted" pop up.

    being a new user and not wanting to do anything bad, I had a friend link in with teamviewer to walk me thru the procedure. he said the pop up was working on his end, and that I ran the adaptation just fine.

    what do I need to check to correct this? [redacted] is the license # I have. also, I get a communication error when trying to access NAV and Radio but my other scanner will get right in. I can watch the screen on the radio go into DIAG with VCDS, and it will get as far as a radio p/n before it aborts.

    pretty sure it's a setting on my end causing this. I can post an autoscan if needed
    Last edited by Uwe; 09-06-2019 at 08:36 PM.

  2. #2
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    24,601
    Post Thanks / Like
    Blog Entries
    1
    Yes, an Auto-Scan and some screen-shots illustrating the problem would probably be useful.

    -Uwe-
    The engineering problems are likely insurmountable. It would be like proposing to land a rocket booster section on a barge floating in the middle of the ocean.

  3. #3
    Verified VCDS User
    Join Date
    Aug 2019
    Location
    USA
    Posts
    19
    Post Thanks / Like
    Quote Originally Posted by Uwe View Post
    Yes, an Auto-Scan and some screen-shots illustrating the problem would probably be useful.

    -Uwe-

    ok, thanks!

    here's an auto scan

    pay no attention to the codes in the engine controller...I was playing around causing issues just to play with VCDS

    Code:
    Saturday,07,September,2019,13:13:23:51893
    VCDS -- Windows Based VAG/VAS Emulator Running on Windows 10 x64
    VCDS Version: 19.6.1.0 (x64)
    Data version: 20190529 DS308.0
    www.Ross-Tech.com
    
    Dealer/Shop Name: Rizzo's Repair
    Workshop Code: 444 00066 001022
    
    
    
    Chassis Type: 8N - Audi TT (1999 > 2007)
    Scan: 01 02 03 08 15 17 22 35 37 45 55 56 76 77
     
       Mileage: 112650km-69997miles
    -------------------------------------------------------------------------------
    Address 01: Engine        Labels: 06A-906-032-AMU.lbl
       Part No: 8N0 906 018 T
       Component: 1.8L R4/5VT     G   0003  
       Coding: 06710
       Shop #: WSC 01236  
       VCID: 428097554E45645FCF-50E6
    
    3 Faults Found:
    16502 - Engine Coolant Temp. Sensor (G62) 
                P0118 - 35-10 - Signal too High - Intermittent
    17536 - Fuel Trim; Bank 1 (Mult) 
                P1128 - 35-00 - System too Lean
    17536 - Fuel Trim; Bank 1 (Mult) 
                P1128 - 35-10 - System too Lean - Intermittent
    Readiness: 0000 0000
    
    -------------------------------------------------------------------------------
    Address 03: ABS Brakes        Labels: 8N0-907-379-MK20-E.clb
       Part No: 8N0 907 379 E
       Component: ESP     20    CAN  V004   
       Coding: 18446
       Shop #: WSC 01236  
       VCID: 3E78E3A53ABD00BFAB-4A9C
    
    No fault code found.
    
    -------------------------------------------------------------------------------
    Address 08: Auto HVAC        Labels: 8N0-820-043.lbl
       Part No: 8N0 820 043 A
       Component: TT-KLIMAVOLLAUTOMAT D03  
       Coding: 00140
       Shop #: WSC 01236  
       VCID: 285425FDC839AE0FF1-2554
    
    No fault code found.
    
    -------------------------------------------------------------------------------
    Address 15: Airbags        Labels: 8N8-909-601.lbl
       Part No: 8N8 909 601 
       Component: Airbag Front+Seite 1005  
       Coding: 10102
       Shop #: WSC 01236  
       VCID: 77F636815507F1F7A8-513C
    
    No fault code found.
    
    -------------------------------------------------------------------------------
    Address 17: Instruments        Labels: 8Nx-920-xxx-17.lbl
       Part No: 8N1 920 930 E
       Component: KOMBI+WEGFAHRS. M73 D08  
       Coding: 07244
       Shop #: WSC 00000  
       VCID: 336EC29101FFDDD754-4A9C
    
    No fault code found.
    
    -------------------------------------------------------------------------------
    Address 22: AWD        Labels: 02D-900-554.lbl
       Part No: 02D 900 554 B
       Component: HALDEX LSC  ECC     0006  
       VCID: 1F463E219D7769B780-4AB4
    
    No fault code found.
    
    -------------------------------------------------------------------------------
    Address 35: Centr. Locks        Labels:. 8Nx-962-267.lbl
       Part No: 8N7 962 267 A
       Component: Central Lock/Alarm  D04  
       Coding: 15964
       Shop #: WSC 00066  
       VCID: 3E78E3A53ABD00BFAB-4E78
    
    No fault code found.
    
    -------------------------------------------------------------------------------
    Address 37: Navigation        Labels: 
       VCID: 55AA5C09ACCBE3E79A-4A9C
       Note: Excessive Comm Errors
    
    
    -------------------------------------------------------------------------------
    Address 45: Inter. Monitor        Labels: 8E0-951-177.lbl
       Part No: 8N7 951 177 
       Component: Innenraumueberw.    D14  
       Coding: 00001
       Shop #: WSC 00000  
       VCID: 7BFE2AB1692FD597CC-50AC
    
    No fault code found.
    
    -------------------------------------------------------------------------------
    Address 55: Headlight Range        Labels: 4B0-907-357-AUT.lbl
       Part No: 4B0 907 357 
       Component: LEUCHTWEITEREGLER  D004  
       Coding: 00005
       Shop #: WSC 00066  
       VCID: 65CA6CC9FFAB73670A-513C
    
    No fault code found.
    
    -------------------------------------------------------------------------------
    Address 56: Radio        Labels: 8D0-035-1xx-56.lbl
       Part No: 8N0 035 186 A
       VCID: 2E58D3E5EADDF03F3B-4AB4
       Note: Excessive Comm Errors
    
    
    End-------------------------(Elapsed Time: 03:49)--------------------------

    you can see the radio and nav have excessive comm issues...but I can get in using other scanners

    here is where the login "bombs" with the pop up that says the controller accepted log in:




    I can type in 40168, hit "do it!" and it just blinks and goes away, never telling me if it accepted the code or not.

    not sure what's going on.

    in terms of the nav/radio (which oddly still works fine) I am just nosey, and wanted to play around. I am not chasing an issue....yet

  4. #4
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    24,601
    Post Thanks / Like
    Blog Entries
    1
    Quote Originally Posted by vwparts View Post
    I can type in 40168, hit "do it!" and it just blinks and goes away, never telling me if it accepted the code or not.
    Ok, that's normal. When talking to a control module that uses the old KW1281 protocol (which this one does), there is no explicit acknowledgement from the module that a login was accepted. There can be a semi-explicit rejection in the form of an generic error in the next packet from the module, but most of the modules in using this protocol don't even do that; they just "hang up" the session. VCDS will then re-start a new session with the module and since it knows you tried a login, it will put a warning in one corner of the scree with the wording "Login lost due to dropped session" (or something very close to that).

    As for the errors in the radio and nav (which are the same module, responding to two different addresses), what happens if you access them directly?

    -Uwe-
    The engineering problems are likely insurmountable. It would be like proposing to land a rocket booster section on a barge floating in the middle of the ocean.

  5. #5
    Verified VCDS User
    Join Date
    Aug 2019
    Location
    USA
    Posts
    19
    Post Thanks / Like
    Quote Originally Posted by Uwe View Post

    As for the errors in the radio and nav (which are the same module, responding to two different addresses), what happens if you access them directly?

    -Uwe-
    if I do an auto scan and the radio is on, I will hear it cut out, it will try to get read...the radio will display "DIAG" and the fields will populate VAG # and component...then it will bomb. sometimes, it will only display VAG # and never get to component. happens radio on or off.

    same thing happens if trying to do a log in with either NAV or radio.

    last time I tried it, it went into diag on the screen and failed the same way. however, upon exiting the module the next key cycle all I had was radio static, could not use any of the buttons except for seek and the radio display was "frozen" in the cluster...radio on or off. hitting seek did nothing except "slot machine" the stations, and never stopped...it was like the antenna was disconnected.

    the only way I got the radio back was to pull the fuse, re enter the radio code and it all came back to life.

    autel, launch and strap-on all communicate just fine

  6. #6
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    24,601
    Post Thanks / Like
    Blog Entries
    1
    That's quite strange/unique, and I'm not sure what's up with that.

    What model year is this car?

    -Uwe-
    The engineering problems are likely insurmountable. It would be like proposing to land a rocket booster section on a barge floating in the middle of the ocean.

  7. #7
    Verified VCDS User
    Join Date
    Aug 2019
    Location
    USA
    Posts
    19
    Post Thanks / Like
    2001 TT 225 quattro.

    like I said, not chasing any issues, I just wanted to "play" now that i'm a hack with VCDS and enough curiosity to get me in trouble

    i'd be happy to let you do a teamviewer session so you can see what's happening if you'd like.

  8. #8
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    24,601
    Post Thanks / Like
    Blog Entries
    1
    I'd like to suggest making a Debug file:
    [Options] -> Set Debug Level to 1024
    [Apply]
    [Select]
    [37-Nav] or [56-Radio]
    Let VCDS try until it fails.
    Exit VCDS as gracefully as you can.
    Look in the Debug sub-folder and send the file(s) DEBUG-37.DLM and/or DEBUG-56.DLM to Support@...
    Please include a link to this thread in your e-mail.

    -Uwe-
    The engineering problems are likely insurmountable. It would be like proposing to land a rocket booster section on a barge floating in the middle of the ocean.

  9. #9
    Verified VCDS User
    Join Date
    Aug 2019
    Location
    USA
    Posts
    19
    Post Thanks / Like
    Quote Originally Posted by Uwe View Post
    I'd like to suggest making a Debug file:
    [Options] -> Set Debug Level to 1024
    [Apply]
    [Select]
    [37-Nav] or [56-Radio]
    Let VCDS try until it fails.
    Exit VCDS as gracefully as you can.
    Look in the Debug sub-folder and send the file(s) DEBUG-37.DLM and/or DEBUG-56.DLM to Support@...
    Please include a link to this thread in your e-mail.

    -Uwe-
    will do. I will try to do it asap. thanks for the help!

  10. #10
    Verified VCDS User
    Join Date
    Aug 2019
    Location
    USA
    Posts
    19
    Post Thanks / Like
    email sent with link to thread. only had the 56 file, not the 37.

    here is a screenshot of how far it will go. this is the farthest I have been able to get. sometimes it won't even populate the "radio" in the component field, just the p/n


  11. Likes Uwe liked this post

Posting Permissions

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