VCDS not showing installed modules in Select Control Module

[Craig.]

Since 2-3 updates ago, Using latest version 23.11.0, no matter which vehicle I plug into with my Hex Net, checked to have latest firmware, none of them show the installed modules in Select Control Module, only "common" modules.

This happens with PQ, MQB etc etc all vehicles.

Is there a setting that needs to be changed?

 

[VWT6]

The same happens with HEX-V2.
However, backing up to main screen and reselecting "Select Control Module" seems to resolve the issue.

 

[Uwe]

Is it possible you guys are just going too fast? Plugging in your interface and immediately hitting [Select]? I could see this happening if the interface hasn't had a chance to finish booting up completely and trying to get a VIN from the car.

-Uwe-

 

[VWT6]

No, I don't think so.

To reproduce:

• plug in the HEX-V2 to the OBD socket
  • left green LED flashes
  • red (left/right) flashes a few times
  • yellow (left/right) flashes
  • red-green (left/right) fast blinking
  • wait 30 seconds
• plug in USB into computer (Win11, already running)
  • wait 30 seconds
• turn IGNition ON
  • wait 30 seconds
• launch VCDS
  • wait 30 seconds
• VCDS - Select (quite a delay before opening)
  • HEX-V2 LEDs now steady green
• Only "Common" modules available
• Go Back - Select - now all the modules available
• Go to a module - save e.g. fault codes - no VIN shown in the pop-up

Vehicle in question https://forums.ross-tech.com/index.php?threads/14188/
Seems somehow relate to https://forums.ross-tech.com/index.php?threads/29332/post-248283

Monday,25,March,2024,08:57:06:38894
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 11 x64
VCDS Version: 23.11.0.0 (x64)  HEX-V2 CB: 0.4643.4
Data version: 20231027 DS351.0
www.Ross-Tech.com

 

[Craig.]

Is it possible you guys are just going too fast? Plugging in your interface and immediately hitting [Select]? I could see this happening if the interface hasn't had a chance to finish booting up completely and trying to get a VIN from the car.

-Uwe-

I've had my HEX-NET for a couple years now and only this year it has started happening and it's consistent on EVERY vehicle. It doesn't show installed modules on ANY vehicle I plug into, including my own (Seat Leon MQB and VW T5.1). No matter how much time I leave between plugging in the interface.

Nothing I do resolves it, including the method mentioned by VWT6 (I recognise your pic from the T6 forum, MMI?).

I have re-installed VCDS too, albeit a while ago now when I first noticed it and it's kept up to date.

Any ideas on why it's happening?

 

[Uwe]

I've had my HEX-NET for a couple years now and only this year it has started happening and it's consistent on EVERY vehicle. It doesn't show installed modules on ANY vehicle I plug into, including my own (Seat Leon MQB and VW T5.1). No matter how much time I leave between plugging in the interface.

What are the exact results when you do [Options] -> [Test] in VCDS with it all plugged in?

What happens if you do an Auto-Scan with Auto-Detect?

-Uwe-

 

[Craig.]

What are the exact results when you do [Options] -> [Test] in VCDS with it all plugged in?

What happens if you do an Auto-Scan with Auto-Detect?

-Uwe-

Here you go bud:

VCDS Release 24.5.0: Port Test


Port Status: OK
Interface: Found!
Type: HEX-NET
Version:
CB: 0.4643.4
FW: 0.257
WiFi: 310C
Status: Ready
Can: OK, K1: OK, K2: OK
VBat: 12.34V, VIgn: 12.36V


Autoscan is absolutely fine, auto-detect works when expected.

Vehicle used for the above: 2016 Seat Leon 5F

 

[Uwe]

Can: OK, K1: OK, K2: OK

Autoscan is absolutely fine, auto-detect works when expected.

OK, I'm scratching my head.

Does the [Gateway Installation List] button on the Auto-Scan screen work as expected?

-Uwe-

 

[Craig.]

OK, I'm scratching my head.

Does the [Gateway Installation List] button on the Auto-Scan screen work as expected?

-Uwe-

It certainly does

 

[Uwe]

@Eric -- Any ideas?

-Uwe-

 

[Eric]

This sounds like what @VWT6 experienced a long time ago indeed. I think the codeblock gets in a state of confusion trying to retrieve the VIN, and then doesn't answer VCDS correctly when VCDS tries to retrieve the installation list. You could get a debug 1024 (should be recorded to debug-inst.dlm) to see the comms between VCDS and codeblock, but to be really useful, it would need to be accompanied by a hex-net debug.
You can do that IIRC by going to VCDS-mobile and setting the debug level to 001f there, then sending us the .EDL file(s) it generates on the SD card. Someone correct me if this isn't the correct hex-net debug procedure.

 

[Craig.]

This sounds like what @VWT6 experienced a long time ago indeed. I think the codeblock gets in a state of confusion trying to retrieve the VIN, and then doesn't answer VCDS correctly when VCDS tries to retrieve the installation list. You could get a debug 1024 (should be recorded to debug-inst.dlm) to see the comms between VCDS and codeblock, but to be really useful, it would need to be accompanied by a hex-net debug.
You can do that IIRC by going to VCDS-mobile and setting the debug level to 001f there, then sending us the .EDL file(s) it generates on the SD card. Someone correct me if this isn't the correct hex-net debug procedure.

Thanks Eric, I've not used VCDS-Mobile, is it critical that I use it via the mobile method or can I do it in the normal VCDS program?

 

[VWT6]

This sounds like what @VWT6 experienced a long time ago indeed.

and is still experiencing...

• Go Back - Select - now all the modules available
• Go to a module - save e.g. fault codes - no VIN shown in the pop-up

 

[Craig.]

This sounds like what @VWT6 experienced a long time ago indeed. I think the codeblock gets in a state of confusion trying to retrieve the VIN, and then doesn't answer VCDS correctly when VCDS tries to retrieve the installation list. You could get a debug 1024 (should be recorded to debug-inst.dlm) to see the comms between VCDS and codeblock, but to be really useful, it would need to be accompanied by a hex-net debug.
You can do that IIRC by going to VCDS-mobile and setting the debug level to 001f there, then sending us the .EDL file(s) it generates on the SD card. Someone correct me if this isn't the correct hex-net debug procedure.

I just updated my VCDS to 24.7.0 and still the same, I also looked to change the debug level to 001f and it refused the change as "f" is an invalid character?

 

[PetrolDave]

You can do that IIRC by going to VCDS-mobile and setting the debug level to 001f there

I also looked to change the debug level to 001f and it refused the change as "f" is an invalid character?

You tried to change the debug level in VCDS not VCDS-mobile.

 

[Craig.]

You tried to change the debug level in VCDS not VCDS-mobile.

Thanks, I am aware of that. I also asked if it was critical to use VCDS-Mobile, to which I didn't get a reply so tried it in the normal program and offered a result as Eric didn't seem 100% sure on the process.

 

[Eric]

I think my instructions were clear, but if they're too complicated for you, I don't have a more detailed step by step guide handy.

 

[Uwe]

I also asked if it was critical to use VCDS-Mobile,

You don't need to use VCDS-Mobile except to set the Debug Level in the HEX-NET itself and then to retrieve the .EDL files it will generate and store internally after you've reproduced the problem with VCDS.

-Uwe-

 

[Craig.]

You don't need to use VCDS-Mobile except to set the Debug Level in the HEX-NET itself and then to retrieve the .EDL files it will generate and store internally after you've reproduced the problem with VCDS.

-Uwe-

Thanks Uwe, I'll learn how to set up and use VCDS-mobile, get the info and then send it to the usual support email address.

 

[Craig.]

So, after much faf, managed to email over an EDL file from today and DLM (didn't have a debug-inst.dlm file, only debug-vin.dlm file?) from at some point.

Interesting things:

Upon logging into VCDS-mobile I had SD CRITICAL ERROR in red at the top.

Autosacans are useless as it doesn't pull any ROD or ASAM data when using it on my phone, perhaps this is why I've never used it but it did the scan regardless.

Autoscans AND select module sections functioned correctly, pulling the installed modules as it should.