hi i have a skoda superb 2011 model will this work for my Columbus?  it crashed on me so i have updated it but lost all maps. tried to add one from a disk that someone sent a link too but would not read it. it has a sd card reader in but was told it wouldnt read from card. any help would be good 

6 minutes ago, Oakeydoke said:

hi i have a skoda superb 2011 model will this work for my Columbus?  it crashed on me so i have updated it but lost all maps. tried to add one from a disk that someone sent a link too but would not read it. it has a sd card reader in but was told it wouldnt read from card. any help would be good 

That's an interesting one. The update is multi purpose for mib1 / mib2 high why the directories have the two inside the download since it dances between the two.  The question is whether mib1 high users are still using MartiniB's links. I only came into mib on a mib2 high.

 

From what you said sounds like the ssd or whatever they put in mib1 high's crashed.  You might be tripping over getting the card formatted and copied correctly, the Mac issue or some other finer detail.

23 minutes ago, Oakeydoke said:

hi i have a skoda superb 2011 model will this work for my Columbus?  it crashed on me so i have updated it but lost all maps. tried to add one from a disk that someone sent a link too but would not read it. it has a sd card reader in but was told it wouldnt read from card. any help would be good 

 

10 minutes ago, Tell said:

That's an interesting one. The update is multi purpose for mib1 / mib2 high why the directories have the two inside the download since it dances between the two.  The question is whether mib1 high users are still using MartiniB's links. I only came into mib on a mib2 high.

From what you said sounds like the ssd or whatever they put in mib1 high's crashed.  You might be tripping over getting the card formatted and copied correctly, the Mac issue or some other finer detail.

Wouldn't this unit be one that requires a dual layer DVD disk to load the maps?

9 minutes ago, Tell said:

That's an interesting one. The update is multi purpose for mib1 / mib2 high why the directories have the two inside the download since it dances between the two.  The question is whether mib1 high users are still using MartiniB's links. I only came into mib on a mib2 high.

 

From what you said sounds like the ssd or whatever they put in mib1 high's crashed.  You might be tripping over getting the card formatted and copied correctly, the Mac issue or some other finer detail.

wow you lost me on thats an interesting one lol sorry i have no idea what you mean.

so my Columbus head unit went mad and went into german im from the uk so no idea what happened. thats ment to mean its crashed so i had to do a software update what worked but no maps. i tried to put the maps on a duel layer disk but the head unit didnt like it. might have been a bad link. the cars a bit old so didnt want to pay for a new map update, was hoping to get a download to upload to the car. seems tight i know 

 

6 minutes ago, john999boy said:

 

Wouldn't this unit be one that requires a dual layer DVD disk to load the maps?

Or is that the one before, RNS ?. I only graduated to mib2 😂.

 

Definitely the file covers mib1 but how it's introduced I pass. We need someone with mib1 high. 2011 would put it at mib1 high in the life cycle of mib. An old mib1 manual should say.

 

Dual layer... fun.

Edited 29 May, 20223 yr by Tell
thinking of dual layer...

3 minutes ago, john999boy said:

 

Wouldn't this unit be one that requires a dual layer DVD disk to load the maps?

yes i was told that i need a dual layer disk. but when i copied it it didnt work. then someone said i had to unzip it lol no idea how to do that so i friend helped out but sadly didn't work 

Dual layer disks are notorious for being 'difficult' to work with.

In saying that, a person would only need one if they were copying a file which had been downloaded from the internet - i.e. an unofficial source of the data. 😜

 

It also depends upon how the file has been downloaded. Usually they came as *.ISO files which can be written directly (with a suitable writing program) without unzipping.

 

 

7 minutes ago, john999boy said:

Dual layer disks are notorious for being 'difficult' to work with.

In saying that, a person would only need one if they were copying a file which had been downloaded from the internet - i.e. an unofficial source of the data. 😜

 

It also depends upon how the file has been downloaded. Usually they came as *.ISO files which can be written directly (with a suitable writing program) without unzipping.

 

 

hmm it still on the other lap top but will check. also i raed that to find the mib type you need the delivery part number or can find it from their. but could be wrong as i dont know any of this lol 

well my number is 3T0035680K   

Does that help at all. 

or show i just forget it and keep using my phone as a sat nav

The Columbus of your era was the VW RNS510 equivalent.

Maybe try a post in the Superb 2 section?

Edited 29 May, 20223 yr by john999boy

36 minutes ago, john999boy said:

Dual layer disks are notorious for being 'difficult' to work with.

In saying that, a person would only need one if they were copying a file which had been downloaded from the internet - i.e. an unofficial source of the data. 😜

 

It also depends upon how the file has been downloaded. Usually they came as *.ISO files which can be written directly (with a suitable writing program) without unzipping.

 

 

You need a dual layer writer as I recall. My old Panasonic DVD TV recorder did that. I don't reckon your average DVD writer does do dual, just single layer.

12 minutes ago, Tell said:

You need a dual layer writer as I recall. My old Panasonic DVD TV recorder did that. I don't reckon your average DVD writer does do dual, just single layer.

I haven't written anything for years but it wasn't the ability to write that was the problem, it was usually the need to select a slow speed and have quality media that was the overriding factor.

 

Just going OT, can you remember also being able to 'LightScribe' a CD/DVD label directly to the disk!

Probably even rarer than dual layer writers?

32 minutes ago, john999boy said:

I haven't written anything for years but it wasn't the ability to write that was the problem, it was usually the need to select a slow speed and have quality media that was the overriding factor.

 

Just going OT, can you remember also being able to 'LightScribe' a CD/DVD label directly to the disk!

Probably even rarer than dual layer writers?

No I don't. The dual layer meant the laser had to hit two surfaces to pack more on.

 

Still sell them

 

https://www.google.com/search?q=dvd panasonic dual layer writer&ie=utf-8&oe=utf-8&client=firefox-b-m

 

I once bought industrial DVDs with no printed label on them. Fine if your nail didn't scratch the surface which should have had the label on, then they fell apart.

 

Will be onto old 78s next 😂.

 

Btw I thought I'd identified the guy that was creating RNS maps from material, Kong ?, on a the Seat board but it wasn't him.

 

Here's a link to chew on

 

https://getnavigationdvd.com/rns510-navigation-map-dvd/

 

I was trying to get the famous Chillout interested in turning mib3 maps into mib2 high for the day when mib2 high maps won't be released. He said that would be a cool project. Let's hope the mib enthuasts take it up since some of us don't want to change our cars till 2030. Life in them yet till EV. Reckon there will be 5 years without map updates. 

Edited 29 May, 20223 yr by Tell

I have patched my unit with the Fec 023000ee, but tried a few different SD cards and kept getting the serious saying no valid maps data found on the medium. 

 

Tried FAT32 EXFat on a 32G SD, NTFS on a 128G MicroSD in an adaptor. 

 

I am using ROW maps for Austraila. 

A4 2016 Model. 

Anyone can help out please?

1 hour ago, TrevW said:

I have patched my unit with the Fec 023000ee, but tried a few different SD cards and kept getting the serious saying no valid maps data found on the medium. 

 

Tried FAT32 EXFat on a 32G SD, NTFS on a 128G MicroSD in an adaptor. 

 

I am using ROW maps for Austraila. 

A4 2016 Model. 

Anyone can help out please?

Not suppose to use microSD cards. Stick to 32gb fat32 class 10 cards or above. Don't use a Mac but if you do run CleanMyDrive on the SD card before you use it. Suspect though it's the firmware. The AIO variant will be the one you want if it's coming off the mibsolution web site. Pass on what needs to be done if anything for the Australia firmware variant. The AIO variant is the ones put together which do everything... The latest ones update Gracenotes as well least for Seat. Hobbyist activity. Need to find an expert firmware hobbyist if it's not a technical issue of just kicking the update off due to formatting, file preparation or using a Mac without using CleanMyDrive on the unzipped image in an SD card. There have been a few Audi folk popping up on these threads with the FeC edit.

 

There are two approaches either replace the firmware with AIO or the in car FeC edit updating the module. For that one you still need working firmware and the mib toolkit needs to recognise the firmware you have. There are folk out there least in Europe who can write the module to work with the firmware release or some releases. That's the alternative way. Whether yours is too early for that I pass. That was my Seat solution which someone kindly did for me on 2018 firmware. But as indicated this approach has been overtaken by the AIO firmware that hobbyists have developed but here you need to observe what needs to be done for ROW. Pass on that. Mibsolution web site you can run your finger down looking for variants for ROW firmware. Needs some Googling. Mib Wiki is the administrator of the hobbyist group if you track him down on websites and the band of hobbyists that chat on closed networks. There will be Audi ones about. Just a question of finding them. It's all the same software though packaged up for each VAG brand. That is how people accidentally get Skoda software running on Seats and it's pointed out that's Skoda firmware not Seat 😂. You see it. 

 

If it's not the firmware and it's just map presentation see the attached. That's the VW documentation. The bible on doing it.

Discover_Media_MIB_Gen.2_June_2020_EN.pdf

Edited 27 October, 20222 yr by Tell
add pdf

I am using Windows. So I think I might have to update my firmware which sounds like a lot involved...

Normally if it's showing the lifelong FeC which presume ending in EE is then the FeC went in right. 7zip is the approved unzipping program till Skoda messed it it last year but I thought that had been corrected.  If it throws up errors it hasn't been. I use the built in Filemanger one now, right click and file whatever it ever is in the examples I gave when it came up before. Build in unzipping program of Windows 10 / 11. Drag and drop to a directory on the PC. Drag and drop then to an SD card, in the root.

I used usb formatted to ntfs

It can be done that way but the recommended way is the VW pdf. Most fail on not getting it in the directory structure and the Mac issue. In the case above may be the FeC written although if you can see it on the FeC screen then it will have been written. Normally a long menu press will bring you up to a screen that allows you to see the FeCs - a visual check. I would say if the FeC can be seen then it's been read in ok.

 

VW and Skoda are blessed with life long navigation FeCs at delivery in mib2 form. Seat and Audi in mib2 form come with the map update locked down at delivery or once purchased Mapcare / sampler period is out of the period. The life long FeC push the limit so updates can be made. For a period some Cupras were sold with life long FeCs. You can actually interchange the Seat with the Skoda FeCs... some retrofitters load all of the brands navigation long life FeCs in for good measure, handy when they dropped the Seat one, in one release so we know if they ever do that again, what to do. I keep the Skoda one in my unit just in case they do it again 🙄. Shows the Seat navigation FeC plus the Skoda one. On the same basis an Audi with would work with a Skoda lifelong FeC. 

 

It could be say Audi was dropped from the RoW if so you use the Skoda one. It could be that. You would have to check that Audi were still getting ROW. It is easy enough to load up the Skoda one by whatever method was used. When it happened to Seat a few years back it wouldn't see the map update.  

 

Looking at my Seat notes I see I noted the Skoda one as a European life long FeC Europe 08300008 that would suggest the ROW is different.... so are we sure we have the ROW Audi one ?. 

 

Reckon not... from the internet

 

0ABCCCDD

 

Code:

A Brand 2 = Audi, 3 = Bentley, 6 = Porsche, 7 = Sitz, 8 = Skoda, 9 = VW, C = MAN
B MIB version 1 = MIB1 HIGH (Harman), 3 = MIB2 HIGH (Harman)
ССС Region 000 = Europe, 100 = USA and Canada (NAR - North America Region),
400 = Middle East (AGCC - Bahrain, Kuwait, Oman, Qatar, Saudi Arabia, UAE),
401 = AGCC + Turkey, 402 = AGCC + Israel, 500 = South Africa,
600 = Australia and New Zealand, 700 = India, 800 = Argentina, Brazil and Mexico,
801 = Chile, 900 = Asia / Pacific,
D00 = Rest Of the World (ROW - Rest Of the World)
DD valid until year (DD is Hex value)

DD:

• 4c= 2030
• FF = ~2075/Lifetime

Examples MIB2 High:

• Skoda: 0830004c → Europe until 2030
• Audi: 0230004c → Europe until 2030
• VW: 0930004c → Europe until 2030
• Seat: 0730004c → Europe until 2030

Source: MIB2_Patch_ENG_v0.7.pdf (page 29)

 

You got 000 in there when it should be 600 or something. Check with before and after. Reckon that's the error using a European FeC.

 

It's the CCC part you got to get right for Australia for it to work. 600 Will do according to the table. This is all the mib wiki stuff of the group in that pdf.

 

Thus model answer is

 

023600ee

 

or

 

023d00ee

 

One or the other

 

😍

Edited 27 October, 20222 yr by Tell
model answer 😎

3 hours ago, Tell said:

Normally if it's showing the lifelong FeC which presume ending in EE is then the FeC went in right. 7zip is the approved unzipping program till Skoda messed it it last year but I thought that had been corrected.  If it throws up errors it hasn't been. I use the built in Filemanger one now, right click and file whatever it ever is in the examples I gave when it came up before. Build in unzipping program of Windows 10 / 11. Drag and drop to a directory on the PC. Drag and drop then to an SD card, in the root.

Hmm don't think I can extract .7z file using windows unzipping programm

21 minutes ago, Tell said:

It can be done that way but the recommended way is the VW pdf. Most fail on not getting it in the directory structure and the Mac issue. In the case above may be the FeC written although if you can see it on the FeC screen then it will have been written. Normally a long menu press will bring you up to a screen that allows you to see the FeCs - a visual check. I would say if the FeC can be seen then it's been read in ok.

 

VW and Skoda are blessed with life long navigation FeCs at delivery in mib2 form. Seat and Audi in mib2 form come with the map update locked down at delivery or once purchased Mapcare / sampler period is out of the period. The life long FeC push the limit so updates can be made. For a period some Cupras were sold with life long FeCs. You can actually interchange the Seat with the Skoda FeCs... some retrofitters load all of the brands navigation long life FeCs in for good measure, handy when they dropped the Seat one, in one release so we know if they ever do that again, what to do. I keep the Skoda one in my unit just in case they do it again 🙄. Shows the Seat navigation FeC plus the Skoda one. On the same basis an Audi with would work with a Skoda lifelong FeC. 

 

It could be say Audi was dropped from the RoW if so you use the Skoda one. It could be that. You would have to check that Audi were still getting ROW. It is easy enough to load up the Skoda one by whatever method was used. When it happened to Seat a few years back it wouldn't see the map update.  

 

Looking at my Seat notes I see I noted the Skoda one as a European life long FeC Europe 08300008 that would suggest the ROW is different.... so are we sure we have the ROW Audi one ?. 

 

Reckon not... from the internet

 

0ABCCCDD

 

Code:

A Brand 2 = Audi, 3 = Bentley, 6 = Porsche, 7 = Sitz, 8 = Skoda, 9 = VW, C = MAN
B MIB version 1 = MIB1 HIGH (Harman), 3 = MIB2 HIGH (Harman)
ССС Region 000 = Europe, 100 = USA and Canada (NAR - North America Region),
400 = Middle East (AGCC - Bahrain, Kuwait, Oman, Qatar, Saudi Arabia, UAE),
401 = AGCC + Turkey, 402 = AGCC + Israel, 500 = South Africa,
600 = Australia and New Zealand, 700 = India, 800 = Argentina, Brazil and Mexico,
801 = Chile, 900 = Asia / Pacific,
D00 = Rest Of the World (ROW - Rest Of the World)
DD valid until year (DD is Hex value)

DD:

• 4c= 2030
• FF = ~2075/Lifetime

Examples MIB2 High:

• Skoda: 0830004c → Europe until 2030
• Audi: 0230004c → Europe until 2030
• VW: 0930004c → Europe until 2030
• Seat: 0730004c → Europe until 2030

Source: MIB2_Patch_ENG_v0.7.pdf (page 29)

 

You got 000 in there when it should be 600 or something. Check with before and after. Reckon that's the error using a European FeC.

 

It's the CCC part you got to get right for Australia for it to work. 600 Will do according to the table. This is all the mib wiki stuff of the group in that pdf.

 

Thus model answer is

 

023600ee

 

or

 

023d00ee

 

One or the other

 

😍

so I need 023d00ee and 023600ee in my FEC, right? If so, how can I do that?  I just used the Increadible Bash to do a patch and got the "ee" FEC. 

30 minutes ago, TrevW said:

so I need 023d00ee and 023600ee in my FEC, right? If so, how can I do that?  I just used the Increadible Bash to do a patch and got the "ee" FEC. 

If your original navigation FeC code didn't have the 000 in positions 4-6 of the FeC what ever you had before you want that in there plus the rest. 

 

If you used mib tool you just edit it in on the txt file. Mib Tool goes in on the green menu. You run it on the green menu via SD card. I guess that's how you did it unless they have another product out or did it on the work bench via Ethernet usb connection. It's the Github jilled work that became the mib tool box of the mib wiki people... but there are variants of the toolbox. If you have done it via the green menu running the tool box there will be a txt file with the FeC codes in it on the SD card in the package. You edit them. Re-run and reboot the unit. I guess however you did it you need to seek out the txt file. I'm sure they will have used the same approach. Mib Tool is on the mibsolution web site.

13 hours ago, Tell said:

avigation Fe

 

Thanks. I have manually added in those two FECs in the text file. going to try to patch it via the green screen. Are those FECs case sensitive? 

It goes in, in upper case looking at the MIB Tool files.

 

Generally you photograph the FeC screen of the car before and after and compare to see whether it's taken it. Thus if you had a picture of what you had before your CCC characters are the ones you want.

 

On my copy of MIB Tool from 2021 they had example for Europe, US and China,

 

 

If we assume their documentation is correct it's one of the codes I posted above. Failing that you'd have to find an Ozzie car to photograph it off.

 

In any case if you had Australian maps in it before you altered the FeC it would have disabled them, so once you get it correct you will be able to see what you had before, then do the map update.

 

So it's addfec in mib tool and a reboot. Assuming you used mib tool all along, otherwise there is the question of whether the module had been written for the patch for your firmware release.

 

 

 

 

 

Do I add the FECs in the "ER" folder? I added them in the addFecs.tex in "MHI2_ER_AUG22_S2148_MU0442_PATCH" folder under "patches" folder, but it didn't get patched in. So i was wondering if I had added those Fecs in the wrong txt file....

I believe the addfecs goes in that directory. Mine went into the Seat directory of that and it picked it up from there. Just one directory. in there ER for Europe. I don't believe the MIB2 high unit for Seat is shipped outside Europe why it doesn't have the sub divisions.

 

For Audi you have that choice. If you look at the attached document FEC List.pdf it shows a choice of three, yours would be 023100EE (the NAR)

 

023000EE Audi EU Maps - Lifetime x
023100EE Audi NAR Maps - Lifetime x
023200EE Audi China Maps - Lifetime x

 

Mean's yours must go in on the US list.

 

The only thing is whether your car was shipped from Europe as an import rather than designated for Australia. If it's got European firmware on it then the patch will be picked up as European then you want to addfec slotting in the NAR FEC in the European directory assuming they have written a patch for it... if you see what I mean. If it's the NAR firmware then the table pre-prepared would be fine.

 

Quite a few expats take their cars with them so it may have European firmware in it.

 

The joys of packages. On a website with Mib Tool experts hanging about you can get answers.

 

Basically you run the package taking a backup. It tells you whether a patch has been written. If not you are invited to submit the module it's extracted to the mibsolutions website. The guys can either write you a dummy patch or the full patch. They wrote me a dummy patch which I then did the addfec with. They also wrote a patch and added it to the list where the Seat 1338 originated. So the question is whether a patch is already within the list. Eyeballing you can see them from your software but it will automatically find the patch if one exists and tell you if it doesn't. Question of whether the car has NAR firmware or European firmware. Using the NAR Fec on European firmware should work to give NAR maps... I reckon.

 

Clear as mud. That's how the software worked last year. You might need one of their Bash programmers if it doesn't recognise your software.  On an Audi site you might find a band of Bash programmers familiar with Mib Tool.

 

 

 

FEC List.pdf