You are looking to get the result, "OKAY." Any other response indicates that the job did not execute successfully. Once the job runs, another window will be brought to the front of the screen and will indicate job status. If the job does not execute properly, you can try ticking this box. The checkbox for "Data" does NOT need to be checked off. Step 6: Now enter your lamp ID or "argument" into the field. About a 1/3 of the way up from the bottom, select the job "_reset_kurzschluss_sperre." Step 5: Once you have your lamp ID(s) ready, you can select the "Select Job:FRM_XX" window and on the left side, you will see the available jobs for your control unit. FRM_70.prg IDs may be different but the translations should be the same. I have attached this list below and translated it into English for the FRM_87.prg group file. Note the lamp ID(s) for the fixture(s) that is(are) out. These IDs are the arguments you need to enter to execute your job. This table lists the lamp fixtures (right) and their corresponding IDs (left). Step 4: Navigate to the window labeled "Tabellen-Info." In the drop down menu, select "LAMPNRTEXTE." maybe different for you. Select the small button in the top left corner that looks like a folder with a curved
A photo of the 4 windows is attached at the bottom of this post (1 Open.jpg)ģc. After the file has been loaded, you should see 4 different windows open. This can be done one of 3 ways described below. You MUST be connected to the car to load SGBD or Group files! Otherwise, you will get IFH-0018 or IFH-0009 com errors and blank windows. Interface does not matter (ICOM, DCAN, ADS, ENET, etc.) as long as it's setup properly in the EBIABAS.ini configuration file. It will probably result in an IFH-0018 error if it cannot load the group file/connect to the module properly. You will probably know right away because Tool32 might not even load the tables after opening the group file in step 3. So I'm assuming this group file will work for FRM3 modules. NOTE: I have not reset a short circuit counter on an FRM3 module yet but the same group file is used in INPA to read/erase faults, run activations, display live data, etc. The default location for these files can be found here: C:\EDIABAS\Ecu\
Unfortunately, I do not know the group files for the LM modules but this can be quickly and easily found through trial and error. These group files can be used for any chassis that uses an FRM module. That will obviously tell you what FRM module your car has.įirst off, these are the files that correspond to their respective FRM revisions. There should be something like FRM2_E89.Cxx or FRM3_E89 in one of the readouts in NCS Expert.
Apologies to whoever I stole the following from, I forgot to keep the URL:Ĭonnect to your car, load NCS Expert > Expert Mode > Chassis (E89) > VIN/ZAS > Process ECU (select CAS) > press BACK > Process ECU again (scroll down to NFRM) > Change Job to CODERIEN_LESSEN > Execute. If that's the case, it will have to be reset in the FRM.
Start by pulling codes with ISTA or another BMW-capable scanner, looking for a 9xxx code such as 9CBB. A broken wire is possible, but a stored FRM fault is more common.