topblog Ivoire blogs


Change Bluetooth voice control language with NCS Expert

Here’s my story of voice recognition language change after the new MULF Bluetooth module installation:

Before I even start, people, don’t use SSS/progman for anything, the software is a joke. Winkfp, ncsexpert are much better alternatives.

I have a 2006 325i Sedan.. My bluetooth module died (Non i-drive car) . I used realoem found the part I need, ordered it etc etc Fitted the part everything was good, except when I pressed voice recognition it started talking to me in German. But I don’t speak German. Need to change the language

I looked through countless threads with everyone saying, this can’t be done, bimmernav ripped them off blah blah etc. To this today, I though it was over and I would just have to get use to it in German.

But then

I thought I would give NCS Expert one more go since, I updated a lot of files from V41 daten stuff. Anyways this time I clicked on the MULF module, dumped the TRC file, opened the TRC file and guess what is the first line.


So I save the file over the man file, change the deutsch to


Do the code.

Press the voice button and the most beautiful words come out. Please add telephone

For those of you reading this that are going how do you setup NCS expert and use it. I really can’t help. I’m ultra noob at it as I just started using it and I had to keep flicking back and forth through the doco as I was doing this.

IT CAN BE DONE :)))))))))))))))))))

Also it would be great if someone could have a look and tell me what any of these other options are as I don’t speak German <img class="emoji" draggable="false" src="" alt="


How to solve Kess v2 ksuite “Protocol not compatible”

Here is a customer solution of Kess V2 Ksuite v2.22 protocol error “Protocol not compatible with version FW”. Put it for sharing. Wish it helps anyone.


The customer bought SE87-C (kess v2 master v4.036 ksuite v2.22).
He got the error message“Protocol not compatible with version FW.”when trying to read a Audi 2,0tdi 2007 BRD engine. Ecu: Siemens PPD1.3 I
I have test software version 2.06-2.22 same problem.

kess-v2-ksuite-v2-22-protocol-error-1 kess-v2-ksuite-v2-22-protocol-error-2

Then the customer have successfully solved the Kess v2 protocol error himself.


He said as below:



“I have solved the protocol error myself.
Here is how: I installed the ksuite 2.06 full, then copy the ksuite 2.08 who is in the token reset folder that has the firmware's in update folder into my install directory. (like you do in the video for the ksuite 2.08)”



(BIG thanks to Konstantinos Raptis)



(solved) Vocom + Tech Tool view DTCs of MACK truck

I'm have a MACK to read faults, but unluckily I failed to diagnose (view DTC's) or use any off the other features of my Tech Tool 2.04.87. PTT says the software is incompatible and that version on the control unit(s) is not supported by Tech Tool.

Here is my version info:

Product: Tech Tool
Version: 2.04.87
Database: Standard

Last updated: APCI (-A) 11/8/2016 12:19:36 PM
Last updated: APCI+ (-A) 9/14/2016 1:56:29 PM

Every time I go to view DTC's I get these errors :
it says: the version of software installed in the engine and vehicle electronic control units are incompatible. Electrical faults will present in one or both modules. Upgrade the software in one or both modules to correct the problem.


then i Click OK and get this one:

Software on the control unit(s) below is not supported by Tech Tool.

Please update Tech Tool and try again.

144 144


Then ask obd2express for help.. solved my issue

I am advised to update the firmware of 88890300 Vocom Interface. Just follow the screen message to do that. Then tech tool works like a charm.

BIG thanks to