Performing Adaptations via WiFi connection

[Dadeos]

I'm currently struggling to perform a module adaptation via WiFi and wanted to check whether such an operation is supported?

I believe that I have successfully connected my HEX-NET HN2 via WiFi, using Infrastructure mode. I have been able to communicate with the device, perform module scans, clear DTCs, etc. However, I have been unable to perform an Adaptation.

I have tried using VCDS-Mobile, via "Cloud Functions", but the drop-down at the top of the page remains empty. I am assuming that it should be populated with various potential adaptation options, but perhaps I'm mistaken?

I also tried using VCDS, for Windows, but my attempt to access "Adapations" results in a dialog box complaining about the need for a registered interface. I understand that the HEX-NET adapter connected via USB acts as a security dongle and perhaps connecting via WiFi does not similarly fulfil this function?

For various reasons, mainly for lack of access to a Windows laptop, it is inconvenient for me to locate my car within the length of a USB cable from my desktop Windows PC, so I was hoping to be able to use the WiFi connection.

I'm currently using:

VCDS: 26.3.0
CB: 0.4713
FW: 1.85

I switched to the "beta" update channel, as recommended, due issues decoding fault codes in VCDS-Mobile.

 

[stefdds]

For context, its probably not a good idea to start another thread.

Garbled (original binary un-decoded?) output for "Faults Found"

My kid got 2017 A3, I did basic diagnostics using BlueDriver (there is no CEL). It gave bunch of stored errors (they reappear if reset), so I decided to invest into Audi-specialized Ross-Tech's "VCDS-Mobile with HEX-NET Enthusiast". Connecting from the browser (I do not use Windows much), I get...

forums.ross-tech.com

 

[Dr Sheldon]

How does it perform with a wired Connection ?

 

[Uwe]

I'm currently struggling to perform a module adaptation via WiFi and wanted to check whether such an operation is supported?

In principle, it is, but you haven't given us a clue as to what module in what car you're trying to do adaptations on.

I understand that the HEX-NET adapter connected via USB acts as a security dongle and perhaps connecting via WiFi does not similarly fulfil this function?

It does. Have you registered this car's VIN against the 10-VIN license in your HEX-NET?

-Uwe-

 

[Dadeos]

In principle, it is, but you haven't given us a clue as to what module in what car you're trying to do adaptations on.

The car in question is a 2016 Audi RS3, the module is the "09-Central Electronics" (see: Scan log below, I believe generated from one of my attempts using VCDS-Mobile):

Sat,Jun,13,2026,13:04:00 
VCDS Mobile 0.4713.0.5

Sat,Jun,13,2026,13:04:00 
VCDS Mobile: 0.4713
Data Version: 00000066

Scan: 01 02 03 05 08 09 10 14 15 16 17 19 22 2B 42 44 52 55 5F BB
     BC

01-Engine -- Status: Malfunction 0010
02-Auto Trans -- Status: OK 0000
03-ABS Brakes -- Status: OK 0000
05-Acc/Start Auth. -- Status: OK 0000
08-Auto HVAC -- Status: OK 0000
09-Cent. Elect. -- Status: Malfunction 0010
10-Park/Steer Assist -- Status: OK 0000
14-Susp. Elect. -- 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
22-AWD -- Status: OK 0000
2B-Steer. Col. Lock -- Status: OK 0000
42-Door Elect, Driver -- Status: OK 0000
44-Steering Assist -- Status: OK 0000
52-Door Elect, Pass. -- Status: OK 0000
55-Xenon Range -- Status: OK 0000
5F-Information Electr. -- Status: Malfunction 0010
BB-Door Rear Drv Side -- Status: OK 0000
BC-Door Rear Pass Side -- Status: OK 0000



-----------------------------------------------------------------
Address 01: Engine  (------CZGB)    Labels: 07K-907-309-V1.clb
    Part No SW: 8V0 907 404    HW: 07K 907 309 C
    Component: 2.5l R5/4V TF H52 0005
    Revision: NKH52---
    Coding: 12250032250601033600
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_ECM25TFS0118V0907404 001006
    ROD: EV_ECM25TFS0118V0907404.rod
    VCID: F6AFC5DB4CDB35DD0A8DFC-80A3

1 Fault Found:
19815 - Control Module for Exhaust Flap
    P14AB 00 [096] - Mechanical Malfunction
    Intermittent - Not Confirmed - Tested Since Memory Clear


-----------------------------------------------------------------
Address 02: Auto Trans  (J743-)    Labels: 0D-02.clb
    Part No SW: 0DL 300 011 D    HW: 0BH 927 711 F
    Component: GSG DQ500     H10 5203
    Revision: 00H10V01
    Coding: 0014
    Shop #: WSC 00000 000 00000
    ASAM Dataset: EV_TCMDQ500021 001001
    ROD: N/A
    VCID: 29155EA74DE5AA25D78FAF-807C

    No ASAM data for: "EV_TCMDQ500021"
No fault codes found.

-----------------------------------------------------------------
Address 03: ABS Brakes  (J104)    Labels: 5Q0-907-379-IPB-V1.clb
    Part No SW: 8V0 907 379    HW: 8V0 907 379
    Component: ESC           H42 0020
    Revision: 00000000
    Coding: 999CF08DBA9915B040950865C398820EC4990F5DA80210C3417023
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_Brake1UDSContiMK100IPB 061003
    ROD: EV_Brake1UDSContiMK100IPB_061.rod
    VCID: 0145260795158265AF1F67-8054

No fault codes found.

-----------------------------------------------------------------
Address 05: Acc/Start Auth.  (J518)    Labels: 5Q0-959-435.clb
    Part No SW: 5Q0 959 435 A    HW: 5Q0 959 435
    Component: VWKESSYMQB    021 0604
    Revision: 00021000
    Coding: 030C0C
    Shop #: WSC 00000 000 00000
    ASAM Dataset: EV_KessyHellaMQBAB 002011
    ROD: EV_KessyHellaMQBAB_002.rod
    VCID: 3A3791EBB84311BDAE55E8-806F

No fault codes found.

-----------------------------------------------------------------
Address 08: Auto HVAC  (E87)    Labels: 8V0-820-043.clb
    Part No SW: 8V0 820 043 D    HW: 8V0 820 043 D
    Component: AC Automat    H14 0060
    Revision: 20028000
    Coding: 03100005000000001000000000001000
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_AirCondiFrontVaAU37X 008020
    ROD: EV_AirCondiFrontVaAU37X_008.rod
    VCID: 3329BCCF9F29E0F56D135D-8066

No fault codes found.

-----------------------------------------------------------------
Address 09: Cent. Elect.  (J519)    Labels: 5Q0-937-08X-HV1.clb
    Part No SW: 5Q0 937 084 CL    HW: 5Q0 937 084 AN
    Component: BCM MQBAB H   H24 0175
    Coding: 07051C46C24106FD03844004B31C07A80800000000000000000000000000
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_BCMMQB 015001
    ROD: EV_BCMMQB_015.rod
    VCID: 844BAF130A07174D0439C6-80D1

    Subsystem 1 -     Part No SW: 8V2-955-119-A    Labels: 5Qx-955-119-V1.clb
    Component: WWS370 160205043 0580
    Serial Number:         160212135611
    Coding: 0A47F7

    Subsystem 2 -     Part No SW: 8U0-955-559-C    Labels: 8U0-955-559.clb
    Component: G397_RLFS    H06 0004
    Serial Number: 61422604            
    Coding: 00006C

    Subsystem 3 -     Part No SW: 8V0-941-531-AA
    Component: E1 - LDS MQB H05 0032
    Serial Number: 04 12 2015  00002002

    Subsystem 4 -     Part No SW: 8V0-951-177
    Component: Sensor, DWA  005 0316
    Serial Number: 000000000ZY110530848

    Subsystem 5 -     Part No SW: 5Q0-951-605-A
    Component: Sirene, DWA  005 0313
    Serial Number: 00000000000065141760

1 Fault Found:
204290 - Remote key 1
    B1479 18 [008] - Current Too Low
    Intermittent - Confirmed - Tested Since Memory Clear


-----------------------------------------------------------------
Address 10: Park/Steer Assist  (J446)    Labels: 5Q0-919-294.clb
    Part No SW: 5Q0 919 294 K    HW: 5Q0 919 294 A
    Component: PARKHILFE 8K  H03 0054
    Revision: --------
    Coding: 0030050011
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_EPHVA18AU3700000 002026
    ROD: EV_EPHVA18AU3700000_002_VW37.rod
    VCID: 43C9EC0FCF895075FDB38D-8016

No fault codes found.

-----------------------------------------------------------------
Address 14: Susp. Elect.  (J250)    Labels: 8V0-907-376.clb
    Part No SW: 8V0 907 376 E    HW: 8V0 907 376 E
    Component: DAEMPFUNGS-SG H09 0072
    Shop #: WSC 00000 000
    ASAM Dataset: EV_AudiMagneRide 002003
    ROD: EV_AudiMagneRide_002.rod
    VCID: 43C9EC0FCF895075FDB38D-8016

No fault codes found.

-----------------------------------------------------------------
Address 15: Airbags  (J234)    Labels: 5Q0-959-655.clb
    Part No SW: 5Q0 959 655 N    HW: 5Q0 959 655 N
    Component: AirbagVW20    012 0361
    Coding: 98CCC000008000005C5400CA00C800000065
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_AirbaVW20SMEVW37X 002126
    ROD: EV_AirbaVW20SMEVW37X_VW37.rod
    VCID: 4BD9C42FE7D9983505E355-801E

    Subsystem 1 -     Part No SW: --------------
    Component: SideSensor_Df001 0887
    Serial Number: 35767000000F7311281N
    Coding: 2D2D2D

    Subsystem 2 -     Part No SW: --------------
    Component: SideSensor_Pf001 0887
    Serial Number: 35867000000B9311281M
    Coding: 2D2D2D

    Subsystem 3 -     Part No SW: --------------
    Component: SideSensor_Dr001 6149
    Serial Number: 3516502A51EDD3E3C19Y
    Coding: 2D2D2D

    Subsystem 4 -     Part No SW: --------------
    Component: SideSensor_Pr001 6149
    Serial Number: 3526502C11EDD3E4E2F0
    Coding: 2D2D2D

No fault codes found.

-----------------------------------------------------------------
Address 16: Steering wheel  (J527)    Labels: 8V-16.lbl
    Part No SW: 8V0 953 521 ET    HW: 5Q0 953 549 E
    Component: Lenks. Modul  003 0120
    Revision: --------
    Coding: 8418
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_SMLSKLOMQB 020001
    ROD: EV_SMLSKLOMQB_020_AU37.rod
    VCID: 906393434E7F7BEDB0B15A-80C5

No fault codes found.

-----------------------------------------------------------------
Address 17: Instruments  (J285)    Labels: 5G0-920-XXX-17.clb
    Part No SW: 8V0 920 971 N    HW: 8V0 920 971 N
    Component: KOMBI         H02 6423
    Coding: 278D081A3B8026000104E8001000000000000000
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_DashBoardVDDMQBAB 009051
    ROD: EV_DashBoardVDDMQBAB_009_AU37.rod
    VCID: 48D3FB23F6AF732D28C172-801D

No fault codes found.

-----------------------------------------------------------------
Address 19: CAN Gateway  (J533)    Labels: 5Q0-907-530-V1.clb
    Part No SW: 5Q0 907 530 AJ    HW: 5Q0 907 530 F
    Component: GW MQB High   128 1244
    Revision: --------
    Coding: 030100043F0860005B000268B80B00000001010000000000000000000000
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_GatewLear 013020
    ROD: EV_GatewLear_013_VW37.rod
    VCID: 79B54EE7FDC5DAA5E7AF5F-802C

    Subsystem 1 - 
    Subsystem 2 -     Part No SW: 8U0-951-528-C
    Component: E221 - MFL   H02 0014
    Serial Number: 16 02 2016  C0045570

    Subsystem 3 -     Part No SW: 8S0-915-181
    Component: J367-BDMHellaH10 9052
    Serial Number: 5711939103          

No fault codes found.

-----------------------------------------------------------------
Address 22: AWD  (J492)    Labels: 0CQ-907-554.clb
    Part No SW: 0CQ 907 554 C    HW: 0CQ 525 130
    Component: Haldex4Motion H52 7754
    Coding: 0601
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_AllWheelContrHA1VW37X 002015
    ROD: EV_AllWheelContrHA1VW37X_002.rod
    VCID: 45CDF217C1BD6E45D3A793-8010

No fault codes found.

-----------------------------------------------------------------
Address 2B: Steer. Col. Lock  (J764)    Labels: 5Q0-905-861.clb
    Part No SW: 5Q0 905 861 A    HW: 5Q0 905 861 A
    Component: ELV-MQBA      H01 0120
    Revision: 00000000
    Coding: 5D00000000000000
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_ELVMarquMQB 004111
    ROD: EV_ELVMarquMQB_004.rod
    VCID: 342BBFD39A27E7CD741956-8061

No fault codes found.

-----------------------------------------------------------------
Address 42: Door Elect, Driver  (J386)    Labels: 5QX-959-X93-42.clb
    Part No SW: 5Q0 959 593 E    HW: 5Q0 959 593 B
    Component: TSG FS        020 0041
    Coding: 00109A205C01040000001002
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_DCUDriveSideEWMAXKLO 006003
    ROD: EV_DCUDriveSideEWMAXKLO.rod
    VCID: 43C9EC0FCF895075FDB38D-8016

No fault codes found.

-----------------------------------------------------------------
Address 44: Steering Assist  (J500)    Labels: 5Q0-909-144.clb
    Part No SW: 3Q0 909 144 J    HW: 3Q0 909 144 H
    Component: EPS_MQB_ZFLS  505 5063
    Coding: 8103
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_SteerAssisMQB 012140
    ROD: EV_SteerAssisMQB_012_VW48.rod
    VCID: 39358EE7BD451AA5A72F1F-806C

No fault codes found.

-----------------------------------------------------------------
Address 52: Door Elect, Pass.  (J387)    Labels: 5QX-959-X92-52.clb
    Part No SW: 5Q0 959 592 E    HW: 5Q0 959 592 B
    Component: TSG BFS       020 0041
    Coding: 001092205E01040000001002
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_DCUPasseSideEWMAXKLO 006003
    ROD: EV_DCUPasseSideEWMAXKLO.rod
    VCID: 42C7E90BD093597DF685B0-8017

No fault codes found.

-----------------------------------------------------------------
Address 55: Xenon Range  (J745)    Labels: 7P6-907-357.clb
    Part No SW: 7P6 907 357 C    HW: 7P6 907 357 B
    Component: AFS-ECU       H01 0120
    Revision: --------
    Coding: 01A600002B230200
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_HeadlRegulAFSMQBMLB 001001
    ROD: EV_HeadlRegulAFSMQBMLB.rod
    VCID: 3FC1E0FFA3613495996BD1-806A

    Subsystem 1 -     Part No SW: 7PP-941-472-J    Labels: 3D0-941-329.clb
    Component: LED LeiMo li.H07 7560
    Coding: E00100

    Subsystem 2 -     Part No SW: 7PP-941-329-M    Labels: 7P-55-02.clb
    Component: LeiMo links  H01 7050
    Coding: E00100

    Subsystem 3 -     Part No SW: 7PP-941-329-M    Labels: 7P-55-03.lbl
    Component: LeiMo rechts H01 7050
    Coding: E00100

No fault codes found.

-----------------------------------------------------------------
Address 5F: Information Electr.  (J794)    Labels: 8V-5f.clb
    Part No SW: 8V0 035 018    HW: 8V0 035 020 D
    Component: MU-H-ND-EU    H45 0404
    Coding: 01730301FF0A000021111101000A00032F00030701000100DE
    Shop #: WSC 19512 003 1048576
    ASAM Dataset: EV_MUHig6C3HBAS 001040
    ROD: EV_MUHig6C3HBAS_AU37.rod
    VCID: EFA1F0BF33810415C94B21-80BA

    Subsystem 1 -     Part No SW: V03-959-801-PN
    Component: ECE 2018     --- 0166
    Serial Number: --------------------

    Subsystem 2 -     Part No SW: 8V0-919-604-C
    Component: DU High      H49 0014
    Serial Number: AUZ8Z9FY2051DG      

    Subsystem 3 -     Part No SW: 8V0-919-614-L
    Component: ControlUnit_HH81 0816
    Serial Number: ALJAL126121500020059

No fault codes found.

-----------------------------------------------------------------
Address BB: Door Rear Drv Side  (J388)    Labels: None
    Part No SW: 5Q0 959 595 E    HW: 5Q0 959 595 B
    Component: TSG HFS       020 0041
    Coding: 000092204001040000001002
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_DCURearDriveMAXKLO 006003
    ROD: EV_DCURearDriveMAXKLO.rod
    VCID: 45CDF217C1BD6E45D3A793-8010

No fault codes found.

-----------------------------------------------------------------
Address BC: Door Rear Pass Side  (J389)    Labels: None
    Part No SW: 5Q0 959 595 E    HW: 5Q0 959 595 B
    Component: TSG HBFS      020 0041
    Coding: 000092204001040000001002
    Shop #: WSC 06314 790 00021
    ASAM Dataset: EV_DCURearPasseMAXKLO 006003
    ROD: EV_DCURearPasseMAXKLO.rod
    VCID: 45CDF217C1BD6E45D3A793-8010

No fault codes found.

End--(Elapsed Time: 02:18, VBatt start/end: 14.4/14.4 Vign: 14.4)-

I believe I explored querying potential adaptations for a number of different modules, all with similar outcomes.

My initial approach was to use an iPhone "Personal Hotspot", which proved moderately successful. I was able to download some ASAM files, albeit somewhat slowly, and connect to the Cloud services, albeit without much luck obtaining potential adaptations.

Having struggled with VCDS-Mobile, I briefly tried using "Remote Desktop" to my Windows PC, where I encountered the errors associated with the need for a registered interface. At which point I began to wonder whether what I was attempting was supported.

It does. Have you registered this car's VIN against the 10-VIN license in your HEX-NET?

I believe so, yes. The configuration utility is showing "VINs Stored: 1" and the car in question is the only one I've connected it to.

 

[Dadeos]

After a considerable amount of time attempting to use the WiFi functionality I finally relented, installed a Windows 11 Virtual Machine (VM) on my MacBook, installed VCDS on the VM, connected the HEX-NET V2 via USB and was able to access and apply the required Adaptation without issue.

If you're interested in assisting in diagnosing why the WiFi connection doesn't appear to work for me then I'd be happy to experiment some more.

As a new user, I doubt that I have a good appreciation of all of the intricacies of the system. However, a broad overview of some of the approaches I tried prior to resorting to using a USB connection include:

VCDS-Mobile:

• Attempted to reset the device by depressing the red button for ~1min - resulting in 4 audible beeps - I'm not convinced that this did anything beyond wiping the WiFi configuration
• Reconfigured the WiFi settings to connect to the "Personal Hotspot" provided by my iPhone
• Load the VCDS-Mobile webpage in Safari on my iPhone
• Navigated to "Options" -> "Clear Dataset Cache" and "Clear Rod Files" - this was probably a mistake
• Connected HEX-NET to car
• Performed Auto-Scan - was warned about missing ASAM data
• Downloaded missing ASAM data - the process of which offered no indication of any failure
• Performed another Auto-Scan - was warned about missing ASAM data (again)
• Download missing ASAM data (again) - the process of which offered no indication of any failure and the file sizes etc. reported were suspiciously similar to the previous time (repeated this process several more times)
• Disconnected HEX-NET from car and connected it to desktop Windows PC via USB
• Use "VCDS Interface Config V2.303" to check for updates
• ROD files seemingly successfully downloaded and installed onto HEX-NET via ephemeral USB drive mount
• Disconnected HEX-NET from desktop PC and reconnected to car
• Went round the Auto-Scan, missing ASAM data, download/installing ASAM data, rescanning, still have missing ASAM data loop a few more times

I believe that the steps outlined above broadly reflect the actions I undertook from the outset (i.e. prior to posting to this forum). Prior to clearing the "Dataset Cache" and "Rod Files" I suspect that somehow I had actually managed to accumulate sufficient data on the HEX-NET to successfully perform an Auto-Scan without complaint regarding missing ASAM data. However, if I managed to navigate to the Adaptations page for a module, I was always presented with a seemingly empty drop-down list (see: attached screenshot).



Perhaps it takes a long time for this list to be populated? I tried to be patient and waited for several minutes, but the page offers no indication that it is doing anything in the background and the drop-down never came to contain any additional entries.


When attempting to use VCDS from my desktop Windows PC, connected via WiFi, using remote desktop from my MacBook I did manage to get to the modules' Adaptation window once, but received the "licensed device required" error when attempting to apply the configuration change. I suspect that these issues might be related to poor network performance. I could happily sit in my car using remote desktop from my MacBook via WiFi but my network diagnostics were showing that, while certainly connected, the connection to the HEX-NET wasn't great. Perhaps a function of being limited to 2.5GHz WiFi, rather than the 5GHz being used by the MacBook, and being slightly further away from the access point, in the footwell of the car, which is after all something of a Faraday cage.

 

[Shaun]

If you want to help test this, go ahead an give it a try with VCDS-Mobile again and see if you can get the adaptation list now.

 

[Dadeos]

If you want to help test this, go ahead an give it a try with VCDS-Mobile again and see if you can get the adaptation list now.

Whatever changed, it appears to be working now…



I must confess that without the assistance of the search functionality offered by the Windows version, I didn't manage the locate the adaptation I was looking for, but that's mostly a me problem.

I'm still struggling with the ASAM/ROD data update loops, but I'll continue persevering…

Thanks for your assistance and for whatever you did to make it work for me!