9th May 2012, 01:30
|
#7
|
|
m5board.comoholic (>1000 posts)
|
-Having a DVD in the CIC will cause an error message. Not positive it can yours the error message you indicated, but you cannot code it with a DVD in the slot
- You code the merged file as normal using what you created as replacement in the E60 folder
- To insure you have all the 45 updated files, you ned 45 DATN (which you did), updated .ipo files which are located in C:>SGDAT folder, then the .prg files, located in C:>Ediabas>ECU. All these should be ver 45 in your case
I really think the merged file is more likely the problem.
lets make sure you followed these instructions when you created your merged files. All inclusive from scratch;
After wiring everything together you need to code the CIC and the Combox in order to make them work properly together in your car.
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.
So if you retrofit a combox to your e60, you will never be able to code it, or retrofit it. This is because the combox was never planned to work with E60 models. 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). The 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.
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. So "if car is E90 and Build date is > 03/2010 and SA $6VC is present" then "ECU XX" is combox... and so on...
Ergo, if combox was never released to E60, you will fail coding it with NCSEXPERT the normal way.
However, you will be able to bypass this, by using SSD-Files with NCSEXPERT.
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 still have to make sure, that this "virtual vehicle order" has to be a valid one.
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.
This trick will make it possible to code an ECU in a car, although it was never an option of the car configuration. (COMBOX in E60 being your example)
With this trick you will be able to code any ECU, which does not belong to your car. Nevertheless, the ECU Address must be recognized by your car gateway. 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.
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.
Never code the whole car with a vehicle order of a SSD-File.
Everything is written as if you retrofitted CIC and Combox by replacing the existing CCC and TCU in an E60. If your situation is different you have to convert these instructions.
-Code CIC to make it work properly in your car (E60)
-Read coding and save it somewhere on your PC
-Code Combox and then the CIC with E90 SSD File (virtual VO) to make them work together (in an E90) one by one
-Now the CIC will not work 100% in your E60. But COMBOX and CIC work perfectly together. (Combox E90 CIC E90)
-Now read the coding from you CIC again and store it somewhere in your PC (E90)
-Now compare both coding files of your CIC and merge the data so that it works perfect with your E60 again. Taking E60 coding file and adding (changing) the combox parts which are in the E90 coding file will be best way. Don't be confused. It takes a long time manually.
Code CIC to make it work properly in your car (E60) (this should be already done) and then read the coding and save it somewhere.
Start NCS-Expert
Select File --> Load profile --> Expertmode --> OK
Select VIN/ZCSFA --> ZCS from SG(f3) --> Chassis E60 --> LMA --> back --> Process ECU --> CIC --> JOB --> Codierdaten_Lesen (read coding data) --> Execute Job
Now a 17KB FSW_PSW.TRC file is in your work dir. Save it somewhere and rename it to make sure you can find it again.
This file contains correct coding data for E60 making sure your cic works propperly in your E60, if you write it to your CIC.
Now code COMBOX and then CIC with E90.SSD file so CIC and COMBOX would work propperly together in an E90 with this virual Vehicle order. Code the devices "the usual way", just instead of reading the VO from ECU(F3) read it from this SSD-File!
The more the VO of E90 matches the VO of your E60, the less you have to change while merging the coding files together... However, the best is leaving it as it is, if you do not know what you do.
After that read the CIC and the COMBOX Codings as described above, and you should get a 17KB file for CIC again (This time with E90 Coding and correct COMBOX settings) and a COMBOX coding file of 5KB. Make them safe aswell.
To get combox work propperly in your E60 you have to make a new coding file for your CIC out of these 2 (E60+E90) CIC coding files. I call that merging.
You have to leave all E90 specific codings alone and just replace the combox relevant ones to your E60 CIC Coding file.
This will take a lot of time, but has to be done. Open your E60 Coding file and your E90 Coding file and compare the codings one by one. Allthough the codable options are the same, some of them will be on different positions (lines) in the file, which makes it more difficult to compare. So get tools which can help you!
For example like this:
Get a powerful texteditor like ultraedit.
make a searchandreplace: Search for LF/CR(enter) like in the screenshot
and replace by
Now sort e.g. Alphabetically.
Then replace by LF/CR(enter).
If you do this on both files, you have 2 files you can compare much better: Read posts #73 and #74
Thats as detailed as it gets.
What isn't working that has you doing this if you're 99% there?
|
|
|
Linear Mode
