I have a genuine VCDS cable running 14.10 software. The cable is a Micro CAN, which works perfectly on my Mk7 Golf. However, on the O3 it doesn't work particularly well in Autoscan mode. When I do an Autoscan it seems to be able to scan some modules without fault and then it says "Cannot be reached" for certain modules (42 drivers door and 08 HVAC are the current favourites). 

 

I can reach the module if I select it and recode it. If I repeat the Autoscan, it is not always the same modules which "cannot be reached". Any ideas on what is going on?

 

When I start the Autoscan, it seems to be able to see all the installed modules and reports back with no fault found and then cannot see the module. Here is an example of what is happening.... I've deleted bits of the scan but you can see that the status of all the installed modules is OK but then some modules can't be reached with the scan!

 

 

 

Tuesday,06,January,2015,18:06:26:26904

VCDS -- Windows Based VAG/VAS Emulator

VCDS Version: 14.10.0.0

Data version: 20141022

 

 

VIN: TMBBG7NE3Dxxxxxxx License Plate: 

Mileage: 19594km-12175mi   Repair Order: 

 

 

 

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

 

 

Chassis Type: NE (5Q0)

Scan: 01 03 08 09 10 15 16 17 19 20 42 44 52 5F

 

VIN: TMBBG7NE3D0033243   Mileage: 19594km-12175miles

 

01-Engine -- Status: OK 0000

03-ABS Brakes -- Status: OK 0000

08-Auto HVAC -- Status: OK 0000

09-Cent. Elect. -- Status: OK 0000

10-Park/Steer Assist -- Status: OK 0000

15-Airbags -- Status: OK 0000

16-Steering wheel -- Status: OK 0000

17-Instruments -- Status: OK 0000

19-CAN Gateway -- Status: OK 0000

20-High Beam Assist. -- Status: OK 0000

42-Door Elect, Driver -- Status: OK 0000

44-Steering Assist -- Status: OK 0000

52-Door Elect, Pass. -- Status: OK 0000

5F-Information Electr. -- Status: OK 0000

 

-------------------------------------------------------------------------------

Address 01: Engine (J623-CLHA)       Labels: 04L-907-309-V1.clb

   Part No SW: 04L 906 021 M    HW: 04L 907 309 B

   Component: R4 1,6L EDC   H22 5517  

   Revision: 84H22---    

   Coding: 01110012032501090000

   Shop #: WSC 73430 031 00125

   ASAM Dataset: EV_ECM16TDI01104L906021M 002009

   ROD: EV_ECM16TDI01104L906021AL.rod

   VCID: 2F43DF1476745459C61-807A

 

No fault code found.

Readiness: 0 0 0 0 0 

 

 

 

-------------------------------------------------------------------------------

Address 16: Steering wheel

Cannot be reached

 

 

-------------------------------------------------------------------------------

Address 19: CAN Gateway (J533)       Labels: Redir Fail!

   Part No SW: 5Q0 907 530 F    HW: 5Q0 907 530 F

   Component: GW MQB High   125 1109  

   Revision: --------    Serial number: 0000512622

   Coding: 030100040B087300EF000648080F00010001000000000000000000000000

   Shop #: WSC 73430 790 00125

   ASAM Dataset: EV_GatewLear 006010

   ROD: EV_GatewLear.rod

   VCID: 3449D0789F527781BB3-8061

 

   Alternator: 

 

   Multifunction unit control module: 

   Subsystem 2 - Part No SW: 5E0 919 719 A    HW: 5E0 919 719 A

   Component: E221__MFL-PR6  H04 0100 

   Serial number: 000000000B0356160413

 

   Battery Monitoring Control Module: 

   Subsystem 3 - Part No SW: 5Q0 915 181 C    HW: 5Q0 915 181 C

   Component: J367-BDMHella  H03 8042 

   Serial number: 8446110403          

 

No fault code found.

 

-------------------------------------------------------------------------------

Address 20: High Beam Assist. (J844)       Labels: None

   Part No SW: 5G0 857 511 D    HW: 5G0 857 511 

   Component: FLA           H04 0002  

   Revision: AA001001    

   Coding: 01028F6B76765D525220343E00

   Shop #: WSC 73430 031 00125

   ASAM Dataset: EV_HighBeamAssisAU37X 001009

   ROD: EV_HighBeamAssisAU37X.rod

   VCID: 2B7BCB04426C2879EA9-807E

 

No fault code found.

 

-------------------------------------------------------------------------------

Address 42: Door Elect, Driver

Cannot be reached

 

-------------------------------------------------------------------------------

 

 

Maybe teaching granny to suck eggs, but you did have the ignition on at the time didn't you?

Of course. I am able to code and access all installed modules, just not able to document/achieve a full autoscan!

It was just a thought (nay, a complete stab in the dark!) The wheel I believe is only powered when the ignition is on, hence the volume etc buttons don't work even when the radio is on.

 

AndyV may have some ideas - he seems to be very knowledgable on VCDS.. Me, I've only just got mine so still learning.

Just realised that I should have posted this in the VCDS forum... so have posted in there as well.

Do you have any doors open?

 

Also, reset all of the port and protocol options to default and re-test the interface then try again.

 

Beyond that, log it with Ross-Tech support

Protocols are set to normal Andy. I think I had the doors both open and closed when doing the scans. Both resulted in comm errors although different ones. Have just emailed Ross Tech.

Doors need to be closed and ignition on but engine not running.

Sent from my HTC One_M8 using Tapatalk

Still doing it with the doors closed. Able to recode all the tweaks that I want, even on modules that apparently can't be reached. RossTech support have asked me to a do a debug with a 1240 setting and send them all the debug files. I have done this and am awaiting a response. 

 

Latest coding done was to stop the Light Assistant resetting itself...

A similar thing has happened to a Golf owner, not sure if it ever got sorted out

Sent from my HTC One_M8 using Tapatalk

I think it may be sorted out Andy. Apparently some of the newer UDS modules do not respond properly to VCDS requests. I am now the proud owner (perhaps the first) of VCDS 14.11.6 to test, which I will do tomorrow.  Excellent RossTech support as usual.

Edited 9 January, 201511 yr by DougL

Brilliant!

Sent from my HTC One_M8 using Tapatalk

The odd thing is I have some significantly newer controllers that seem to work fine!

Sent from my HTC One_M8 using Tapatalk

Couldn't wait to try it and unfortunately it didn't work. Last autoscan couldn't see 17 and 42, this scan couldn't see 3,8 and 42. Very odd. I think it might be my PC. Might try my old netbook! Here goes!

Turn off any antivirus and malware protection.

Sent from my HTC One_M8 using Tapatalk

Did a perfect Autoscan from my old netbook. I wonder did windows defender cause a problem?

What AV do you have installed?

Sent from my iPad using Tapatalk

What AV do you have installed?

Sent from my iPad using Tapatalk

 

None. Use neither for online use. I gave the Lenovo to my father, who never used it. The little netbook was only ever used for VCDS and emailing the scans so none on it either. Normal machine is a Mac running Sophos AV, but obviously I can't run VCDS on that. (Probably could if I used an emulator..)