Tell
Members
-
Joined
-
Last visited
Everything posted by Tell
-
Suppose to use Keka and CleanMyDrive. Mac's produce garbage characters at the of the data rows. CleanMydrive run on the SD card after getting the files onto it wipes that out. However there were / are issues with the compression used on the latest maps (195). See MartiniB's thread. Possible that the Mac software can handle the unzipping without throwing up errors but is highly likely you will need to give the resulted output a good buffing with CleanMydrive. Keka and CleanMyDrive are the recommended VW Mac tools. If you still have an issue unzipping use the VW download. That's zipped without the variable compression that causes issues with Skodas 195 release. Refer you to MartiniB's thread. Footnote. Why the Mac random characters cause an issue is that the mib2 high unit performs an sla1 signature check before importing the map so stops in its track if one byte is out. I know this since I spent a long time trying to edit the import file, it's cryptographically signed. Mac's don't get on well with these files.
-
Possibly why with mib3 they made it so "easy" it's useless 😉. Mib2 does contain a proper traditional navigation system which you can augment into a proper navigation system with bells and whistles.., whilst mib3 ain't. I'm waiting for mib5 myself 2030 🤣. I'm hoping by then VAG will have returned to its roots or I'll by a Chinese MG from the garage up the road. Poinspector came into its own again after VW pulled the POI import website. They have a habit of doing that, they did it with RNS the unit before mib1. They dont support the customer base. There is / was a Skoda alternative but that was ropey. There are some Excel sheet macro people about that offer the same functionality of Poinspector but don't give you pretty screens. The db3 database it writes for import is well documented.
-
Mine takes it in either slot I reckon... I pull both cards out then put the map card SD in so it doesnt get confused. I'd give you the Poinspector site where I'm Radas the programmers official technical author so it seems. Does take some effort setting it up then you use Pocket GPS World POIs. Problem with freebies and rip off you don't know their pedigree and may well get out of date. https://poinspect0r.blogspot.com/?m=1 The advantage is you can use the old Skoda trick of importing a destination as a POI. Tap on it and then save as a destination. That way your sat nav looks like a traditional one with destinations shown up on the screen. What would we do without practical Skoda drivers 😉. I got 350 destinations imported that way. Useful when revisiting places. Some GPS knowledge of x,y coordinates useful for that.
-
Read down from this post. Known issue with 7zip on the Skoda site. You can use the built in unzipped in Windows Filemanager or use the VW download with 7zip. Skoda changed their compression software so it throws up errors on 7zip since they use variable levels of compression. The built in Windows tool is more accepting. MartiniB uses another tool as he says. It then comes up latter in the thread with naysayers checked it again and posted up the analysis. Probably best to still to the VW download that MartiniB posted at the top of the thread with 7zip or use the Filemanager build in one. See also this link. Two images. If you use the Skoda file, open as that example that uses the built in Windows unzipped, right click. Second image if VW file, open with 7zip. Zip files, sit on it. Right click, Click Windows Explorer... that's the built in one which comes free with Windows, it does the job. Drag and drop to a directory you created for it. Then copy all of that onto a blank SD card, fat32, 32gb. No issues. Posted that up before when people got confused. Basically Skoda are zipping the files in a way that 7zip throws up errors but we knew that at the start of the thread. So we don't use 7zip on them but use the Windows built in method. No issues or in MartiniB's case his favourite unzipping software 😉.
-
Was it in Fat32 on a 32gb SD card and not using a mac. Following the Vag guidance I attached further up. Stick to the VW download, unzip using 7zip, you shouldnt have problems. It uses the signature on the files. If you open them about resave it will fail. Use a mac but not use CleanMydrive on the SD card it will fail. Both lead to the signature failing so it won't see the update.
-
There are a bunch of ones called Mib Toolxxxx it's the mib tool one you want written by Chillout not any xxxx ones, he does write another one which I don't think you want. You find that on a Google, the one he wrote for this was for the Mib2 Collective as I call them or they used his code and adapted it. The collective are not for profit individuals who hate retrofitters making money out of quite simple programming as they see it. They write in Bash. I will look later to see which firmware releases of Audi are listed within it. The tool makes a backup of a key module of the firmware then replaces it with its own one. If it hasn't got that module it invites you to send the backup to the "collective" (as I call them). They then study what has been sent and give you a module back. It realises on helpful people with Bash skills. I'm not sure the helpful person I communicate with covers Audis but he sorted out my Seat and someone else's for free. The latter one was in a pickle where a retrofitter had made a pigs ears of what they had done. They then remotely sorted it out giving them a new module to clear out the rubbish left by the retrofitter. I got into using the tool when Vag on one release dropped Seat from it, so you populated the car with the Skoda navigation FeC as well as the Seat one. They are happy to run with other brands FeCs. I'd spotted a couple of posts bragging about they had that release on their Seat car, one was Chillout the programmer himself who said he wasn't bragging... and a Spanish board Seat mod who's retrofitter had populated the car with every lifetime navigation FeC from every VAG brand. Then it became clear. During lock down couldn't drive to a retrofitter to get it done so reverted to Mib Tool and DIY. Some retrofitters are rubbish eventually found a decent one but reverted to DIY. Retrofitters method put the unit on a bench and use a program called whatthefec to change the FeC. Mib Tool delivers the retrofitters methods as DIY in the car using the green screen. It uses a back door that was found to add FeCs into the unit. There are retrofitters in Australia I've seen it being discussed, depends how good the one is if you go that route. The first one I used just extended the navigation FeC by a year but pretended it was a lifetime FeC as Skoda and VW. Had to get them to "correct" this a year later. Photographing the FeC screen before and after and his Polish mumbling about a FeC. I subsequently decoded the Seat ones from the before and after pictures, so it became apparent how it worked. Posted up a table so that people with Seats could understand when their Mapcare was up. My message was if using a retrofitter make sure they don't short change you for repeat business. The collective know all the FeCs now so put them in their not for profit tool. The lifelong FeC is just a hex code at the end 30+ years away. mib2 map releases will probably stop in 2025 in any case based on VAG mib1 published time table. They give 5 years free map updates after the model is superseded so puts it at 2025 for mib2, as mib3 was 2020. There is a German DEB board, Digital Elite Board search under Audi and Mib Tool all in German but worth a read. If it says GEM as well you are in the correct area (Green menu). That's where the German speaking collective hang out. The Seat link on the Google covers the Seat English speaking one. A pan European project 😉. Probably like Eurovision Australia would be allowed. https://www.google.com/search?q=digital-eliteboard mib tool%3Aaudi&ie=utf-8&oe=utf-8&client=firefox-b-m
-
Ok see other thread where if it's a mib2 high and you want to trick it.
-
Post crossed answer your other question on the mib2 standard thread. Having read that and what you have said you are in Australia. If it's an original Australian car not an import then you would use the RoW file for mib2 high. That is this thread, but as I said on the other thread Mapcare will limit you on an Audi. Traditionally you got a retrofitter to hack the navigation FeC, on vehicles which use Mapcare, Audi and Seat still do, VW and Skoda don't. A more recent approach is Mib Tool which had been developed by hobbyists in Europe which cuts out the retrofitter since its done in the car. Only works with specific firmware but the hobbyists adapt it if not supported. You need to be on a board with the hobbyists to help for that. Not sure if they post around here. Basically you need to be quite clear about whether you have a mib2 standard with map card, or mib2 high with the maps held on the SSD in the unit. If it's a mib2 high and Audi Australia don't want to sell you at map update or you don't want to buy it then a retrofitter is required to adjust up the navigation FeCs to "lifetime" then the RoW import will work or you go down the Mib Tool route. I know where the Seat enthusiasts hang out for this but not the Audi ones. Think you'd need an enthusiast since the fragment of code for your Australian firmware release would not exist unless you got Ozzie enthusiasts (files in the tool reveal what it works with). Unless you got a European import car that an expat imported then head scratching on getting the map in if mib2 high. Mib2 standard can be done. Covered in the other thread albeit mib2 standard Mapcare workaround.
-
I noticed you have posted on both of the threads. Does your vehicle run with a map card in it, this thread or with the maps held internally in the unit. That unit is otherwise called a mib2 high. Mib2 standard for this thread. I've answered you mib2 high question on the other thread. As far as Audi is concerned a fly in the ointment is that Audi still uses Mapcare which limits your ability to free updates. VW and Skoda scrapped it. There are technical ways around it for mib2 high and mib2 standard a trick. But before getting into that which unit is in the car. One that uses a map card or one that runs the maps within the unit with no map card in and the maps show.
-
You use all files, school boy mistake to use too much intelligence. It dives into both of those directories. Just historic internal naming. The VW ìnstruction are attached which are good for Skoda and Seat. Obviously they are for the November 2020 release so the file names different and screen layout slightly different. Skoda did change its zipping method on the latest release. Conversation in the thread. You might just as well use the VW release where 7zip will work. Note Mac OS instructions if you are using a Mac. Stringent validation is used in the unit as the files are read in. Mac's leave additional characters in the files that will stop the import dead in its tracks. CleanMydrive Mac utility run on the SD removes that. Thats covered in the VW instructions. Discover_Pro_November_2020_EN.pdf
-
Answer your question... The next release... this thread which is out. 192 was the June 2020 release, 195 is the November 2020, the latest. You go the one before. Still it's a good learning curve.
-
You can move to 195 now 😄. Those cards are sold for people who feel unable to copy cards. On the plus side you do know now what it's suppose to look like on the card.
-
Good money if you can get it and are a retrofitter 🤣. Retrofitters scrapping around for money. If it was a Seat they would be adjusting your navigation FeCs but that's not the case for VW and Skoda Mib2 high. There are DIY solutions for that in any case. Get yourself a 32gb class 10 SD card from Amazon Prime for £7-50 or something like that. If it's got utilities on them, delete them. It will be in Fat32 already. Don't reformat it. Stick your fingers in your ears to people that say you can use a MicroSD card with an adaptor, you are advised not too, they are cheapskates. Don't bother with a USB. Certainly don't format it to NTFS. Unzip to the HD of your PC. Then copy that to the SD card. If Mac follow the Mac instructions, put the SD card in. Attached is the official VW guidance. You need to use the latest file as per MartiniB top post. I'd use the VW server link and 7zip if you are using a PC. The guidance covers Mac and you do need to use the special guidance on that if you do it that way. Discover_Pro_November_2020_EN.pdf
-
As MartiniB above is saying you Dont have a problem. The guy here updates your maps on your model: https://forum.vwpassat.nl/index.php?/topic/45008-discover-pro-kaartupdate-2019/&do=findComment&comment=863123 Not a problem. I'd pay attention to how you unzip it, built in Windows unzipped as I went into above in the thread if you use the Skoda download, 7 zip if you use the VW download. It's just zipped differently, same file. If using a Mac use CleanMydrive on the SD card. Takes out the dross that Mac systems put on and you would use the VW download link and Unarchiver... whatever I normally say at this point.
-
I think to be sure the original poster needs to get the part number and Google as above. You might right thou. I'd do it on the part number thou.
-
The screen you need in the car is the one with the Part number on it. That's generally on setting, not within the navigation menu. You put the units part number into Google and look at the images. Read what is printed on the unit sticker. It's going to tell you whether mib 1 high or mib 2 high. Tap the Part number in of yours into a Google to resolve. Then you really need a VW pdf of the time of how to do it 😉. It's going to be knocking about on the net somewhere or in the original manual. I always thought it was DIY along the lines of mib2 pro given they share the same upload file. The RNS units before mib1 high did use DVD's for the upload. Those arent updated now and there was a period when someone was manipulating those files obtained from map updates into shareware DVDs. The name was Kong associated with that one. I came into this with mib2 high... No past history of updates on mib1 high. Example of mib1 high with over lap maps to mib2 era:
-
I'd put it at the top end ~ 40 mins but newer units have faster processors which may be why you get the quicker values quoted.
-
From what you say it is a European car imported in with a European map that worked. Check it still works with one of the smaller zones that fit the 16gb card. Having checked the card is fine then do the steps 1-7, you might not need to go beyond step 7. The method has been used by quite a few of your country folk on import cars... Well two I know 😂.
-
It has to be Fat32. Reports now of cards not taking too kindly to being reformatted... they stop working. 4096 has to be the cluster size. I'm not too sure whether the recent mess ups reported on Seat board is due to the default on Windows 11 format that ismy 4096. NTFS is known not to work on mid2 standards. It is Row 1. A map pack for another area won't work unless you mod it. Is the car an original one for the region or imported ?. If it's imported with a European card there are tricks: Got a car with a working installed map but outside of the region - need to get local map working ? (Mib2 Standard only) Example taking a car to Morocco. Exporting a US VW to France. Exporting a European car to Palestine. Emigrated with your mib2 car from Europe to Australia. The T6forum perfected some of this but joint working across the boards got it going for more modern units. Guy in Palestine sorted that out for latest VWs which were the problem. Arona standard Mib2 is happy with the original T6forum method with the workaround above. Advanced method with example with Israel as the map (text taken from a VW user): https://www.t6forum.com/threads/how...-in-non-eu-countries-e-g-morocco.10331/page-2 1. Download the required Region Map Update. (For example, "Non-European countries - Package 3") 2. Use a VW SD card, as VW SD Cards have a special [CID] card identification code, and normal SD cards cannot be used for browsing data. 3. Erase everything on the card, (Before making a backup of what's on it). 4. Copy and paste the maps folder after unzipping it (do it in Windows because the mac fails something when unzipping, or use a recommended program "see volkswagen page"). 5. Use a file explorer to open the 'maps' folder on the SD card. Depending on the map package you have, you will see several numbered folders. 6. Change the name of the corresponding folder of the Region number found inside the 'maps' folder on the SD card to '00'. For example; To use the MRM3 Region SD card to navigate in Morocco, etc., rename the folder '27' to '00'. 7. Copy the OVERALL.NDS file from the original (European) maps folder, which is in the “maps / EEC / EEC_WLD / OVERALL.NDS" path, and subscribe it to the card in the same path. 8. Copy the file OVERALL.NDS from the original maps folder (European), which is in the path “maps / 00 / nds / PRODUCT / E1 / OVERALL.NDS”, and subscribe it to the card in the path “maps / 00 / nds / PRODUCT / XX / OVERALL.NDS ”where XX is the code of the desired region (ME1 in the case of Morocco). 9. Copy the PRODUCT.NDS file from the original (European) maps folder, which is in the "maps / EEC / PRODUCT.NDS" path, and subscribe it to the card in the same path. 10. In the car, restart the Infotainment System by keeping the on / off button pressed for a few seconds, then insert the card and you're done. Basically 7. is the Exciter workaround 8 and 9 are the two additional steps that some VAG heads required to make it work on out of zone maps. Was fine for the Arona, step 1- 7 was sufficient and only presenting the target country in 00 directory not editing and leaving the rest as is. Suspect the wifi standard heads of Seat would need steps 8 and 9. Had maps of Morocco and Israel on a European Arona unit. The method with steps 8 and 9 was used on the VW car brought to France from North America and the car that was exported to Palestine from Europe. For the US car the country code is 01 so 00 content is renamed to 01. ---- Those instructions can also be used on UK cars exported to OZ, USA ones to Europe. ---- if you have messed the card up with a dubious reformat you'll have to obtain another original Vag card from an eseller. Frankly bad guidance is given on reformatting these cards. You should never. Just delete what is on them.
-
Probably a production problem, they may have slightly moved the roads in that area so it put you off road or left out the element that does the navigation. Probably the map allignment. Mib1 one had tuning parameters to get the car on the road. Mib2 high teaches itself via the roads turns after you have done something significant to the unit. Not sure what mib2 standard has. Think you can hope the issue will be sorted in six months. Kent not exotic 😉.
-
Have you tried the alternative downloads in post 1 from MartiniB ? eg. a different zone. I'm wonder whether there is a specific problem for the geographical area you are looking at. The maps work fine in the UK. The other test is you can do in the advanced menu is to put the navigation system into demo mode. You then place the car somewhere else by street, town etc then navigate to a destination. Try it in the UK say if your download covers that. If the maps have been incorrectly prepared wherever you live, it would show it working in the demo area but not where you are. If that's true keep your fingers crossed that, that will get fixed in the next release. In some parts of the world the maps are not fully digitised so you might get an instance of the road showing but the navigation not working since that's a separate set of data it uses. You see that sometimes in car parks where the road is drawn but it won't navigate. In East Europe, Middle East etc you can expect to see that effect. Obviously an error if they had it previously but not now.
-
OK we applied the scientific method. Replicated your links and checked the SLA1 signatures they are all identical so the same file :). On the Skoda zip file you use: On the VW 7zip, 7zip: & look at the metainfo2.txt in the route and in Mib1 and Mib2. Identical in each which means they are the same. The other way of comparing is to run the 7zip CRC SHA SLA1 checksum on each of the unzipped directories within. These all tally: Folders: 832 Files: 1574 Size: 31256300045 bytes (29 GiB) SHA1 checksum for data: F18EF2285597436B90FA3F7AE2EE1A545D1ECAF2 SHA1 checksum for data and names: EB8A20606DA52783848E7E1F8577AA7C461E95DF So the two downloads between Skoda and VW are identical if unzipped correctly. Don't know where you got your results from... suspect you got a bit of dross in one of your files perhaps during download or unzipping. MartininB gets the prize again. 🤩
-
I used Windows 11 in built no issues. You might have had a data error on your comparison. The old test is if it doesn't unzip don't use since its corrupted. Hence the October 22-30 conversations. If you read the thread people succeeded with three different unzip programs without error. That Skoda one is being installed fine on Seats I know that using the inbuilt unzip of Windows and MartiniB's links.... but either way VW and Seat servers run better so best to take it from their (links above). In October there wasn't a choice so we used the Skoda one. MartiniB makes reference to the Drive2 rebate at that time as well. I never use the Skoda VIN method, I've got two Skoda VINs one for each 🤣. Given Skoda are always late to the party you look for the direct file links and MartiniB's excellent posts. On your comparison the SLA1 signatures would have to be different for both to work in the car else one would get rejected. It's possible that VAG made twigs on the final production, but if you said the SLA1 signature was the same then one would be corrupted. The signature isn't the one on the top level metatxt2 file but in the ones it dives in... that which protects the payload to the unit in that area from data corruption / user meddling, the bottom line in those. If they are all the same between units then the data in the files can't be different. Different data, different SLA1 signatures for the files to load up without rejection if they are valid alternative uploads to the mib2 high. The Skoda ones on MartiniB's link least in October worked fine....but best not to use 7zip now. That was the conclusion in October 2021 and still stands.
-
My post 31st October shows the File Manager right click into Windows Explorer the built in free method that works with the Skoda files. MartiniB links he posts up for Skoda files are identical to the ones on the Skoda board with VIN when they go live. Once unzipped all serial VAG files are the same across brand. 😉
-
It's not that you shouldnt use it, read above, it's they changed the compression between the files in it so it throws up 7zip errors. MartiniB used his method he recommends above (Total Commander on it I seem to recall), I used the built in File Manager unzipper of Windows. See above also... or just use the non Skoda alternatives for the 195 release. Think Skoda now assumes you use the built in File Manager unzipper, right click on the zip file within File Manager, pick the unzip, drag and drop to a new directory on HD, copy out. Bob is your Uncle. All on the thread above, 22nd / 23rd October.
