Page 3 of 37 FirstFirst 1234513 ... LastLast
Results 21 to 30 of 365

Thread: Current Versions

  1. #21
    Verified VCDS User romad's Avatar
    Join Date
    Feb 2014
    Location
    Oroville, California People's Republic
    Posts
    169
    Post Thanks / Like
    Question: I just ran an update and was told that there was a CB update available but it showed the FW was the same. After that update was installed, I was reading this thread and found out there was a newer FW than what was installed on my Hex-Net unit. I then told it to check for updates and it found the new FW update. Why weren't both updates found the first time?

  2. #22
    FoRT jyoung8607's Avatar
    Join Date
    Feb 2014
    Location
    Cincinnati, OH
    Posts
    2,390
    Post Thanks / Like
    Quote Originally Posted by romad View Post
    Why weren't both updates found the first time?
    It's a little hidden and it's listed under the last release, but...

    Quote Originally Posted by Uwe View Post
    NOTE: Check for Updates twice -- the CodeBlock and FW (firmware) are separate updates.
    Jason

  3. Likes jakematic, romad liked this post
  4. #23
    Verified VCDS User romad's Avatar
    Join Date
    Feb 2014
    Location
    Oroville, California People's Republic
    Posts
    169
    Post Thanks / Like
    Thanks, Jason!

  5. #24
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    24,955
    Post Thanks / Like
    Blog Entries
    1
    VCDS Beta 14.5.3

    • Requires codeblock 4105 which has fixes for partial measuring blocks
    • More reliable DTC read in 1281. Please test this on all things KW1281 (old cars!)
    • Improved handling of HEXNET timeout while receiving slow messages
    • Sanity check while receiving messages that would take too long
    • Improved detection of dropped sessions
    • Improved reliability of slow measuring blocks with 1281 controllers at low baudrates
    • Fixed potential crash writing ADP or MWB map header if no part number was retrieved

  6. #25
    Ross-Tech Employee
    Join Date
    Jan 2014
    Location
    USA
    Posts
    851
    Post Thanks / Like
    Two part update is out today, including CB V0.4106 and DS00000027
    Make sure you get both, as they will download as separate components.

    They include some fixes, especially for newer cars, as well as some hopefully helpful tweaks to the formatting of some things. More details above.

  7. Likes jakematic liked this post
  8. #26
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    24,955
    Post Thanks / Like
    Blog Entries
    1
    VCDS Beta 14.6.0

    • Requires codeblock 4106 -- so update your HEX-NET first!
    • More responsive and informative K-line init status
    • Fix for GVL recode on MQB platform cars.
    • Fix for RLFS-type slave recode on UDS
    • Fix corrupted data when generating debug with HEX-NET and long packets
    • Fix Auto-COM crash

  9. #27
    Verified VCDS User
    Join Date
    Apr 2014
    Location
    Toronto, Canada
    Posts
    80
    Post Thanks / Like
    Quote Originally Posted by Shaun View Post
    Two part update is out today, including CB V0.4106 and DS00000027
    Hi Shaun:

    I have figured out that 'CB' means Code Block, but what does 'DS' mean? Are you now introducing support for elderly Citroen limousines? Also, does this 'DS' component install onto the computer (meaning, it is part of the VCDS 14.6.0 package), or does it install into the HEX-NET interface?

    Michael

  10. #28
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    24,955
    Post Thanks / Like
    Blog Entries
    1
    Hey, you work in an industry where practically EVERYTHING is expressed as an acronym. ADF, DME, FBO, HF, ILS, KIAS, NDB, VOR, OTS, PMA, RNAV, TCA, UTC, VOR, etc, ad infinitum. So please cut us some slack.

    DS = Data Set. On the HEX-NET, it's almost everything that isn't actual program code. It installs in the HEX-NET; it is not part of VCDS (which might be construed to stand for "VAG COM Diagnostic System").

    -Uwe-

  11. #29
    Verified VCDS User
    Join Date
    Apr 2014
    Location
    Toronto, Canada
    Posts
    80
    Post Thanks / Like
    Quote Originally Posted by Uwe View Post
    Hey, you work in an industry where practically EVERYTHING is expressed as an acronym.
    You are correct - however, when I write manuals, technical documentation, or technical support publications (such as the Aircraft Flight Manual, the Aircraft Maintenance Manual, and the Avionics Pilot Guide), I make certain that if I do use an acronym, I always spell out in parentheses, at first use, what the acronym represents. Doing that does not increase my workload (other than having to type a few more letters), it does not inconvenience readers who are familiar with the acronym, but it most certainly improves comprehension and saves time for readers who may not have immediate recall of that particular acronym at the very top of their head. This is an especially important consideration for readers who don't have English as their first language.

    My experience, which comes primarily from training and safety management, is that acronyms rarely provide any benefit unless they are extremely well known (USA, NATO, USB, etc.). Acronyms other than extremely well known ones detract from the clarity, lucidity, and effectiveness of technical publications. One of the only circumstances I can think of where use of an acronym improves clarity of written communication is when the same lengthy phrase needs to be repeated numerous times in a series of paragraphs. In that case, using the acronym (after spelling it out at first use) simplifies the text by avoiding continuous repetition of the phrase the acronym represents. But using an acronym 'once only' instead of spelling the words out in full yields no benefit to the reader.

    My suggestion to Ross-Tech, so far as acronyms are concerned, is that you critically evaluate the benefits (none, really) versus the disadvantages (noted above) of acronym use, both in publications and in the support fora. Sure, it's fine to use acronyms in internal correspondence such as memos between the programming team members or between two employees - but in any writing that will be read by your customers, either avoid using acronyms altogether, or, if a phrase needs to be repeated several times on the same page, spell the acronym out in parentheses at first use.

    Michael

  12. #30
    Benevolent Dictator Uwe's Avatar
    Join Date
    Jan 2014
    Location
    Earth
    Posts
    24,955
    Post Thanks / Like
    Blog Entries
    1
    Agreed about the documentation, which is a bit sparse ATM (at the moment).

    As for the forum, Santos and I were discussing that earlier. We don't think we'll ever get some people to spell stuff out. However, there's a plug-in that uses a custom dictionary to decode acronyms when the user hovers his cursor over them. We plan to install that ASAP (as soon as possible).

    -Uwe-

Posting Permissions

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