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
#86 ·
You can try disabling the other serial ports, any AV/firewalls you may have including Windows, test it on a laptop with a serial port, test it on another e39, etc. I can tell you that USB-serial adapters without additional onboard hardware don't seem to virtualize the serial ports as effectively. Take a look at your adapter and then take a look at a Belkin: http://imagehost.vendio.com/a/3578944/aview/belkin_usb_serial_adapter_f5u109_final_no_logo.jpg

Also, this site has common causes of the IFH003 error: http://www.bmwland.co.uk/forums/viewtopic.php?p=842420

Realistically though, a laptop with a serial port dedicated to BMW diagnostics completely eliminates all this guess work and frustration...
 
#88 ·
Well, I ended up getting a Dell Latitude D610 w/ serial port (made sure with seller first) running Windows XP Pro, 512 megs of RAM, 40gig hard drive, 6mo warranty all for $80. This will be dedicated to running INPA/Ediabas, Progman etc... Hope that this thing works out. Worst that can happen I gues is re-sell on Ebay if it doesn't. Will report back with success or horror stories as it happens.
 
#90 ·
Yes, tried with key on, anti virus off, firewall disabled, and every other hint or trick.
New USB to serial should be here soon hopefully that will do it. New ( old) laptop will be here next week to be also loaded and configured for sole purpose of using software. Hopefully one or both will work to full potential.
 
#91 · (Edited)
OK, worked on installing EasyDIS and GT1 last night. "Worked on" implies failed so far. Gotta few questions though.
1. The "read this first" says to burn the base on a CD and the Programs on a DVD. Had some struggling, but got it done. But why? I thought we were gonna run these from daemon tools.
2. Daemon tools lite only appears to support two images at once. With INPA, easyDIS base, and GT1 Programs, that would be three. Is it necessary to have all three mounted at once?
3. The "read this first" references an "EasyDIS installation .PDF", notably page 8a. Where am I missing this? I have googled it and was able to come up with page 8a, but not the whole thing. Maybe I am overlooking something.
4. When I try to start the virtual machine (Randomy's guide, after mounting EasyDis base), it is telling me that I need to be registered or get a a license or something. There is a link that takes me to VMware 8 purchasing for $200. Not gonna do that. I recall I didn't disable the virus or firewall thing, not sure if that has something to do with it, but I wont have the opportunity to try again for a couple of days.
5. How to #2: http://quick99si3.home.comcast.net/...AS_6_4_3_-_Running_with_CarSoft_interface.mht does not appear to be a how to, but contains a great deal of what appears to be coded data. What is it? - wait, figured this one out, as this link only works in Internet Explorer, never mind.
 
#92 · (Edited)
1. You do not need to burn any disks. It's a waste of media, time, and it makes installations slower. The burning is effectively substituted by DaemonTools and VMware, as you seem to have understood. If you're looking for confirmation that you can bypass the CD/DVD burning, then yes, I can confirm you can simply mount in DT, though I believe the GT1 ISO will be mounted from within VMware.

2. Install INPA/EDIABAS, unmount the image you used to install it and move it somewhere for safekeeping. You don't need it anymore unless you wish to run the install program again. STOP here and test your cable, if you haven't already. If your cannot commnicate with the car, you need to resolve the issue before moving on.

3. No comment yet, I need to do some reasearch for you on this.

4. Have you tried the recommended version of VMware? There are ways to get that specific version, there's a link in Bluebee's first post, but PM me if you need help with this one ;)

5. The MHT file extension was a pain to download so I re-uploaded the guide URL to: http://quick99si3.home.comcast.net/...AS_6_4_3_-_Running_with_CarSoft_interface.htm. That file is my offline archive of this page: http://www.dvsntt.com/INPA/ with credit given to Randomy. Scroll down to the heading "DIS with INPA interace" (bottom half) or the purpose of installing EasyDIS/GT1.
 
#93 ·
#94 ·
The best way to get answers to most of the questions raised in this thread is to search the Bimmerforums Diagnostic software forum. Except for Quick99Si, there are few people with much knowledge of and experience with INPA, DIS, etc who pay much attention to this thread.

The best place to get the software and instructions is David McLean's 4shared site. You will need some help to access the files. David's "Supp Page 8a" is in the Easy GT folder.

One major source of confusion seems to be what was labeled the "ADS" connector/interface in the first post of this thread. It's misleading to label the 20-pin diagnostic connector under the hood the "ADS" connector, because that implies you need an "ADS" interface. The ADS interface uses pin 15 (RXD), which was phased out in 1996. None of the E39's in this 1997-2003 forum should need an ADS interface, but if you have any doubt, check the voltage at pin 15; if you see about 11v you need an ADS interface. If not you need an OBD interface. In any event, if you have the 20-pin under hood diagnostic connector you must use it, not the under dash OBD connector, to access all the modules.

BTW, I'm now using a MacbookPro with a bootcamp windows XP partition and a Syba true serial port express card. It works flawlessly.
 

Attachments

#95 · (Edited)
The best way to get answers to most of the questions raised in this thread is to search the Bimmerforums Diagnostic software forum.
I was wondering 'when' you were going to chime in Jeff! Remember, you started all this by your discussions with me as to the usefulness of the 'quick sensor test' versus the detailed INPA/NCS/DIS methodology! :)

Then, Quick99Si reported that the quick sensor test gave different results than the detailed fancy schmancy tools test ... and we were off (dozens of PMs later) with the first post of this thread being what it currently is.

I do agree with you that this thread (indeed, this forum) is NOT the best place for detailed Q&A with installation problems.

What this thread is 'supposed' to be about is to simply make sense of the bare minimum software and equipment to get an E39 user going on the most basic factory & dealer setup of the E39 era.

If this thread allows E39 owners to simply 'obtain' and understand the E39-era tools, then this thread has done its intended job.

In summary, you're right about 'where' to get help once you've obtained the E39 software & hardware (i.e., it's not here).

The best place to get the software and instructions is David McLean's 4shared site.
If that's the site we originally obtained the software, then that's the wrong answer.

The best place to get the recommended E39-era software is, now, actually, Quick99Si's site.

Quick99Si took great pains to download 'just' the versions needed for the E39; and he compressed the files into far far far fewer files; and, best of all, the horrifically punishing 4shared site is eliminated from the mix! (Trust me on how horrid it is for a user on a 1Mbps connection. It's actually impossible to obtain all the files needed due to the timeouts that occur.) So, anyone reading this for the E39, DO NOT go to the 4shared site unless you enjoy complexity and failure; use Quick99Si's site instead for the exact versions of E39-era software discussed in the initial post of this thread).

In summary, Quick99Si's site is 'just' what you need for the E39 (not what you'd need for all BMWs); and, most importantly, Quick99Si's renditions don't have the heinous download problems of the 4shared commercial site (which is designed to be onerous to the freebie users - and which amply accomplishes that odious goal).

One major source of confusion seems to be what was labeled the "ADS" connector/interface in the first post of this thread.
The whole point is to REDUCE confusion: not create it!

Check that first post in about an hour and let me know what else needs to be fixed as I'll try to incorporate your suggestions into the original post.

Thanks for the help. Remember, you started this ... it's only fair that you're part of the solution! :)
 

Attachments

#96 · (Edited)
The files hosted on my server came directly from the 4shared location listed above. Other sources scattered throughout have mostly the same files, likely having originated from that 4shared account, but they typically require premium accounts or days to download. I only uploaded the install files and pertinent documentation because I went through the tediuous 4shared shuffle and spent way too much time downloading stuff from there piece by piece. I realized that I myself would have LOVED a one-click-and-walk-away download location when I started this, so there you have it and it's all linked in the first post.

Fact is, my mirrors should only be considered as an alternative to the original because I did not author any of this, nor have I included the totality of the 4shared website. I only uploaded the exact files and documentation which I used from scratch, which is to say that you can grab those on your laptop, disconnect your modem, and finish the installations without the need for any additional tools or guides.

With that said, I consider David McLean's 4shared to be the Bible of our operation here and I myself am very grateful for what he has provided to us all. If there is anything important that may need rehosting for easier download, please PM me the information and I'll get it done immediately. During my installations, I would have also appreciated a guide and a breakdown of all the requirements and suggested material (eg what software does what, which is preferred, and how to run it). I wasn't able to find any of this myself, and all the information I came across was all over the place with various intents and uses in mind... this thread would have saved me so much time by simply breaking down the process into organized steps, yet it goes so much deeper than that. Heck, I still refer to it to keep up with the updates myself :)
 
#97 ·
FINALLY! SUCCESS!

Finally got both bat and ign lights to come on and all modules are accessible. I had to use a Belkin F5U409 USB to Serial and a 3 foot serial extension to do it. Note to all: When you run the OBDsetup.exe all the results must say OK for program to work smoothly. (in my case anyway) I had to change serial enum values with registry editor unitl everything matched the OBDsetup expected values. I would like to thank everyone who chipped in with all the advice to get this program working. Now on to next step and practice and install DIS/GT1, Progman.

So thrilled I had to share.
 
#98 ·
DIS/GT1 Network Problem

Need your assistance again folks.

When installing DIS/GT1, the stage were you have to configure the network editor instead of getting the "VMware Network Adapter VMnet1" under VMnet1 I get this config instead.





I have changes IP address and all instructions as per install guide. Proceeded to install the software and everything went smoothly.

After reboot and try to fire up DIS I get the following screen warnign next but program then loads normally.



Once I get DIS running to the point "Calibrating Touch Screen" to run "Configure EDIABAS" then "API test", I get a error 009, which according to the guide is a network communication problem. Unfortunately, I have no idea what to do next to fix it. Any help would be greatly appreciated again.

THANKS
 
#99 ·
Got everything in DIS up and running as well using Bluebee's associated guides and links! Guess you really have to be patient and take the time to read every little note thats out there. :thumbup:

Need your assistance again folks.

When installing DIS/GT1, the stage were you have to configure the network editor instead of getting the "VMware Network Adapter VMnet1" under VMnet1 I get this config instead.





I have changes IP address and all instructions as per install guide. Proceeded to install the software and everything went smoothly.

After reboot and try to fire up DIS I get the following screen warnign next but program then loads normally.



Once I get DIS running to the point "Calibrating Touch Screen" to run "Configure EDIABAS" then "API test", I get a error 009, which according to the guide is a network communication problem. Unfortunately, I have no idea what to do next to fix it. Any help would be greatly appreciated again.

THANKS
 
#101 ·
Linux?

Does anyone do this under linux? Does that eliminate any of the problems with the windows/vmware stuff? Is installing inpa/edabas any different? Which flavor? Ubuntu? Fedora, Red Hat? Suse? Others?

Seems to me, if you're going to install this on a dedicated laptop for that purpose anyways, why wouldn't you?
 
#102 ·
Does anyone do this under linux? Does that eliminate any of the problems with the windows/vmware stuff? Is installing inpa/edabas any different? Which flavor? Ubuntu? Fedora, Red Hat? Suse? Others?

Seems to me, if you're going to install this on a dedicated laptop for that purpose anyways, why wouldn't you?
None will run in linux outside of a virtual machine.

INPA, NCS Expert, and WinFKP are Windows programs, run best in XP.

DIS is programmed in SCO UNIX.

SSS/Progman is a Windows XP Embedded system.
 
#103 ·
DIS may work in Linux but not without extensive modification. The hardware emulation, as it is used by everyone right now, involves using EDIABAS in Windows as a bridge between the software and the interface cable. A dedicated Linux box will not satisfy this unless you were to change it to your needs.
 
#104 ·
Linux

Jeffstri, Quick99si,

That is pretty much what I thought, but I just thought it was a good question to ask. Given the problems I have been having with VMware and all.

Just out of curiosity, will any older versions of VMware, like 5 work? That one is pretty inexpensive on ebay...
 
#105 ·
Jeffstri, Quick99si,

That is pretty much what I thought, but I just thought it was a good question to ask. Given the problems I have been having with VMware and all.

Just out of curiosity, will any older versions of VMware, like 5 work? That one is pretty inexpensive on ebay...
I have EasyDIS and Progman working with the free VMware Player from VMware's site.
The attached JPGs show the network settings required. These can be adjusted using vmnetcfg.exe which is included with Player. Found in
C:\Program Files\VMware\VMware Player
after Player install.

As mentioned several times in this thread, make sure that you have INPA working before trying to install EasyDIS &/or Progman, i.e. your OBD plug is functioning & talking to the car.

Regards
RDL
 

Attachments

#107 ·
Thanks,
I will give the VMware player a shot. It might be good to update the VMware section of the first post too.

:)
It (belatedly) occurs that I may be able to help somewhat more. It seems that VMware Player stores everything it needs in a set of files, maybe. See the attached JPG for my directory. Perhaps one could:
1 download my set of files
2 install VMware Player
3 set up VMnet settings with vmnetcfg.exe
4 use Player to run a virtual machine from my files
EasyDIS might just start up without any of the installation agony.

Or, perhaps someone knows in advance if this approach will work - yes or no? There may be machine specific setting that I'm oblivious to - oops, Bluebee may be watching :D - to which I am oblivious. Probably yes, or others would have been uploading "installed" file sets already.

Now for the snag. I have zero experience uploading large files. I have BitTorrent but only ever downloaded; never made a link to start an upload. Don't have an account at a file server such as 4Shared. Not aware of other options. (When I need to transfer large files I use a USB key - the modern version sneaker net)

If someone provides detailed, step by step instructions, I'm willing to make the attempt. If all works and EasyDIS starts up for someone - great. If not, only a little time lost.

FYI, the RAR archive for my ~4GB EasyDIS directory is 691 MB (724,682,924)

Regards
RDL
 

Attachments

#108 ·
VMware

@RDL,
That is an interesting idea. The info about vmware player says it will run virtual machines created elsewhere, however, it looks as though you are running DIS 57 and Progman. I was planning on the DIS 44 route, as I dont have the disk space to run Progman, and I am still trying to keep it (relatively) simple.

I am wondering though, I created the virtual machine using VMware workstation (it did let me do that, just not start it). I am wondering if I could just use it instead of creating a whole new one using VMware player.

This just gets better all the time... :drink:
 
#109 ·
@RDL,
That is an interesting idea. The info about vmware player says it will run virtual machines created elsewhere, however, it looks as though you are running DIS 57 and Progman. I was planning on the DIS 44 route, as I dont have the disk space to run Progman, and I am still trying to keep it (relatively) simple.

I am wondering though, I created the virtual machine using VMware workstation (it did let me do that, just not start it). I am wondering if I could just use it instead of creating a whole new one using VMware player.

This just gets better all the time... :drink:
I have EasyDIS (which I put in a file set labeled GT1 - to my regret), Progman & DIS V57 all installed and running. I pick which to use from the Player menu. So, what you see listed in directory GT1 is in fact EasyDIS, i.e. V44. Also the one in the RAR archive I described.

I then copied the V44 directory, as a separate directory/file set, and upgraded it to V57 with more recent car files which does diagnostics only. Mostly to see if there was any difference in diagnostics for my E39 - none that I've observed. V57 is about 5GB on disc.

Progman is 22 GB on disc.

Regards
RDL
 
#110 ·
RDL, do you know how to use FTP? I should be able to free up some space where you can upload the 700mb file for others to test, including myself. I've seen full hdd images floating around, though they were for T30 laptops, but never such (relatively small) vm images.
 
#111 ·
FTP - that brings back memories. And gopher, telnet, whatis, etc. But it's been ages.

I don't have an FTP program installed at the moment. But I could follow the IE procedure described in the attached JPG image. Does that work for you?
Send me an address (& p/w if you wish) I'll give it a shot.

I'll try other suggestions if they suit you better.

Regards
RDL
 

Attachments

#112 ·
OK, guys, I really do appreciate all the help and info, etc. But, the first post lists a 40gb HD to do the inpa/ediabas, with EasyDIS44. That looked like an OK option to me. To go the extra distance and do the Progman thing, it calls for an additional 100gb. So, now, RDL is talking 5gb for DIS V57, which may make sense, since the coding/programming stuff isnt there in that version. But the 22gb for Progman is a long way off of what I was expecting.

Am I missing something here?

-- and the plot sickens.... :beerchug:

Really, I am having fun, honest...
 
#113 ·
It is 4 GB for EasyDIS V44 giving you diagnostics, coding and programming. EDIABAS & INPA combined are 0.25 GB. VMware Player another 0.25 GB. So call it 5 GB total.

I think the 40 GB was a result of original DIS versions being installed on computers with 40 GB drives. So the hackers set up virtual machines with 40 GB pre-allocated to avoid any size problems. But I've found that EasyDIS / Player is quite happy with dynamic sizing which works out to 4 GB for EasyDIS.

I've said in earlier posts that Progman is not worth the time & effort for E39s, at least in my opinion. And it does take a lot more space.
V57 maybe; it is a simple upgrade to do once V44 is running, but I haven't seen the benefit, at least so far. And you lose coding and programming functionality unless you keep a separate copy of V44.

Your choice of course, but it's 5 GB not 100 +. And that gives you the same capability the dealers had until the mid to late 2000's.

Hope this clarifies the matter of drive space you need.

Regards
RDL
 
#114 · (Edited)
SSS Progman load hive error

Need your help guys! Trying to install progman and am stuck at the part were the instructions say to open regedit and load hive then point to z:\ drive.



As you can see, my regeditor can not see the z: drive. What am I doing wrong? Any help or advice in solving the problem would be greatly appreciated.:dunno:

PS. This maybe a stupid question but here goes. Since i have the available hard drive space and more to install Progman, why not install a cracked WINDOWS XP PRO full version in VMWare and once done install Progman the normal way? Is it even possible? I do see a installation file on the installation DVD.
 
#116 ·
Need your help guys! Trying to install progman and am stuck at the part were the instructions say to open regedit and load hive then point to z:\ drive.

As you can see, my regeditor can not see the z: drive. What am I doing wrong? Any help or advice in solving the problem would be greatly appreciated.:dunno:
Make sure you've done the following:

Stop the VMware server.
Double-click the VM hard drive
Select Utilities > Map
Select the first partition, uncheck read-only and press Ok.

From: http://forums.bimmerforums.com/forum/showthread.php?t=1401774

Those steps basically map the virtual machine OS to the Z: drive on your laptop so that you can manipulate the registry hive.
 
#117 ·
For those trying the EasyDIS image from Quick99Si site

1 the VMware Player settings that are working on my computer can be seen in the attached images.

2 you must set VM network settings as described in post #105 above before starting the virtual machine

Good luck
 

Attachments

#119 ·
OK, I tried to install VMware player on my dell D600. It would not install with an error saying that my computer did not have certain features necessary. So I started going back in the versions from 4.0, backwards. The older versions gave me more specific messages, like exactly what CPU instruction was necessary, like CMOV, etc. When I got to 2.5, it finally installed. But it doesn't look like 2.5 will create a virtual machine, it will only run them or an "appliance" if you already have one.

Which version of VMware player works? I might try RDL's image, but I only have a 40Mb HD, so I am not sure how if that will work well.

For that matter, what versions of the VMware workstation might work? Are these untested? I hate to think I bought a computer that is just short of being able to do all this stuff.
 
#120 ·
OK, I tried to install VMware player on my dell D600. It would not install with an error saying that my computer did not have certain features necessary. So I started going back in the versions from 4.0, backwards. The older versions gave me more specific messages, like exactly what CPU instruction was necessary, like CMOV, etc. When I got to 2.5, it finally installed. But it doesn't look like 2.5 will create a virtual machine, it will only run them or an "appliance" if you already have one.

Which version of VMware player works? I might try RDL's image, but I only have a 40Mb HD, so I am not sure how if that will work well.

For that matter, what versions of the VMware workstation might work? Are these untested? I hate to think I bought a computer that is just short of being able to do all this stuff.
I'm using all the software that came with Randomy's package. I purchased a Dell D610 to use with the software but I did have to upgrade the ram to 2gigs and the hard drive to 120gigs. All and all the computer and the upgrades costs all together about $150. Once upgraded all the software provided installed correctly with no errors, except for progman. Still working on that one. Allthough, INPA and DIS are all you need to really diagnose the vehicle. Answer to your question ; using VMWare workstation 6.0.2.
 
#121 · (Edited)
Hi, above you said:

5th INPA 5.0.2 update

INPA 5.0.2 update (480MB): http://quick99si3.home.comcast.net/b...02_Updated.rar
Warning: It is unknown as yet whether this upgrade will work with the E39 (needs to be tested & reported back by someone).
This probably isn't worth the risk & effort to install.


This version is customized by me and works ok on E39 ...:)
So, the last one looks like in the picture attached (1.5 Gb)
In addition, now and DIS with the full working TIS and more.... :) (Not installed by me...only updated)

I will upload all these goods in my 4 shared very soon.

BTW: original archieve logo was replaced :)))
 

Attachments

#122 ·
This version is customized by me and works ok on E39 ...:)
Thanks for confirming that.

I will upload all these goods in my 4 shared very soon.
I'll change the first post once you get a link up so that others aren't confused.

Just let me know what the resultant links are ... (thanks)
 
#124 ·
I will upload only the "Step 3" because this one is relevant
Drat. The two-month period for updating the first post has expired (we opened it on 08-12-2011 and edited it over a hundred times before it closed on us on 10-12-2011, less than a week ago).

So, the interested user will have to, unfortunately, read forward to find the update.

Thank you very much for your information about it working well on the E39 (that was our biggest concern), and for making it available to the tribe!

It's people like you (and Quick99Si & RDL in particular for this thread) who make this forum work for the rest of us!
 
#127 ·
To help others, as always, and with permission of the sender, I post the content of the following PM (sans identifying information, of course), which shows an alternative solution that may be useful to some.

I am very grateful to your time and organization for this thread. I was able to install and run on my 05 X5 DIS and inpa. I am running INPA 447 and EASYDIS v44. I was able to install the programs on my 2009 MacBook pro running Lion. I installed it two different ways. One is through VMware Fusion running XP and the other with Bootcamp running native XP.

I did an easier install which worked for me.

  • Instead of using VMware Workstation, I installed the VMware Player- which is free.
  • I also installed the pre-built GT1 VMware image (3.6gb). It is very easy to install and you don't have the issues with base and program iso, etc.
The only thing I had to do in VMware player inside DIS was to remove and replace the LAN adapter. I think everything else was already set in the image.

There is one trick to VMware player. You have to go to Windows XP and run "c:\vmwareplayerxx.exe -/e c:\temp. This extracts a bunch of files to the temp folder. You double click on the network.cab file and it will ask you to extract vmnetcf.exe to the c:\programfiles\vmware\player directory. You have to run vmnetcfg.exe and change vmnet1 and vmnet8 to the ip values listed in the guides.

For anyone having trouble with VMware workstation or if they are running on a Mac, this information might be helpful to the thread.
 
Top