I just used VCDS-Mobile to perform an auto-scan of one vehicle, my 2019 Mk7.5 Golf R (NAR). The HEX-NET said ASAM files were missing, and when I tried to have it update, it seemed to get stuck on verifying the update. After 2 minutes while connected to my vehicle I cancelled the update to avoid draining my battery and brought it back to my laptop. I connected it via USB, opened VCDS-Mobile again, and manually checked for updates. I was again prompted to update ASAM files, which I chose to do. Initially the ETA was 2 minutes, but it's now been running for over 15 minutes, and at this stage the progress bars are as follows:
Updating ASAM dataset: 40%, ETA 40 minutes
Step [2/3] Verifying Update: 1/5
Status: Verifying: 1 KB.
Since the ETA has been incrementing up from 2 minutes to 40 minutes, it doesn't appear to be hung, but neither of the progress bars have moved, and it's been verifying this 1 KB of data for over 15 minutes now. Is this normal? Is there a server-side issue somewhere? How long should it normally take to update ASAM data for a single vehicle? I have a 400 Mbps Internet connection, but I doubt it makes a difference here.
I've power cycled the HEX-NET several times with no change in behavior. The HEX-NET is running CB 0.4529 and FW 1.53.
Updating ASAM dataset: 40%, ETA 40 minutes
Step [2/3] Verifying Update: 1/5
Status: Verifying: 1 KB.
Since the ETA has been incrementing up from 2 minutes to 40 minutes, it doesn't appear to be hung, but neither of the progress bars have moved, and it's been verifying this 1 KB of data for over 15 minutes now. Is this normal? Is there a server-side issue somewhere? How long should it normally take to update ASAM data for a single vehicle? I have a 400 Mbps Internet connection, but I doubt it makes a difference here.
I've power cycled the HEX-NET several times with no change in behavior. The HEX-NET is running CB 0.4529 and FW 1.53.
Last edited: