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

Thread: Latest VCDSToolbox version

  1. #1
    VCDS Distributor NEtech's Avatar
    Join Date
    Feb 2014
    Location
    Denmark
    Posts
    2,086
    Post Thanks / Like

    Latest VCDSToolbox version

    Here is the latest VCDSToolbox test version.

    Latest change log:
    { 19.8.0}
    { Show German umlaut correct}
    { Model info corrections }

    { 19.9.0}
    { A search icon instead of to short text in some languages}
    { Show differences in color for coding read from coding change log }
    { Model info corrections }




  2. #2
    VCDS Distributor NEtech's Avatar
    Join Date
    Feb 2014
    Location
    Denmark
    Posts
    2,086
    Post Thanks / Like
    Here is the latest VCDSToolbox test version.

    { 19.10.0}
    { Show German (and some other UTF) umlaut correct again - file saved with MAC!}
    { Model info corrections }
    { 19.11.0}
    { Model info corrections }
    { 19.11.1}
    { Model info corrections }
    { Alternator information bottom of autoscan }

    On many new CAN Gateways from 2018, there is LIN data for Alternator.
    First try on decryption of the data (a lot is still missing), here an example from Autoscan:

    • Alternator:
    • Component: 4-00-03-00-04


    If Alternator data is available in the Autoscan, it is showed at the bottom of VCDSToolbox screen.
    Amp data are from PR-codes.

    Last edited by NEtech; 01-12-2020 at 09:55 AM. Reason: Corrected link

  3. Likes Uwe, Boki Ar, NitrousOxide liked this post
  4. #3
    VCDS Distributor NEtech's Avatar
    Join Date
    Feb 2014
    Location
    Denmark
    Posts
    2,086
    Post Thanks / Like
    Here is the latest VCDSToolbox test version.

    { 19.11.2}
    { Model info corrections }
    { Battery hist. correction }
    { 20.01.0}
    { Model info corrections Golf 8 / ID.3}
    { Search for 2-3 character Acronym }


  5. Likes Eric, Uwe, Mats@MFT, NitrousOxide liked this post
  6. #4
    Verified VCDS User
    Join Date
    Feb 2016
    Location
    Jamaica
    Posts
    196
    Post Thanks / Like
    I'm just looking at these screenshots here.
    Does CFW Injector Coding, mean I can now do some calibration to these new Audi S3 injectors that has been giving me a rather lumpy idle on my MK5 GTI (but OEM smooth everywhere else in the revv range)?

  7. #5
    VCDS Distributor NEtech's Avatar
    Join Date
    Feb 2014
    Location
    Denmark
    Posts
    2,086
    Post Thanks / Like
    This is special injector coding for CFWA engines.

    Please make a new thread with autoscan about your problem, for coding new injectors.

  8. Likes Uwe liked this post
  9. #6
    VCDS Distributor NEtech's Avatar
    Join Date
    Feb 2014
    Location
    Denmark
    Posts
    2,086
    Post Thanks / Like
    { 20.02.0}
    { Model info corrections}
    { Text changed in "Sendscan"} It is not for support

    Definition and English changed a little in GitLab.

    Link is updated in #1.

  10. Likes Uwe, Eric, Boki Ar, downtime liked this post
  11. #7
    VCDS Distributor NEtech's Avatar
    Join Date
    Feb 2014
    Location
    Denmark
    Posts
    2,086
    Post Thanks / Like
    { 20.02.1}
    { New Acronyms added}
    { New controller for Battery history}
    { 20.03.0}
    { New Acronyms added}
    { Model info corrections}
    { Program action button failure improved}
    { First test for comparing two UDS Adaptation Channel files}

    Link is updated in #1.

    Comparing 2 UDS Adaptation Channel files, can be done from different languages, but must be from same controller.

    For comparing you can either choose the two files (In Explorer) and Drag&Drop them into VCDSToolbox.
    Or choose the two files, Right click > Copy, then Right click in VCDSToolbox and choose [Insert (Paste) 2 UDS adaptation files].

    Drag & Drop:


    Right Click:


    Compared:

  12. #8
    Verified VCDS User DV52's Avatar
    Join Date
    May 2014
    Location
    Melbourne, Australia
    Posts
    3,445
    Post Thanks / Like
    ^^^ NEtech: very impressive indeed - yet another in a long list of VCDS triumphs!!!

    May I ask 3x related questions, please?

    First- Sort Criteria: given that most (all?) instances where a user would seek to compare 2 x admaps is to find instances in which the settings are different, is it possible for your App to sort the compare-results by this variable, rather than by Tag number (which I assume is what happens now) - and is it possible to display those channels with different settings first? This would streamline the subsequent user task greatly, especially in modules with a high channel count - like the BCM for modern MQB vehicles (I think).
    And apropos of my third question below - can the sort criteria for channels with different settings separately identify the "missing channels" as a bunch?

    Second- File Export: Is it possible to export the admap compare results from your App- perhaps as a .CSV file?

    Third- Missing Channels: Can you confirm that the "join-string" in what I assume is an SQL search algorithm in your App - will return ALL the channels in BOTH admaps regardless of whether they appear in both admaps (i.e. how does the compare facility handle channels that appear in only 1 x admap and in particular - if the the channel appears only in the 2nd selected admap)? I ask because this scenario has proven problematic for me in the past (but then I'm terrible with SQL queries!!)

    Again - much kudos for simplifying what can be often a tedious process!!

    Don
    Last edited by DV52; 03-26-2020 at 12:36 AM.
    VW Golf MkVII (MY13) - A3 8V hatch (MY17)

  13. #9
    VCDS Distributor NEtech's Avatar
    Join Date
    Feb 2014
    Location
    Denmark
    Posts
    2,086
    Post Thanks / Like
    It is a very simple search/compare, nothing sql or something like that.

    I check which file is biggest, that goes on the left side (I asume it has most lines).
    I just take one line at a time, so it is not possible to do a lot of search hocus Pocus
    If a line is missing on the right that should mostly be found and show empty cell, if there is an line on the right that is not in the left, it should be showed at the end.
    But there are certainly files, where there will be a problem.

    I will think about csv file, thanks.

  14. Likes Uwe, Dana, DV52 liked this post
  15. #10
    Verified VCDS User
    Join Date
    Apr 2019
    Location
    Worcester, UK
    Posts
    22
    Post Thanks / Like
    This is a great tool.

    I have a slight issue though.

    When I load an autoscan from my Touareg, the engine is shown as 190kw (258 HP) but according to the vehicle data sticker in the handbook and spare wheel well it is actually 210kw.
    Code:
    4RJ CR7
    CR74RJ Touareg BMT V6TDI 210KW
    SBT LC5M ID TDI A8A DEN
    The autoscan contains
    Code:
    Address 01: Engine (J623-DENA)       Labels: None
       Part No SW: 760 907 401 G    HW: 059 907 309 L
       Component: 3.0l V6 TDI   H26 0002  
       Revision: CAH26---    
       Coding: 292A4032057E050335180000000400000000000000000000
       Shop #: WSC 31414 039 00001
       ASAM Dataset: EV_ECM30TDI011760907401G 001002
       ROD: EV_ECM30TDI011760907401G.rod
       VCID: 197A3B6B18550E4EE5-804C
    BTW, the label for this value in the software has changed from HP to Hk somewhere along the line
    Last edited by technodevotee; 05-02-2020 at 04:46 AM.

  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
  •