Quote:
Originally Posted by undecided1
I guess so but it would still be better if the code matched the map as intended/as BMW would supply. I know CIC Pro is getting on a bit and not fitted to cars since 2016 but some will still have warranty and filling nav with codes BMW would never have supplied just seems a bad idea in the same way lifetime would be... Probably just being picky for most people but since the Jagaer XML set the two different 2022 entries to use the same fscshort it just seems sensible that when doing so you'd try and use the 'right' one. I can see how it happened and totally understandable but if the info_map.imp file from the map itself has 5A in it then that's what I think it should be set as, same as all previous maps.
|
I think that is a neglegible risk:
If the code was bought from BMW, it will be recorded in their central database, so they know if the code on the car does not match theirs. You can, at some point, determine without reading out the car if the code was a "lifetime" one - because you won't be asked for a new code when you upgrade the map data.
Having a code that extends to the next version is fine, since BMW sells 1 and 2 year subscriptions themselves. The difference can be determined via coding and then, it does not matter if the code is correct but was not bought via official channels.