![]() ![]() Now a 17KB FSW_PSW.TRC file is in your work dir. Select VIN/ZCSFA -> ZCS from SG(f3) -> Chassis E60 -> LMA -> back -> Process ECU -> CIC -> JOB -> Codierdaten_Lesen (read coding data) -> Execute Job ![]() Select File -> Load profile -> Expertmode -> OK It takes a long time manually.Ĭode CIC to make it work properly in your car (E60) (this should be already done) and then read the coding and save it somewhere. Taking E60 coding file and adding (changing) the combox parts which are in the E90 coding file will be best way. Now compare both coding files of your CIC and merge the data so that it works perfect with your E60 again. #E90 coding ncsepert PcNow read the coding from you CIC again and store it somewhere in your PC (E90) But COMBOX and CIC work perfectly together. Now the CIC will not work 100% in your E60. Code Combox and then the CIC with E90 SSD File (virtual VO) to make them work together (in an E90) one by one Read coding and save it somewhere on your PC Code CIC to make it work properly in your car (E60) If your situation is different you have to convert these instructions. #E90 coding ncsepert codeNever code the whole car with a vehicle order of a SSD-File.Įverything is written as if you retrofitted CIC and Combox by replacing the existing CCC and TCU in an E60. ![]() When using NCSEXPERT to code your modules, take care that you code each module you want to code one by one by, choosing the module you want to code in ncsexpert ONE BY ONE. So for example coding a F02 TV-Module (ECU Address 09) will not be possible to be coded in an E60 which identifies the TV-Module at ECU address 4B. ![]() Nevertheless, the ECU Address must be recognized by your car gateway. With this trick you will be able to code any ECU, which does not belong to your car. This trick will make it possible to code an ECU in a car, although it was never an option of the car configuration. So if you make a SSD-File for an E90 Car, you cannot add for example $611 for Night-Vision, because there was never a configuration E90 and Night Vision. However, you still have to make sure, that this "virtual vehicle order" has to be a valid one. In an SSD-File you can configure your "virtual" vehicle order and code the ECU’s (alltogether or just a single ECU) which are in the Vehicle order (written in the SSD-File). However, you will be able to bypass this, by using SSD-Files with NCSEXPERT. and so on.Įrgo, if combox was never released to E60, you will fail coding it with NCSEXPERT the normal way. So "if car is E90 and Build date is > 03/2010 and SA $6VC is present" then "ECU XX" is combox. The BMW scripts are smart enough to know if there is a combox in your car just by reading the build date and the vehicle order and the car model. #E90 coding ncsepert how toThe scripts of the BMW tools just do not know how to handle the combination of ECUs which are not an existing configuration to order from BMW. You can add to your vehicle order what you want, you will not be able to recognize the ecu combox for coding if you make it the usual way (adding it to vehicle order). This is because the combox was never planned to work with E60 models. So if you retrofit a combox to your e60, you will never be able to code it, or retrofit it. You must understand that you cannot code ECUs (modules) in your car, when it is not usually equipped from factory with your car with BMW tools. All inclusive from scratch Īfter wiring everything together you need to code the CIC and the Combox in order to make them work properly together in your car. Lets make sure you followed these instructions when you created your merged files. I really think the merged file is more likely the problem. ipo files which are located in C:>SGDAT folder, then the. To insure you have all the 45 updated files, you ned 45 DATN (which you did), updated. You code the merged file as normal using what you created as replacement in the E60 folder Not positive it can yours the error message you indicated, but you cannot code it with a DVD in the slot Having a DVD in the CIC will cause an error message. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |