Latest VCDSToolbox version

[NEtech]

Here is the latest VCDSToolbox test version.

Feature list Version: 20.11.0
Drag and drop Autoscan file, you are then able to use/see this information:

Number of DTC, search DTC on Ross-Tech wiki/forum​

Engine data (if engine name available)​

Change power Hp/kW and link to Engine Wiki​

Model year, Model type, Platform​

Mileage if in Autoscan​

Link to erWin for current Model​

Where car is produced, link to factory in Google maps​

Link of Distributor for the current showed Autoscan​

Click on VIN, if you have access to Partslink24​

You can also click on Tree-view Window to find and load an Autoscan file
Open the current Autoscan in Windows Notepad Program

Buttons with link to:

Ross-Tech Wiki​

Distributor​

Partslink24​

Ross-Tech videos​

Distributor shop​

12 Buttons with different help/programs for VCDS, several can be added/changed in vcdsscan.ini​

Search possibilities:

Search in all Autoscan files​

Search and show Abbreviations​

Search direct at Ross-Tech Wiki/Forum​

Easy send Autoscan files to NEtech/Ross-Tech for development (NOT support, use Ross-Tech Forum for support!)
See many information's of Battery History data made with VCDS, if available.
Analyze different Adaptation or measurement values.
Compare log files for adaptation or coding changes, made with VCDS.
Calculate Coding for Injector for CFW engine.

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 }

 

[NEtech]

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.

 

[NEtech]

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 }

 

[NitrousOxide]

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)?

 

[NEtech]

This is special injector coding for CFWA engines.

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

 

[NEtech]

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

 

[NEtech]

{ 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:

 

[DV52]

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

 

[NEtech]

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.

 

[technodevotee]

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.

4RJ CR7
CR74RJ Touareg BMT V6TDI 210KW
SBT LC5M ID TDI A8A DEN

The autoscan contains

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

 

[NEtech]

Thank you very much, I have fixed it.

 

[NEtech]

New version, link is updated and feature list added, in #1.

{ 20.11.0}
{ New Acronyms added}
{ Model info corrections}
{ Pull down menu for more search options}

 

[NEtech]

New test version, link is updated in #1.

{ 21.2.0 }
{ New Acronyms added }
{ Model info corrections }
{ UK DE CZ translation }
{ 21.3.0 }
{ New Acronyms added }
{ Model info corrections }
{ CI translation }
{ 21.4.0 }
{ New Acronyms added }
{ Model info corrections }
{ Information about Service History }
{ High resolution mileage is shown also }

Drag and drop file named: "blockmap-17*.csv"
The Controller Blockmap csv file made by VCDS, must include IDE03911 etc.
They are used in many model, like these for example:
MQB
Golf 8 platform
Skoda superb (3V)
Skoda Rapid (NH)
Skoda Fabia (NJ)
VW Polo (6C)
VW Polo (AW)
VW Touran (5T)
VW Tiguan (AD)
VW Arteon (3H)
VW Passat (3G)
VW Tourareg (7P6)
VW Crafter (SY)
Audi A6/A7 (4G)
Audi Q7 (4M)
Audi Q5 (FY)

Just drag & drop one file, as showed above for comparing controller map files.

 

[NEtech]

New version, link is updated in #1.

{ 21.4.2 }

Additional info for service history, from Drag and drop file named: "blockmap-17*.csv"

These models have a high resolution mileage, seems to be 1 mm instead of normal 1 meter !
(4G) 2013-2018?
(4H) 2010-2017?
(7P5) 2013-2014
(7P6) 2015-2018?

If it is possible to calculate, I have not been able to find out (yet).

 

[NEtech]

New version, link is updated in #1.
{ 21.5.0 }
{ New Acronyms added }
{ Model info corrections }

 

[NEtech]

New version, link is updated in #1.
{ 21.6.0 }
{ New Acronyms added }
{ Model info corrections }
{ ID.3/4 Battery history file support}
I have no success finding what the data in Record 16 is related to

 

[NEtech]

New version, link is updated in #1.
{ 21.8.0 }
{ New Acronyms added }
{ Model info corrections }

 

[NEtech]

New version, link is updated in #1.
{ 21.9.0 }
{ New Acronyms added }
{ Model info corrections }

 

[NEtech]

New version, link is updated in #1.
{ 22.1.0 }
{ New Acronyms added }
{ Model info corrections }

 

[Uwe]

New version, link is updated in #1.

Any chance we could have an English version rather than Danish?

-Uwe-