6.30.2016

How to get BMW halogen angel eyes as DRLs?

Share are two common methods to complete Halogen to LED DRL conversion, one with NCS expert and the other by hardwire. Follow at your own risk!

Method 1 - Use NCS expert to get the halogen light angel eyes as DRL

Here, all complete with BMW ICOM A2 emulator as well as NCS expert. BMW INPA K+DCANUSB cable is also ok. It is a good choice for E series owners.


To disable the DRL (halogen), if you have access to a NCS setup, you just disable it. If you are in Canada or any other country where the DRL are mandatory, only NCS expert will be able to do the change, not GT1. The reason is because GT1 reads the country code when connecting, and disable options that are not allowed for those country.

bmw-icom
ncs-expert

To get the halogen light angel eyes as DRL (on all the time) and still working as welcome lights, the following lines need to be looked at in the NFRM.

VERHALTEN_DRL_TFL
drl_s
DRL_TFL_MIT_BFD
nicht_aktiv
DRL_TFL_MIT_NSW
nicht_aktiv
DRL_TFL_MIT_BLK_V_GED
nicht_aktiv
DRL_TFL_MIT_SML
aktiv
DRL_TFL_MIT_KZL
nicht_aktiv
DRL_TFL_MIT_RL_BL_2
nicht_aktiv
DRL_TFL_MIT_RL_BL_1
nicht_aktiv
DRL_TFL_MIT_RL_BL
nicht_aktiv

The blue ones are the lines I had to change but I've copied the others just to make sure. Once this is done, just go into the OBC and enable the DRL - Voila!

Note that this is for cars with halogen LCI angel eyes, I'm not sure of the procedure for cars with Xenon lights but I believe it's roughly similar.



Method 2 - hardwired the angel eyes as DRL

If you want to do it the hardware way, like I did, just rewire your DRL like the schematic I put below.

I already disabled the halogen DRL, and hardwired the angel eyes as DRL, but the light output is so low, I would like to have the fog as well for safety.

When there is 12v coming from the car (flashing to pass), the 12v relay kicks in and send that 12v to the halogen bulb. When running normally, there is 6v going to the relay, but it is not enough voltage to trigger the relay, so no voltage to the bulb. The 10 ohms resistor is there to put a load and avoid the burnt light indicator. You will need to install a resistor on each side L-R, but the relay circuit can be used to feed both DRL.


For the Angel Eyes, it is similar. You need to use the red-white wire in the ECU box (red wire with white stripes). You will see many wires with that color, just use the one with the biggest size. They are all ignition 12v feeding different parts of the car. Disconnect your battery before doing connections in the ECU box to be on the safe side. Without cutting the wire, just skin a portion of the insulation, and feed a new wire in the rubber grommet into the ECU box and solder it to the red-white wire and tape it.
Again the resistor circuit needs to be repeated on both sides but the relay can feed both AEs.

I did that modification on my E46 (2004-2011) and my E53 (2011-now) and it works very well.

Attachment:
DRL circuit
DRL-circuit


Angle-eyes circuit:
angle-eyes-circuit

6.27.2016

How to use NCS Expert with BMW ICOM A2

It’s a dummy guide to help many out and try to make sense of NCS expert with BMW ICOM A2.

All said by a ICOM A2 user at bmw forum...

He said:
Before all operation, you need a good ICOM A2 emulator, clone or original
I used clone bmw icom a2 wifi at

Used it for years and updated to ISTA-D 3.54ISTA-P 3.58 in SSD... Much faster and more stable

Then, i have to mention that ALL PROCEED AT YOUR OWN RISK. This is just my interpretation for educational/entertainment value only. I am not responsible for you blowing up your car or damaging your modules.

So here goes the key point:
DUMMIES GUIDE TO UNDERSTANDING NCS AND CODING

This is roughly how it works... and my dummy interpretation of it. Please read it fully if you want to understand, this isn;t exactly a quick cheat sheet guide.

On Pre '02 cars the coding is slightly different method than Post '02 cars. I am only going to elaborate on coding individual parameters, you can go learn how to code entire modules thru the VO later once you learn the basics below.

The first part to understand is what this stuff about ZCS/VO or "vehicle order" is. When BMW makes a car, they create whats called a "vehicle order", this is basically a bunch of numbers writen into the car that tell what modules are installed in the car, regional info etc. This is like your car's DNA! for example if the car has a sunroof, or a convertible or radio etc etc and that it was meant for US,Canada,France etc. Because each car is different with a different set of options/modules or country that its located, the "vehicle order" aka. "ZCS" or "VO" may be different. Why is it called ZCS you ask? because its abbreviated german, and its confusing as hell.

The VO is written into a couple modules of the car, usually ones that start with an "A", like AKMB or ALSZ. On some cars its written elsewhere. In my 02 M3, the VO was written in ALSZ and AKMB. On my '00 328ci it was stored in EWS, KMB. Its nothing more than a string of text/numbers stored in the flash memory of these modules, nothing special. Why is it written into two places? because if one module is failed and has to be replaced, then the other will serve as a backup so you can code the new replacement module to your car. For example ALSZ is the "light switch module" in your car, for some reason it fails. When you buy a new LSZ/LCM, you can retrieve all your settings of VO from AKMB and then code your new LCM to YOUR factory settings. The chances of both modules failing is slim, but if it does... you'll have to contact BMW so they can give you the VO for your car from their records.

OK the one difference is pre-02 cars dont have a VO. Those cars have their ZCS (which acts like a VO) stored in the EWS or KMB modules. The stuff below is basically identical however for individual parameter coding.

Now go get into the basics of coding.

1. When you load NCS expert, you need to load a profile. These profiles just change how ncs expert behaves when you read your car. The two profiles i stick to are "expertmode" and "revtor's expert profile". if you dont have it, you can find it on the net easily. In order to code your car the first time, you should pick "revtors". This has something called "manipulation" enabled... ill elaborate on that later.

2. Once the profile is loaded, you basically need to select Vin/ZCS/FA in order for ncs to download VIN info off your car. Once it does this, it will ask you to select a module. Why? because it needs to know your "vehicle order" information. In most cases it will probably be in an "A" module. if it doesnt load, or cant be accessed, no harm done, just try a different module. When it is able to read it, you will see a long string next to "FA" starting with your chassis "E46_" followed by numbers and text along with #'s and $'s. This is your VO. Now that NCS Expert knows it, it can code your car properly!

CODING HAS NOTHING TO DO WITH THE MODULE YOU JUST SELECTED TO READ THE VO FROM! This perplexed me for the longest time, I didn't understand why i selected two modules each time, or what the difference selecting AKMB or ALSZ or etc the first time was. Well... It has no bearing!! all NCS is doing is reading the text/number string that is your VO off the memory in these modules in this first step. You will actually select the desired module to code in later steps.

** PRE-02 cars, you wont see the long FA "VO" string, instead there will be a few lines FG, GM, VN, SA followed by numbers, its basically the same thing different format. For all intents and purposes this is referred to by me as the vehicle order or ZCS for a pre-02 car.

ON POST-02 cars select any module with "A' in front of it, on PRE-02 the "A" modules wont work, you will need to use EWS or KMB for this step... It doesnt matter which. 

Now this guide will touch on the basics to code INDIVIDUAL items on your car. The steps to add items to your VO and code your modules is different and i wont comment on that here, because it will confuse the amateur. Just understand the basics of individual coding first, then coding from your VO will all make sense later.

3. The next part is to download your factory settings in your car to your PC. Once you get the VO loaded, you hit the BACK button. The default job in NCS is to write SO BE VERY CAREFUL here. You will see all your modules listed, for example "EWS,ABG,ASC,KMB,APL,.....etc" and underneath "SG_CODIEREN"

NCS at this point is set to SG_CODIEREN, which means to WRITE to ALL modules listed. You dont want to do that.

4. So now select "Process ECU", and select the INDIVIDUAL MODULE you want to code. For example LSZ (light switch module). Once you do this, it will say only LSZ (and not all the modules in your car).

5. Now you want to change the job from WRITE to READ. Select "CHANGE JOB", then select "CODIERDATEN_LESEN". This is to READ DATA.

6. Once selected it will confirm this by indicating the module and job type on the screen. Now you are ready. Hit "EXECUTE JOB".

It will say Coding Activ, then Coding Ended.

7. At this point, in your NCSexpert/WORK/ folder there will be a file called "FSW_PSW.TRC"

This is what we want, the coding of your LSZ module that we read earlier. IMMEDIATELY save a backup of this file, rename it to FSW_PSW_LSZ_ORIGINAL.TRC and save it somewhere incase you decide you want to revert to the original copy. Now I want you to resave another copy of this FSW_PSW.TRC file as FSW_PSW.MAN (manipulation...hint hint). Make sure it doesnt save as FSW_PSW.MAN.TXT or some crap like that, it wont work properly.

OK why all this juggling?? because NCS expert only reads modules and saves EVERYTHING as a FSW_PSW.TRC file. Regardless of what module you read in your car, this is what the filename will be. And everytime you load NCS expert, this file is constantly erased, written and re-written. So thats why we are saving it as FSW_PSW.MAN so we can alter it safely without our copy being overwritten.

8. Now open up FSW_PSW.MAN with a text editor.

You will see a long list of stuff like this..

LEUCHTWEITENREG_AUTOM
aktiv
FEHLER_BREMSLICHT
nicht_melden
TAGFAHRLICHT
aktiv

This is where you can code. now its all in german, so you will need to run these words in a translator (google) to understand it, OR you can use NCS Dummy that translates this stuff for you and gives you all available parameters, but thats a whole different program and you ought to learn how to use it.

This is what the above looks like if translated. Now you can see how we can deactivate/activate certain things. Im going to deactivate DRLs here.
Translated...

AUTOMATIC HEADLIGHT CONTROL
active
BRAKE LIGHT ERROR REPORTING
dont report
DAYTIME RUNNING LIGHTS
active 

edited...

LEUCHTWEITENREG_AUTOM
aktiv
FEHLER_BREMSLICHT
nicht_melden
TAGFAHRLICHT
nicht_aktiv

By changing to nicht_activ, it deactivates this setting. Now don’t go crazy, some codes are redundant so changing just one thing wont do the trick. This takes some time and effort to find the right code/codes to work with.

9. Once you are happy, SAVE your FSW_PSW.MAN file.

10. Open up NCS expert, load up "revtors" profile (with manipulation enabled), and reload it to the part where the VO is loaded and its asking you to process ecu (Basically steps 1-3) Look above how to do this. Once you're there, select "PROCESS ECU", select the correct module you are coding, in this case "LSZ". Then select "CHANGE JOB" and make sure you pick "SG_CODIEREN". Once this is done, you are ready to code the car.

NCS will basically now take the FSW_PSW.MAN file, and overwrite the codes in your car's LSZ module with your new settings. It only uses the MAN file because you are using a profile with "manipulation" enabled. The other mode "expertmode" does not have manipulation, and you cannot code individual stuff like this using that profile.

11. Hit "EXECUTE JOB". Wait till it says "Coding ended". Now your new LSZ is coded. Turn off the car, and restart, and check to see if your results are as expected!

12. Open up the /WORK/ folder, open the FSW_PSW.MAN file, select all, delete, save and exit.

Viola! That’s it. You are now an expert on coding individual features!



Now what do you do if you screwed it up or something is behaving funny and you want to go back to original settings. Or you cant remember all the stuff you changed, or dont like the results.

To load up the ORIGINAL factory defaults if you mess up.

Go to your /WORK/ folder. Open FSW_PSW.MAN, select all, delete, save & exit.

Load NCS Expert

Select "Expertmode" profile

Hit "VIN/ZCS/FA" to load your Chassis and Vehicle order info

Hit BACK

Hit PROCESS ECU

Select the chassis, then module you F'd up on. For example "LSZ"

On Pre-2002 cars It will say "LSZ" and underneath "SG_Codieren" along with some files LSZ.Cxx, LSZ.PRG, etc etc. SG_CODIEREN is the correct job you want.

On Post-2002 cars It will say "LSZ" and underneath "SG_Codieren" along with some files LSZ.Cxx, LSZ.PRG, etc etc. Hit CHANGE JOB, Select "FA_WRITE" Job.

"xx" is usually the specific Coding index used in your default module, its a number. think of this like "firmware version".

These files are basically from your /DATEN/ folder and contain the proper coding information specific to your car. How does NCS know which files to use? Because it knows by looking at your VIN and VO, then selects the correct files. NCS will then basically read these files, then read your VO and re-write the proper codes, features, activate, deactivate everything to your factory settings.

The job is SG_Codieren or FA_Write because you will WRITE your original settings back in.

Hit EXECUTE JOB.

Viola, your original data is re-written and your car will work again. Hopefully.


That’s all my interpretation of BMW ICOM NSC expert; hope this helps someone out there.

6.26.2016

BMW INPA IFH-0018: INITIALIZATION ERROR (solved)

Collect all customer solutions here for BMW INPA Edibas IFH-0018: INITIALIZATION ERROR. Just for sharing!! AT RISK TO TRY IT YOURSELF.

Error message 1:
ApiCheckJobStatus: Error #95
SYS-0005: OBJECT FILE NOT FOUND
API job error or no such result !
inpa-Edibas-error
Ediabas error #95 means that some INPA script (.IPO file) is requesting a result from some .prg file that does not exist. This is most probably caused by a missing .prg file.

Error message 2:
2.5 IFH-0018: Inizialisation Error
INPA doesn’t work but Toolset yet

The error occurs if a SGBD is running by INPA or CASCADE. If the same SGBD is loaded in
the Toolset it will not occure an inizialisation error.

Reason : The communications port COM1 doesn’ exist, but COM3 yet. The Toolset is
working without the inizialisation error, because the file OBD.ini exists in the
directory C:\Ediabas\bin\. But the file OBD.ini has to exist in the direcory
C:\Windows.
Solution: Copy the file OBD.ini in the directory C:\Windows or create a new one. (Creation
of OBD.ini q.v. 3.3).

Error message 3:
Edibas error:
ApiCheckJobStatus: Error #28
IFH-0018: INITIALIZATION ERROR.
API job error or no such result!
Varuantenkonrolle:
IFH-0018: INITIALIZATION ERROR. Das Programm wird abgebrochen!
inpa-IFH-0018-INITIALIZATION-ERROR
Reason: Ediabas is attempting to access port COM1. However, the port doesn’t exist, or it
has been taken by another programme (e.g. HotSync from Palm, infrared).
Solution: Install a COM1 interface or free it.

Real feedback on INPA initialization error with solution above:
Yesterday my BMW INPA K+DCAN software showed error: INITIALIZATION ERROR. killed several hours with this knock-off. The car i connected to is BMW 2011 – e92 – LCI.
To set the COM to 1, obd.ini is also COM1.
I seek help from forums and one of them provided a solution to the problem:
(solution offered by an experienced user with K+Dcan cable)
Modify the EDIBAS.INI as follows
RemoteHost
; Description : server address/name
; Default = –
; RemoteHost = Desmo16
Desmo16 being my computer’s name (note that this must be maximum 8 chars)
and
Port
; Description : IP communication port
; Value : 1000 < port < 30000
;
; Spezialfall OP(P)S /ICOM:
; Value : 6801 ;OBD-Treiber (CAN)
; Value : 6802 ;Most-Treiber
;
; Default = –
; Port = 6801
OBD2 notice that you should be sure port is 6801 as mine was 3000. It worked like a charm after i made these mods.

6.23.2016

How to do BMW E9x FRM Coding

Question:

currently I am trying to fix a FRM3 module, therefor I have flashed the µc already and finally receive a PT-CAN signal again. The module was completly dead before due to corrupt eeprom.

My question is: Is it possible to do coding and programming on the workbench without installing it in a E9x ?
Do I really need a junction box electronic or is it possible to hook it up on the right can interface and do the programming?

CAN adapters for a bus simulation are available.


Well, I connected KL30 and KL31 of course and KL15 for ignition. The unit starts and outputs stuff on the PTCAN and then goes to sleep.

Connecting my DCAN onto PTCAN (obviously) doesn't work. I am not really familiar with the OBD interface but there are also some K Line and L Line pins, which I am not able to use because the FRM doesn't address them.

I guess I have to input the ignition signal as can frame but on which can? PTCAN or KCAN?

There is some guy on YT updating a MS45 on his desk with some kind of OBD Adapter. Does someone know what the name is? I guess I am not allowed to submit a link but you can easily find it.

Why all of this? I don't have a E9X car anymore. I have this FRM left which I would like to repair and get rid off.


Solution:
you need KCan - high and low. Here is scheme the from ISTA.
frm-coding

in the car:
D-Kan ( high and Low) from OBD connector goes to JBBF and from JBBF K-kan (high and low) to FRM.
you need use an adapter: D-can - K-can,


get the JBBF as well

it is kind of tcp/ip router between different networks in the car


You just need a Gateway /Body Module from say an E60, connect pins 8 & 9 of X16760 on the body/gateway to the FRM pins 45 & 46 on connector X14260 (K-Bus High & Low) . You can connect to the diagnostics output on the Body/Gateway module ( i haven't got the pin number to hand but i will check tomorrow). You need to apply a permanent 12 volts to the CAS input (pin 12 of connector X14261) on the FRM module otherwise it will shut down after a few seconds. I have used a setup like this for a couple of years now without any issues, i use all the BMW coding tools 2.12 coding software on it.


Results:

I am just now working on it and got some results:

Connected everything, FRM is running, KCAN is sending instantly.
I have checked the messages with a CAN Adapter, they seem valid.

I really need a JBE for the address translation between the different CAN's.
Are you sure I can use one from a E60? As far as I know a E60 doesn't have a FRM. The light is managed by the LCM.

6.22.2016

2015.10V BMW ICOM ISTA-D not connected (solved)

Problem:

I bought the 2015.10V BMW ICOM windows 7 HDD with ISTA-D 3.51 ISTA-P 3.56.


Packaged delivered fast within 5 days, the ISTA I use on Lenovo T420 the ISTA-P it working perfect but ISTA-D not connection and also the screen of ISTA-P is small (Picture attached ).
bmw-icom-small-screen
Solution from obd365.com:
  1. For the ISTA-P Screen Small Problem ,  please ICOM laptop do self-testing,checking if the device can connect ICOM system
  2. The ISTA-D not working, the picture showing it is your firmware version is old. Need update BMW ICOM A2 firmware to the latest version V1.40
I followed their suggestions and updated the ICOM Firmware to 1.40 , now everything is okay and working now !


6.14.2016

BMW E89 CIC Retrofit by K+DCAN & NCS EXPERT

Good news! BMW E series CIC retrofit coding success!! Share the instruction here on BMW E89 CIC retrofit with BMW INPA K+DCAN INPA cable & NCS EXPERT software.


NOTE:
Try at your own risk!


You need:

BMW INPA K+DCAN cable (i used 2016 version with a switch)
working NCS EXPERT software
valid daten files for your car

bmw-inpa-k-dcan-cable


Model:
BMW E89
(this method applies to all BMW E series)

BMW CIC retrofit coding procedure:
connect the BMW K+Dcan cable to the car
read VO

program CAS and FRM/ NFRM for CIC retrofit

run NCS EXPERT software
select File-> Read Profile
select Expert mode
select-expert-mode

press F1 or click the VIN/ZSC/FA button
press F3 or click the ZSC/FA| ECU button
select CHASSIS: E89 for E9x models
select chassis e89
then select ECU: CAS
note: VO on CAS and FRM pr NFRM needs to be changed
select cas

then get the car details identified (CHASSIS, FG, FA)
press F2 or click the Enter FA button
select CHASSIS: E89
check VIN and click OK
enter vin

highlight old build date
e.g. #0607 add press delete
(keep note of your build date)
add build date #0909 for E9x CIC.
add 0909 for fa

later date needed for combox (possible #0910)
add &6VA and press OK
add 6va

press the BACK button
then press PROCESS ECU
note: avoid Process car as it programs every module (RISKY), and not needed
select ECU: CAS
press CHANGE JOB to: FA_WRITE)
check for FA_WRITE and EXCUTE JOB
FA-Write

press CHANGE ECU
select ECU: NFRM
note: FRM module or NFRM depending on model
EXCUTE JOB again to make sure FA_WRITE and correct module selected
excute job

coding done!!

now to make sure the coding went well in the new VO and the CAS, FRM/ NFRM

again, run NCS EXPERT software
select File-> Load Profile
select Expert mode
press VIN/ZSC/FA
press ZSC/FA| ECU
select CHASSIS: E89
select ECU: CAS
press ENTER FA
select CHASSIS: E89
check VIN and click OK
!! check build date #0909 and &6VA you added just now
then press BACK
press ZCS/ FA f. ECU
select ECU: NFRM
press ENTER FA
select CHASSIS: E89
!! check build date #0909 and &6VA you added just now

coding done & verified!

now to default coding the CIC unit to recognise your cars features, such as AS PDC, Bluetooth...

again, run NCS EXPERT software
select File-> Load Profile
select Expert mode
press VIN/ZSC/FA
press ZSC/FA| ECU
select CHASSIS: E89
select ECU: CAS
press BACK
process ecu

press PROCESS ECU
select ECU: CIC
note:
CIC now should be displayed in the list of modules
select cic

press CHANGE JOB to make sure that SG-CODEREN is selected by JOBNAME

SG-CODEREN

check and press EXCUTE JOB
the CIC unit will reboot and load up with all of your options
cic reboot


note:

NAVI and VOICE/ DVD in motion have to be activated in other ways

6.09.2016

Rewrite VIN to used EGS on E36 with BMW ICOM

Problem:

So one of my first jobs (on my own, been a BMW tech for 20 years) has given me a challenge. Trans MIL light on, BMW 328i E36 is obviously in limp mode. He had second hand EGS fitted. I refitted original EGS, connected Rheingold with ICOM and got CAN communications error. No signal from DME, and in live data RPM and load signals are 0%.

DME has CAN fault relating to EGS also. DME has RPM and load signals no problem.

I could clear CAN fault in DME if I disconnected EGS and that suggests EGS (as per instructions in Rheingold). Also did Ohms test on pins 86,85 on EGS (CAN H and CAN L) and the lines checked out OK.

So opened up original EGS and found one small chip to be suspect, like overheated solder joins. I checked against 2nd hand EGS and looked quite different.

So now I want to recode 2nd hand EGS to this cars VIN. I only have BMW ICOM A2 head currently. I have recoded a E39 DME before using the yellow head and SSS but i don’t have access to that equipment anymore.

Is it possible to get used EGS working on this car? With ICOM and maybe Winkfp or something?



Customer solution:

For sure you could use BMW ICOM with WinKFP to recode the EGS. Just go to comfort mode, ZUSB Update and enter VIN. Then Program ZUSB Update and the VIN should be changed.

Use OBD_ab625 of ICOM. Open WinKFP and pull down the setting menu. Make sure to check boxes to write UIF/AIF in comfort mode. Also from this menu enable BSU (boot sector update) force programming in comfort mode and fast baudrate. Also enable the option to test checksum. Close the menu and save the settings.

Choose comfort mode > update ZUSB >choose EGS > enter VIN (full 17) and finally Program update. Accept the dialog for remaining writes to the user information fields.