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

Thread: VCDS 18.2.1 changelog

  1. #1
    Verified VCDS User
    Join Date
    Mar 2018
    Location
    Australia
    Posts
    14
    Post Thanks / Like

    VCDS 18.2.1 changelog

    Hi there,

    I hope I am allowed to open a new Thread for this. This is the first time I've opened a new thread EVER... before I've always only recycled old ones! This time I couldn't find an existing Thread which asked about this.

    Anyway, as the title says, I am after a changelog for the latest update of VCDS. I had a look around on the Ross-Tech site and found the product revision page (http://www.ross-tech.com/vcds/revisions.php) however that one stops at 18.1:

    Release 18.1 published 25 January 2018

    • Info pending.
    Is there a changelog ors similar? Basically I was just wondering if the control module map for my car had made it to the release :-).

    Cheers

  2. #2
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    27,099
    Post Thanks / Like
    Blog Entries
    1
    There is no published change-log at the moment. Even if there were, it would not cover every nuance of changes in the label files.

    -Uwe-
    Lock-down of sick people: Quarantine
    Lock-down of healthy people: Tyranny

  3. #3
    Verified VCDS User
    Join Date
    Mar 2018
    Location
    Australia
    Posts
    14
    Post Thanks / Like
    Ah okay, thanks for the info.

    Is there a way I can see if a label file has been added for my vehicle? Sorry I am only new to all this (VCDS and Forums)... 3 Months or so...

    Cheers

  4. #4
    Verified VCDS User
    Join Date
    May 2014
    Location
    Melbourne, Australia
    Posts
    3,179
    Post Thanks / Like
    ^^^^^ Uwe - I suspect that my question is probably bordering on heresy, but I ask for your brief indulgence as you consider the following:

    Because I'm a relative new-comer to the heady and fascinating world of VCDS, I assume that Ross-Tech has always had a one-size-fits-all concept for it's software release versions. I've noticed when updating that the exe-file seems to delete and then re-load the label files for every vehicle type in what I assume is the full VCDS repertoire of cars (which is an impressively large list).

    Having a diagnostic tool that is fully capable of accommodating such a wide variety of vehicles is doubtless of great value to professionals where any car can roll-into the workshop at any time. However, for the vast majority of "enthusiasts" (like me, and many other VCDS cable users - I assume), the huge VCDS-ready database is............ well, without wanting to sound too critical about an otherwise excellent device - of limited value. For this market sector, the likelihood is that the tool will be used for a small range of cars. I also assume that as new vehicles roll off the VAG assembly line in the future, the need to create new label files as well as the requirement to retain existing files into each SW release version will mean that the update exe file will continuously grow (I assume that this has happened over the intervening years since the fledgling VCDS SW version 1.0 was released).

    So with the above as a context, has RT thought about "sectioning" the update file so that the user can decide which vehicle, or vehicle type to load into the software on their laptop/tablet/mobile phone? I'm not sure, but I suspect that the user can achieve a similar outcome by culling the database in the existing arrangement, but my question is about a different approach. I'm not suggesting that the availability of vehicle types be in any way restricted to users that have limited VIN devices.

    I've not given any deep consideration as to how this option might operate, but I suspect that the update process would be a two-pass process where the new underlying VCDS software would be first loaded and the user would then request the database for specific vehicle types (including the option "ALL" - for professional workshop users). The updated label files for those vehicles that the user did not select would be remain available on the RT web-site, so additional vehicles could be loaded at any time. I suspect that that the process for updating will be more streamlined and for many (most?) users, the data transfer files will be much smaller - I think?

    Interested in your thoughts - please

    Don
    VW Golf MkVII (MY13) - A3 8V hatch (MY17)

  5. #5
    Verified VCDS User Zenerdiode's Avatar
    Join Date
    Jun 2014
    Location
    Newcastle, England
    Posts
    994
    Post Thanks / Like
    Quote Originally Posted by DV52 View Post
    (I assume that this has happened over the intervening years since the fledgling VCDS SW version 1.0 was released).
    I remember a 'Release' of VAG-COM (notice I was careful not to say VCDS) that came with a note; boasting "...still able to fit on a 1.44MB floppy."

    You see kids, this was a while ago. I'm talking way back, to a time of Windows98, Visual Studio, 00-Auto-Scan just being implemented and when Uwe did the coding. Yes, there was a time before 'smart' phones, when BlackBerries made delicious pies and jams, and laptop computers didn't have Wi-Fi cards. No USB sticks either, so you had to download VAG-COM on a desktop computer, with a bulbous monitor that had turned an awful beige, after getting your sister off the phone so you could dial-up the Internet. You then copied on to a 1.44MB floppy; so you could then transfer from the desktop to your laptop.

    Only to find "General failure reading drive A", waiting for the drive to stop, ejecting the disk and like an Advent calendar, opening the little slidey door to find the minutest grain of dust had scored concentric circles on the surface of the disk. Of course that little bit of grit wouldn't be happy living in the disk, it had to find a new home on the disk drive head, so another four floppies brand new out of the packet got etched with the same concentric rings...

    Good times though.

  6. Likes DV52, Santos, Uwe, NZDubNurd, Dana liked this post
  7. #6
    Verified VCDS User PetrolDave's Avatar
    Join Date
    Dec 2014
    Location
    South Molton, UK
    Posts
    2,996
    Post Thanks / Like
    Quote Originally Posted by DV52 View Post
    I've not given any deep consideration as to how this option might operate, but I suspect that the update process would be a two-pass process where the new underlying VCDS software would be first loaded and the user would then request the database for specific vehicle types (including the option "ALL" - for professional workshop users). The updated label files for those vehicles that the user did not select would be remain available on the RT web-site, so additional vehicles could be loaded at any time. I suspect that that the process for updating will be more streamlined and for many (most?) users, the data transfer files will be much smaller - I think?
    Given that most (not all) users have high speed ADSL/VDSL/FTTH connections I don't see value to other than a tiny minority of VCDS owners in efforts to reduce the update size.

    And I have to disagree with the apparent assumption that only professional users would want/need the updates for all vehicle types - many enthusiast owners help out friends/colleagues/social media contacts (for beer tokens ) with diagnosis and retrofitting on many different (and unpredictable) vehicle types.

    I do have a different suggestion - in much the same way that many AV programs have small daily(?) incremental updates I think it would be helpful if VCDS data file updates (that don't require a program update) could also be offered/pushed incrementally and as soon as available (weekly?) instead of having to wait for a full data update to be made available.

  8. #7
    Verified VCDS User iichel's Avatar
    Join Date
    Aug 2016
    Location
    The Hague, NL
    Posts
    1,607
    Post Thanks / Like
    Quote Originally Posted by DV52 View Post
    Because I'm a relative new-comer to the heady and fascinating world of VCDS
    Join Date May 2014
    Posts 2,257
    Does not compute :P

  9. Likes Eric, Uwe, NZDubNurd liked this post
  10. #8
    Verified VCDS User hadez16's Avatar
    Join Date
    Jun 2017
    Location
    Germany
    Posts
    694
    Post Thanks / Like
    Don,

    I don't know if I get your point.
    Are you placed in the outback with 33k dial-in modem?

    Who should be the victim deciding which parts of the gigantic ASAM/ROD dataset is for which car? RT had to hire a bunch of autists for this.

  11. Likes DV52 liked this post
  12. #9
    Ross-Tech Employee Sebastian's Avatar
    Join Date
    Feb 2014
    Location
    Magdeburg, Germany
    Posts
    1,950
    Post Thanks / Like
    @A6Aussie - At the present time there are no procedures in place to publish information about specific vehicle documentation changes (i.e. label file updates), in order to accomplish that we would need to change our internal procedures to a point where the administrative work would be in my view a little too excessive. That said, I am not saying it will never happen - just for the time being I don't see a specific label file changelog being published for customers.

    If you happen to need specific coverage, please send a complete Auto-Scan to Labels@Ross-Tech.com and we'll review it and make sure to put any missing files etc. on our todo list. If you happen to have specific recommendations or feedback regarding existing label files, please make sure to include an Auto-Scan in your email as well as detailed information as to what needs to be addressed. Thanks in advance.


    @DV52/Don - VCDS has a rather crude update mechanics at the moment and while we discussed more sophisticated methods in the past, there is no implementation planned. What I am reading between the lines, the time it takes to install the update is your concern - based on the size of the installed files, I am at least assuming that's not it. That time to install is related to the amount of small files, that is something we might tackle with incremental updates as well as something new Uwe and I have talked about a few weeks ago. The update process, the time it takes etc. applies to both VCDS and VCDS-Mobile - so streamlining the process surely is in our interest.

    There are a few reasons which speak against your idea of selecting a model/platform. In many cases, control modules are used across several platforms and in order to make this work, each file would need to know which platform(s) it applies to. Something, which in the process will take a lot of time to be properly documented (the functional implementation shouldn't be a problem). Downloading files by demand (i.e. after an Auto-Scan) only makes sense with big files, which is not the case for us. In fact our number one use case, take VCDS offline and w/o any internet connection it will work just fine on any car. That's what I believe most of our customers are doing...

    Quote Originally Posted by hadez16 View Post
    Who should be the victim deciding which parts of the gigantic ASAM/ROD dataset is for which car? RT had to hire a bunch of autists for this.
    The ASAM/ODX database is actually not an issue, as that is already platform specific by design. The older label files are the issue with that...
    Sebastian @ Ross-Tech.com // VCDS Rookie since 2003

    »Nichts erweitert das eigene Wissen mehr,
    als die Meinung eines Andersdenkenden.«

  13. #10
    Verified VCDS User
    Join Date
    Mar 2018
    Location
    Australia
    Posts
    14
    Post Thanks / Like
    Oo wow, looks like I‘ve kicked off quiet some conversation 😅.

    @hadez16: even in the outback we have either NBN (VDSL) or sat 😀. But it’s certainly not as fast as in the cities.

    @Sebastian, thanks for getting back to me on that one! I already did all that and sent an email on 13/04/2018. Dana got back to me to say “thx” and that all info came through i think.

    Now I was just curious to see if my stuff had made it to the latest update (can’t check it on the car currently) and hoped there was a way to easily see it (change log, list of all lbl files...), that’s all :-). Not asking for a procedure change or similar... haven’t even gotten my head around the current software 🤣.

    Cheers

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
  •