[Svaen]

I’m trying to update my navi with Road map Europe premium west 2021-1, but the problem is that my Bmw cic/fsc generator v1.9 can’t generate the right code, since there are no newer maps than 2019 in the generator.
Is there a updated generator out there?

Edit: Nevermind, forgot to cross out the lifetime code option. Case solved.

[penfold2105]

Originally Posted by Svaen

I’m trying to update my navi with Road map Europe premium west 2021-1, but the problem is that my Bmw cic/fsc generator v1.9 can’t generate the right code, since there are no newer maps than 2019 in the generator.
Is there a updated generator out there?

Edit: Nevermind, forgot to cross out the lifetime code option. Case solved.

If you open the the generator whilst connected online the first time it will update the lookup file.

Watch my video

https://f30.bimmerpost.com/forums/sh...8#post27996338

[CKH50d]

Hello! OSX Link is expired...

[Michael Z.]

Hey folks, I'm new to this community, but certainly not to BMWs. I recently purchased a 2013 BMW X1, my 6th BMW. It came with a failed iDrive. In my quest to keep repairs cost low, I got a used replacement with the exact same part number, albeit out of a 128i. It's fully functional, apart from the navigation, which states "Function not currently available". If I attempt to pull the FSC file, will it be accurate for my vehicle or the donor vehicle? Ultimately, I'm looking to have the system fully functional with the most up to date maps. Sorry for the specific issue, I don't think I have privileges to start a new thread.

[opjose]

The FSC file on the donor car's idrive is specific to the vehicle it came from.

A new FSC will be required for your car after updating the VIN on the new CIC and installing it in your car.

The new FSC will then match the car's numbers.

[Michael Z.]

Originally Posted by opjose

The FSC file on the donor car's idrive is specific to the vehicle it came from.

A new FSC will be required for your car after updating the VIN on the new CIC and installing it in your car.

The new FSC will then match the car's numbers.

Can I do this with the FSC generator or will I need to buy a cable and use the CIC Patcher, virginize the CIC and then build from there?

Before I head down any path, is there anyone here from the Toronto area that could help out (will pay for your time)?

[opjose]

If you are talking about the code generator for maps, then no.

That generator is for MAP codes to enable specific map years. It does not generate the codes that enables the CIC matching the rest of your car.

Virginizing is best.

Scripting can be problematic.

[Michael Z.]

Originally Posted by opjose

If you are talking about the code generator for maps, then no.

That generator is for MAP codes to enable specific map years. It does not generate the codes that enables the CIC matching the rest of your car.

Virginizing is best.

Scripting can be problematic.

Much appreciated.

I *think* I have an idea of what is necessary to move forward. There's some great information on these forums, however, I noticed it gets quickly outdated. What was done in 2017-18 isn't necessarily what people are doing now.

So, my plan is to pick up an ESYS ENET cable from Amazon. Then, I get CIC patcher on a USB and virginize the CIC. Finally, install certificates using FS Tool via ESYS cable. Please correct me if my theory is off.

[mjn77]

Just pulled down a new XML, but still hasn't got 2022-1 for Europe West Premium for generating a code

[meyergru]

Originally Posted by mjn77

Just pulled down a new XML, but still hasn't got 2022-1 for Europe West Premium for generating a code

According to the steps for the last few years, every half year the increment was 6:

2019-1 = 00280038
2019-2 = 0028003E
2020-1 = 00280044
2020-2 = 0028004A
2021-1 = 00280050

So, I assume this goes on as:

2021-2 = 00280056
2022-1 = 0028005C
2022-2 = 00280062

You only have to edit the Lookup.xml accordingly and change SWID_FscShort.

BTW: The comparison is done via ">=", such that a higher SWID_FscShort will work for earlier years. Thus, you can use 002800FF as a "lifetime" FSC.

[mjn77]

Yes. I have edited XML file.

[undecided1]

Originally Posted by meyergru

According to the steps for the last few years, every half year the increment was 6:

2019-1 = 00280038
2019-2 = 0028003E
2020-1 = 00280044
2020-2 = 0028004A
2021-1 = 00280050

So, I assume this goes on as:

2021-2 = 00280056
2022-1 = 0028005C
2022-2 = 00280062

You only have to edit the Lookup.xml accordingly and change SWID_FscShort.

BTW: The comparison is done via ">=", such that a higher SWID_FscShort will work for earlier years. Thus, you can use 002800FF as a "lifetime" FSC.

Hi, Sadly not, for 2022 the correct one is 0028005A. Bizarrely the lookup file from BMW has two entries for 2022 with one as 5A and other as 5C, they still haven't cleaned it up yet. I see the generator is now pulling down a new lookup file and even has the same fscshort for the 2022 usb and non usb entries which should be good BUT it is using 5C on both which is incorrect :(

Jagaer can you please correct so it uses 0028005A on both?

thanks

[meyergru]

Originally Posted by undecided1

Hi, Sadly not, for 2022 the correct one is 0028005A. Bizarrely the lookup file from BMW has two entries for 2022 with one as 5A and other as 5C, they still haven't cleaned it up yet. I see the generator is now pulling down a new lookup file and even has the same fscshort for the 2022 usb and non usb entries which should be good BUT it is using 5C on both which is incorrect

Since the comparison is done by ">=", 0028005C should still work just as good for the 2022-1 version.

[undecided1]

Originally Posted by meyergru

Since the comparison is done by ">=", 0028005C should still work just as good for the 2022-1 version.

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.

[meyergru]

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.

[undecided1]

Originally Posted by meyergru

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.

I agree, risk is likely negligible but I know BMW do look for lifetime codes as a reason to reject a claim, whilst perhaps unlikely it wouldn't take much effort for them to realise this 5C code is not something they would ever have supplied paid or not... I have a friend who had their nav replaced no problem by BMW under warranty whilst using a generated (correct) code, I remember they were warned beforehand if they found any lifetime code they would reject the claim. It all just seems a little more risky than sensible to me to use obviously non BMW supplied codes especially when there is zero benefit...

Anyway this was more of a heads up for Jagaer that he might want to set the fscshort to what it should be and avoid all these potential problems people might get.

[meyergru]

So glad I could not claim anything any more since my car is now nearly 10 years old...

I would never sell that car, so there is no difference, but YMMV.

[rodrigues]

bonjour ou je peux trouver le fichier Lookup.xml pour actualizer la nouvelle carte 2022-1

[meyergru]

You don't need to, the program linked here:

https://www.e90post.com/forums/showthread.php?t=1453464

always updates the Lookup.xml online from here: http://www.cicfsc.com/Lookup.xml

[Roxland48]

x6 fsc.zip

Originally Posted by Jagaer

caracartal

Repaired 1B as att.

I extracted the file 1b but as you can see the file 1b is corrupt and does not accept me to do any kind of update FSC code after I generate it does not work the machine is bmw X6 E71 2010 database Route Europe Premium 2009
vin is : WBAFG01000L337476

[opjose]

The 1b extraction does not work for Route.

[Roxland48]

Originally Posted by Jagaer

caracartal

Repaired 1B as att.

I extracted the file 1b but as you can see the file 1b is corrupt and does not accept me to do any kind of update FSC code after I generate it does not work the machine is bmw X6 E71 2010 database Route Europe Premium 2009
vin is : WBAFG01000L337476 x6 fsc.zip