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

Thread: 2014 Crafter Limited Connectivity

  1. #1
    Verified VCDS User
    Join Date
    Oct 2019
    Location
    Scotland
    Posts
    7
    Post Thanks / Like

    2014 Crafter Limited Connectivity

    I just purchased a HEX V2 interface from Gendan Automotive to diagnose an ABS issue with my 2014 VW Crafter. As you can see from the attached auto scan only a limited number of modules are being scanned by the unit.

    When trying to access any of the other modules directly (not via auto scan) I get 'No response from controller' message. The engine module more often than not fails to connect 'CAN failed' can been seen in the top left of the VCDS interface before showing the 'No response...' error.

    Test shows CAN:OK K1:OK K2:OK

    The primary system I'm using VCDS on is a late 2008 Macbook Pro running Windows 10 home bootcamp. I've now run the software on two other laptops - Windows 10 Pro on regular laptop and lastly an older laptop running Windows 7. All three give the same results.

    I've covered all the points listed on the FAQ page, in particular the points pertaining to flakey connections, none have changed the outcome on any of the aforementioned operating systems. I'm using the latest version of VCDS available.

    The VCDS manual states "Communication with all control modules is supported with the following functions; Control Module ID and Advanced ID, Fault Codes (Read and Clear), Supported Codes, Security Access, and Adaptation" - but the deeper I dig into the forum it seems this might not be the case, since the crafters limited availability in the US makes them difficult to study.

    Has anyone overcome a similar issue or have I just been wasting my time?
    Code:
    Sunday,13,October,2019,18:23:29:31478
    VCDS -- Windows Based VAG/VAS Emulator Running on Windows 10 x64
    VCDS Version: 19.6.2.0 (x64)  HEX-V2 CB: 0.4508.4
    Data version: 20190930 DS308.0
    www.Ross-Tech.com
    
    
    VIN: WV1ZZZ2EZE6017076   License Plate: 
    
    
    
    --------------------------------------------------------------------------------
    --------------------------------------------------------------------------------
    
    
    Chassis Type: 2E-N/A (2E - VW Crafter Panel Van (LT3 / 2006 > 2016))
    Scan: 01 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F A0 A1 A2 A3
              B0 B1 B2 B3 B4 B5 B6 C1
     
    VIN: WV1ZZZ2EZE6017076   
    -------------------------------------------------------------------------------
    Address 01: Engine (J623-CKTC)       Labels:. 03L-906-012-CKT.clb
       Part No SW: 03L 906 012 C    HW: 03L 906 012 A
       Component: R4 2.0l TDI   H26 9977  
       Revision: 72H26---    Serial number: VWXDZ0M1047972
       Coding: 0119401020440C080000
       Shop #: WSC 131071 1023 2097151
       ASAM Dataset: EV_ECM20TDI01103L906012C 002018
       ROD: EV_ECM20TDI01103L906012A_002.rod
       VCID: 2411EC4DDE5C50478DF-8070
    
    No fault code found.
    Readiness: 0 0 0 0 1 
    
    -------------------------------------------------------------------------------
    Address 93: LT3 Immo        Labels: 2E0-905-865-93.clb
       Part No SW: 2E0 905 843 B    HW: 906 900 370 2
       Component: IMMO          1231  1306  
       Revision: 00231000    Serial number: VWXDZ0M1047972
       Shop #: WSC 00000 000 00000
       VCID: 2615F645A4E0A25793B-8072
    
    No fault code found.
    
    -------------------------------------------------------------------------------
    Address 94: LT3 Airbag 
       Part No HW: 9069005701
       Shop #: WSC 00117 555 00000
       ASAM Dataset: 3 3332
       ROD: CRFT_AB_3_3331.rod (*)
       VCID: 55F78189C586F9CFCA1-8000
    
    No fault code found.
    
    -------------------------------------------------------------------------------
    Address 96: LT3 Instruments 
       Part No SW: 9069025601    HW: 9069010401
       Shop #: WSC 00000 000 00000
       ASAM Dataset: 32 1048
       ROD: CRFT_KOMBI_32_1048.rod
       VCID: 065596C548A08257F3B-8052
    
    No fault code found.
    
    -------------------------------------------------------------------------------
    Address 99: LT3 Ign. Switch 
       Part No HW: 9069003702
       Shop #: WSC 00000 000 00000
       ASAM Dataset: 67 259
       ROD: CRFT_EZS_67_259.rod
       VCID: 55F78189C586F9CFCA1-8000
    
    No fault code found.
    
    -------------------------------------------------------------------------------
    Address 9A: LT3 Central Locks        Labels: 2E0-905-865-93.clb
       Part No SW: 2E0 905 843 B    HW: 906 900 370 2
       Component: HF-FFB        1231  1306  
       Revision: 00231000    Serial number: 12345678901234
       Shop #: WSC 00000 000 00000
       VCID: 2615F645A4E0A25793B-8072
    
    No fault code found.
    
    -------------------------------------------------------------------------------
    Address 9B: LT3 Driver Door 
       Part No HW: 9069000501
       Shop #: WSC 00000 000 00000
       ASAM Dataset: 33 263
       ROD: CRFT_FTUHR_33_263.rod
       VCID: 55F78189C586F9CFCA1-8000
    
    No fault code found.
    
    -------------------------------------------------------------------------------
    Address B4: LT3 Central Elec. 
       Part No SW: 9069024301    HW: 9069014500
       Shop #: WSC 00000 000 00000
       ASAM Dataset: 33 852
       ROD: CRFT_EZE_33_851.rod (*)
       VCID: 025D8AD56488BE77DF3-8056
    
    No fault code found.
    
    -------------------------------------------------------------------------------
    Address B6: LT3 Steering Wheel 
       Part No SW: 9065402545    HW: 9065402545
       Shop #: WSC 00000 000 00000
       ASAM Dataset: 72 257
       ROD: CRFT_SML_72_257.rod (*)
       VCID: 084998FD42B49427817-805C
    
    No fault code found.
    
    End----(Elapsed Time: 01:02, VBatt start/end: 12.0V/12.0V. VIgn 12.0V)-----

  2. #2
    VCDS Distributor
    Join Date
    Feb 2014
    Location
    Denmark
    Posts
    1,776
    Post Thanks / Like
    Quote Originally Posted by cblack_999 View Post
    As you can see from the attached auto scan only a limited number of modules are being scanned by the unit.
    They are all showed in the AutoScan, what other modules do you think should be showed ?

    Quote Originally Posted by cblack_999 View Post
    When trying to access any of the other modules directly (not via auto scan) I get 'No response from controller' message.
    Use the tab called "LT3".

  3. Likes Mike@Gendan, Uwe liked this post
  4. #3
    Verified VCDS User
    Join Date
    Oct 2019
    Location
    Scotland
    Posts
    7
    Post Thanks / Like
    Iím using the LT3 tab as instructed in the manual.

    I expected communication with the ABS module, either under ĎABSí or ĎESPí as exampled in the Ross Tech Crafter functionally section.

  5. #4
    VCDS Distributor
    Join Date
    Feb 2014
    Location
    Denmark
    Posts
    1,776
    Post Thanks / Like
    Quote Originally Posted by cblack_999 View Post
    I expected communication with the ABS module, either under ‘ABS’ or ‘ESP’
    Address 95.

    I guess Eric or Uwe, will answer this. (FS#504)
    Last edited by NEtech; 10-14-2019 at 11:04 AM. Reason: FS

  6. Likes Sebastian, Dana liked this post
  7. #5
    Ross-Tech Employee Eric's Avatar
    Join Date
    Jan 2014
    Location
    Lansdale, PA, USA
    Posts
    2,789
    Post Thanks / Like
    Crafter is a whole other universe, and as you mentionned, it is hard for us to study them in the wild. Case in point, you may have a different family of ESP than the module we've been working with, and although the data for it should be in VCDS, it's possible there's something special that needs to be done to get communications started with those.
    The last debug we have from a Crafter ESP with issue is from 2015, when interface codeblock and LT3 interaction might not have been so great, so if possible I'd like to start with a fresh debug 1024 of you trying to connect to address 95. I can't promise you we'll make it work, but I can promise to keep you updated with my findings.
    You ain't metal till you got a clutch pedal

  8. Likes Dana, Uwe, PetrolDave liked this post
  9. #6
    Verified VCDS User
    Join Date
    Oct 2019
    Location
    Scotland
    Posts
    7
    Post Thanks / Like
    Thanks for your response Eric. I'll be back in the garage tomorrow where I'll have a go.

    Just to clarify, when you say "debug 1024" is this what I should enter in the debug input box to generate the right info dump?

  10. #7
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    25,092
    Post Thanks / Like
    Blog Entries
    1
    Quote Originally Posted by cblack_999 View Post
    Just to clarify, when you say "debug 1024" is this what I should enter in the debug input box to generate the right info dump?
    [Options]
    Put 1024 in the field labelled 'Debug Level'
    [Apply]

    Now do stuff without exiting VCDS. Debug level reverts to 0 every time you exit VCDS.

    -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.

  11. Likes Dana liked this post
  12. #8
    Ross-Tech Employee Eric's Avatar
    Join Date
    Jan 2014
    Location
    Lansdale, PA, USA
    Posts
    2,789
    Post Thanks / Like
    Thanks for the debugs. Unfortunately the codeblock sees nothing at address 95. We're going to need to come up with a new plan of attack.
    You ain't metal till you got a clutch pedal

  13. Likes Dana, Uwe liked this post
  14. #9
    Verified VCDS User
    Join Date
    Oct 2019
    Location
    Scotland
    Posts
    7
    Post Thanks / Like
    I took the van to my local independent garage to help establish if the inability to communicate with the module was a due to a fault with the vehicle itself rather than the interface/VCDS software. The garage had no issues communicating with all of the modules. The warning lights were the result of failed wheel speed sensor.

    Since the debug reports weren't enough to formulate a solution for VCDS I've asked to return the interface for a refund. I've now asked twice via email. Both requests have been ignored. Hopefully someone can acknowledge the request through the forum?

  15. #10
    Verified VCDS User PetrolDave's Avatar
    Join Date
    Dec 2014
    Location
    South Molton, UK
    Posts
    2,467
    Post Thanks / Like
    Quote Originally Posted by cblack_999 View Post
    I just purchased a HEX V2 interface from Gendan Automotive
    Quote Originally Posted by cblack_999 View Post
    Since the debug reports weren't enough to formulate a solution for VCDS I've asked to return the interface for a refund. I've now asked twice via email. Both requests have been ignored. Hopefully someone can acknowledge the request through the forum?
    Since you purchased the HEX-V2 from Gendan maybe you should be contacting them about a return & refund?
    https://www.gendan.co.uk/

  16. 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
  •