Skip to content

Tell

Members
  • Joined

  • Last visited

Everything posted by Tell

  1. Suppose to be a digital ID but he's corrected me in the past and may be over the air jpeg for DAB. If the logo as a jpeg is never transmitted then you can see you are a bit stuffed when the station ID is recycled. Seen that in the UK. Think actually the logos are not transmitted just a station ID. You can inspect the mib2 ones via sql light or whatever its called. I'm travelling at the minute so can't check. It's the SQL commonly used so if you have database skills you can poke about in the tables but no good to change anything. All locked down.
  2. I stuck with the 32gb sd card in Fat32. After vag stopped the support of the mib1 component in the update you didn't need the 64gb card since it stopped outgrowing the 32 gb card... however if you had some 32 gb SD cards that combined release would just fit on. MartiniB was like me when some started moaning and we didn't have an issue with our SDs 32gb cards. Aldi ones I inherited 😉... nothing fancy. Probably the Format command in Windows was playing up in exFat. Windows 10/11 did have a bug at one stage that messed up the sector size by not retaining it in a format. Probably something like that happened. Think that is what was messing up mib2 standard map cards that got zonked. I have certainly seen one release of Windows defaulting the sector size to the max it can.
  3. Yes that would be inline with the November release and ECE 2026. Normally in old naming the June release was a combination of current year and next year. Whilst the November release is named to the following year. That I seem to recall got corrupted for mib2 standard when they lost a release due to processing issues.
  4. Great suspect that's the November 2025 release 👍
  5. I guess this is a catching up release since way back when the six monthly release got delayed and missed a six month period. Now this could be the official June release caught up ?. Away on holidays. Let @MartiniB check the production dates. Note the next post on that Ateca link says the all European link doesn't work. Needs validating whether that is the case.
  6. Tell replied to RodDuggan's topic in Skoda Karoq
    I could see if you had poor 4g you may have to wait over a month if you never moved your car... 4g is shocking where I live and it's a piggy back low bandwidth service they use. I would get zero success.
  7. Tell replied to RodDuggan's topic in Skoda Karoq
    USB method isn't bad but if I had mib3 I'd probably pay up for rest of what connect services can offer.
  8. It's either the development database you are looking at is correct but the production database which is either what is loaded in the car or held centrally doesn't tally. Either it's been subsequently sorted but the cars system doesn't reflect that or the production database has drifted from the development one ie. They have not taken the correction put into the development database so the production one is out. Last edits were done by the Here Maps Team in October 2024. It's a precision road so small adjustments are not allowed so it locked down from movement. It's conceivable that if it was changed in October 2024 it would not get into the shipped files for six months or so. 25.05 was your map in the car. I'd give it till Xmas 2025 to see whether it passes through or take it up with Here Maps.
  9. Unless it's reading it off some small sign somewhere. You get those bin stickers and it's not on the digital map in Herecreator ?. I think you might find a toggle to turn off TSR. One in mib2 for a test drive. Dynamic sign recognition. The other one that started to effect me a couple of years back it decided the local street was 5 mph. I put that down to slight misalignment where it reckoned you were off road. Always when I turned into the street getting home. Dong. I got Here Maps to look at that found nothing. Mib2 high auto recalibrates it's position if the maps are reloaded. So by driving a route few hundred yards through bends it places the car back on the map. Interesting one when you see it. Did that with the latest maps that I loaded up. We had a 5mph limit for quarter of a mile. Then learned from GPS and the road contour so then behaved itself. That issue has gone. It was the recalibration. I have had this one in France, reading the traffic signs off the back of lorries you are following on the Calais / Dunkerque road. The only place it does that one. The Heremaps creator database you see is the development database, whilst the production database is different, so they might be out of synch in that area. Sometimes you get two roads on top of each other. Which need to be weedled out. Previous edit error and what appears to be an AI system going off on one which can take a few days to straighten out. So a few things to check. You might have a report something wrong icon. The systems they sell for lorry navigation etc have report issues from the cab. They get pulled up into the Here Maps validation. A select few were allowed to validate and change the source materiel, then it became apparent that the select few were not much good and that features was removed, so I did see everything their validation teams saw at one stage. They were hoping to get validation on the cheap. Might be your issue falls into the one the production database needs to be looked at if the development database isn't showing it. If it's not a TSR misread or misalignment. The other thing is Vag contracts out the development of the mib3 files from the cartography. If the programmers misunderstood the source files then cartography doesn't work. In the first year they had the postcode controids pointing off road. The postcode is matched to the road but they were taking you to an offroad centroid. They were interpreting the files in a GIS market research method than navigation. In Heremaps house numbers are allocated to a centroid to the building and the navigation point on the road. You walk from there. The postcode only guys were getting taken off road. That's been corrected now in mib3.
  10. Yes you'll be on connect services OK withn25.05. There is a way of offering up user corrections. You need a Heremaps login and you do it through their portal mapcreator.here.com/ The mobile app of it allows you to upload the evidence via a photo. May help. Generally the camera recognition works well except where the council put the 20mph speed limits in on side roads and it sees the sign as going past. The signs need to be a bit further down the road. Only effect of the speed limits coming in and grumpy people thinking they don't apply to them. I did do my bit where you could enter the village here on an unauthorised farm track. Council had left the old sign up of 30, got that changed so no excuses for those taking the short cut. The radar signs had been turned off that we had a whip around for. Got that reprogrammed. Heremaps has more stringent validation process than Google and Waze being run by a proper cartography company. The official 20mph roads in Wales are here. https://datamap.gov.wales/maps/roads-affected-by-changes-to-the-speed-limit-on-re/ This is what was examined to update the Here Maps roads. Use to do health planning in a department that did gravity modelling for services planning. When the NHS use to build things and not close them down. So our analysts would pour over maps, travel times, timetables etc as part of siting work, ambulance stations, regional centres etc. Was heartened to hear that HereMaps geographers went over the Welsh Government files. Assorted notices also go in on road speed changes so they go back to them as well. Published road plans for road developments. The survey cars for precise road position on A roads etc for self drive cars... they are set up for that. The architectures stuff. Regenerative predictivd breaking is another one. Being mere mathematical modellers we like to make sure the geographers do it correctly 🤣. As you know the 20mph limits are being revisited in Wales so that process will be repeated.
  11. The part release of the manual one for the last period is: (doesnt include all of Europe yet... so you'd update manually with the one above if connected services was not working or configured. YY.MM is the serial designation on the unit.
  12. 2024 means it's a mib3 since that is what was fitted to 2020- models, mib2 generally 2015-19. If you have connected services working with mib3 then the maps should auto update. Annual fee or free if you do it yourself. Some people manage not to have connect service set up correctly with mib3 and in that case the maps don't update. The update release can be read off the infotainment system. If we are talking about Welsh 20mph speed limits that date and maps not being updated could leave it reflecting the old speed limits. Certainly the Welsh speed limits are in the database for the last year or so. Mib3 maps use Here Maps cartography. It's that team that have put the road speeds in using the Wales Government's negotiated speeds and agreed speed limits with the local authorities oublished on a public map. The later play, parse the parcel with these but they had the final say by agreement with the Welsh Government. Some local authorities in Wales pretend they were mandated. No they could change them back to 30 mph, if they so wished based on local knowledge of what speed they thought was suitable for that road. The manual update is shown on this link:... note the map is designated yyyy.mm. Thus if your system is above 2024.06 then you have newer maps and connect services is running fine. If it's 2023... something or other your maps won't be updated with the Welsh road speeds. It was in the 2024 maps when the Welsh speeds got into them. My mib2 high started donging that I was speeding as I left the village from start up without reading any traffic signs.
  13. That's TomTom not on top if it. Try http://www.tomtom.com/mapshare/tools They are reluctant to take users speed suggestions though preferring their survey cars. Wales they have the Welsh Government marked up map.
  14. It's the digitised road speed on the map. Ah Wales... where I'm sat. If it's mib2 high columbus or mib3 it's Here Maps. They updated all the roads on the system. For mib2 high you need to update the maps. Connect services for mib3 would do it for you but if out of contract MartiniBs files pinned. SD card based mib2. Use the latest maps, these are TomTom equally they updated the digital roads like HereMaps from the Welsh Government map file where they agreed the speeds limits with each LA. So I'd say you are using old maps. TSR will override the digitised road speed but once you pass onto a new digital segment on the map it will take the map speed. Hence it will revert if you are using old maps. Check out MartiniBs pinned map updates. If mib1. May be more tricky. I have pointed people to a mib1 2023 update where it's possible it may have the new Welsh speeds. Mib1 update you have to use a teething approach which is used on Seat's. Works on Skoda as well. Since the Welsh speeds came in, in 2023 and the latest mib1 for Audi which can be used is 2023... might not be in it. You'd have to check. Whether there will be an Audi 2024 release pass. The files are compatible with a small edit.
  15. Yes. You need someone with Audi mapcare to then cut and paste the link out just to see whether it's protected. May be a cookie or it would be accessible only via the login. So that was as far as my checking was concerned... I needed a subscription to dig deeper.
  16. If that's the Audi version that got leaked by Russian boards and mibsolution.one last year it was just manufactured differently. The UK was identical apart from how it was put together with the meta check sum and signature. I gave up checking every country and concluded the early release via Audi was identical. Ofcource it might not have been a release but a beta test file put out. Other year's I caught site of the file being discussed on the German Skoda Commumity board. Only last year did I lay my hands on it. MartiniB will tell me whether I've got my years wrong. It's on the board where I said, no difference based on my check. So as I've said Audi files are behind a pay wall on their server.
  17. When I looked last year with the Audi ones, since I was intrigued about them, they sat behind a pay wall. If you had coughed up for Audi mapcare you got past the pay wall, if you didn't, you couldn't. Expect Porsche ones may be like that, hence why Audi and now Porsche come looking on Briskoda.
  18. Thats an Audi unit based on https://mib-helper.com/index.php?train=MHS2_ER_AU_P0448#details A MIB2 High Scale whatever that is. Wiki: https://wiki-online.vcds.de/de/Plattformen/MIB Not a mib2 high as we know it. Not come across those before.... does it look like this: https://www.audi-mib.bg/audi-delphi-mhs2-scale-map-activation-2021/ Reckon you need an Audi forum / trawl Russian websites for knock offs... Audi map were sold with mapcare so were never free. FeC can be adjusted so maps for Skoda and VW etc can be used but whether they were fitted to those cars... least not. So a nitch unit. You might find they have fallen off the back of an annual generation or may be not. If not ebay may be a source for a map card. Your best bet is an Audi forum. Your unit / file still needs to be patched hence the need for an Audi forum where people are familiar with the process... Your man that you have lost.
  19. Those are on the threads but as he said they have messed up their library now on some of them... least I think that what he said. Too early here. Where he lists out the alternatives by brand you try each one till you find one that works. I say map files are like hot cakes best to get them fresh before they go off... mib3 waiting for the next batch. Then nothing new at the minute.
  20. That bit yy.mm found by using that SQL browser file I got told about on the threads here after I spent about a year asking did someone know where it was in the files.... will be the key (thanks to a bright spark). They won't have two or three sets of that running. All the package / file names you can disregard. That's the one that MartiniB uses now to publish with the yy.mm. We needed that lookup so we could look across releases of the brands. The Derivation: Technical Note - Derivation of the YY.DD as shown on the Infotainment Screen I have now been told how to read that YY.DD date off the files after putting out my request for some time for a bright spark into these Mib3 files. It's been delivered. If you don't want to load up the file you can look up what year the and periods the files relate to. It's important with MIB3 files you don't alter the contents because you can't they are signed and they will refuse to load. So no tampering with the files like mib2 standard maps. Anyhow, this is how you do it thanks to C34 on the Briskoda site... only two posts popped up to tell me. You need to install DB Browser for SQLite. This has an extension in it to read the NDS Associate files, the normal SQL Lite brower that is popular won't. Install the MSI of DB Browser for SQLite in the link above. We now use C34's text... In this example on the file Update OI_P119_EU_202425_Offline_Update.zip contains data from 23.12 (YY.MM). You can check this for example in the MIB31_EU.ROOT/3D/PRODUCT.NDS file. This is a SQLite database, you can find this information in the updateRegionTable table. You open the table up and have a look. Does help if you have database experience . On the VW file, for 2024/25 I got this: View attachment 43716 So that is they, for the technically minded of where the YY.MM is stored in the files. Handy if you come across one and not sure. That's how you nose about those files not that you need to... or you can just trust websites like this.
  21. In MartiniB we trust... think that's a religious quote. Seat haven't managed to get anything up different ?. When we were having this debate recently a Seat poster was quoting a file reference which was published of the last release (one current, 24.6) but not on their website wrapped page so it's reference had been found by someone. Might be worth scouring that server if not already. At one stage they were quite good at filing the map files that they had been given, not so good at publishing of recent.
  22. It was when Times Radio opened it had a logo of Talk Radio where the delete thingey comes in. MartiniBs one would be delete the icon and re-import but if you aren't seeing anything then it won't be that. Well the mib3 manuals, early ones told you how to import the logos like mib2 in png form but they never implemented it. Think it was all part of the lock down to prevent unauthorised access to the unit. It was the POI import in mib2 that had no signature controls on which gave rise to the tool kits and tool boxes and a dic tac came out to remove it. Other people think the same. So you got this not very well executed method which Vag probably think is dandy.
  23. You got to nag phonostar radio for the missing ones. Basically they are a poor contractor to the Vag group for the logos. Poor QA from Vag not making sure that the phonostar database of logos is upto date. You see MartiniB said about deleting some. This will be where the channel has been recycled into something else so as to get that to take effect you delete what you have....
  24. Unfortunately, this one isn't blessed with SE in the manifest file so doesn't work with Seat. However, a Google on the part code brings up what the Russians have been up to on these units: https://www.drive2.ru/b/652194564542564317/ The red menu is where the existing database is shown... we probably knew that. Might be some other bits and bobs in those links of interest. I see from the read, Phonostar is pretty diabolical at having up-to-date logos even for Austria. I'm sitting out Mib3.
  25. The v1.31.58 will be the reference of the logo database packaged up in the different versions of the files for the unit. So v1.31.58 is the same logo database to the next one but different to v1.31.56 say 🫢. Clear as mud so not to be at cross purposes.

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.