Inpa 5 0 2 Ncs Expert
How To Install INPA & NCSExpert 50sKid. Unsubscribe from 50sKid? BMW E60 5 series How to code AUX in Idrive ncs expert step by step - Duration: 12:00. BMW INPA Download & Install on Windows XP/ Vista/ 7/ 8/ 10. Posted on January 18, 2017 by sales. BMW INPA Ediabas 5.0.2 download, inpa 5.06 download, inpa 6.4.7 download hereand install it on Windows XP/ Vista or Windows 7/ 8/ 10 (32bit or 64bit), to get it work with K+DCAN USB cable. Links to BMW Standard Tools 2.12 and NCS Expert. Dec 14, 2016 - You can use 7-Zip (free software) for this purpose from here. On DVD you will find EDIABAS 7.3.0, INPA 5.0.6, INPA 5.0.2, NCS Expert, WinKFP, device drivers, installation instructions and other useful tools. Please note, that latest INPA 5.0.6 is not completely translated into English. Older INPA version 5.0.2.
I recently purchased a PA Soft BMW Scanner program 1.3.6. Hppt://www.bmw-scanner.com It has limited capabilities.
It scanned my car, let me rewrite the odometer and VIN to a new LCM, but it does not have the reprogramming capabilities like the later 4.1.0 version. The newer version connects only via the OBDII connector and may not be able to communicate with my car (a 2000 323i) because it has the 20-pin connector under the hood.
All the coding information it read was useless because there's no way to interpret it. The error codes are useless because it does not tell you what they mean. Absolutely no instruction manual and the one document I found on-line is so poorly written (Is this english?), it is imposible to made heads or tails out of it. I would have to say don't bother with it.
I just got a ODBII cable to usb and PA soft 1.4.0. I plan on using the cable and various programs to try to figure out the whole auto windows up with key fob reprogramming for my car.
I plan on doing this next weekend when I'll have three days to work on it. In the mean time, I'll be loading programs and testing connectivity from car and computer. The only problem I see now, is that most of these programs require serial port connection to OBDII and not usb. Might have to purchase a different cable and a usb to serial port connector.
I'll post what I'm able to do if it works or not, to assist others who are trying so that we can all make heads or tails of this. Thanks for the thread start. I too need a cable that will work with EDIABAS/INPA. I have Carsoft that has a cable but it won't work with the other programs. I just want to program my ABS module. Like you, I'm realizing belatedly the Carsoft 6.5 serial-port cables stink; and, like you, I also need a good cheap reliable INPA/EDIABAS USB cable source for my E39. The main reasons the Carsoft 6.5 cables stink are:.
They don't (easily) work with the INPA/EDIABAS tools. They are serial port only (yuck - what we need is USB operation) So you and I (and practically everyone else), both need a good source for the INPA/EDIABAS USB cables. This site sells a the latest 'INPA/Ediabas K+DCAN USB Interface' cable for a and says it 'Works with INPA, SSS, Progman and others'; but my E39 doesn't need D-CAN capability so I should be able to make do with a less expensive INPA/EDIABAS cable. I'm not sure if my E39 needs K-CAN or PT-CAN (I need to add these to the glossary above, whatever they are) based on what this cable purports to support. Quote: Features: - Connects to USB (built in 1,5m long USB Cable, creates virtual comport) - Double K-Line support (See Screenshot) - High Speed D-CAN and PT-CAN support (500 kbit/s) (See Screenshot) - Low Speed PT-CAN support (100 kbit/s) - Battery voltage detection by control line (See Screenshot) - Ignition voltage detection by control line It may be useful that the website lists compatibility as ' (all functions as in OMNITEC interface)' so 'Omnitec' is yet another keyword we need to put in the glossary. Can someone clarify the cable options for the E39 using these diagnostic tools? Note: This may help to answer the questions (I'm in the process of reading it).
Quote: #1: You need a cable that plugs into the OBD port. Many people have had success offering $85 including myself. This is the cable that works consistently, including 2011s.
(update I heard lowest price is $90 now) #2: Download the programs required for coding (NCS Expert, INPA, EIBAS) all files needed #3: A simple DIY guide to get started #4 (Optional): You will need newer daten files for NCS Expert to code 2011 CICs (iDrive). I was able to read a 2011 CIC with v39 daten files. This can be found in newsgroup and/or bittorrent sites. Or here's one from from rapidshare: Update instruction from: In each “sp-daten-Exx” folder in the subfolder “daten” find a file “laden.bat” execute this.bat file and your ncs will be updated automatically with the new data for the corresponding model. Or u can do the following copy-paste procedure: Target -Source.(SP-Daten-Exx directory from ISTA-P) NCSEXPER SGDAT -.ipo files NCSEXPER DATEN - coding data (daten) for models EDIABAS Ecu -.prg files.
Please make sure you make a backup of your EDIABAS ecu folder. When you get error message from NCS Expert that you have a 'Version' problem, you need to put your original prg file back to EDIABAS ecu folder. The question for E39 users is where to get a CHEAPER cable (since we don't need the D-CAN cable)?
Stuff deleted. The question for E39 users is where to get a CHEAPER cable (since we don't need the D-CAN cable)? An ebay search on 'bmw inpa' turns up over 100 cables. Serial port versions price + shipping start $25 and most also include a round 20 pin adaptor used up to '98 (or so, I think) in addition to the OBD connector. USB versions $45 but none seem to have the 20 pin adaptor; OBD only.
If you need it the 20 pin adaptor too, search 'bmw obd' It will turn up 2000 items. Sort by price + shipping - all the less expensive items are 20 pin round to OBD adaptors for $5 to $10 delivered. As noted above, E39s do not need the D-CAN version which started around 2006 (I think, but not sure) D-CAN versions start at $60. So far as I know, D-CAN cables also support the K-line that E39s use. As noted above, E39s do not need the D-CAN version which started around 2006 (I think, but not sure) D-CAN versions start at $60.
So far as I know, D-CAN cables also support the K-line that E39s use My frustrating problem is that I can't make any sense out of the cables (yet)! Normally I'm good at searching - but - in this case, searching just brings everyone's confusion to the fore! Including mine. Taking your post as my starting outline, are 'these' the available E39-related cable types?. Carsoft 6.5 cables (RS232 only, ADS + OBD1 + OBD2 connectors). INPA/EDIABAS cables (OBD2 connectors + adapter for ADS interface).
INPA D-CAN cables (OBD2 connectors only). to. Quote:: K-Line only cable: All K-Line cars All Double K-Line cars No D-CAN cars K+DCAN cable with PIN 8 connected: All K-Line cars All Double K-Line cars D-CAN cars without Ethernet interfaces, i.e.
Cars produced from 9/06 or 3/07 (depending on model) up to but NOT including 3/09 K+DCAN cable with PIN 8 disconnected: All K-Line cars All D-CAN cars No Double K-Line cars (except with an adapter) The reason is that cars from 3/09 onward have an Ethernet interface on Pin 8, and if the car detects a signal on that interface, it drops the D-CAN connection that's being used for coding. A cable with Pin 8 already disconnected (or desoldering it yourself) solves that problem but breaks Double K-Line because BMW used Pin 8 for Double K-Line back in the day. Unfortunately that recycling of Pin 8 means there's no universal cable, so it's something to be aware of. Some vendors sell an adapter that will allow you to code Double K-Line from a cable with Pin 8 disconnected though because the adapter bridges Pins 7 and 8, so that's how you'd get truly universal coding if you need it. However, I don't know of a way to block Pin 8 without desoldering. QUOTE=bluebee;6260670My frustrating problem is that I can't make any sense out of the cables (yet)! Normally I'm good at searching - but - in this case, searching just brings everyone's confusion to the fore!
Including mine. Taking your post as my starting outline, are 'these' the available E39-related cable types?. Carsoft 6.5 cables (RS232 only, ADS + OBD1 + OBD2 connectors).
INPA/EDIABAS cables (OBD2 connectors + adapter for ADS interface). INPA D-CAN cables (OBD2 connectors only).
to. That sentence confuses me because I don't know what a is (yet) but I had thought that the E39 didn't use D-CAN. So I'm going to have to add these to the glossary in post 1 so we can make some sense out of the words ' and 'D-CAN'. Image deleted. /QUOTE Bluebee Sorry I threw you a curve with the reference to K-line. What you need for your 2002 is an OBD cable that claims BMW INPA compatibility. Although it may not be stated these will be K-line cables.
Your 2002 does not have the 20 pin round plug (commonly called ADS) used in earlier E39s. If you wish, buy the more expensive D-CAN cable so you can connect to newer models too, they are backward compatible. There have been about a dozen signalling protocols commonly used by various manufacturers for OBD and OEM proprietary ports. The various protocols use different pins in the plug. For the E39, BMW chose a protocol that uses the so called K-line; one of the ISO 9141 versions I think. The more recent models use a flavour of CAN, which also/still uses the OBD port. The most recent BMW models have an additional port, MOST, which is a very high speed fibre optic system.
Models with MOST still have the electrically based OBD port for diagnostics as mandated by law. Some people use ADS as shorthand for the 20 pin round plug found in the engine bay on earlier E39s (and other models) before OBD was mandated by law. Apparently this terminology is not accurate. I've seen expanations that ADS is a diagnostic head used by BMW, but since it was used only with the 20 pin plug the the association has become established. Some, but not all, early E39s with the 20 pin port need virtual ADS software (trick EDIABAS, INPA, DIS, etc. Into thinking an ADS head is attached) in order to access all modules in the car.
The BMW dealer systems use a diagnostic head (there have been several versions over the years) which has provision for additional leads that turns DIS into a full featured, multi-function voltage, current, oscilloscope, etc. Diagnostic system in addition to DTCs, coding and programming. These heads cost hundreds to thousands; only the exceptionally keen DIYers go to the expense. It seems to me that the reference to INPA is used for the following reason.
The only 'tricky' part (and it is actually easy if you follow the instructions) getting started is configuring EDIABAS for the cable you have. EDIABAS is automatically installed with INPA. Once EDIABAS can talk to the car through the cable all the BMW software can: INPA, NCS Expert, WinKFP, DIS, Progman etc. Since INPA is simple to install, does not require configuration itself and won't change anything other than clear DTCs and adaptation values, INPA is an easy, safe method to verify that you're in business for any of the BMW software.
I've no experience with other cables. But people in the diagnostic software forum describe how Carsoft, Modified VAGcom KKL, J2534, etc. Cables can be made to work on BMWs with varying degrees of customization and difficulty. If you subscribe to the KISS philosophy, buy 'BMW INPA' compatible cables; OBD only or with extra 20 pin round adaptor (that plugs into the OBD cable) depending on the car's model year. Now THAT's the kind of simple summary I need! As long as they're backward compatible, that makes sense.
However, I 'thought' from the reference prior, that cables were mutually incompatible! It seems to me that 'universal' in this context means every model from 1990 through 2011. I'm interested only in my E39, the BMW INPA cables will work. I'll cross those other model bridges when I come to them I'm sorry I'm so dense. You're not dense. This is a complicated topic and there is no single comprehensive description, at lease that I've found. Lots of jargon, and many people that have mistaken concepts that add to the confusion.
Here's hoping I'm not one of them This is all ( only very slowly) starting to make sense. Just like dealer equipment went through something like these iterations:. MoDiC = GT1/DIS = GT1/DISplus = SSS/Progman = SSS/OPS = SSS/OPPS = ISIS = ISTA There might be a transition in standards of something like: OPS and OPPS are newer diagnostic heads, not software versions I think ISIS is the BMW software control system - automatic updates. Implemented long after E39s. ISTA/D and ISTA/P is the new, current, dealer level software. ALDL = ADS = OBD1 = OBD1.5 = OBD2 = K-line = CAN = D-CAN = MOST = BYTEFLIGHT K-line is an indirect label for several protocols that are used through OBD ports.
CAN and D-CAN also work through OBD ports. Again, this is ( all too slowly) starting to make some sense. These are apparently the 'K-Line' protocols our E39's use:. Chrysler, European, & Asian vehicles (including BMW E39).
pin 7: K-line (K-line idles high, with a 510 ohm resistor to V batt). pin 15: L-line (optional). KWP2000. pin 7: K-line.
pin 15: L-line (optional) I don't know for sure which protocol BMW uses. What I do know is that EDIABAS understands it and will work with E39s. While these are the other protocols:. All vehicles sold in the US as of 2008. (250 kBit/s or 500 kBit/s). ISO 15765. pin 6: CAN High.
pin 14: CAN Low. Standard of. J1850 PWM. pin 2: Bus+.
pin 10: Bus–. High voltage is +5 V. Standard of.
SAE J1850 VPW. pin 2: Bus+. Bus idles low. High voltage is +7 V.
Decision point is +3.5 V Ah. This is good to know. I wasn't aware of this (I thought the 'cables' were the diagnostic heads). I see now that the cables are the poor-DIYer's diagnostic head. The diagnostic heads handle lots of other stuff that we poor-DIYers don't have, such as oscilloscope probes. Also, your list above is not comprehensive.
There are lots of other protocols in use. But why worry about them? EDIABAS/INPA works for out E39s I 'was' wondering why the cable is often called an 'INPA cable'.
I'm still a little confused whether we should install the 'factory' software (i.e., I NPA/EDIABAS, NCS, NCSExpert, NSC for Dummys, NFS, Toolset32, WinKFP, etc.) or the dealer software (i.e., DIS, DISplus, EasyDIS, SSS/Progman, CIP, OPS, OPSis, ISIS, ISTA, etc.). It depends on what you wish to do. One of my prior posts lists capablilities. For your door locking, either NCS Expert (+NCS for Dummies) or EasyDIS or Progman. INPA, NCS Expert and WinKFP are easy to install.
NCS Expert and WinKFP have little documentation and can f.ck things up if you make a mistake. As in the car won't run until I figure out what went wrong & can I fix it. BTW, WinKFP is used to update programming in the modules. If it fails on an update for whatever reason, you may have to buy a new module. EasyDIS and Progman are tedious to install but user friendly; little chance of converting your car into a 2 ton paperweight. As the adage goes: you pays your money & you takes your choice.
Don't know what NPA is. So far as I know, Toolset32 is a front end menu system for selecting between INPA, NCS Expert, WinKFP. I haven't installed it so can't comment much. CIP is an acronym for Customization and Individualization Programming. CIP is not software. All the options offered can be set/changed by NCS for Experts, EasyDIS and Progman. OPS is one of the diagnostic heads, not software.
OPSis - not heard of it. OPPS is also a diganostic head. ISIS and ISTA are current dealer software. Not available 'in the wild' i.e. To us DIYers This is good great to know. I think what you're saying is:.
a) Get the cable (either K-Line or the later more expensive ones). b) Configure EDIABAS for the cable (easy if you follow instructions).
c) Then, all the software will recognize the cable Since INPA is simple to install.INPA is an easy, safe method to verify that you're in business for any of the BMW software. Yes, this is correct. This is also very good to know to simplify the software problem!. a) Install INPA (which also installs the EDIABAS API). b) Get it to work with the cable (by configuring EDIABAS).
c) Then, if desired, install the other software That's what's confusing me about the plethora of cables!. I don't want to modify the cable. I don't want to do 'tricks' to get the cable recognized. Things are already complicated (from lack of knowledge).
That cable-modification stuff is for the expert. I'm slowly getting to the 'simple' answer in my brain!. Buy 'BMW INPA' cables that fit your BMW. Mine is a 2002 so I only need the OBD2 connector. I prefer cheaper (i.e., K-Line as opposed to CAN bus). I prefer USB.
Download INPA/EDIABAS software. You have to find the software (and password) first. is a 100MB. is INPA2010.rar. is another directory. Install INPA software & configure EDIABAS for the cable. You will need to learn how to unpack RAR format files.
UNIX:. WinXP:. And you will need forum help. Run diagnostics and perform your first coding. My first task will be to turn OFF the fustugeneh!.
If desired, after INPA, install other software. Emulation.
(emulates UNIX OS on Windows PCs). Factory:. INPA (EDIABAS API comes with this). NCS, NCSExpert, NSC for Dummys, NCS made easy (which ones would you install?).
NFS. Toolset32. WinKFP. Dealer:. GT1/DIS, DISplus, EasyDIS (which ones would you install?). SSS/Progman. CIP.
Inpa 5 0 2 Ncs Expert Test
OPS. OPSis. ISIS. ISTA (not available in the wild yet). Aftermarket:. (is this software only?). Carsoft 6.5 SP1.
Carsoft Ultimate Home Bullet 4 'run diagnostics. ' should be after bullet 5. Except however, INPA does diagnostics. BTW, given that factory/dealer software list. What ORDER would you install the software (after first installing INPA/EDIABAS first)?
For me personally after INPA for my E39 1 NCS Expert and NCS for Dummies = enable coding and installation is easy. But be carefull, get help on the forum if you're not sure before using it. 2 EasyDIS for the diagnostic support and aids. Plus it will do CIP and module programming updates if you wish.
Also do resets after component replacement, e.g. Steering position sensor. Excercise the ABS if you have to do a brake bleed after draining the system dry. It was the dealer software while our E39s were current models. I believe that the data files are circa 2005. I have installed Progman V32 too, but haven't used it other than to verify it works. It is a pretty face on EasyDIS but does only coding and programming.
One still needs EasyDIS for diagnostics. Doing all over again, I wouldn't bother. If I had a newer model it would probably be worthwhile for the newer data files. Guys, I need some help if someone could. I already have INPA and the rest of the stuff, but they are old versions and I don't have programming files.I just bought a used T61 with the software already loaded.
It also has Gt1 and Progman VM. What is the best way to update everything(INPA, NCS, Ediabas) and if I download the files from another file share site would they just migrate where they need to go or is there a special trick to load them onto INPA and NCS. You are much more likely to receive best advice in this forum which is dedicated to BMW diagnostic software. EDIT Oops, the link above is incorrect.
This is the correct one Sorry about that. There are several guys there who are really expert in this field. And dozens who are very knowledgeable. You're unlikely to find any more than a (small) handful of people here familiar with the software. No offense to the E39ers in this forum BTW, the Progman that you mention does have programming files. It's sole purpose is programming and coding - no diagnostics.
You might also keep in mind that BMW does not likely devote much time or effort on updating E39 data files any longer. You probably already have the most recent available, even though your E39 files might be a few years old. OTOH, if you're also interested in more recent models an update may be in order.
The Hardware If you have an interest in programming your E90 BMW vehicle, there are 2 important hardware components are you are doing to need:. Computer (Laptop Recommended) We recommend that the computer you use has a Windows XP 32bit operating system (OS) installed. Although, others have reported to get the software needed to program BMW E90 vehicles to work on Windows 7 and above OSs as well as 64bit OSs, but most users have the most programming success using the recommended OS (Win XP 32bit). USB-OBD2 Cable Obviously you need a way to connect your computer to your BMW vehicle. The cable we recommend for accomplishing this is the over. There are cheaper cables out there, but sometimes you get what you pay for, and when programming a car that probably cost you thousands, it is worth spending the extra cash to invest in a reliable cable.
The Software The 3 programs below are needed or recommended for coding your BMW E90 car:. NCSExpert (Version: 3.1.0 with Daten Files Version: 51.2 or above). Inpa (Version: 5.0.2).
Ediabas (Version: 7.2.0) The following text editor program is optional but recommended, and is what will be used in some of our tutorials:. We recommend buying cj83lex’s for $5.00. You will probably want to go ahead and grab the latest data files addition he has for $10.00 extra. So for a total of $15.00 you will have everything you need software wise to program your BMW E90 car. Note, everything that he does provide in the package you can find around the internet, but it can take a lot of time to gather up the right software versions as well as finding download links to the software that are still active.
Step: 1 – C Directory Configuring & OBD Setup. Unzip the “ NCSEXPER.rar” file, and place the 3 folders (EDIABAS, INPA, and NCSEXPER) inside the zipped file in the C: folder. Your C: folder should have the following highlighted folders added:.
Navigate to C: INPA BIN. Right click on INPALOAD.exe and create a shortcut to desktop.
Navigate to C: NCSEXPER. Create a shortcut to your desktop of the “ WORK” folder. Navigate to C: NCSEXPER BIN. Create a shortcut to desktop of “ NCSEXPER.EXE”. Navigate to C: EDIABAS Hardware OBD and run the OBDSetup.exe.
Your screen will look something like the image below. Since I have ran this script previously, it might look a little different the first time you run it.
Press any key to close the window, and then restart your computer! Step: 3 – USB Interface Configuring For this step, I am assuming you have the BMW INPA / Ediabas K+DCAN USB Interface cable mentioned above under the Hardware section. If not, the following steps may not apply to you, and a different configuration may be needed to properly setup communication to your car. From desktop, press the WINDOWS KEY + R and type devmgmt.msc and click OK. After clicking OK, Device Manager will open. Expand the Ports (COM & LPT) section and plugin your USB Interface cable into your computer. You should then notice a new device show up called USB Serial Port (COM.).
For my computer, since COM1 and COM2 were already in use, my computer automatically assigned the device to COM6. Since INPA and NCS Expert are by default setup to use COM1 to communicate with the vehicle, we will need to change the assigned port to COM1. Note, there is a way to change the communication port INPA and NCS Expert uses to communicate to your car, but I find it easier to just assign the USB Interface cable to COM1.
Since in my case COM1 is already being used by something else, I needed to Disable that device from using that communication port. Right click Communications Port (COM1) and click on Disable. Now we need to make some changes to the USB Serial Port. Right click on USB Serial Port, and click on Properties. Click on the Port Settings tab, and verify the following values are as follows:. Bits per second: 9600. Data bits: 8.
Parity: None. Stop bits: 1. Flow control: None. Click the Advanced button. Change COM Port Number to COM1. Change Latency Timer (msec) to 1 and click the OK button and exit out of Device Manager and return to the Desktop. Plug your USB Interface cable into your car if you have not done so already.
Do not start your car just yet. Next, open up the INPALOAD.EXE program located on your Desktop. Step: 4 – Using INPA INPA is a great tool to use to verify that your car is correctly communicating with your computer.
Again, INPA is only a diagnostics program used to check the conditions for different parts of the car. For now, we only care to use it to make sure there are no communication problems and our USB Interface cable is working.
When the program opens, you should see 2 circles. One for Battery, and the other for Ignition. At this point, if you have not turned on your car’s ignition, only the Battery circle should be solid black. Turn on your car’s ignition but do not start the car’s engine.
After doing so, in INPA, the Ignition circle should turn solid black. Next we need to tell INPA what type of car we are dealing with.
Press F9 for the E90 menu. On the Scrip selection popup window, select Karosserie, and in the second window pane, double click Airbag. If you receive a “ Versions do not match” and “ Language variants do not match” error, everything is usually fine. According to some, it has something to do with the newer version of EDIABAS. If you do not receive any errors, that is fine as well.
Normally, if you did not receive any errors after clicking on Airbags, or if you received the 2 errors mentioned above, most would say you are ready to move on to using NCS Expert. However, just as a precaution, let’s verify we do not receive any errors if we check the state of our seat beat buckles.
This test will only work if you do not have any seat belt buckle issues already. So I’m assuming your seat belts are in working condition. Unbuckle any buckled seat belts in the car.
In INPA, click the Status (F5) button. Click the Buckle (F5) button. You should now be on a Buckles screen that has several sections with circles. We are going to only focus on the Driver’s buckle for this test.
If you are following this guide step by step, the Buckle plugged should read “no” and Buckle attached should read “yes” with a solid black circle. On the driver side of the car, buckle the seat belt into the buckle.
After doing so, in INPA, the Buckle plugged should read “yes” with a solid black circle. If you received no errors while performing the seat buckle test, congratulations! You are now successfully communicating with your car and ready to move on to using NCS Expert. Again, INPA is a great tool to use to make sure the communication between the car and your computer is working correctly before using NCS Expert.
Inpa 5 0 2 Ncs Expert 2017
Close INPA and start NCSEXPER.EXE located on the Desktop. Do not skip any of the following steps. AGAIN, do not, do not, do not skip any of the following steps. Doing so leads to the risk of you screwing up your car from starting or worse. If you receive any errors from NCS Expert at anytime, STOP moving forward in this guide and recheck your steps or try Googling the problem you are having. When you open NCS Expert, you should be presented with a window that looks like the following:. Click File, and then click on Load Profil.
Choose the Expertmode profile and then click the OK button. Note, the list of profiles you have to select from may be different than mine. That is fine. If you do not have an Expertmode profile, you need to retain a copy before moving on. Click File, and then click on Edit Profil, and for the Password, input the following and click the OK button: repxet. In the Profile editor popup window, click on the Car-Keymemory button and make sure all 3 boxes are checked on the Car Memory popup window and then click the OK button.
Click on the consistence check button, and you should receive a popup Info window that says “konsistence check OK”. If so, click the OK button on the popup window. Click on the FSW/PSW button, and verify the from CVT option is selected, and check both boxes for FSW-/PSW-Trace and FSW-/PSW-Manipulate with FSWPSW.MAN. Next click the OK button. Click on the consistence check button again, and you should receive a popup Info window that says “konsistence check OK”.
If so, click the OK button on the popup window. Click on the OK button to close the Profile editor. Click File, and then click on Save Profil as. Change the File name to FZG2.PFL, and make sure the File name does not already exist in the select pane below it. Also make sure the PFL folder is selected in the Folders select pane. Then click the OK button.
Click File, and then click Edit Profil, and enter the same password (repxet) as before. Next click the Profile info button and change Profile name to FSW PSW MAN and then click the OK button. Then click the OK button to close the Profile editor window. Click File, and then click Save Profil.
To sum of what we just did, we have just now created a profile that will write information to the car from a.MAN file that will be located in our NCS Expert WORK folder. We will get to that in a minute. The most important point here is, in the future when you start NCS Expert, you need to load the FSW PSW MAN profile instead of the Expertmode profile. If you click File, and then click on Load Profil, you will notice the new profile (FSW PSW MAN) you just created is now listed as an option to select. After you load the profile, you will see new options to select from under F1, F2, and F3. Press F1 or click the VIN/ZCS/FA button. Press F3 to choose the CHASSIS for the vehicle.
I am going to assume you are trying to code an BMW E90 vehicle, so in the pop-up window, choose E89 from the list and press the OK button. We are basically telling what type of vehicle we are working with. Another window will pop-up after clicking OK, and from that window, choose CAS for the ECU and press the OK button. We need to choose the ECU so NCS Expert can retreive the car’s VIN number and Vehicle Order (VO) so that it knows what parameters to use to program the car.
In NCS Expert, you will notice beside FG is the VIN number and FA contains the VO for the vehicle. The FA string can be changed if needed, but we will not get into that in this guide. To learn more about how to change the FA. Press the F6 button or click the Back button. Note, the Function buttons may be grayed out for a few seconds.
When you press the Back button, NCS Expert is reading all the values from every module in the vehicle and storing them in a FSWPSW.TRC file located in the NCS Expert WORK folder. It does this automatically, and will overwrite the file if it already exists. Open your NCS Expert WORK folder (you should have a shortcut on your desktop to the folder). As mentioned before, you should notice a file in your work folder called FSWPSW.TRC. This file was automatically created or updated by NCS Expert.
A common practice is to make a backup of this file each time you plan to make coding changes to a module in the car. I normally have a folder inside the WORK folder called Backup, and I place all my backups in that folder. So copy the FSWPSW.TRC file and paste it in the Backup folder or somewhere else on your computer in case you need to restore your settings. In NCS Expert you will notice under getcoded a list of modules selected to get coded. All the parameters/settings for these modules are what’s listed in the FSWPSW.TRC file you just took a backup of. Since to activate the BC Digital Velocity we only need to deal with the KOMBI module, we are going to select only that module to get coded instead of all the modules. Press F4 or click the Process ECU button.
Choose the KOMBI ECU from the pop-up window and press the OK button. Note, for my 2009 BMW E90 my BC Digital Velocity settings were located in the KOMBI module. For some, it may be the CAS ECU you need to select. But for now, just follow along, and if you cannot find the line to edit in the KOMBI module, just start back at this step and select the CAS ECU instead of the KOMBI ECU. You should now notice in NCS Expert under the get coded text that only the KOMBI module is listed instead of all the vehicle’s modules. Press F4 or click on the Read ECU button. This will overwrite your FSWPSW.TRC file in the NCS Expert WORK folder again.
However, this time around it will only read in the values from the KOMBI module instead of all the modules in your car. You will notice the size of the FSWPSW.TRC file is a lot smaller than before as well.
In my case, it was only 9KB instead of 234KB when NCS Expert read in all the values for every module. You will also notice a NETTODAT.TRC window pop-up. Just exit out of that window.
Additionally, you will notice a string of text under KOMBI that says Coding ended. That means NCS Expert has completed reading the ECU.
In the NCS Expert WORK folder, open the FSWPSW.TRC file in Notepad. Note, if you do not have Notepad installed, you can also open the file in the standard Notepad program. We need to go ahead and save this file with a.MAN extention instead of.TRC since NCS Expert is setup to code your car with the FSWPSW.MAN file located in your NCS Expert WORK folder. So in Notepad, click on File, then click on Save As, and then change the file name to the following: FSWPSW.MAN Note, it is okay if the FSWPSW.MAN file already exists in your WORK folder. Just overwrite it. After you save the file, notice in Notepad the tab should have a title that says, FSWPSW.MAN instead of FSWPSW.TRC.
In Notepad use the search option to search for the following parameter: BCDIGITALV. If you have not noticed already, some parameters have the word “aktiv” under them, and some parameters have “nichtaktiv” under them. The basic fundamentals for most parameters are, if it has the word “ aktiv” underneath it, it means that parameter is active (enabled).
If the parameter has “ nichtaktiv” underneath it, it means that parameter is not active (not enabled). As you can see from the above screenshot, the BCDIGITALV parameter is not active. So to activate the BC Digital Velocity feature, replace the word “nichtaktiv” with the word “aktiv” and save the file. In NCS Expert, press F5 or click the Basic functions button. In the pop-up window select the coapiReadSgGetFswPsw function and press the OK button. Selecting this function simply tells NCS Expert that we would like it to use the parameter values from the FSWPSW.MAN file that we just edited when we code the car.
Another pop-up window (coapiReadSgGetFswPsw) will appear that has the CBD name and other text fields. Do not change anything, and just press the OK button. A pop-up window (coapiReadSgGetFswPsw) should appear with the message that says, “basic function perfect ended”. If it does, pres the OK button. If it does not, you may have done something wrong in one of the above steps, and do not continue forward.
We need to change the JOBNAME from CODIERDATENLESEN, which means NCS Expert will read the information from the module instead of writing to it, to SGCODIEREN, which means we want NCS Expert to write the information to the module. Press F2 or the Change job button, and in the pop-up window, select SGCODIEREN and press the OK button. Finally, the step you have been waiting for. We are now ready to write the changes to the module. Make sure beside JOBNAME NCS Expert has SGCODIEREN selected. Next, Press F3 or the Execute job button. Next under KOMBI, you will notice a text string that says Coding activ, which means coding is taking place, and after it is done coding the changes, the text string will say, Coding ended.
Congratulations! You have coded your first feature on your car! After the coding has ended, the vehicle will restart. Afterwards, press the BC button a few times until you see the velocity screen. So even with “get coded” set to “KOMBI” and “jobname” set to “SGKODIEREN”. When you hit “Execute job”, all modules including KOMBI will be overwritten in the car instead of only KOMBI??
If so that’s kind of scary 🙂 since when reading from the car we selected only info from the KOMBI module (9kb code file instead of 234kb on the complete code file including all modules) and on the way back, writting to the car we are using the KOMBI only file Is there any chance that we wipe out all other features doing that? I apologize for the question but this comment “I believe all the modules get overwritten, not just the one you tweaked” made it a little confusing to me.
Fellas, This tutorial is awesome! I did not get the expected results when running OBDsetup.exe, I got some failures if I remember correctly, but everything else went without error when coding my E82 and the wife’s E84. I realize that once you’ve successfully completed this tutorial that you can start on Step 5 Using NCSExpert, but I don’t have a firm grip on where I can skip steps in the loading, saving, and backup process so I’ll do a little more reading before I start asking questions.
In the mean time, I have nothing but thanks for the work you guys have done and shared with the rest of us.