dgc188

Well, I'm totally confused now after reading the various sub-forums on here. All this talk of MIB2STD, MIB2.5, MIB2 High, Skoda Connect option (or not), wi-fi enabled (or not). I used to think I had a bog standard MIB2STD - but I'm not so sure now. I, like many of us, have been dismayed at the loss of TMC (over FM/RDS) during April due to the demise of the TrafficMaster service and the unwillingness (or whatever) of the VAG group to come up with a replacement service (INRIX) that we all know is out there (still on FM/RDS, I believe, as well as a service via DAB). I guess we're all looking to enable a replacement Traffic service for our vehicles - and to add the to complication - there seems to be differing ideas surrounding which vehicle manufacturer you might be driving, which year it was produced and even which NAV system was fitted into it. Nowt seems to be "standardized" across the group. Me? I'm driving a Skoda Octavia Superb Technology 2016 with an Amundsen MIB2 (of some description!). Quite how I might find out if I am able to attach a dongle to give me connectivity to a server somewhere out there that will provide me with Traffic data I do not have a clue. As PetrolDave indicated in his post, above, it seems he also drives a Skoda Octavia III 2016 and he doesn't have the Skoda Connect option. My Nav system (believed to be a MIB2STD) has a part number of 5Q0035874B; Version information.... V03959820MP 2110 ECE1 2024 (I believe this is the latest map data from the VAG mapdata site) SHIELD: SHIELD 2016-03 (build 020); --not sure if the following have been updated since the new 2110 maps were installed-- Installed software train is MST2_EU_SK_ZR_P0359T; Software version: H28.28.133_STD2Nav_EU Installed SW MU version: 0359 HMI Versions.... Model: GuideModel_28.28.69 Software Base: H28.28.133-201605251448 CGRun Number: H28.28.133-210605251455_STD2Nav_EU_2016052 All these numbers must mean something to someone - to me? not a lot (other than the map info)! I don't have need to make use of the Traffic data all that often and I'm trying to find an option that will work and won't cost a fortune - maybe the dongle option (Humax?) and a cheap SIM (RWGmobile 1p/MB), no need to reload cash every 120 days like another 1p/MB option I spotted). And, I presume, if all is well with my NAV system and the dongle option is likely to work without delving into the unit with the VCDS/VCP, I simply plug the SIM into the dongle, plug the dongle into any spare 12v (with USB adapter) port, enter a few details on-screen, and away it will go. So, the base question is - will my Amundesen work (as is) if I were to go and buy a dongle & SIM? And how am I likely to find out from the numbers shown above whether it would work or not? Or don't the numbers relate to anything useful? Maybe a new TomTom (or similar) would be the answer, but I don't want or need to pay that sort of on-going money. Definitely "confused.com" !!!

Many thanks to pcbbc for the update ( and to all the others involved in the search for this solution to getting TMC up and running again for the Skoda MIB2STD ). Am I correct in thinking that this is for a straight file(s) swap/unzip to the SD card and there's no need for any external connection to the MIB by way of adapters or other software? i.e. copy files to SD card and whack it into the MIB. Looking at step 4 "Check/configure....using VCDS/OBD11" makes it uncertain (in my eyes, at any rate). Or is it simply a check in the relative SD card files. I would also ask if there is a 2020/V12 version the the very much smaller ECE 1 file (about half the size of that in the link) - the free option of the MEGA software has so many limits on downloading it'll take while next year to receive it !! (well, almost) - or would this involve further tinkering to get it to the same level as for the full 13.5GB file - if so, we'll live with the bigger file. Is anyone still working on (or even looking at) getting the INRIX data onto the new/latest TomTom files for the MIB2STD? Or is this dead in the water due to licencing, etc.? Either way, this fix is a great step forward, albeit without TMC. So stuff you VAG. And to perhaps clarify an earlier question, from Tell that wasn't confirmed for denied, in that it would now be possible to swap between the modified "with TMC/V12" files with a download of the current/up-to-date "without TMC" files simply by re-writing the SD card (or having 2 SD cards) depending on requirements? Great work guys, well done. Appreciated.

Interesting development ? I tend to keep a regular check on map updates on the Skoda website. The latest (202245) was there a couple of days ago - today? Gone. Maybe, at last, they realise I am no longer due for free updates (66 plate) - or maybe, just maybe........ there's an update coming re TMC. Now, that would be a turn-up for the books!! I'm just being referred to my local dealer. I await any further development.

Similar to the above, I also had a response from Skoda support: We're sorry to have kept you waiting. We would like to apologies for the delayed response due to an increased volume of requests, we kindly ask you to wait a little while. Our information department is working on the solution in order to provide you with the most accurate and detailed instructions. As soon as we receive further information, we will inform you immediately. Thank you for understanding. With kind regards, Support for Digital Services ŠKODA AUTO a.s T: 00800 80 247 247 *****@*****.tld, www.skoda-auto.com Load of twaddle if you ask me. Need to keep the pressure on them - and they'll still probably do nothing.

I recall "them" saying FM would be dead by 2020 - well that's gone by. Then I heard 2025 - that's not far away. Then I've heard 2030. Goalpost movement? Where to next? I agree, there's a good many FM radios still in daily use, and not just in cars (personally I prefer the better quality of FM - but that' another story). I recall when analog TVs went to the digital service - that cost me a couple of TVs to keep being able to watch the thing. So, one day, I can see the same thing happening with FM, maybe even DAB as well, with it all going on-line. If these sat.navs can be got working by whatever means and by whoever (the hobbyist probably) - be it FM or DAB - it might give a bit of a breathing space for when FM does finally go.

Likewise, I had a survey from Skoda - it won't be a pleasant read for them I'm sure. Certainly not complimentary in any shape or form. And they sent me a 2nd survey form. Let me think what I'll put in that one! I've yet to visit the local dealer - later this week maybe. Thinking about things, I wonder just how many VAG drivers that have this issue with their sat.navs are actually aware that TMC is no longer working. I certainly wasn't aware until I needed it on the first trip out with the caravan a week or so ago with the prospect of holdups on the M62 and looking for a diversionary route. And then just how many have made the effort of contacting their dealer (or direct). I would expect it to be quite a small minority of those actually affected, who maybe don't know it yet or just can't be bothered, thinking it's just an temporary outage. Based upon that I can possibly see why VAG are not rushing to fix the issue and putting the traffic onto DAB and INRIX. Forget TMC/FM - FM's reportedly going to be dead in a few years anyway. I note that the Garmin sat.nav (the Dezi 760LMT-Digital) that has DAB/INRIX traffic (referenced above by the article from 2012) has, it might appear, since been discontinued according to some sites, but might still be available form Garmin itself - albeit with a 5-8 week delivery. Even Garmin have now gone down the smartphone/app route. So, unless there's someone in the know of how this all hangs together (outside of VAG) then I think we're stuffed on getting VAG to fix it. Here's to the hobbyist, may they never die.

Like others here, I also emailed the weconnect-support @ voltswagen . de (minus the spaces) and had this most informative (NOT!) response: Thank you for contacting Volkswagen Digital Services. Please be informed that the Digital Services department only provides technical assistance and support for the use of the digital services within the Volkswagen vehicle and related apps – “We Connect”, “We Connect Go”, “We Connect ID”. We kindly invite you to contact Skoda Digital services who will be able to assist you with your enquiry: *****@*****.tld Thank you for your understanding. Warm regards, Your Volkswagen team I have further emailed them such that if they are not responsible - after pointing out again (in both bold and red) that this affect VW vehicles as well as Skoda - then perhaps they could point me in the direction of someone who could assist as this is a VAG-wide problem. I expect they had all gone home by the time this was sent. I await they're fresh response - but I'll not be holding my breath I'll get anywhere. Incidentally, I've been in touch the other day with their advised email address @skoda and they advised they would pass it on to their "information department". Again, I am awaiting a reply from there. The phrase which includes "head" and "brick wall" comes to mind!

Looks like the (simple) change of <provider_ref id="2" mode="non-exclusive" /> to <provider_ref id="12" mode="non-exclusive" /> in TmcProviderSets.xml in entry <!-- PayTMC UK --> failed to make any change. I still have the TMC symbol struck through and obviously no messaging coming through. It was (perhaps) too much to hope it was that straight forward. So - if I got the suggestions correct from pcbbc above..... This is the top section of the fie: <!-- PayTMC UK --> <tmc_provider_set id="21" use_free_tmc="true" use_online_traffic="false"> <provider_ref id="12" mode="non-exclusive" /> .....line altered here from id="2" </tmc_provider_set> Should I also need to make any change in the <!-- ------------- Online Traffic Provider Sets --------------- --> section here: <!-- PayTMC UK --> <!-- 32768 + 21 --> <tmc_provider_set id="32789" use_free_tmc="true" use_online_traffic="true"> <provider_ref id="2" mode="non-exclusive" /> <provider_ref id="12" mode="non-exclusive" /> </tmc_provider_set> Surely this for section is for the online data collection, nothing to do with FM data collection. And should there be any changes made in the SEAT and VW sections as well? Can't see why, as this is in a Skoda vehicle with a MIB2 Std unit. The one file was simply over-written and put back into the nav unit. I can see no way of indicating to the nav unit that the data has changed, so presume it reads what it needs on-the-fly/as required. There's obviously more to it than that simple change [thought it would have been "too" easy a fix] - simply getting rid of the TMC strike through would be a step forward. Any further ideas?

I'm probably barking up the wrong tree here, but... Is it likely that the described change of the provider ref in "TmcProviderSets.xml": <provider_ref id="2" to ="12" will provide a fix on the MIB2 standard units to look at and decode INRIX? It seems too simple a fix - if it was to work. [the chat seemed to move onto the MIB2 high units]. Based upon this possible and simple change to the "TmcProviderSets.xml" file just by adding a single character.... it appears the file on the root [1910_MP213-1240.x_EU1.md5sum.txt] lists MD5 checksums for this (and every file). How is this MD5 calculated? I've copied/pasted the (unchanged) file contents (opened in Notepad) into a suitable on-line calculator and get a different MD5 checksum to that indicated on the root file. Does the MD5 shown on the root include ALL the file contents or just the data (and not the comment lines)? And would I need to change the name of the entire file from STD2_1910_EU1_202245.zip, or is there something coded into that filename as well?

Well, just as expected.......! I emailed support@... ref the missing TMC data and received the following - and within 24 hours over a Bank Holiday (what a surprise!): "We received your email, in which you requested information about TMC. We're sorry to have kept you waiting. We kindly ask you to wait a little while, we have sent your enquiry to the information department in order to provide you with the most accurate and detailed instructions and answers to your questions. Thank you for your cooperation. With kind regards," Like most others on here I've been having a drag around the 'net and can only find map updates (even later those on the official Skoda portal) and a number of minor firmware updates, but these pre-date this TMC change of provider issue. I have SW MU version 0359 and the best I could get would be 0369 - with a harder to install 0480. Would I be able to update to 0369 without the likelihood of errors for which I would need an add-on box to clear the code? Or maybe it's not worth the hassle for a few (minor) fixes. The full SW Train is MST2_EU_SK_ZR_P0359T - Part number: 5Q0035874B - and Software version: H28.28.133_STD2Nav_EU. BBC's Watchdog might be a further lever to get this sorted, given there are so many owners affected across so many marques. I did shake that stick at support in my email. I doubt it will make any difference to them but maybe getting the Beeb involved might. Matt Allwright and his team are quite good at getting things done.

I've just had need to make use of the SatNav on my '66 plate Octavia on the first trip out with the caravan and found, like all of us on here, that the TMC traffic didn't work and the SatNav failed to provide the mapping warnings. This has had quite a major issue for me this week in getting back across the Pennines and the horrendous traffic jam on the M62 and the failure of TMC and the SatNav to provide a suitable alternative route. I've been reading through most of this thread (admittedly, not all of it) and find - in some ways - thankfully it's not MY car and, therefore, unnecessary to take it back to the dealer to attempt to diagnose and fix the problem (which they won't) and charge me for the privilege. I've noted here that it seems various config files loaded onto the car need to be "in sync" with each other. I've not had any "system" firmware during the past 12 months or so but the map data was updated earlier this year. Is it likely that this updated map had broken the sync'ing between these config files. I've had a look/comparison at various map config files between different versions of the mapping and - without knowing exactly which file(s) to compare - they seem to be the same. The current map data file is STD2_1910_EU1_202245 - previously it had been STD2_1810_EU1_202222. I still have the 1720_EU1_202148 file. The Hardware is H30 - Software is 0359. a) Would there be any mileage in reverting back to a previous map data file? b) Or simply write the current status off and contact Skoda Support. c) Anyone have the personal CEO email? d) Any other ideas/conclusions/ etc.?

Thanks surreyslowcoach for the comment. It seems like Skoda (VW, etc) don't want us to mess with their databases and add our own POIs in. It begs the question, what are they so afraid of. Having said that, I'm on the point of getting a new TomTom and saying to hell with the on-board satnav. Especially when the other week I used the satnav for the first time since I got the car in '66 (new) and it wanted to take me down some very narrow lanes especially when the location was a yard or two off the main road and also down some very weird routes on the way. Thankfully I knew where I wanted to be and the route to get there. Never again will I be tempted to use the satnav. And this while towing a caravan. No way would I have been able to navigate those lanes! Stuff the satnav, bring back TomTom. signed - "angry and not impressed of Doncaster"

I have a Skoda Octavia Technology '66 plate and now that my TomTom has gone kaput and has finally been laid to rest, I am wanting to add a whole load of camping/camp sites into the Amundsen (MIB2 I think) using the SD card (would it be on SD1 [map] or SD2 [media]) but can find nothing that relates on the "how to" - only maybe a few old guides that have since been broken by newer equipment or missing/broken links. The files I have are mostly CSV with some of the TomTom OV2 style as well. Any help would be appreciated. Thank you.