I got myslef a good deal on ebay on a used KM/H Navigation-Speedo and replaced my original MPH (brought the car from the UK, now in Cyprus).

However, the speedo bought is the newer version with a scale upto 260KM/H (160MPH) vs. 240KM/H (150MPH) and has an additional LED for the DSC system in place of the CEL, the CEL is now next to the flat tyre LED.

Problem 1 is that the scale is way off, i.e. it reads the speed wrong.
Problem 2 is that the DSC lamp goes on instead of the CEL.

Now I did add $548 KM_TACHO in the FA of the car with NCSExpert and recoded the KOMBI to defaults. But that changed nothing...

I am inclined to believe the KOMBI needs reprogramming, not just coding. Any ideas or suggestions?

 

Update:

I took the car for a test-drive and the speed is reading is indeed correct! I tested it with INPA and it gave wrong speeds so assumed it wasn't working.

Also, in the CCC where I give the speed limit up to now it would always read in MPH. Since installing the new speedo, the units went to KMH, which makes me believe there is bi-drectional communication between the KOMBI and the speedo. So if I flash a newer KOMBI software version, then the wrong lamp problem should correct itself (hoping...).

 

The speedo is just a slave to the KOMBI module. So basically they are the same module.

The light position will probably not change with a software update...I bet only the coding revision date of the vehicle and/or region settings will fix the lamp positions (both of those are part of the VO string).

However, if you do get the software updated, maybe you can find the correct setting in the trace file to fix the lights.

 

-My mistake: the KOMBI was never flashed, had original factory software from 03/2007-

I will change the VO to reflect a later build date and recode the KOMBI. I have removed the region code (UK). I hope that one will help...

Update:
1. The VO build date does not affect the functionality of the KOMBI. It only changes the defaults like the permanent digital speedometer options...
2. I flashed the KOMBI to v44 ISTA level using WinKFP and after the procedure ended I finally got correctly working lights on the cluster!

So it really is the software version, the rest it automatically detects. The CCC now also lists 260KM/H maximum speed in the speed limit page, not 240 as before.

 

Interesting!!! Very, very interesting update!!

for your update #2 did you have your original build date or a later version to get the correct working lights? If your original build date is there, that means the software update must have an updated database of cluster part numbers (which defines the correct lights).

SWEET!

 

Well, I did have a later build-date in but I doubt that was any useful. Besides I am only allowed to go up to 03/2010, because later dates error with option 609, the CCC Nav.

You see the updates in the DATA folders have a history structure which takes you to the latest version available. It only uses the previously installed version to determine the current one, not the VO. Also the coding index of the KOMBI has never changed over the years, it has always been 5. So the coding options are the same.

 

I'm pretty interested on this thread. I ordered a used KOMBI from ebay for my E90. From what i've learnt, it could be impossible to reprogram the module to correct the VIN and mileage without replacing the M35080 chip. However, according to your thread, it appears that you can reprogram the KOMBI module through WinKFP and make it matching your original car data. Please kindly correct me if my understanding was wrong.

Thank you so much!

 

Let me clarify something: the MINI has a physically separate speedo from the actual KOMBI. What I replaced was only the speedo, which is known as KOMBI2 and is a slave to the master KOMBI (i.e. the actual ECU is the KOMBI).

Then I reprogrammed the KOMBI, but that was still my original module. Therefore mileage and VIN did not change. In essense a firmware update.

Now what you want to do is more difficult. You can reprogram the module with WinKFP and it will write the latest firmware, but that's it. The memory used to store mileage etc is protected and is not overwritten with the standard flash procedure. The VIN I am not sure, as you can easily change it on some other modules.

PS: I did some reading and found out that, if the cluster you buy has less mileage stored than the car, then you should be fine. If it is the opposite, then it will reset the DME to match the highest number. I suggest you just replace the chip... I replaced a similarly sized chip on my PC once and it was not a very hard job to do just be patient and careful). It is the cheapest way to do it, as the tools that can reset the chip are more expensive than the cluster :S