Tell

They are just sitting on the respective servers without being wrapped in the web page to trigger the download off. All of them are incredibly difficult to manufacture. The high ones need the VW keys which I don't reckon anyone has. For non believers that they are all the same files from whatever source you do a hash check on them: https://www.raymond.cc/blog/7-tools-verify-file-integrity-using-md5-sha1-hashes/

Thanks for that and thanks MartiniB for the heads up.

I see another board (German Skoda community) is reporting they have found "Amundsen is leaving soon. Variants 1, 2 and 3 are already on the VW server". Using a Linux sniffing program when questioned how but didn't publish the link. Perhaps it won't be week 48 as some suggest. Have to check your drive2 page. No problems with 189.

Those are the retrofit instructions. Backend menu (SWDL) is locked down in Mib2, wasn't in Mib1. Once unlocked and the navigation FeCs can take the update then off you go (Skoda / VW mib2 you are fine, Seat not, have published a table on the Seatcupra forum which provides the boundaries, ready reckoned for mib2 high navigation FeCs). You can use this method even if it's not a retrofit if you unlock the backend menu via VCDS / Obdeleven but won't work if the navigation FeCs aren't up to it (Seat only). It locks the navigation up within 30 seconds after selecting a destination. You must reload the maps that tally with the navigation FeCs. But as said not an issue or shouldn't be for VW and Skoda mib2 high. I do the open and close the door trick every 15 minutes to keep the unit powered up using this method, so don't have the engine running during the the update, do it off the battery. After 20 minutes if you dont open the door the unit will power down and you loose the updates - have to start again unlike the front menu. 15 minutes gives you a 5 minute safety buffer. Cup of coffee, go to the loo, back out to the car to see how its going. Should be done in about 40 minutes via the back end menu.

& if a MAC OS you work in the VW PDF instruction which is imperative to remove the operating system hidden characters it enters into the download which will stop the upload to the car in it's tracks (CleanMydrive is run against the SD after copying the files over): If the map update is performed using the Apple® OS X operating system you may find that Discover Pro does not recognise the map material or displays it incorrectly. This is due to a lack of compatibility between the “7 zip” program and the OS-X operating system. In addition, the OS-X operating system has a tendency to create hidden additional files on external data media. We therefore recommend that OS X users use the “Keka” unzipping program. We also recommend using the “CleanMyDrive” program to remove any hidden files.

See what you mean, the best written one is the original VW PDF. Most issues are due to the use of MACs and not following the VW instructions on CleanMydrive or if a PC trying to be smart and not using 7zip. Going in and not presenting the full directory... need to present mib1 & mib2 as the mib2 high download (some people try to be clever and leave off the mib1 subdirectory - no). Others insist on formatting not in Fat32. Nope, the unit runs QNX so doesn't like anything other than Fat32. VW Mib2 high notes then you follow the Columbus update menu once you have the clean upload to the unit. https://webspecial.volkswagen.de/vwinfotainment/dam/jcr:c08aab64-ee73-4082-86a6-0fa82362282a/Discover Pro June_2019_EN.pdf

Google Maps isn't brilliant. The satellite images and aerial views can be old which means crowd sourcing of new roads doesn't happen / can't be validated by their team when told that their maps miss features out. A proper digital mapping company invests in uptodate aerial images which don't have cloud cover. Depends a lot of where we are talking about, as an experiment I didn't tell them about a large housing estate that had been there for ten years after two, I told them

Have a look at the top of the thread it's this on VW servers. Basically Skoda servers are rubbish. http://vw-maps-cdn.lighthouselabs.eu/vw-maps/P88_N60S5MIBH3_ROW_NT.7z

I'd read what the existing card says and Google the serial number if it's printed on the label. The hardware part number is another. Seats have 6P as the software part number for Mib2, Skodas will be... ?. But you will find it on a Google from the code on the card or the info screen. Also if you down load it will be instantly recognisable by file structure. Three tests :). Reckon from year mib2.