BimmerFest BMW Forum banner

Making sense of INPA, EDIABAS, NCSExpert, NCS Dummies, DIS/GT1, EasyDIS, & Progman

1M views 515 replies 145 participants last post by  BIMMini 
#1 · (Edited)
Making sense of INPA, EDIABAS, NCSExpert, NCS Dummies, DIS/GT1, EasyDIS, & Progman

EDIT: PLEASE IMPROVE! We are constantly updating this first post, as new information comes in (until it won't let us update it anymore).

Kudos: Many people collaborated on this BMW factory & dealer software explanation, especially Quick99Si who ran through all the installs and created a nice collective site for download (including combining & compressing the RAR files to the max!) & RDL who provided clarification on the unintuitive software intricacies.

Tribal knowledge requested to make organized sense of recommended E39 factory/dealer diagnostic hardware & software.


Based on the available diagnostic tools and in concert with the various BMW coding forums let's try to meaningfully organize the following E39-specific diagnostic-related scanning, coding, and programming tools & interfaces for the entire E39 tribe to benefit.
-----

  1. Assess your portable computer:
    • Almost any laptop hardware will work
      • The classic BMW dealer diagnostic laptop is an IBM T30
      • You'll want at least 40GB available hard disk space (100GB+ if you're installing Progman)
      • And, as much RAM as the PC can handle (Quick99Si had 2GB RAM in his Dell D620 laptop).
      • However almost all Windows PCs should work though (best with WinXP).
        • Warning: Most would NOT use their everyday laptop as their diagnostic laptop simply because software installation was intended for a stand-alone application (and, as such, it modifies many emulation, registry, and root entries).
    • Most programs run on Windows (e.g., INPA & NCS).
      • You can't go wrong with WinXP but others are reputed to work:
        • Windows XP <== by far, the best
        • Windows 2000
        • Windows VISTA
        • Windows 7 (NCSExpert requires XPmode)
      • Some programs run on Windows only with UNIX emulation (e.g., EasyDIS & Progman).
        • Typically EasyDis is set up on Windows via VMware UNIX emulation (details below)
        • Typically Progman is set up on Windows via Daemon Tools UNIX emulation (details below)
    • The biggest hardware factor on the PC is the I/O interface:
      • USB (see details below)
      • Serial (see details below)
  2. Order the right cable (1) (2) (3)
    • Three constraints focus your cable decision:
      • Vehicle end:
        • 20-pin round "pacman" OBD connector or 16-pin trapezoidal OBD connector
      • Computer end:
        • USB or RS232 serial
      • Interface support:
        • L-Line &/or K-Line &/or D-CAN
    • 20-pin round "pacman" OBD connector vs standard 16-pin "trapezoidal" OBD connector
      • If your E39 has the round 20-pin "pacman" OBED connector in the engine bay, then you MUST use that connector with these tools.
        • Note: It doesn't matter whether you 'also' have a 16-pin trapezoidal OBD connector; you still must use the round pacman OBD connector with your cables!
        • Note: While the 20-pin round ADS pacman connector looks similar to the 20-pin round OBD pacman connector, no E39 uses the ADS interface!
      • If you do not have the round 20-pin pacman OBD connector in your E39 engine bay, then you MUST use a 16-pin trapezoidal OBD interface cable.
    • USB vs Serial
      • USB is virtually 100% compatible with the software listed below and most recommend USB cables at this point.
      • Serial cables are cheaper & more information exists about their use; but, as time goes on, USB is winning out over serial (as serial port laptops dwindle away).
      • Most serial cables included adapters or cables to fit both the 20-pin round "pacman" OBD plug in addition to the 16-pin trapezoidal OBD port.
      • Warning: Some serial-to-USB conversion cables work (1) (2); others don't. Try to avoid the hassle with good up-front decisions
    • L-Line vs K-Line vs D-CAN
      • L-Line is the communication protocol on BMW cars from circa 1987 (first year of the ADS connector) to about the 1997 (before the E39).
        • Note that E39s (built from 1998 onward), do NOT use the ADS interface!
        • Older E39s may have a similar 20-pin round pacman connector; but it's 'not' a round ADS interface; it's a round OBD interface.
        • The round ADS interface uses pin 15 (RXD), which was phased out in 1996.
        • None of the E39's should need an ADS interface, but if you have any doubt, check the voltage at pin 15 of your round pacman connector; if you see about 11v you need the round ADS interface. If not you need the round OBD interface.
        • For further details, see the connector diagrams included below and the documents (e.g., bus system.pdf from JeffStri in post #94)
      • K-Line is the communication protocol on BMW cars from around the end of L-LINE to around 2006, including all BMW E39s.
      • D-CAN started on BMW in 2007 and is the current protocol (no E39 is D-CAN but most D-CAN cables are backward compatible to the K-Line).
    • Warning: No cable (yet) handles all three interfaces!
      • The best you can do is two out of three
        • Serial cables are often L-Line & K-Line compatible
        • USB cables are often K-Line & D-CAN compatible
        • All E39s require at least the K-Line interface
      • 1st choice: BMW INPA EDIABAS K-Line USB Interface (e.g., USB K-Line, aka "BMW INPA EDIABAS K+CAN USB OBD2")
        • $50 1, 2, 3
        • Primary K-Line on pin 7 (for the engine & gearbox); secondary K-Line on pin 8 (for all else)
        • FTDI Chip [Note: Get FTDI drivers here (1)]
        • Works on all newer E39s from 2001 to 2003 with the 16-pin OBDII connector above the driver's left knee
        • Note that there is a secondary K-Line on pin 8 (which is not on most DCAN interface cables) in addition to the primary K-Line on pin 7.
        • Models that use the K-Line OBD interfaces are:
        • - E87, E30 E36 E46 E83 and new E90, E34 E39 E53 and older E60 E61, E63 E64, E38 E65 E66, E31 E52, E53, E85 E52, R50 R52 R53
      • 2nd choice: BMW INPA EDIABAS K-Line Serial Interface (i.e., RS232 K-Line)
        • $25, 1, 2, 3, ...
        • Computer must have a serial port
        • Usually comes as two cables, one for round 20-pin interface & one for the 16-pin OBD connector
      • 3rd choice: BMW INPA EDIABAS K+DCAN USB Interface (i.e., USB K-Line+DCAN)
        • $120 1, 2, 3, 4, ...
        • Be careful: There are TWO kinds of K+DCAN cables with respect to E39 compatibility
          • Primary K-Line on pin 7; secondary K-Line on pin 8
          • Pin 8 removed (needs adapter to restore 2nd K-Line)
        • Models that require D-CAN:
          - E60, E61 after 3/2007, E83 after 9/2006, E81, E87 after 3/2007, E90, E91, E92, E93 after 3/2007,
          - E70 (New X5), R56 (New Mini), New F Series, as well as all other new models.
        • Uses the FTDI FT232RL USB to Serial Converter chipset
      • 4th choice: BMW INPA EDIABAS ADS + K-Line USB Interface (e.g., RS232 ADS+K-Line)
        • $65 1,
        • This is the serial cable that Randomly & Quick99Si bought for their round pacman OBD interface cars, for $80, and which, unfortunately, needs a six-to-ten-foot serial port extension to be practical since it has a hard inflexible adapter.
        • The connection is from round pacman connector to cable to adapter to computer or from OBD to adapter to computer; but realize since the adapter is a hard card, there's no way (without an additional flexible cable) that you can connect your computer physically!
        • Works on older E39s from 1997 to 2000 with the 20-pin round pacman connector under the hood.
        • If you have both the 16pin OBD2 socket AND the round 20pin socket you will still have to use the 20pin connector for factory diagnostics because not all modules talk to the OBD socket.
      • 5th choice: $35 Carsoft 6.5 RS232 Interface
      • 6th choice: Volkswagon (modified) VAG-COM KKL 409.1 cables with a FT232RL chip.
  3. Download the required Windows-helper software
    • WinRar
      • WinRAR 4.01 32-bit (1.4MB): http://www.win-rar.com/download.html
      • Needed to extract the downloaded RAR files.
      • This is a free 40-day trial version (which is plenty of time for what you need it for).
      • Note: While most use WinRAR, any RAR archive unpacking tool will suffice, e.g., IZArc or FreeRarExtractFrog freeware, etc.
    • Daemon Tools Lite (1)
      • Daemon Tools Lite v4.41.3.0173 (10.9MB): http://www.disc-tools.com/download/daemon
      • The purpose of this emulation software is to make the downloaded *.iso & *.nrg files on your hard disk 'look' (to the OS) like CDROM/DVD optical disc media (which is what the BMW diagnostic programs expect).
      • Installation requires 29 MB of disk space.
      • This is a free version with no time limit (for personal use only).
      • For example, Daemon Tools will mount the INPA /EDIABAS *.nrg image file as a virtual cdrom (which includes inpa / ediabas / ncsexpert / winkfp / tool 32)
      • Apparently, VMware has the ability to mount images also (based on Progman installation instructions); so Daemon Tools may not be needed if we can find instructions how to mount EasyDis v1.0 using VMWare instead of using Daemon Tools; however, the instruction PDF calls for Daemon tools so that's why it's listed here.
      • Some instructions also note that Alcohol 120% trialware can be used for mounting ISO & NRG images as cdroms.
    • VMware, v6 (315MB) (1) (2)
      • VMWare v6.0.3-80004 (315MB): http://www.4shared.com/file/yAihspKS...-603-80004.htm
      • The purpose of this software is to make the operating system (OS) of your PC 'look' (to the program) like UNIX, even though it's actually Windows.
      • VMware is used for UNIX virtual-machine mounting when installing DIS/GT1 for the first time, and then again for VM-mounting the Progman hacked ISO.
      • Note: Interestingly, the INPA v6.4.3 installation package (which includes INPA, the EDIABAS API, NCSExpert, WinKFP, & Tool32) requires another image file to be mounted as well (using daemon tools) because that virtual machine boots and uses the daemon-mounted image file to install the "EasyDIS/GT v44 programs"
  4. Download & install the required BMW-diagnostic software (only INPA/EDIABAS & EasyDIS are needed in most cases, both kindly re-imaged by Quick99Si for your convenience)
    • 1st INPA / EDIABAS package (i.e., INPA 4.4.7, EDIABAS 6.4.3, NCSExpert 3.0.8, NCSPlant 3.0.5, NFS 4.2, WINKFP 4.2.3, ToolSet32 3.2.4, & WINELDI 2.6.1)
      • Download: http://quick99si3.home.comcast.net/bmw/INPA-6.4.3-full.rar
      • How-To: http://quick99si3.home.comcast.net/bmw/ENGLISH_SETUP.pdf (1MB)
        • Notes: This version seems to be preferred over the optional 2010 v5.0.2 update.
        • Set up version 6.4.3 to make sure everything works.
        • Using WinRAR, point to the first RAR file & extract to create a folder called "INPA-6.4.3-full" containing the 347,183KB image "ediabas-6.4.3-full.nrg".
        • Then mount that "ediabas-6.4.3-full.nrg" image file using the "Add Image" button in Daemon Tools Lite.
        • It will mount, by default, as X:\NEU containing the folder X:\NEU\Referenz
        • You will need to run the installation program X:\Referenz\INSTALL\Instprog.exe
        • Follow the steps in the PDF file referenced above, but select the "BMW Group Rectification Programs USA" option instead of "UK" on page 5.
        • On the same page, you can select the option to install NCS Expert and WINKFP in addition to INPA and EDIABAS (it's not required now, but it's useful for later).
      • That INPA package contains INPA 4.4.7, the EDIABAS 6.4.3 API (which is required for most of the tools), NCSExpert 3.0.8, WinELDI 2.6.1, NCS plant 3.0.5, NFS 4.2, WinKFP 4.2, & ToolSet32 3.2.4 according to this reference.
      • WINKFP can program, i.e., it can update software on a module to a newer release (if you already have that newer release file available)
      • INPA is much easier to install than EasyDIS and will read module data, read & clear DTCs & perform car module function checks.
      • INPA will read DTCs, clear DTCs and activate functions, e.g. turn on a warning light, or move the Xenon headlight aiming up & down in order to test functionality.
      • While INPA is good for diagnostics, it will not do coding.
      • INPA is easy to install. The install package simply copies files into the following four 8+3-named Windows directories C:\{EDIABAS,INPA,NCSEXPER,NFS}
      • One then has to modify a couple of INI files to specify the adapter cable & you're in business.
      • Note: Later versions of EDIABAS are known to cause problems with DIS and Progman so INPA v6.4.3 is the recommended version.
      • ToolSet32 allows you to query detailed option information & is used for adjusting personal settings, key memory, & interrogating modules.
    • NCS Expert
      • NCS Expert is included in the INPA package listed above.
      • NCS Expert is easy to install (if you already have INPA working, NCS Expert will work too, with no further changes).
      • Can code dozens of options in every module in the car (e.g., the automatic door locking at 5mph in the General Module)
        • See, for example this file:
        • http://quick99si2.home.comcast.net/bmw/FSW_PSW.TXT
          That's the output Quick99Si obtained when he read his general module using NCSEXPERT.
        • You'll see the following lines for allowing opening/closing of the windows via the remote.
          • KOMFORTOEFFNUNG_FB aktiv (i.e., comfort opening, FB=key fob)
          • KOMFORTSCHLIESSUNG_FB nicht_aktiv (i.e., comfort closing, FB=key fob)
      • Most relate to different markets variants.
      • Figuring out what to change to get a result can be very tricky.
      • NCS Expert comes with virtually no documentation or detailed instructions.
      • NCS Expert reads or writes to modules using parameters in German words and abbreviations.
      • NCS Expert is difficult for a native German speaker to understand, let alone English speakers.
      • If you want to "play around" & give your car a European flavor, NCS Expert is needed (e.g., Comfort Close, which EasyDis won't set).
      • WARNING: Do not start NCSExpert until you've read the NCSExpert and dummy PDF's twice (NCSExpert is VERY dangerous and the GUI is in German to make it doubly more dangerous, in effect).
    • 2nd NCS for Dummies (also called NCS Made Easy or NCS Expert for Dummies, by Revtor)
      • Note: For a description of the latest update from Revtor, please see this thread.
      • For the latest download from Revtor, click here: http://revtor.be/ncsdummy/ncsdummy.zip
      • For a Quick99Si archived download, Download: http://quick99si2.home.comcast.net/bmw/NCSDUMMY.rar (154KB)
        • Note: NCSExpert needs profile files to read and write files. One of those profiles is included with Revtor's packages (it's the PFL file).
        • Quick99Si kindly included two others sourced elsewhere.
        • All these profile files are included in Quick99Si's NCSDUMMY along with the Revtor guiding PDF.
      • Revtor has developed this very nice standalone (and much-needed) aid to understanding & using NCS Expert.
      • For a five-minute walkthrough, using NCS for Dummies, please see post #50 below.
      • The PFL file is a profile used later by NCSEXPERT.
      • The included PDF is a guide on reprogramming, not installing, and it is definitely worth reviewing multiple times.
      • This NCS for Dummies installation provides a detailed description of how NCS Expert works.
      • It contains step by step guides for reading and writing to modules.
      • It tells you how to make a backup of one's starting point, in case a coding change has unintended results.
      • It reads NCS Expert input and output files with translations of many, although not all, of the hundreds of parameters from German to English.
      • With these translations, one has a reasonable chance of success when trying to change (i.e. code) an option.
    • 3rd EasyDIS 1.0 (which is DIS v44) and the READTHISFIRST document from DavidMC
      • Download 1: http://quick99si3.home.comcast.net/bmw/EasyDIS-base-44-v1.0.rar (240MB)
      • Download 2: http://quick99si2.home.comcast.net/bmw/GT1_v44_programs.rar (758MB)
      • How-to 1: http://quick99si3.home.comcast.net/bmw/DavidMC-EasyDIS_READ_THIS_FIRST.pdf (125KB)
      • How-to 2: http://quick99si3.home.comcast.net/...AS_6_4_3_-_Running_with_CarSoft_interface.mht (1.7MB) (bottom half for this step)
      • How-to 3: http://forums.bimmerforums.com/forum/showthread.php?t=1297683 by Randomy (2.5MB)
      • How-to 4: http://quick99si3.home.comcast.net/bmw/DIS_v44_&_v57_Installation_Check.pdf (2.1MB)
      • Notes: There are a few functions that will need to be performed from within the DIS virtual machine Administration menu.
        • These include changing the translator to and from FISTER (ADS) or SOFTING (OBD) to correspond with your interface; performing the APITEST to verify functionality, configuring the running processis; and shutting down DIS.
        • To do this, click the Administration button in the bottom right; select "Calibrating Touch Shield"; and enter 12345 as the password.
        • VM should be set to "not run"; and the others should be set to "run."
        • The "Installation_Check" PDF can be used to ensure that your entire configuration works.
        • The toughest part is probably having the virtual machine properly networked to your Windows box with EDIABAS.
        • Always run IFHSrv32.exe before starting DIS; in fact, it wouldn't hurt to have IFHSrv32.exe autostart with Windows.
      • There is only one version of EasyDIS, which is EasyDIS 1.0 (more properly called "EasyDIS 1.0 based on DIS v44 and GT1").
      • EasyDIS is a hacked version of DIS v44 that was modified to make installation and configuration in the UNIX virtual machine easier.
      • DIS v44 was the dealer software for the E39 era & is the most useful software you can install.
      • However, DIS runs on UNIX. Installation is difficult for most since one must set up to run DIS inside a UNIX virtual machine (via VMWare)
      • EasyDIS diagnostics are excellent & the software is in English.
      • EasyDIS does coding (e.g., the automatic door locking at 5mph in the General Module) and programming.
      • EasyDIS exercises components & resets service intervals.
      • All the Car & Key Programming options available in North America can be changed.
      • New modules can be installed & retrofitted.
      • Note: Do not install any later DIS than v44; DIS v45 to v57 are a step backward from DIS v44 because DIS became diagnostic only (Progman was added for coding/programming & confusingly has lower version numbers than DIS)
      • Read the Randomly: How to install GT1\EasyDIS v44 step-by-step in the Bimmerforums Diagnostic Software forum ... The first post there is decently helpful as an overview, but, according to Quick99Si, it is outdated and lacking key details.
        • For example, it doesn't say how to perform apitest in easydis; nor how to change the translator from softing (obd) to fister (ads); nor does it say that you need to exit DIS by shutting it down first (using the DIS administrator button, then calibrate the touch screen, then enter 12345 for a password, & then 0 to shutdown or other #'s to perform the apitest/translator/restart ediabas).
  5. Download any desired optional software
    • 4th Progman v32
      • WARNING: Progman installation is more involved than those above!
        • Don't even 'think' about installing Progman until you have the programs above in working order!
        • Program requires a working EDIABAS API (which is installed with the INPA setup).
      • Progman has a user friendly interface for coding & programming new modules than EasyDIS provides.
      • But Progman has no more functionality than EasyDIS does (it is said Progman's primary benefit has to do with coding used modules)
        • While brand new modules can be coded with EasyDIS/GT1, it seems that Progman is often used to code old (used) modules containing an old VIN that needs to be coded to the new VIN.
      • Progman does not have any diagnostics; its sole purpose is programming and coding.
      • Progman will, for example, code the automatic door lock feature at 5mph in the General Module.
      • Progman runs under UNIX (so most people run it on Windows using VMware UNIX emulation).
      • Confusingly, Progman version numbers started around v20 or so (superseding DIS v44).
      • The currently available Progman version "in the wild" (i.e., outside BMW dealerships) is v32.
      • There are those who say Program isn't worth the installation & learning trouble over EasyDIS.
      • Note: Progman calls for the creation of another VMware virtual machine plus a whopping 80GB of virtual space. It needs another image mounted to CD so it can install itself, but the instructions here call to use VMWare for mounting instead of Daemon Tools.
    • 5th INPA 5.0.2 update
  6. Run your first coding experiment
    • Spit out all the available options for your general module:
      • Here's how, without even reading your car.
      • Open NCS for Dummies.
        • Select E39 for chassis
        • Select GM3_C05 for module (or whatever your module is)
        • "Translations" will be checked
        • Manually check "Order Options"
        • Click "Module Functions,"
        • Click export sorted by keyword
        • Save it somewhere and open the text file in Notepad
        • You will have all the available options to code for that module (along with most English translations, and most importantly: the available "settings")
        • For example, look for VERRIEGELUNGSSCHWELLE, and you'll see the speed settings you can change.
        • This shows you'll likely want to set VERRIEGELN_AUT_AB_X_KM/H to nicht_aktiv and you're done!
    • Change the automatic door locking feature of the E39 at a preset speed (e.g., at 5 mph, all four doors autolock):
      • VERRIEGELN_AUT_AB_X_KM/H aktiv (i.e., automatically lock all doors at a specified speed)
        • If it's aktiv, then VERRIEGELUNGSSCHWELLE is also used, which can accept a bunch of values representing various speeds
      • VERRIEGELN_AUT_AB_X_KM/H nicht_aktiv (i.e., automatically lock all doors at a specified speed)
        • If it's nicht_aktiv, then VERRIEGELUNGSSCHWELLE is ignored.
    • Note: We need to flesh this out further for others to benefit.
  7. Run your first diagnostic experiment
    • PLEASE IMPROVE!!! (help the team!)
      • Test the ABS control module & wheel speed sensors
-----
ORGANIZATION: (please correct as needed!)

  • Emulation Software:
    • VMware used for UNIX virtual-machine mounting when installing DIS/GT1 for the first time, and then again for VM-mounting the Progman hacked ISO.
    • Daemon Tools Lite used for virutal CDROM/DVD mounting of the ISO & NRG images downloaded of the BMW diagnostic software.
  • Factory Software:
    • INPA (the typical downloaded RAR file also installs the EDIABAS API, NCSExpert, WinKFP, & Tool32)
    • NCS Expert (aka NCS)
    • NFS
    • ToolSet32
    • WinKFP
  • Factory Services:
  • Dealer Software:
    • DIS v44 (the dealer software of the E39 era)
    • DISplus
    • Progman
    • ISIS (BMW software control system)
    • ISTA/D (the current dealer level software)
    • ISTA/P (the current dealer level software)
  • Dealer Hardware:
  • Dealer Diagnostic Heads:
  • Aftermarket Software:
  • Aftermarket Hardware:
    • IBM T30 laptop (serial port, running Windows, with VMware UNIX emulation)
  • Hacked Software
    • Carsoft 6.5 SP1
    • EasyDIS v44 (this is the same as DIS except it was hacked to be easier to install)
  • Hacker Hardware
    • CAS3 mileage correction tool
  • DIY Hardware:
    • Actron
    • AutoXray EZScan
    • MaxiScan
    • PEAKE
    • SR-300
  • Professional Hardware/Software:
-----
DEFINITIONS: (please correct as needed!)
Note: Each tool is roughly categorized as:
- Factory === Tools written by and for the BMW factory
- Dealer
=== Tools used by the dealer (supplied by the Factory)
- Professional === Tools used by professional mechanics (often > $1,000)
- Aftermarket === Tools intended for use by BMW aficionados (e.g., >$500 Carsoft Ultimate Home Edition)
- DIY === Tools intended for use by BMW dilettantes (e.g., <$100 OBD scanners)
- Hacker === Modified versions of the above (often out of China, often in German, often freely downloaded with no support, often with no cables supplied)
- HW === Hardware- SW === Software

Let's ask each of us to please add and/or correct organization and/or definitions so that, at the end of this thread, we can finally summarize for the world, the relevant currently available 'things' & 'actions' for BMW diagnostic purposes.

ACTIONS:

  • Coding tools: MoDiC, GT1/DIS, GT1/DISplus, SSS/Progman, Easy-DIS (to v44), NCS, NCS Expert, INPA, Carsoft (v7.x & v8.x only), Launch X431, ?
  • Programming tools: MoDiC?, GT1/DIS?, SSS/Progman?, ?
  • Diagnostic tools: Easy-DIS versions after v44, P.A. Soft BMW Scanner, ?
  • Reset tools: Carsoft, Peake, ?
  • Scanning tools: Actron, MaxiScan, SR300, AutoXray EZScan, ?
ORGANIZATION:

  • Actions
    • Coding (verb): setting available options that the programming in a module will recognize & permit (e.g., the door autolock feature)
    • Programming (noun): the set of instructions stored in a module that give it functionality
    • Programming (verb): loading updated BMW firmware into a module
    • Reading: Reading error flags & diagnostic fault codes in a module & version and other information ?
    • Resetting: ? Clearing error flags in a module ? (is it the same as coding?)
  • Cables
    • BMW INPA / Ediabas K+DCAN USB Interface (~$120)
    • Chipsets:
      • ADS interface (confusingly, no E39 uses the ADS interface! The round 20-pin pacman connector on the E39 is an OBD interface!)
      • FTDI FT232Rx: VAGCOM KKL
      • ?
  • Protocols:CAN, D-CAN, K-CAN, PT-CAN, EDIABAS, ?
  • Tools:
    • Factory: INPA, ISIS?, NCS, NFS, WinKFP?
    • Dealer: MoDiC, GT1/DIS, DISplus?, SSS/Progman, ISTA/D, ISTA/P
    • Hacker: EasyDIS, INPA, NCS_expert?, NCS_made_easy, ?
    • Professional: Autologic, Diagun, Genisys EVO, Launch's X431, SnapOn Solus, ?
    • Aftermarket:
      • BMW: Carsoft, Peake, P.A. Soft BMW Scanner, ?
      • OBDII: Actron, MaxiScan, SR300, AutoXray EZ-Scan, ?
NOTE: Do not assume anything in this post is accurate (yet!) as I don't know anything; but I'm trying to organize this for all, including for me!

Summary of References:
- INPA, EDIABAS, NCS Expert, DIS, EasyDIS, Progman, & other BMW factory & dealer programming, coding, and diagnostic software (1) (2) (3) (4) (5) (6) (7) (8) (9) & related BMW diagnostic tools forums (1) (2) (3) (4) (5) & the most often recommended BMW diagnostic tools & cable interfaces (1)

Note: Key users' posts to pay close attention to (alphabetically):Aca84, DavidMC, Dracon, Quick99Si, Randomly, & RDL (on a variety of forums).

[ Temporary backup 09/02/2011 ]
[ Temporary backup 09/13/2011 ]
[ Temporary backup 09/29/2011 ]
 

Attachments

See less See more
21
#226 ·
bluebee That DIY you cross referenced isn't too great... EDIBAS, DIS etc work just fine with windows 7 so no need to start messing up your computer. Why on earth would you want to install xp to a win7 computer? If one insists on XP one can simply virtualize it. On windows 7 professional you got XP mode, if you don't have win7 pro/ultimate you can always use vmware. A good DIY on EDIBAS, DIS etc. is BMW DIS V57, SSS V32 & TIS V8 Installation Procedure. That cover pretty much everything. Even how to virtualize operating systems with vmware.
 
#232 ·
I just ran into this document - and wonder WHERE I should archive it?
Does it belong here? Or elsewhere?
 

Attachments

#233 ·
Based on this note today from another thread, and, noting that the cable recommendations in the first post of this thread are about 18 months old, I wonder if anyone has an update on the cable situation lately for USB cables on modern PCs?

There are so many inpa edibas USB cable and softwares out there but I'm still unsure witch one would be the best one to buy as I'm looking into coding modules, read and clear codes basically a full functional tool with most features that dealer may have.
 
#234 ·
OT... but not really. I installed INPA as per your instructions (and the instructional PDF). Thank you. I am using a new USB/OBD II connector.

Opps... almost forgot; I have a 2004 545; 6 sp MT... all stock.

I have seen pictures of the INPA interface with the battery and ignition round indicators either "lit" in black or in clear. How can you tell if you are connected and communicating?

Are there instructions on how and when to connect, when to start the engine, etc...

Also, the instructional PDF on page one of this thread says to start INPA (_.IPO). What about INPA (_.IPS)? What's the difference?

BTW, awesome job here!
 
#239 ·
Thanks. I was not thinking about the '99's, rather the '01 530. I probably should find something that will also work on the '99's.
 
#241 ·
Thanks. Finding quite a few on fleabay.
 
#242 ·
Couple of updates since I was last around here:

1. INPA 5.02: it works on E39/E46 just fine, but the package replaced the language in INPA from English to German for me. It isn't difficult to use or navigate, but there are no features worth updating for if you're only using it on an E39. INPA 5.02 was beneficial for messing around with Mini Coopers (R50 and on) and some of the later models like R56 aren't supported by the daten files in INPA 3.x. Again, I do not recommend updating for dedicated E39 use.

2. DIS/GT1: it is possible to have both v44 and v57 running as separate installations on one machine. To accomplish this, simply install v44 as noted in the top post, clone that VM (FULL clone, roughly 20GB), run cloned VM, and install v57 as per the guide. It will require DaemonTools and the DIS v57 image file. If my memory serves me right, v57 lost the ability to code new modules, but gained the ability to support newer cars. Like with the point above, for dedicated E39 use, you will be perfectly fine with DIS v44.

3. NCS Dummy continues to be updated, and you're probably better served to check the developer's website and download from him directly rather than using the copy that I'm hosting. Latest update seems to be from just over a month ago: http://forums.bimmerforums.com/foru...NCS-Dummy-Taking-the-expert-out-of-NCS-Expert

4. Speaking of hosting, the files my not be on my server for much longer. I've slowly been uploading them to this location: http://www.4shared.com/dir/YzvDi-2F/BMW_Software.html. This will have every single thing you will need for an E39, down to instructions. I will create another mirror on Box.net in the coming days, while handing over the 4shared account to BlueBee.

5. Has anyone tried meddling with the new BMW ISTA software? My buddy and I were looking into it last night and it seems to be the same feature set as DIS/INPA/Progman, but included in one suite and geared toward newer BMW's. Apparently the Chinese hardware connectors alone cost upwards of $1k and the software runs in their cloud? Would love some input on this.
 
#244 ·
I am using ICOM Chinese clone about four month and have no problem.
It was purchased for $650 but it came with malfunction hard drive for IBM T61
And I bought VM version software ISID and ISSS on EBAY.
For programming procedure it require 50 amp power supply and can take on some cars up to 4 hours for complete programming, and it not allows you program modules separate.
.
 
#243 ·
As a sidenote, I will probably be selling my complete setup soon with the hopes of recouping some my expenses. It's a turn-key diagnostics + coding/programming solution proven to work reliably on E34, E39, E46, E60, and R50 with all modules on all cars:

a. Dell Latitude laptop: dual-core 1.83GHz, 2GB RAM, 120GB HDD, fresh extended battery
b. $80 cable with the standard K-Line/D-CAN (as well as L-Line that worked with an early E34)
c. 10-ft extension cable
d. INPA 3.01, INPA 5.00, EasyDIS, NCS Expert+Dummy, WinKFP, updated E39/E46/R50 daten files, etc. preloaded
e. Microsoft Office 2010 (Word, Excel), FileZilla FTP, Foxit PDF, etc..

I made the mistake of giving the little 20-pin adapter a while back, but I ordered a new one last night as a replacement. Probably selling for $300/all.
 
#248 ·
One of my old friends recently got his station set up with Windows 8 64-bit + USB + unknown cable on a Lenovo Thinkpad. He says that everything works fine aside from NCS, and I'll be meeting him this weekend to program his car and so how well his setup runs. It seems that we're no longer bound by XP or 32-bit operating systems in general.

I have a spare Lenovo T420 that I would love to put to use in case I'm ever in a BMW again.
 
#252 ·
You will not be able to manipulate the engine tune with this (or any similar) software. You can, however, reflash the DME with newer software using WinKFP. This is not considered within the scope of this thread, but I can tell you that I've succeeded in doing this to an E46 M3 DME as well as SMG.

More at bmwcoders.com and m5board.com
 
#253 ·
I'm not looking to manipulate the tune, just want to make sure I dont lose it.

I currently have a Dinan software tune, but was looking reflash the DME with software from an X5 4.6is so that I can enable the oil temp over can and have a working M5 cluster. I'm familiar with how to flash it with WinKFP, just worried about losing my Dinan tune. Will a software reflash affect that?
 
#254 ·
Anyone have a D-CAN cable they are willing to lend for testing (with deposit of course)? PM me.
 
#255 ·
I have a MY 97 E39 540i6 with a build date of 06/96. It has the OBDii connector in the cabin and the 20 pin connector under the hood. I keep reading that no E39 requires an ADS compatible cable setup. However, as its mentioned in the OP, if you want to be sure you can always check the voltage on pin 15 in the 20 pin connector. Well, I bought a cable and have been fighting with it to work using the 20 pin connector. So, I decided to check the voltage on pin 15..... 12v. So, am I the only owner of an ADS 20 pin connector E39, or am I doing something wrong?

Windows 7 running VMware Player Windows XP.
Ebay 20 pin adaptor to 16 pin USB cable.
INPA 4.4.7
Key to ON position.
Battery and Ignition status OFF.

EDIABAS.ini STD:OBD
USB Port set to COM1, Latency Timer = 1

No error messages, just no connection.
 
#256 ·
Not at all. Many of us with vehicles older than 00' require a ADS connector so that we can communicate with all the modules in our cars. I do also think that not all ADS adapters are made equal. I have had a problem in the past with a cheaper one bought off of eBay compared with a slightly pricier one from one stop electronics.
 
#257 ·
I will vouch for this. I've had 4 different 20-pin adapters and only one worked as designed. It was designated as an "INPA" cable that I originally received with the interface cable from onestopshop. The others simply did not work with any of the software, only generic OBD scanners.
 
#258 ·
Well, that kinda blows. In the meantime I bought an ADS interface and am hoping to set up a PC in my garage over the weekend. I'll be testing both the ebay cable (via usb) and the ADS connector (via serial port) and if I can get the ebay cable to work then I'll resell the cable and recoup the expense of the ADS module. Wish me luck!
 
#259 ·
Not Impressed with BMW design expertise

I bought a 2008 Z4 with 17K miles. It drives real nice. I enjoy driving it a great deal, but I have to say I am not impressed with BWM's design capabilities.

Going into transport mode if the voltage drops below 11.4 volts, is not great. But requiring you to go to a dealer a pay to have it reset just adds insult to poor design. Alternatively you can install some really nifty software, buy a cable, and spend a few hours configuring a PC to be a dedicated diagnostic tool, and then click on the reset button. Nice. Perhaps BMW should consult with Yugo or Trabant on how to design a heating and cooling system. While they're at it they could ask them how to design a CHEAP cup holder, because the CHEAP cup holders in the z4 are only suitable for drinks you are willing to wear.

I expected better.
 
#260 ·
I bought a 2008 Z4 with 17K miles. It drives real nice. I enjoy driving it a great deal, but I have to say I am not impressed with BWM's design capabilities.

Going into transport mode if the voltage drops below 11.4 volts, is not great. But requiring you to go to a dealer a pay to have it reset just adds insult to poor design. Alternatively you can install some really nifty software, buy a cable, and spend a few hours configuring a PC to be a dedicated diagnostic tool, and then click on the reset button. Nice. Perhaps BMW should consult with Yugo or Trabant on how to design a heating and cooling system. While they're at it they could ask them how to design a CHEAP cup holder, because the CHEAP cup holders in the z4 are only suitable for drinks you are willing to wear.

I expected better.
Why would your voltage drop below 11.4v? Voltage that low means your battery is practically empty and most likely won't be able to start the engine. The cup holders, well germans have a bit different take on driving compared to US. Germans think that the driver consentrates only on driving nothing else. A cup holder is just an unnecessary distraction. They just included cup holders due to some customers demanding it (mostly US).
 
#262 · (Edited)
I'm heading off to Tahoe at 5am Friday morning, and I got the dreaded TRANS FAILSAFE PROG message today:


I can't read the transmission codes, because my ancient Carsoft 6 cable was built for parallel-port computers:


I can run down to Staples today, to pick up this $40 parallel-to-USB converter:

But, it's probably a long shot that it will work.
So, I'm hoping to find a double-K-line USB cable in the local vicinity ...

EDIT: I've always been confused as to which cables work best for my bimmer.
Here is what I 'think' is the current summary; but almost no sellers give you this information about their cables:

  • Preferred cable (with double k-line support):
    • K+CAN with the Primary K-Line on pin 7 (for the engine & gearbox); and with the secondary K-Line on pin 8 (for all else)
  • Less-preferred cable:
    • K+DCAN with the Primary K-Line on pin 7 (for the engine & gearbox); and with the secondary K-Line on pin 8 (for all else)
  • Non-preferred cable:
EDIT: This information posted in the TRANS FAILSAFE PROG thread may be useful for choosing the right cable:
To me it's quite clear, if you want to diagnose BMW between 96-07 you'll be fine with K-CAN cable.
If you want to diagnose 96-2013 get K+DCAN.
I personally have K-CAN, because that was affordable choice when I was buying it.
Now I would buy K+DCAN, because I read codes, code modules, change settings etc. for local Bimmer enthusiast.
To read codes you need to use INPA, DIS. AFAIK EasyDIS is just easier version to install compared to DIS.
 
#266 ·
For the record, this was asked today:
My k+dcan usb cable has pin 8 in place, is there any easy way to know if I have the right 16 to 20 pin adapter for a 1997 528i?

I cannot get inpa to talk to the car, the following error every time I try. IHF-0003: DATATRANSMISSION TO INTERFACE DISTURBED

Pc is fresh install XP, ftdi set to com 1 latency 1

should I try working with obd port & ecu before moving to ADS port? I had no luck on obd port either but I did not try real hard
 
#267 · (Edited)
I bought my 2007 328i in March of this year and last night I started looking into coding/reading errors/clearing errors. I have to tell you I was completely lost even though I'm VERY computer software/electronic repair literate, all of these acronyms confused the crap out of me. I got frustrated and decided to take a lunch break today from all the forum reading. My girlfriend had seen the frustration on my face and asked me what was wrong so I told her about all the acronyms for BMW's coding/reading errors/error clearing. Within 5 mins of searching Google she found this thread. I have to say you guys have made this SOOOO much simpler and I just wanted to say thank you for putting all this together! This thread is freaking amazing!!! Don't get me wrong I'm no pro after reading this, but it at least helps me to get started on my road to modding and fixing my BMW. I know this thread is geared more towards E39s, but I still feel the need to ask which cable/software would be best with my E90.

Here is what I've been thinking about getting:


Laptop for programming use only *will put windows XP pro on it * (unless you guys know of a cheaper alt that will work perfect with the programs)


BMW INPA / Ediabas K+DCAN USB Interface kinda expensive IMO, but I'm not trying to skimp when it comes to programming my car.

This disk for the programs (unless you guys know that the links under 'Download & install the required BMW-diagnostic software' will work for my car)

Please don't bash on me to hard for posting in here LOL. I just had to ask because you guys have done extensive research and seem extremely knowledgeable on all this; plus I've asked a question similar to this in the E90 thread and never got a response.

My question in another post.

Thanks.
Adam
 
#268 ·
1) Any Windows Laptop with XP will suffice. Make sure if it is new, it has a least one legacy USB 2.0 Port.

2) The One-Stop Electronics K+DCAN USB Interface Cable is a very good one. A great many people are using this cable, and all the feedback has been good.

3) The eBay item is just another K+DCAN USB Interface Cable. The DVD is just the USB Driver. There are no programs included with it.

For your car, you need SP-Daten files and EDIABAS (low-level ECU communication program), along with NCS Expert for Coding, INPA for Diagnosis, and WinKFP for Flashing.

EDIABAS, NCS Expert, INPA, and WinKFP are all part of BMW Standard Tools, the latest version being 212. SP-Daten comes from ISTA/P (Dealership Programming Software), the latest of which id 50.4; however, 50.2 was the last to have an Exx Chassis update.

I have PM'd you what you need.
 
Top