dasalias said:
Sorry to say, but this is categorically incorrect. I am now on my second Ateca. My first was a 2016 Xcellence, bought as an ex- demonstrator. It came with the Media System and Navigation V4. Obviously, navigation was already setup and working when I took delivery. As new map versions became available, I was nervous about screwing up the original card, so I bought another genuine Seat V4 from Ebay. When it arrived, I inserted the card and it worked straight out of the box, without changing anything.
Well, yes and no - I did admit about 4 posts later that I appear to be mistaken on the head unit. That was the prevailing theory when I was digging in to how to update my Ateca's map software 2.5 years ago. As always, the wonderful thing about anecdotal evidence is it's just that... anecdotal.
So point taken. However, CID is a factor. (See a bit later though...)
dasalias said:
I did change the overall.nds file, but next update, I won't update this file initially, just to see if it really does make any difference.
If you have MapCare then this will probably work, if not then it won't. There's been a good few posts here about a lost 'overall.nds' to indicate that, but it will deffo be a good test - didn't work for me, but things can change, so let us know!
Tet70 said:
But why is there an overall.nds file in the update then? If the overall.nds contains information that is related to the specific card, that file should be missing from the downloadable update package, right?
Well, unless you're part of the MapCare programme or have completely reverse engineered the system, then we can only speculate. Last time I tried that I got burned :roll: BUT... I can't resist speculating on a good puzzle though! :twisted:
So what
do we know?
- The file overall.nds is the main factor for the maps update
- The card-specific CID is a factor for the SD card to load maps from
I could speculate that if you have MapCare then overall.nds is ignored and if you don't, then a valid overall.nds is required. Doesn't quite seem right though. A better suggestion would be, if you have MapCare enabled then the overall.nds that comes with map downloads is seen as valid and if no MapCare enabled then it's not. But even that doesn't fully fit .
CID is a factor otherwise you could use any old card. But maybe it's not as big a factor as I originally thought. Others have suggested that it could be as simple as a vendor hardware validation check (CID is formed of multiple components, one of which is manufacturer ID).
Could overall.nds just be a filter list of supported SD card manufacturers, with different signing keys depending on MapCare (or lack of it)? Perhaps that's exactly what you're getting at Tet...?
Maybe the head unit does a filter on the CID for recognised vendors and overall.nds is a licence file for the maps and if you have MapCare then it has one licence key that works with the downloads and if no MapCare then it uses a different key that only works with the file on the SD cards?
Both attributes are a factor in updating maps, but are they linked, or do they serve completely different purposes?
All of this is speculation though!