Skip to content

Tell

Members
  • Joined

  • Last visited

Everything posted by Tell

  1. They also changed away from the mib2 high naming convention a few years back so the xxxx/yyyy was the same but isn't anymore so with the standard and high only best to talk in the release code rather than the year one... Any how for me else I say the wrong stuff mixing the standard and high naming convention. That came about when the standard maps were not published at a six month period. Then Skoda moved onto the six month lag. Neither Skoda or Seat can you trust to publish the latest release, only VW does and this release is the one laying on their servers waiting for the web page for June to be linked to it. Joek666 you can register on the TomTom site and tell them about missing roads and mistakes. Mib2 standard maps are TomTom. Mib2 high and Mib3 are Here Maps cartography. I tell them about all local developments then you get the publishing lag of 6 months or so. Many I've told both companies are now in. If I hadn't of told them they wouldn't have been in. I don't tell Google since they are refusing to remove a local farm track that people use as a public road. It's mud and cuts into no through road where a delivery driver using that route ran over a dog. I've got that off the other mapping systems. Some home Charlie mappers enter farm tracks as roads and they get incorrectly published. The council planning maps managed by Ordance Survey are the defacto street maps with features. They are commercial maps that OS sell in digital form but since they cost cartography companies in the UK don't use them and don't validate against them. It's those maps that you can browse if you know where to look which reveal features the armchair mappers miss, like bollard in roads to stop cars. They don't tell you road speeds or direction of traffic but do reveal statuary public roads and house numbers etc. Used by the post office in their postcode house numbering system. The council annotate house numbers, post office allocate the postcode and grid reference. All part of the geo information system in the UK. They contain the land use, planning orders etc.
  2. It's the naming convention that VAG use. 2110 is the release code for the June 2023 release. Any code lower and they are older maps. VAG did introduce an ambiguity in their naming convention but if you go by the release code you won't be wrong. Skoda themselves release six months later. So the November release will be the June release of Vag. Like heated up old bread of old, fresh bread cooked six months ago.
  3. John, that's the name. What you need on each release is to note the new release on the old thread (like here) so followers get the nototication, the link to the new thread and tell John to get it pinned. Anyhow all very good. I see the mib3 ones get posted up on an Italian Leon thread. I guess there will be a similar interest in these. You don't fancy finding those similarly ?. Example the forth post down on here: https://forum-auto.caradisiac.com/topic/468096-mises-à-jours-logiciel-leon-4/page/49/ For those out of contract on mib3 connect services they can do a similar update. Now tested on Seats. Looking at the Seat and Skoda web pages of their links they were old whilst the VW was up-to-date to the last November release. Needs your program twigged for sniffing out these. Mib3 VW one for that was https://navigation-maps.volkswagen.com/vw-maps/EUR_9PR085_FCT3WS-22105_Offline_Update.tar The Italian guy has published the series to this one there, other than that you register with the VW site and check.
  4. So he did but you need the mention on the old thread for direction then Mr Mod.... terrible with names will pin it.
  5. Or June. June / November are the VW publishing dates but get found by MartiniB in advance more often than not.
  6. PS I'd format it to exFat and start again.
  7. I don't think there is a limit but use exFat. I did some timings and NTFS is slow on an SD card. Above 32gb you change to exFat on SD cards. Best not to have a love in with NTFS. That's a HD formatting method. I did come across a Skoda site recently if not VW that warned the 32gb SD card limit is broken (which we knew you can't guarantee it will fit with the November 2022 release, so it's now official you need a bigger card) telling you to buy bigger.... I didn't bookmarket thou. 64gb card that I've got ready. Also there is a limit that you won't get above on speed that I posted up on the November 2022 release thread. The upshot of that was dont buy really fancy cards the chipset in the infotainment unit probably wont work any faster. You can do it via USB and that will be NTFS in that case. Macs can floor you but I don't think you were using that. CleanMyDrive and Keka is the order of the day on them. The latest thread with the links to the map files... difficulties etc. SD v USB etc. My musing and timing might be on another release of the maps. Conversations spill across like this one. On buying SD cards you are unlikely to get speeds above the 100 MB/s due to the chip set in the unit. I posted that up somewhere. Golden rule SD 32GB fat32 SD >32GB exFat USB (big) NTFS Beware Macs need the CleanMyDrive and Keka. Follow the unzipping instructions. Attached VW gospel but doesn't cover the new >32gb SD card which it should. Tells you location etc on the copy. Discover_Pro_November_2020_EN.pdf
  8. Columbus means it's a high. The maps are held on an SSD rather than SD. If you stab away at the media button and see "Juke box" it's a high. The spare SSD space is offered up for a juke box. That's the easy check. Think you know if you had a mib3. The 2.5 was an interim unit but all the same download for the mib2 high which is the generic name between VAG brands. Different firmware, same map update. Mib2 standard is otherwise called an Amundsen in Skoda naming. That's the one with the map card.... the other thread. The high is the RR one. Uses Here Maps cartography. Amundsen uses Tom Tom cartography. The screens in that aren't executed so well on roundabout. Slower to react but does.
  9. You just buy a 32gb vag card off ebay, Skoda, VW or Seat. Deleting files is a hack and it will catch up with you as the cartography and POIs expand. However if you are tight for money / don't believe in wasting things this was the method reported on the last release: It could be that this no longer works as the growth in data has caught up with it. When VAG became aware that the all Europe map was going to out grow the 16gb mib2 card they gave ample warning by about two years. That is why they released the zones so you pick the zone you drive in. They also released the 32gb card. Reckon it's been about 5+ years since they originally gave the indication that the all Europe map would breach the 16gb card. Three or so years since it did. The original hack for people who were tight or just wanted to experiment was to delete all language files other than their own. As expected this hack became not enough. So more aggressive hacking was required. Either way it's going to catch up with you as the cartography growth is quicker than what can be hacked out as not required. Saying that the mib2 releases probably only has a couple of more years to run based on the 5 year support cycle that VAG operates on past map files. Always advice buy a 32gb Vag card if you are planning to drive across all regions of Europe or just use one of the zoned regions. For the vast majority of people that will be fine. Only if you holiday or your work takes you across the zoned regions do you need the 32gb card.
  10. Joco's situation was compounded by using a firmware update off train and customer stuff so I reckon that element is off topic here. The rest was presentation of the map file. In his case on the USB which is the custom bit. You use the Vag SD card normally and all works if presented correctly.
  11. There are a few reliable retrofitters in the country that know about these things. East Yorkshire Retrofit is one. This guy is their specialist. He's sorted out fair few Seat people who have messed up their units by meddling with the software. If local that's an option. He might say don't bother. https://northeastvagadaptions.co.uk/
  12. Generally when the maps are loaded in the first time there is a delay. Think it writes new FeCs in, how on Seats you get a collection of FeCs when you use the "workaround" for Mapcare that isn't required on Skoda and VW so there is a first time day. You do have the 20 minute power on after turning off and if the infotainment system is left on, unlocking starts the process. Probably enjoying that one.
  13. Took a little time to pick it up off the USB, presume the USB port speed. That's my conundrum of which is best on the mib2 high updates SD or USB on the other thread when the high maps pop the 32gb limit. Going wait till that release. You don't really know the port speed of the USB or SD and indeed the bus speed of these units. On the high the maps gets copied over to a built in SSD whilst the standard unit run off the SD or in your case modded firmware the USB.
  14. Pass on what happens if you have the software adjusted to work with normal SD card rather than VAG cards with the VAG CID. You'd normally get a complaint that it wasn't a map card in that case but if you are running modded software it wouldn't. May be that's the effect. Out of region maps loaded in, would show you the country boundaries but not the roads on a working VAG card. Why I said zoom back till you see the borders. Either way the card should be in Fat32 and 4096 cluster size. Mib2 standard which is what the unit is doesn't take to kindly to map cards reformatted in anything other than Fat32 and 4096. Seen issues where people format to NTFS and it doesnt work. QNX operating system so doesnt support all formats on all devices. Specifically mib2 standard maps have to be in Fat32, 4096 cluster size. Attached is the VW pdf on the preperation of the file for the card. You use 7zip if using a PC or the built in Windows 10 or 11 right click on the zip file. Placement of the folders has to be correct and a blank card to start off with. Avoid reformat on VAG cards since they can be damaged, just delete all and copy back on. Macs can / do dump garbage onto the copied folders so you use CleanMyDrive on the SD card (mentioned in the PDF) after unzipping. It's an issue with the mib2 high units which do a check before touching what is on the card. Mib2 standard less reported but could be that. Discover_Media_MIB_Gen.2_June_2020_EN.pdf
  15. That looks like an out of region map. They appear like that when the map geography doesn't tally with the gps signal. I know its marked up for Czech Republic, suggest you try out one of the other regions. The other way of checking what the map represents is to zoom back. That's the right hand knob on the infotainment unit if its got one. You turn and it will zoom in and out, other than that you pinch and squeeze the infotainment screen. Stroke left, right, up or down and you will eventually see some roads to the zone it represents. If it's a GPS issue of the units getting confused you can do a long hold on the on/off button till it resets. If for example you have the car in an underground car park not getting a signal would / could lead to that issue. More likely than not the country is missing from the file if the gps signal is good. You might want to upgrade to the Skoda 32gb card if you haven't got that and use the all Europe file. Martini Bs first one.
  16. If using SWDL if like the mib2 one is, you start a manual download on the SWDL (top button of the two) then you can force it but forcing it will show the new map then generate an error screen 30 seconds. Peak a boo and it's gone. Where you need the original release to match the FeC to revert back.
  17. The dash it's showing against navdb in the screen means nothing to update. It can't. Then the one below means it's on 30, offering 49 but can't do it since the FeC isn't allowable. You can force it but then will hang if it's like the mib2 high swdl. You play a game with the SWDL menu but then you are stuck if you haven't got the copy to put back in. Reckon it's at 30 so you need that as a fail safe.
  18. Pretty sure it will since the matching access FeC is contained in the downloads for the maps. I did do a quick Google. Basically the FeCs were less common knowledge in the early days of mib than they are now. The menu key fumble should allow it to show enabled and available codes if you find the key combination. Mr Mi Bonk people... may be its Mibwiki goes under that name is administrator of the mibsolutions database. He'd know and Chillout who has been working with mib1 high then mib2 high units. It was Mibwiki that gave me the link to pass to the Australian guy who had issues with the addfec command in the mib2 toolbox. Was Chillouts code they used for that. Embodiment of the retrofitters work bench method. The other Ozzie for mib2 had used the package but that was setup for the the EU. Just need the FeC put in the control file and addfec button pressed in the tool. I'd hit a brick wall explaining. I suspect yours will need the work bench method. But as I said before I arrived into this with mib2. Zero mib1 hands on knowledge. Reckon the user updates came with mib2 but the mib1 ones were via the SWDL command as you are showing but need the correct FeC in the unit. Seems to be a suggestion online that these FeCs carried over from mib1 to mib2 on code as well ?. The Mr FixIt page gives an explainer but only really for mib2. http://wiki.mr-fix.info/index.php?title=MIB2#MIB1_High The toolbox substitutes MIB2_FEC_Generator.sh whilst the workbench method uses WhatTheFec.exe. You might want to chase down Chillouts web pages that covered his work on mib1. The mib enthusiasts have a Telegram group where you could try for help.
  19. This is another mib1 high question being Australia you would need a RoW FeC in that unit if its like mib2 high. Now whether its a DIY task not sure. For mib2 high it is now although you might need some help even if you got a mib2 high. The DIY experts hang out on this discussion thread. It's the one I was given to pass on to the Australian with the Mib2 high who had imported a Europe unit to Australia. https://github.com/Mr-MIBonk/M.I.B._More-Incredible-Bash/discussions The "more incredible bash" people are the enthusiasts that have written the code for mib2. They were writing code before it got to mib2. So someone will be able to direct you if you speak to the right person on that software thread although that's the support thread for the mib2 high toolbox as it's called. Chillout / Jilleb who were the original authors and did most of the tinkering to package the tools up. Retrofitters take these tools and offer paid services although the tools are not for profit developed by hobbyists for hobbyists. You might find a retrofitter who is versed in this in Australia for a paid service or speak to one of those able guys. Traditionally the units were put on workbench, a usb-wifi dongle was plugged in then laptop tools were used, "whatthefec" being one. Mib2 high tool box of the "Mr-MIBonk" variety are loaded into the green menu and bypass putting the unit on a bench, the dongle and the program like "whatthefec". It could be that a tool box was never written for the mib1 high and it's a case of using the old retrofitter / hobbyist methods of the workbench. As I said to the other guy if you load maps into the unit where the navigation FeC is not of the life long one e.g.. Life long ones have a sufficiently high hex code that it allows the map to be imported. Wrong navigation FeC it won't work. You can only get back the maps if you have the map file for the unit that matches the FeC or any previous maps. So best not to toy with the unit if you haven't got the original year of release or any before.
  20. Bit more reading on the problem above. It seems at the time they used the SWDL menu that I use now. For Audi the warning would be the navigation FeC. Thus if you forced the update that way you would delete the current maps but if it's anything like mib2 high without valid navigation FeCs it would time out and blank the screen. Been there done that. You would only experiment if you had a copy of the original map then you can revert back. That's what I had to do back in 2017 when I messed my unit up since Seat's unlike Skoda arent delivered with life long FeCs. It could be that the FeCs were not deployed like this in mib1 highs. Pass on that but that's how they did in on Skodas. I have seen something similar on VW Mib1 which is why back in 2017 I experimented with the SWDL menu. It forces an update but came stuck on the navigation FeCs. Had to educated myself on that after. The engineering menu is locked down on mib2 highs you enable the developers menu via coding. On mib1 it was never locked down. Hence that thread shows them doing it that way.
  21. This one has come up before. Mib1 is before my time. Only had mib2. One of your issues with Audi is they are like Seat they don't give you life long navigation FeCs unlike VW and Skoda so they wish to sell you the map update rather giving it you free. These updates. For Audi and Seat mib2 high units you can update the life long FeC yourself if technically skilled these days or take it to a retrofitter. That software is designed for mib2 highs. Your other problem is you have a mib1 whilst it's a shared download I believe to get it into the unit it goes in via DVD. I had thought it was SD. But past conversation here where we head scratch on history, concluded it's a two layer DVD which normal DVD writers don't do. The moderator of this thread is versed in the subject. So even if the files are common between mib1 and 2 you would have technical issues getting them in, let alone the Audi navigation FeC. So basically you are a bit stuffed. If it was a mib2 high Audi unit you can embark on using the mib2 high toolkit to write a life long navigation thread then you can do the map update (seems quite common now) but afraid you fall at two hurdles. For mib2 high on Audi people arrive on this thread looking at Mr Fixit video. One being this one: Mention that for completeness. In that instance they got the navigation FeC via the software but didn't get the paid traffic reports. That's outside of the navigation FeCs for Audi. Fixed the first issue thou.
  22. It is a bit technical true. Assumes you got GPS knowledge and technical skills. Not helped when VAG removed their web site for POI import. The next best thing is to just photograph the screens on your old car and use that as a record for your new car to manually reconstruct it. That way you ensure you don't leave anything out.
  23. Just read your follow on question. Not to my knowledge it would be low level programming in the system. I used Co-pilot previously and extracted the coordinates and names out using a mapping program. I documented that on the SeatCupra site then used the Skoda trick, yes it's a Skoda trick I was told, you import them in as coordinates to a user POI. Tap the spot of the POI and saves as a destination. That works. The problem is now that VW / Skoda took down the import web based program that people were using. There is a solution, there are some macro excel sheet programs around or you use Poinspector. I use Poinspector and became the programmers unofficial technical author. https://poinspect0r.blogspot.com/?m=1 It does need some skills. It can be used to import speed cameras and your own POIs. I run with five categories. The four types of cameras off the paid speed camera database + my own favourites which is the destination file I talked about. Being a GPS enthusiast I don't trust mapping system POIs they are often out so "I walk the street" using Streetview and Google Maps to get the exact x,y decimal coordinates. That's inline with what came off the Co-pilot export. So I've added to that, some 200+ saved destinations, then keep two cars up-to-date with these. The car imports a type of dbase file with checksums for POIs. Poinspector and those excel macro sheets you come across import the x,y coordinates, generate the dbase type of file with the checksums in it. That's basically what the VW and Skoda webpages did when they were active. You can use SQL to open these files up. There was a preoccupation of doing this at one stage in the development of the RNS / Mib units over getting the beep for the speed camera at the right time. Mib2 it's computed automatically, so that history. If you got traffic sign recognition you get plenty of beeps if speeding and don't need a speed camera database.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.