Problems updating ASAM data OTA

   #1  

martrobgray

Verified VCDS User
Verified
Joined
May 2, 2020
Messages
6
Reaction score
4
Location
UK
VCDS Serial number
C?ID=361178
I received my hex-net today and so far I'm really impressed. The only issue I have is that I can't
download ASAM data by OTA in VCDS mobile when connected in infrastructure mode. I've got a good solid wifi connection with FTTP broadband and everytime the update hangs at 9% 6/26 kb. Ive tried infrastructure mode connected to my Android phone mobile hotspot aswell and the same result.

If I update RODs via VCDS desktop and cable its fine. VCDS mobile reports updates are upto date, and no ASAM missing pop-up when I scan again.

It's not a deal breaker for me but its counter productive and inconvenient if I have to go back to the laptop everytime to update the device. Even more inconvenient if I haven't got my laptop with me.

I know there are alot of threads about this issue, and I hate adding more unnecessarily but I upgraded from my Hex-v2 so I could go wireless.

For reference my update channel is set to release, as a baseline for reporting to you guys.

Keep up the good work, but would be nice to have this fixed. 👍

Thanks, Martyn.
 
  • Like
Reactions: Uwe
   #2  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
29,921
Reaction score
21,361
Location
USA
VCDS Serial number
HC100001
FWIW, the ASAM data should not need to be updated very often. Once you have it for your car, you're good until there's a a whole data-set update.

-Uwe-
 
   #3  

martrobgray

Verified VCDS User
Verified
Joined
May 2, 2020
Messages
6
Reaction score
4
Location
UK
VCDS Serial number
C?ID=361178
FWIW, the ASAM data should not need to be updated very often. Once you have it for your car, you're good until there's a a whole data-set update.

-Uwe-
Thanks for the reply Uwe. It's not a big thing, just thought more feedback for you guys might be useful. I did come across another issue today.

On our sharan 7N I attempted an autoscan with VCDS mobile and every time it stops at 78% on address 61. It gets to 61 says: trying address 61 briefly then disappears. I left it like that for a good 30 mins but nothing happens and can't complete the autoscan. Using VCDS desktop and hex-net in AP mode the autoscan completes without issue.

Any thoughts on why this is?

I've now changed my update channel to beta and downloaded the required updates. Still no change.

So it hangs at 78% in both release an beta.

For reference our TT 8J completed an autoscan on vcds mobile in infrastructure mode and AP mode without issue as seen on our 7N.
 
   #4  

Shaun

Ross-Tech Employee
Joined
Jan 29, 2014
Messages
960
Reaction score
1,547
Location
USA
You can make a debug log in mobile by going to [Options] -> Debug level = 001F, and then making an autoscan. Then email us the results or make sure they are uploaded to the cloud. Do the lights on the interface do anything unusual when this occurs?
 
   #5  

martrobgray

Verified VCDS User
Verified
Joined
May 2, 2020
Messages
6
Reaction score
4
Location
UK
VCDS Serial number
C?ID=361178
You can make a debug log in mobile by going to [Options] -> Debug level = 001F, and then making an autoscan. Then email us the results or make sure they are uploaded to the cloud. Do the lights on the interface do anything unusual when this occurs?
Hi Shaun,

Yes I'll do another scan in debug mode. From memory i can't remember the state of the leds in this condition. I'll confirm when I scan again.

Will a separate debug log be saved to the saved files? I will save the autoscan when its in a state of no activity when it hangs also. If it will save.

I'll get it to you as soon as possible. Thank you
 
   #7  

martrobgray

Verified VCDS User
Verified
Joined
May 2, 2020
Messages
6
Reaction score
4
Location
UK
VCDS Serial number
C?ID=361178
Hi Shaun,

I did a new autoscan in debug mode 001F, the files are uploaded to VCDS Cloud the DocID's are below:

Autoscan: 00005EEC
Debug log: 00005EED

Regarding LED behaviour:
In normal condition --> led 1, solid green. Led 2, solid green. Led 3, flashing green>amber>red (then cycle repeats at each new address)

Abnormal condition when autoscan hangs --> led 1, solid green. Led 2, solid green. Led 3, just flashing green.

Please let me know your findings.

Thanks, Martyn.
 
   #8  

dgigauri

Verified VCDS User
Verified
Joined
May 24, 2020
Messages
8
Reaction score
0
Location
USA
VCDS Serial number
C?ID=77972
Any progress on this issue? I have same problem, every time when I try to use my HEX-NET interface in infrastructure mode and mobile app. Tried update rod data though PC config, but after starting scanning with mobile app, it still requests update ASAM data and stuck at downloading. Actually I can't use mobile app :(
 
   #9  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
29,921
Reaction score
21,361
Location
USA
VCDS Serial number
HC100001
Any progress on this issue? I have same problem, every time when I try to use my HEX-NET interface in infrastructure mode and mobile app. Tried update rod data though PC config, but after starting scanning with mobile app, it still requests update ASAM data and stuck at downloading. Actually I can't use mobile app :(
Hmm. Server thinks you're on a current Data Version, 0000060. Let's see what @Shaun thinks here.

-Uwe-
 
   #10  

dgigauri

Verified VCDS User
Verified
Joined
May 24, 2020
Messages
8
Reaction score
0
Location
USA
VCDS Serial number
C?ID=77972
Hmm. Server thinks you're on a current Data Version, 0000060. Let's see what @Shaun thinks here.

-Uwe-
May be, because today I've updated it through PC config utility once again.
 
   #11  

Shaun

Ross-Tech Employee
Joined
Jan 29, 2014
Messages
960
Reaction score
1,547
Location
USA
Can you post a network test from the options pages in VCDS-Mobile, so I can see what your connection is like? When you say you can't use Mobile, do you mean it doesn't have asam data, or are you having other issues?
 
   #12  

dgigauri

Verified VCDS User
Verified
Joined
May 24, 2020
Messages
8
Reaction score
0
Location
USA
VCDS Serial number
C?ID=77972
So, after updating through PC Config utility, I took my interface, connected to car and started autoscan and still got "ASAM data missing ..." warning



During scan I see No ASAM data for: "........." for varoius modules


During middle of autoscan application requested to download update


Started update, but it stucked here


This is screenshots of my network profile and network test




I am back home and connected interface to PC, tried to update rod files and Config utiity requested to update data and started updating. Weird, before it was already updated.




So, I am walking in a circle and when I said I can't use mobile app, I mean that every single time it requires updating ASAM data and stucking when updating. That's all.
Note, I am using mobile phone with data connection and Wifi hotspot mode.
 
   #13  

Shaun

Ross-Tech Employee
Joined
Jan 29, 2014
Messages
960
Reaction score
1,547
Location
USA
Can you try updating from mobile over a regular infrastructure network and see if that helps? What is the history of this car, was the immo swapped or defeated? That might be causing you issues.
 
   #14  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
29,921
Reaction score
21,361
Location
USA
VCDS Serial number
HC100001
There's some really strange data on the server. Could you have a look at Advanced ID on your 01-Engine, 17-Instruments, and 25-Immbilizer and post them here? We think this might be responsible for some of the confusion.

-Uwe-
 
   #15  

dgigauri

Verified VCDS User
Verified
Joined
May 24, 2020
Messages
8
Reaction score
0
Location
USA
VCDS Serial number
C?ID=77972
@Shaun I'll try over a regular infrastructure network. Car was on accident, but immo and other electrical components won't touched, only body and mechanical repair.

@Uve I'll do it next days.

FYI, my car is Audi A4 Technik 2017. Thanks for replies.
 
   #16  

dgigauri

Verified VCDS User
Verified
Joined
May 24, 2020
Messages
8
Reaction score
0
Location
USA
VCDS Serial number
C?ID=77972
This is part of my first saved autoscan from VCDS PC Version, including only Engine and Instruments modules, I'll post code from mobile version also as requested.
Note, I have no 25-Immobilizer module at all.

Code:
Chassis Type: F4-AU49 (4M1)
Scan: 01 02 03 08 09 15 16 17 19 20 29 36 39 3C 42 44 46 47 52 5F
          6C 81 82 BB BC CA CF D6 D7

VIN: WAUFNAF41HN057489   Mileage: 16607km-10319miles

01-Engine -- Status: OK 0000
02-Auto Trans -- Status: OK 0000
03-ABS Brakes -- Status: OK 0000
08-Auto HVAC -- Status: OK 0000
09-Cent. Elect. -- Status: Malfunction 0010
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: Malfunction 0010
29-Left Light -- Status: Cannot be reached 0100
36-Seat Mem. Drvr -- Status: OK 0000
39-Right Light -- Status: OK 0000
3C-Lane Change -- Status: Malfunction 0010
42-Door Elect, Driver -- Status: Malfunction 0010
44-Steering Assist -- Status: Malfunction 0010
46-Central Conv. -- Status: Malfunction 0010
47-Sound System -- Status: OK 0000
52-Door Elect, Pass. -- Status: Malfunction 0010
5F-Information Electr. -- Status: Malfunction 0010
6C-Back-up Cam. -- Status: Malfunction 0010
81-Gear Shift -- Status: OK 0000
82-Heads Up Display -- Status: OK 0000
BB-Door Rear Drv -- Status: Malfunction 0010
BC-Door Rear Pass -- Status: Malfunction 0010
CA-Sunroof -- Status: OK 0000
CF-Lane Chge Asst 2 -- Status: OK 0000
D6-Light Ctrl Left 2 -- Status: Malfunction 0010
D7-Light Ctrl Right 2 -- Status: Malfunction 0010
-------------------------------------------------------------------------------
Address 01: Engine (J623-CYMC)       Labels:. 06K-907-425-V2.clb
   Part No SW: 8W0 906 259 J    HW: 06L 907 425 C
   Component: 2.0l R4 TFSI  H15 0002 
   Revision: --H15---   
   Coding: 0A2500322326010E34280000000000000000000000000000
   Shop #: WSC 02391 785 00200
   ASAM Dataset: EV_ECM20TFS0208W0906259J 001003
   ROD: EV_ECM20TFS0208W0906259J.rod
   VCID: 48DC72A9F37385C683-801C

No fault code found.
Readiness: 1010 0101

-------------------------------------------------------------------------------
Address 17: Instruments (J285)       Labels:* Redir Fail!-SRI2
   Part No SW: 8W5 920 790 C    HW: 8W5 920 790 C
   Component: FBenRDW       H15 0309 
   Coding: 08A651C1288800080223E9401800000000000000
   Shop #: WSC 02391 785 00200
   ASAM Dataset: EV_DashBoardAU736 001022
   ROD: EV_DashBoardAU736_AU49.rod
   VCID: 42C86081D54FAF965D-8016

No fault code found.

-------------------------------------------------------------------------------
 
   #17  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
29,921
Reaction score
21,361
Location
USA
VCDS Serial number
HC100001
Yeah, OK, the strange stuff on the server seems to be from another car; some 5K0 and 5C0 parts that don't belong in this car, and the interface is telling the server that the VIN these parts belong to is: '12345678901234567', which of course it finds confusing.

Have you tried telling the HEX-NET to start fresh with ASAM data? In Mobile:
[Options] -> [Clear ROD Files].
Then reboot the interface, do an Auto-Scan on your car, try getting the files again thereafter, preferably via your PC and VCIConfig's Update.

-Uwe-
 
   #18  

dgigauri

Verified VCDS User
Verified
Joined
May 24, 2020
Messages
8
Reaction score
0
Location
USA
VCDS Serial number
C?ID=77972
@Uwe About two or three weeks ago I connected my interface to my buddy's VW Jetta and it has too much of DTC's, I guess this generated strange logs on server.
I tried to do [Clear ROD Files] coupe month ago, will try again.
Thank you.
 
   #19  

dgigauri

Verified VCDS User
Verified
Joined
May 24, 2020
Messages
8
Reaction score
0
Location
USA
VCDS Serial number
C?ID=77972
Hi,

So, tried over regular infrastructure network, dongle and mobile phone connected over Wifi Access Point, same results. App requested ASAM data update and it stuck at 0% progress.
Did [Clear ROD Files] from App and nothing useful. Hope in future updates this issue will sorted. My mobile App still useless in infrastructure mode.
 
   #20  

Shaun

Ross-Tech Employee
Joined
Jan 29, 2014
Messages
960
Reaction score
1,547
Location
USA
Have you tried this process: [Clear ROD Files] in mobile, do Autoscan and ignore all download prompts, connect to PC and [Check for Updates] with VCIConfig, then try Autoscan again?
 
Top