[Andystobbs]

You talk about firmware levels as though they're a MAN file.
I repeat, the only way to make the CIC have C1A firmware is to flash it. You say you have done this yet your firmware is still C09 so it clearly hasn't worked.

The build date in the VO would work alongside the 609 option to establish whether NCS would target a CCC or a CIC. You're obviously getting around this anyway if you're managing to get NCS to talk to the CIC at all

[TiAgAu]

Originally Posted by Andystobbs

You talk about firmware levels as though they're a MAN file.
I repeat, the only way to make the CIC have C1A firmware is to flash it. You say you have done this yet your firmware is still C09 so it clearly hasn't worked.

The build date in the VO would work alongside the 609 option to establish whether NCS would target a CCC or a CIC. You're obviously getting around this anyway if you're managing to get NCS to talk to the CIC at all

^Indeed. I been following along but i think herbp got abit lost in the sauce.

@Herbp So i take it when you did the CIC Patcher v2 by intel123 copied the copie_scr.sh to USB inserted into glovebox it never rebooted? which would mean it didn't work. As you don't have C1A.

Anyway if you wanted to confirm what actual firmware version is actual on the CIC you must Read the ECU with NCS. It will just give you vesion info. as said above it's not actual firmware it just settings/options.

[TiAgAu]

Originally Posted by HerbP

Could my factory I Level have anything to do with the C1A update, not the current I Level? I just saw this is another post?

Thanks

Sounds like you have an ICOM? CIC upgrade to C1A is a painfull update though.

[Andystobbs]

The I level is not that important, nor indicative of the actual programming state of individual modules. An integration level is a known working set of firmwares across the modules that is tested and reliable.

Many many cars will have an I level of X but be full of older (or newer) module firmwares because people (like me) don't have ICOM so carry out updates on only the wired modules (as opposed to fibre). Or people buy a used module slap it in and it works, it could be older or newer. My car has a TRSVC and a HKL module fitted, neither was originally intended to be installed in an E9x but they work fine, I also have a converted X5 DAB CIC, works fine. I level isn't important.

[HerbP]

I went ahead & changed the factory I Level to 03-10-500. This removed the CCC from ISTA, but did not help me any as far as reading the patcher file.

Any other suggestions

Thanks

[HerbP]

Now that can rule C1A out as a problem, my next item is to study the USB port to the glovebox. The USB cord I purchased is made 180 degrees off from where it should be. I had to slide the cover off of the cable, to get it to read a portable hard drive I used for troubleshooting. I can read the USB port for the music part of the USB this way, could the wiring to the CIC be backwards? It is possible that the cable is not made correctly causing this problem? If I made a cable thru the USB port to Ethernet, could I use this to connect to the CIC to get the data persistency files?



Thanks

[Andystobbs]

How have you ruled C1A out exactly?

Don't know what you've been upto for 10 months but if I was struggling with a retrofit and knew my USB wiring was questionable I'd have replaced it within 10 days.

[HerbP]

I actually made some progress today after double checking a few things. After reviewing the VO, I had actually removed the coding for the USB port. I added that back today, along with some coding for an ULF, which I don't have. The donor car had all of the options, so I just tried anything at this point. Once I got the USB port working maybe correctly, I actually got the patcher to run, & turn the IDrive screen red. This was progress! I can get some of the FSC's to run, & some still want check? I am not really sure what the problem might be, it could be something going on with JAVA? It could also be a cable issue or the speed of the processing thru the cable? I might try to run FSTools thru the ICOM, just to see if that helps?

At least I made some progress, not sure what to try at this point?

Thanks

[HerbP]

I have actually got the 1b file pulled from the CIC. Will the 1b file only help to give map codes, or will it unlock the Nav menu on the IDrive display?

Thanks

[TiAgAu]

Originally Posted by HerbP

I have actually got the 1b file pulled from the CIC. Will the 1b file only help to give map codes, or will it unlock the Nav menu on the IDrive display?

Thanks

Map codes only.

Must activate with FSTool

Certificate Designation:
0017 - Voice control
0019 - Professional Navigation System
001B - Professional Navigation System
009C - Applications BMW
006F - Satellite Tuner
009B - Arabic

You can check whats activated by using FSC tools

[Andystobbs]

You can't remove the coding for the glovebox USB as its always installed with CIC. 6FL is the armrest USB.

[HerbP]

I don't have an armrest USB, as this is a retrofit from a 2010 650. The USB would not read, until I coded this back in.

S6FLA USB/AUDIO INTERFACE

[HerbP]

Originally Posted by TiAgAu

Map codes only.

Must activate with FSTool

Certificate Designation:
0017 - Voice control
0019 - Professional Navigation System
001B - Professional Navigation System
009C - Applications BMW
006F - Satellite Tuner
009B - Arabic

You can check whats activated by using FSC tools

Thanks I forgot that I had this program!