30 minutes ago, Tell said:

I do it with swdl where if you had a FeC issue it would shown an N against the navdb attribute.

Well I do have an F ...

Fat 32. I'd enable developers menu as I said above. This has to be done via vcds or obdeleven Pro then you hold the menu key, keep holding then a second menu with swdl will appear. You tap that with the SD card in. Eventually by tapping around with the SWDL menu you will see the entities against each of the navigation attributes they should all show Y which means yes, N no, can't be done. If the navigation FeC is no good it will show an N on navdb. If it can't read the card swdl won't go on to try to import the file. Swdl is the backend menu which covers all backend files that can be imported via the front end but shows you what is going on.

From the screen above, sure it's not a mib1 high ?. You shouldn't get ERR on the other attributes. A few issues gives you an N but not ERR on the other stuff.

If it is a mib1 high you wouldn't have needed vcds coding to unlock the developers menu. That got locked down in mib2. Another litmus test.

Edited yesterday at 16:501 day by Tell

12 hours ago, Tell said:

From the screen above, sure it's not a mib1 high ?. You shouldn't get ERR on the other attributes. A few issues gives you an N but not ERR on the other stuff.

If it is a mib1 high you wouldn't have needed vcds coding to unlock the developers menu. That got locked down in mib2. Another litmus test.

Yes quite sure is a MIB 2 H: no dial cursors but only touch buttons

I never played around with vcds or obdeleven Pro because the maps updates so far just went smooth. Download > copy to SD > Insert and apply the upgrade

Only from this one I'm experiencing this kind of troubles

Well I put your software train as per the picture into mib helper and it says it is indeed a mib2 high. Went on a search of mib2 high and 450 navigation and it gives you the second post on this thread:

https://www.briskoda.net/forums/topic/537850-columbus-map-update-2026-2027-mib2-high/#findComment-5996496

Which says it doesn't work with Seat or VW without a change in navigation FeC. This was the guy that found the file so they know what they are talking about. To get it working on a mib2 high you need to add the Skoda or Audi navigation FeC (either will do) to the end of the addFeC file that it uses.

You first install the mib2 high Mr Bonk toolkit in the green menu of an SD card. You do a back up using the commands. Then you have to look on the SD card for the file it is using with the FeCs on it. Then you add the Skoda life long navigation FeC and do the addFeC command. Reboot the unit. Check installed FeCs and you should see in addition the FeC you added. Running SWDL that F will appear as T and you are good to go. Some people had issues with deleting the back up and generated another one in the github project. You only back up once. That is what one guy was stumbling on so the addFeC menu didn't work. Difficult on posts to work out what people are actually saying but I reckon that was the issue. They tried to backup twice and found they couldn't. Other people have had success first time. The toolbox you only use once then forget about it but I did get help from the people familiar with it at the time since the module had not been written for my release, so they wrote it for me. The documentation will tell you whether your firmware is covered. Another Seat poster update the firmware to All in One (AIO) because theirs was to old, then used the toolbox to do the FeC addition. Now I'm assuming that the VW firmware is like the Seat one and can handle many navigation FeCs. Thus it tries VW navigation FeC and failing that the Skoda one you added. Mine has been working happily like this since February and prior that 5 years before why I was already setup.

The link to the toolkit is this:

https://github.com/Mr-MIBonk/M.I.B._More-Incredible-Bash

Additional reading:

https://www.seatcupra.net/forums/threads/updating-the-inbuilt-mib2-satnav-mib2-tricks-and-mib1.388586/page-163#post-5097617

Read on beyond and you will see people using the toolbox with success.

The other way if you dont feel comfortable with using the Toolbox is to find a reliable retrofitter to do it for you.

Edited 13 hours ago13 hr by Tell
link

1 hour ago, Tell said:

Read on beyond and you will see people using the toolbox with success.

The other way if you dont feel comfortable with using the Toolbox is to find a reliable retrofitter to do it for you.

Many thanks!

I prefer do it by myself so I've an opportunity to learn.

First I need to get the VCDS, set up a laptop with Win11 and read thorough the instructions, then I'll try.

This means I'll be absent for a while from posting.

Just one question:

in this video

https://www.youtube.com/user/SEATCupranet

that shows how to install MQB toolbox I saw in the menu there's a Testmode line that I don't have in my unit.

Do you perhaps know how to enable it?

Edited 12 hours ago12 hr by k-s

1 minute ago, k-s said:

Many thanks!

I prefer do it by myself so I've an opportunity to learn.

First I need to get the VCDS, set up a laptop with Win11 and read thorough the instructions, them I'll try.

This means I'll be absent for a while from posting.

Just one question:

in this video that shows how to install MQB toolbox I saw in the menu therre is a Testmode line that I don't have in my unit.

Do you perhaps know how to enable it?

I don't think you need VCDS or Obdeleven Pro for the toolbox. There is a code clearing algorithm in it which does clear the marker for a firmware change although the unit will run happily with that "error" just a marker that the firmware is changed. So I dont bother clearing that now. If the toolbox does say clear errors before installing it ?. It would be a good idea.

I keep out of the esoteric back end screen if I can help it. The green menu where the toolbox gets installed does have some engineering screens so does the developers menu. I have turned off the sat groups in the past to see whether its using the Chinese satellites. Mine doesn't. Russian and US. New mib2 standard do. Sees over 20 mine sees about 11 max. Reasonable number but wondered what the difference was. 2016 mib2 high.

Pass on what test mode is but that's in the developers menu, not the green one where the toolbox goes. The navigation in the green menu up and down does slightly vary by whether its the older mib2 high front screen or newer. There are videos of the use of the green menu and its just slightly different key presses dependent on the layout. Put one person off.

Example video on installing the toolbox but you should read the documentation before:

https://m.youtube.com/watch?v=oQaE-uaMRZY

Navigation up and down the guy uses the right hand button, turning... that can vary as I recall on the front screen fitted that.

Its back up, then patch and addFeCs. Then reboot, but you take a screen shot before and after of the FeCs installed. Then search on the SD card for the file it up loaded and then add that Skoda navigation FeC to the list. Then addFeCs again, you have to read the documentation to see whether you need to delete the FeCs before the second addFeCs command. Been 5 years since I did it. Reboot, photograph and check the new one is added. Then all should be good for map update.... assuming the developers wrote the module for your firmware release. That will be listed in the documentation and the software installed will indicate that it hasn't if that's the case.

Edited 11 hours ago11 hr by Tell