VCDS

  • Logging Data / Channel Maps with VCDS (section 7)

    screen shot of VCDS with controller channel maps showing

     

     

     

     

     

     

    Help on logging data and making controller channel maps when asking for technical support using VCDS

    Choose a page below to see full instructions and help

  • Making Controller Channel Maps using VCDS (Video 7.11)

    Here's a short video showing how to make controller Channel map files using VCDS. We sometimes ask for these to help you if you need technical support

     

     

     

    Video Transcript WEBVTT

    1
    00:00:01.340 --> 00:00:03.000 line:15%
    Hello, this is Derek from ilexa

    2
    00:00:03.000 --> 00:00:04.680 line:15%
    and this is a quick guide to making

    3
    00:00:04.680 --> 00:00:07.400 line:15%
    a controller channel map in VCDS.

    4
    00:00:07.400 --> 00:00:09.850 line:15%
    So, first choose Applications

    5
    00:00:09.850 --> 00:00:11.493 line:15%
    and then Controller Channel Map.

    6
    00:00:12.520 --> 00:00:14.180 line:15%
    Type the controller address.

    7
    00:00:14.180 --> 00:00:17.810
    In this case I'm going to do 03 for ABS.

    8
    00:00:17.810 --> 00:00:21.170
    Tick measuring values and adaptations.

    9
    00:00:21.170 --> 00:00:24.491
    Leave the output as pre-label file and click Go.

    10
    00:00:24.491 --> 00:00:27.000
    (beeping)

    11
    00:00:27.000 --> 00:00:29.080
    VCDS will now work its way

    12
    00:00:29.080 --> 00:00:31.630
    through all the available measuring block channels.

    13
    00:00:32.810 --> 00:00:35.070
    There are a lot of channels and not all of them

    14
    00:00:35.070 --> 00:00:38.350
    will be available on any particular controller.

    15
    00:00:38.350 --> 00:00:42.650
    So, you will see many boxes where it says error

    16
    00:00:42.650 --> 00:00:44.180
    that the group is not available.

    17
    00:00:44.180 --> 00:00:46.110
    Just ignore that and allow VCDS

    18
    00:00:46.110 --> 00:00:47.860
    to work its way through the groups.

    19
    00:00:54.770 --> 00:00:56.270
    When it finishes the measuring blocks,

    20
    00:00:56.270 --> 00:00:58.343
    it'll move onto adaptations.

    21
    00:01:04.060 --> 00:01:06.400
    And again, you'll see many channels not available

    22
    00:01:06.400 --> 00:01:07.900
    and you'll also see some channels

    23
    00:01:07.900 --> 00:01:10.343
    that say security access required.

    24
    00:01:16.415 --> 00:01:18.590
    When VCDS is finished, the screen will go back

    25
    00:01:18.590 --> 00:01:21.603
    and it will have written the data to some log files.
     
  • VCDS - Diagnosing an ABS fault using a Ross-Tech HEX-NET, VCDS Mobile and a Smart phone

    Here's a short video I took while diagnosing an ABS issue on a SEAT Altea. It shows how to connect to the HEX-NET in AP mode, and open VCDS Mobile on a SmartPhone. Next, I read and describe the fault codes and view the live data to determine the fault.

     

    After replacing the faulty ABS wheel speed sensor, I re-read the codes and clear them, and then check the live data to make sure everything is OK

     

  • VCDS - Reading and Clearing fault codes (Video 5.1)

    Here's a 4 minute video showing how to read fault codes using VCDS.

    In it I also show you how to view the live data measuring blocks to confirm the diagnosis and clear the fault code

     

     

    Video transcript
    Hello, this is Derek from ilexa
    This is a quick guide to reading fault codes from a single module using a VIN-limited interface, in this case it's a three VIN HEX-V2 interface and I haven't registered it to any cars yet, so it has no VINs stored at all.

    I'm going to choose Select and then I'm going to choose Central Electrics because I have disconnected the rain and light sensor
    so I know there will be a fault.

    VCDS prompts me, do I want to add this VIN to the interface?  It says it's currently not registered, would I like to add it?

    In this case, I'm going to choose no and that will still allow me to read fault codes, clear those fault codes and look at live data, but I won't be able to do adaptations or codings or things like that on the module unless I allow VCDS to add that VIN to its list.

    I'm going to read fault codes, and we have interior monitoring sensors intermittent and rain and light sensor, no communication.

    The rain and light sensor, no communication is expected because I have disconnected it.

    So, I'm going to clear those, first off, I'll just click Save.

    I'm going to save that and now I'm going to clear those codes.

    And I'm expecting that the rain and light sensor fault code will come back but it might need the ignition cycling just to register it.

    No, it's instantly come back however, the interior monitoring one is gone.
    That was intermittent, so that's okay.

    So, now I'm going to look in the measured values and we're looking for the rain and light sensor. So, I'll type Rain into the search box to narrow them down, tick those two.

    So, we have no communication and also we have no component info. So, that confirms again that the rain and light sensor is not talking to the rest of the car.

    I will save that to the log and then I'll go done back out of there, and I'll close the controller and now I'm going to turn the ignition off, reconnect the rain and light sensor. Put the ignition back on and go back into Central Electrics.


    Straight away we can see a difference there that there are four slave units now where there were only three previously and  the rain and light sensor part number has popped up in the slave list,

    We'll go into Fault Codes and I'm expecting that to be intermittent now which it is.

    I won't clear it just yet but I will save those to the log.

    I kept the log open even though I closed the controller so that all of these saved files will be in a single file as a good record for this job.

    And I'll choose Advanced Measure Values, type Rain again and tick those two.

    And so, now this time I have the live value from the rain sensor.

    There is indeed no rain and I have component info showing so that's a good sign, the communication is back and that's all looking good.

    So, I'm going to clear that code and we know what that fault was, so I don't expect that to come back and I'll just quickly read it again and that's it, and so, that's all done.

    And I close the controller.
     
  • VCDS - Reading and Clearing fault codes with a HEX-NET and VCDS Mobile(Video 5.2)

    Here's a 7 minute video showing how to read fault codes using Ross-Tech HEX-NET®, VCDS Mobile® and an Android Smart Phone

    It shows how to diagnose an ABS fault but you can use the same process to diagnose almost any fault

    In it I also show you how to view the live data measuring blocks to confirm the diagnosis and clear the fault code

     

     

  • VCDS Help. How to register your new HEX-V2 or HEX-NET interface with Ross-Tech

    Here's a short video showing how to register your new Ross-Tech HEX-V2© or HEX-NET© interface with Ross-Tech©

    In it, I show you how to open the registration form and which boxes you need to complete, next I show you how to enter the Transaction ID you'll receive by email

    NOTE, not shown in the video, but if you are registering a HEX-NET, please also add your chosen user name and password for the VCDS Cloud account (you should make these up as you wish, they are NOT your WiFi details or the login for this or any other site)