See if you can reach the yellow head by executing ping 192.168.68.33 (or whatever the yellow head's address is). Switch to the Ediabas/INPA computer and open a command prompt. Make a note of the yellow head's IP address on the 'Administration' > 'Connection setup' page and return to the DIS main screen. In DIS make sure the diagnostic head is shown as connected in the top right corner of the DIS screen. Now hook up the yellow head to a car and launch DIS.

If DIS runs on another computer, you'll have to change the network settings of the Ediabas/INPA computer to the same network segment as DIS and the yellow head (by default in the range 192.168.68.*). If DIS runs in a virtual machine on the same computer, that's easy - just make sure the virtual machine's virtual network adapter(s) are set to bridged mode. Do you have any clue if NCS Expert can be setup using the GT1 as its communication interface?Yeah sure, I use the yellow head myself.įirst of all the computer on which Ediabas/INPA is installed must be able to reach the yellow head over TCP/IP. Now I want to do some coding with NCS Expert/Dummy. I hope you know the following: I have a GT1 yellow head which I use with DIS and Progman. BMW did not even bother changing the file names. Jayster0966: The E53 instrument clusters are based on those from the E38 and E39. Īnyway, this is nothing to worry about as long as you do not enable function 'ACC_V_EFF_ANZ' with parameter 'kennlinie_02'. It appears the compiler BMW uses to build the module description files does not perform much syntax checking. Another erroneous parameter can be found in the E60 'ARS.C0E' module description file where parameter 'e70' of function 'SCHENKEL_V' is also one byte longer than permitted. Parameter 'kennlinie_02', however, has 21 bytes which is obviously invalid (its last byte would run into the next function).

Function 'ACC_V_EFF_ANZ' has 6 parameters, 'kennlinie_01' to 'kennlinie_06', with a data length of 20 (14 hexadecimal) bytes. This particular error is caused by a bug in the 'KMBI_E38.C12' module description file. is this critical? are the module-data wrong, or is it a problem of this module? I expect the module-data, as at this point NCS Dummy does not know anything about the car.There's nothing wrong with the module in your car or the trace file you read from it. how can I find which parameter is erroneous in the editor? On a X5 I get an '1 erroneous parameter' message when loading KMBI_E38.C12 into NCS Dummy.

Ncs expert dummy profile