(note: this is not for the Garmin thingie but the built in nav portion of COMAND)
Our pal @traxem posted a really good link for an inexpensive option to get maps updated from the stock maps included in our 2014s (which by the way was a lot older than 2014) but that was in one of my other threads (about using iPhones with the media interface) so thought I'd move map updates info to a thread of its own ... in case more folks want to stop driving through nonexistent roads on the "map"
So after downloading 17.7GB (good grief !!) and then decompressing and stuffing all that onto a SD card (another good grief !!), it was time to see if the all important "PIN" code from the vendor really works (entered right after the next pic):
Then the update process time from start (5:12pm) to stop (6:07pm) is just under an hour ... no too bad (5.36MB/sec update rate):
An engineering menu check shows an obvious "delay" between maps release and their "year" designation ... 2016/2017 in this case:
An interesting note is the process date (at the company HERE) for the primary map database files is 03/14/2016, so I suppose the "2016/2017" moniker is appropriate?
Our pal @traxem posted a really good link for an inexpensive option to get maps updated from the stock maps included in our 2014s (which by the way was a lot older than 2014) but that was in one of my other threads (about using iPhones with the media interface) so thought I'd move map updates info to a thread of its own ... in case more folks want to stop driving through nonexistent roads on the "map"
So after downloading 17.7GB (good grief !!) and then decompressing and stuffing all that onto a SD card (another good grief !!), it was time to see if the all important "PIN" code from the vendor really works (entered right after the next pic):
Then the update process time from start (5:12pm) to stop (6:07pm) is just under an hour ... no too bad (5.36MB/sec update rate):
An engineering menu check shows an obvious "delay" between maps release and their "year" designation ... 2016/2017 in this case:
An interesting note is the process date (at the company HERE) for the primary map database files is 03/14/2016, so I suppose the "2016/2017" moniker is appropriate?