What is vcds12/8/2022 If you come across a control module that uses UDS but has no Label File, then again no PLA or PLB would help us to create one. On a related note, UDS modules still have label files as well, for things like Coding and Security Access. That means as much as you'd like to help, the only thing you can send us is a regular AutoScan: Unfortunately, with UDS, no such files are possible since a ROD file is needed to even READ any of the data at all. Sending us PLA and PLB files for those old style controllers is a great way to help us to incorporate documentation for the missing stuff in new versions of VCDS. Many of you are (or should be) familiar with the process used on older pre- UDS control modules when you found ones with no label files: If the ROD file is still missing and you see some message like ' No ASAM data for: "EV_ECM14TFS01104E997016B" (VW37) ' and you have made sure you are running the latest version, then please send us an AutoScan. If that happens, the first thing to do is to ensure you are running the LATEST version of VCDS: If the Advanced Measuring Values button is grayed out then that means there is no ROD file (the translation file needed for that specific type of control module). Instead you will need to use the Advanced Measuring Values function where you pick from a list of possible things to measure: Notice the top left corner shows "Protocol: UDS" and there are some functions that are simply not available like Measuring Blocks (since there are no longer any measuring block numbers). This is a colossal PITA for scan tool manufacturers like us since we need to maintain special files for every type of control module.Īnyway, on to practical matters, this is what it looks like when you are communicating with a control module that uses UDS: So now when you get a fault code there is no way to know what it means unless you have a special translation file UNIQUE TO THAT SPECIFIC TYPE OF CONTROLLER. Although I would never trust Chinese vcds ripoffs for re-coding my cars or even service interval resets, in fact I wouldn't trust any write instructions from them. In theory this could have resulted in our software being really useful (beyond just Generic OBD-2) on other brands, right? Wrong! What the ISO 15765 ( UDS) did instead was to put in an extra layer of translation that was needed to interpret fault codes, measuring data, etc. However, VCDS is fairly bomb proof in beginners hands when used just for diagnostics and car bricking is not a high risk which it is with OE workshop diagnostics. My understanding is that the big European automakers, along with their suppliers, decided to get together on some common diagnostic "language" that would reduce differences for example, in what Bosch would need to do for control modules going into Volkswagens compared to the same type of modules going into Mercedes. The scan tool didn't need to know anything about the type of car in order to give you the fault code meaning. In a 2006 Audi A8L, the same fault would have the same meaning. For example, in a 1993 Golf 2.0 ABA, if you got a fault 00532, VCDS would interpret that as "Supply Voltage B+: Signal too Low" or something like that. Before UDS ("Unified Diagnostic Services"), Measuring Blocks used somewhat standardized numbers (like group 115 shows requested and actual boost pressure in many drive by wire gasoline engines) and fault codes had fairly consistent numbering. These first appeared circa 2008 in cars like the 8T/8K Audi A4/A5. This thread is intended to address frequent questions from customers about control modules that use the "new" UDS/ ODX protocols. We can merge my stuff together with Jef's stuff to make a mad goulash with it: Please enter security code that you see on the above box.I made this draft post a while back but never "published it". Send me an email when anyone response to this However, if you wish to receive a response, please include your email and name. Sharing your feedback about this process or ask for help Here is the list of instances that we see for the process: VCDS-Release-11.11.2-Installer.exe If you think this is a driver issue, please try Where do we see VCDS-Release-11.11.2-Installer.exe ? Let try to run a system scan with Speed Up My PC to see any error, then you can do some other troubleshooting steps. What can you do to fix VCDS-Release-11.11.2-Installer.exe ? If you encounter difficulties with VCDS-Release-11.11.2-Installer.exe, you can uninstall the associated program (Start > Control Panel > Add/Remove programs How to remove VCDS-Release-11.11.2-Installer.exe Let try the program named DriverIdentifier to see if it helps. Is VCDS-Release-11.11.2-Installer.exe using too much CPU or memory ? It's probably your file has been infected with a virus. Something wrong with VCDS-Release-11.11.2-Installer.exe ?
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |