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
#269 ·
Oh man that was a fast response! Thanks a lot! I feel 100% more confident in what to purchase. I was afraid to spend money on stuff that won't work or that might mess something up. I owe you big time!
 
#270 ·
The only money should have to spend is on a quality K+DCAN Interface Cable.
 
#271 ·
Well,
I purchased one of the eBay K+DCAN cables pretty much identical to the one listed by LiquidSiver. It did come with a disc that included drivers as well as the INPA and EDIABAS. Not that I used them because I had already downloaded everything.

My issue is that it doesn't recognize ignition on my 2003 e39. I can view codes in INPA, but the ignition dot is not black. I jumped pins 7 & 8 (because they aren't despite the ebay ad saying it is), but it still didn't recognize ignition. It does have the FT232RL chip though. The biggest problem is that DIS coding won't work because it doesn't see ignition. That's the main reason I bought it. Looks like I'll be dropping the coin on a known good cable. Should have done it right the first time. :(
 
#272 ·
Well,
I purchased one of the eBay K+DCAN cables pretty much identical to the one listed by LiquidSiver. It did come with a disc that included drivers as well as the INPA and EDIABAS. Not that I used them because I had already downloaded everything.

My issue is that it doesn't recognize ignition on my 2003 e39. I can view codes in INPA, but the ignition dot is not black. I jumped pins 7 & 8 (because they aren't despite the ebay ad saying it is), but it still didn't recognize ignition. It does have the FT232RL chip though. The biggest problem is that DIS coding won't work because it doesn't see ignition. That's the main reason I bought it. Looks like I'll be dropping the coin on a known good cable. Should have done it right the first time. :(
Whenever someone posts an issue relating to INPA and having trouble recognizing modules, the first thing I point to is battery age. INPA is very voltage sensitive.

How old is your battery?
 
#275 · (Edited)
I finally gave up on the laptop I was trying to use. It had an issue with a repeating = in VMware that could not be resolved. I switched to one of my other laptops and was able to get INPA and DIS/GT1 working. Well, sort of. The issue is the ebay cable, the one I have is a clear connector and cable, and it doesn't seem to connect to the car without 'tricking' the cable firmware into making INPA see the battery and ignition. I was able to get INPA working completely and DIS can diagnose the car, but I am unable code the car with DIS. I get to the key cycle step and it won't recognize the key cycle because the cable is fooling INPA into thinking the ignition is on (since it apparently doesn't sense ignition or battery). I'm not the only one having issues with this cable. http://www.bmwcoding.com/showthread.php?88-Global-thread-INPA-connection-problem

I have a few other things I want to try with Mprog 3.5. I am curious if the same true ignition/battery detection mod for the vagcom cable can be used on the one I have.

All I am attempting to do is deactivate the daytime running lights. I do have NCSexpert and NCS dummy. I am also downloading Progman now. I am wondering if either of these will successfully code without an ignition cycle.
 
#276 ·
the car is a 09/94 530i
the laptop is a thinkpad 600
connectors are: rs232 to bmw compatible v1.3.6 black box to 20 pin bmw connector.
software is pasoft 1.3.6
objective is to scan/clear codes and maintenance interval

i have not connected this setup to the car because i have not found anyone else who has and i am very concerned that this may kill my car.
please advise as to the correctness of this setup and how to sequence the power on for the laptop and the car.
 
#278 ·
I wonder if anyone can help me with this.

I got the USB OBD cable from one-stop-electric-shop. It came with the adapter. I downloaded the INPA/EDIAS/NcsExpert... package. It has a setup program that installs everything. This is on a Windows XP.

The problem is, when INPA starts, it doesn't list any of the platform (e85, e46, etc). Basically, F3 to F8 are not mapped to anything. F2 is mapped to "Script". Is this an indication that the cable/driver wasn't working, or is there something wrong with the INPA installation?

Thanks!
 
#279 ·
...
The problem is, when INPA starts, it doesn't list any of the platform (e85, e46, etc) ... Is this an indication that the cable/driver wasn't working, or is there something wrong with the INPA installation?

Thanks!
You should post this question in the forum below too.
http://forums.bimmerforums.com/forum/forumdisplay.php?233-Diagnostic-Software

There are lots of people there with experience solving INPA and EDIBAS glitches.
Double your chances of a solution.
 
#281 ·
Hello everybody. I was unable to keep the files hosted on my server anymore, so they won't be available at the links above. Everything has been mirror to this location:

http://www.4shared.com/folder/tyVl_fZD/Install.html

PM me if it doesn't work. I think I another mirror location to Bluebee some months ago, in the event that I am unreachable.
 
#282 ·
I would strongly recommend that you not buy from ECUTOOL.COM - specifically the BMW 4 in 1 found here:

http://www.ecutool.com/4-in-1-BMW-Diagnostic-Interface_7547.html#.Ur4NFyiYDcY

The disk they sent me had the Parite.B virus hidden in the Driver_D_CAN_USB folder (this is on the regular sized ECUTOOL disk). Since we have to disable firewall and virus protection when using the software (INPA) in the car, it took over my old laptop.

I've tried to leave messages with the firm but the vehicle to do so croaks and throws me to a Chinese page.

Their product did work (once) and then I lost the PC. Unbelievable. Fool me once....
 
#285 ·
If you don't want to join 4shared and still want to copy the files, click on the link in post #283. This will take you to the folders. You will have to do this one file at a time within each folder. click on the file and then copy the link in the resulting explorer or safari or whatever page. open 4server.info

Click in the text box and paste the link, then click on the button beside the text box "Generate Link". This will initiate the download.
 
#290 · (Edited)
I'm not seeing a textbox after clicking on the individual file. It just brings up another window with a bunch of download buttons to files that I don't want. None of them direct you to the file you are trying to download. Can someone just post some direct links to the files without all of the nonsense?

EDIT:
Ok, I figured out how to download the files. I was trying to do without being logged into a 4shared account and if you do that it just pops up windows about social media. After I created an account and logged into it, when I click the download link it lets me download the files.
as counted down.
 
#286 · (Edited)
I have INPA, EBIADAS, EasyDIS, GTI, and [ TIS and ETK ] (the last two from another source that I purchased), the first two from I can't even remember where, and DIS and GTI from the link listed above (along with the VMWARE and Daemon utility) - all installed on a Panasonic C-29 toughbook under Windows XP. Thanks very much to QUICK99Si for providing a source for the software and to all who have contributed to this thread.

My $0.02 - is that there is a lot of confusion, even if you read everything end to end - especially if one doesn't understand the technical aspects of what is really happening behind the scene. One is unable to judge how different software has to be put together in different circumstances, along with the complication of trying to do it with a USB to serial converter. I read what was here, I read all of DavidMC's docs. I read the install by Randomy and MikaelK of BimmerForums. I read the install by ZigzagSky of ********* (here: http://www.meeknet.co.uk/7sf/diagnostic_codes/bmw-gt1-dis-install-831k.pdf )

A couple of things:

If you are only running INPA under XP, you don't need all the 198.168. stuff in the EDIABAS.INI file. You just have to make sure that the OBD.INI file is correct. I have a USB to Serial emulator (FTD...) and my OBD.INI looks like this at the start. Because I have a non-Dell machine, I don't worry about the UBATT and MODE stuff - just let the software take the defaults. When I was installing my version - and it came in a rar that expanded to a folder called INPA_502_Updated - I selected Com7 and ticked the box that said "USB etc".

[OBD]
Port=Com7
Hardware=USB
RETRY=ON

Before I installed EasyDis, my C:\EDIABAS\BIN\EDIABAS.INI file had:

Interface = STD:OBD (I'm using it on a 1998 528i which has the OBDS II connector in the car - but also the 20 pin under the hood [USA]. The 20 pin connector DOES NOT have a pin 15
so I don't need to use ADS)

Remotehost = OPPS
Port = 3000

When I installed EasyDis, there is a section (in the "SKY" user guide) where one has to ensure that EDIABAS.INI has the 198.168.68.... in this area with Port = 6801. That file must be within the VM machine because I have that in it, but my Windows XP EBIADAS.INI file still has the OPPS and 3000 entries. (Note that I haven't tested all this in the car yet - but it all comes up fine and my 'Ping' of the IP address works. [EDIT: I suspect that I might have to put the IP address and 6801 in my EBIADAS.INI file to get it all to work once I'm in the car. We'll see]

My BMWDiagnostic computer runs - I have tested INPA previously and it worked with the car. Now I have to test it in the context of EasyDIS and GTI. Fingers crossed.

INPA installs outside of the VMWARE. EasyDIS/GTI has TIS within it. My separate TIS and ETK (parts list that Realoem taps into) also runs on a virtual machine. I had to 'reduce' the version of TIS and ETK to get them to work in the same VMWare Workstation as the EasyDIS/GTI I had to go to an earlier virtual machine version (there are versions 4, 5, and 6 that can be accessed through the VMWare Workstation menu at the top of the window by clicking on "VM" then "Upgrade or Change Version" then following the <Change Version Wizard> that starts up and selecting Workstation X - all without any individual 'machine' started yet, just at the start of running VMWare Workstation. The reason that I tried this is that I got a message when I installed VMWare, it uninstalled the version I had for my existing TIS and ETK. When I tried to run the latter again - it gave me a conflict with the new VMWare PLAYER that had been installed. So I tried to access the TIS and ETK from inside a new machine in the VMWare Workstation - and got a version conflict. I poked around, found the change version by accident when looking for "Install VM Tools" and tried reducing the version. It worked. Then I increased the version back up to 6 and it stll worked. The conflict was mainly that my TIS and ETK had been installed with a newer version that that of the 'supplied' vmware. So now I have two virtual machines in VMWare Workstation, one with EasyDIS/GTI (which also has it's own version of TIS), and another with my original version of TIS and ETK.

My only regret at this time (there may be more once I try to talk to my car) is that the good folks who put the EasyDIS package together used the "Calibrate Touch Screen" button to put in their menu for some technical steps needed in the install. I have a touchscreen and I can't calibrate it - although it does work for the most part, some screens behave funny.

Just one final thing:

When entering the Dealer number in the EasyDIS installation, it later becomes the password for a whole host of things. 12345 is suggested. When I did that, I entered 123455 by accident. The DIS and GT1 software drops the FIRST DIGIT on the left - so my password became 23455. ie don't enter more than 5 digits and don't complicate things. :)
 
#287 · (Edited)
Here is an EasyDIS User guide - NOT installation, but how it actually works since there doesn't seem to be anything around. The pictures in the document leave something to be desired, but unless someone has other options......

http://www.motodok.com/Documentation/Files/BMW/GT1-05a-BMW-Diagnosis.pdf

If there is anyone paying attention who knows something about EasyDIS - the actual operation thereof.....

1. I've done the EasyDis install and I am using OBD not ADS. do I have to do anything similar to the ADS /FISTER protocol to have DIS/GT1 communicate with the computers in my car (1998 528i using MS41.1 DME/ECU)? the reason I ask is that everyone and their aunt seem to be using diaghead or ADS. I have neither.

2. I've done the German API menu test via the "Calibrate Touchscreen" Hidden menu. It works fine. But in DIS, I had to enter my car's data manually - and when I finally got to the screen with all the computers and systems on it, none of them were hi-lighted in black. I suspect this was because I had firewall and virus protection activated. However, before I bang my head against myriad walls - is this a correct assumption that disabling virus and firewall will work (It's too cold to go sit in the car and try things right now - I'm just looking for a little confidence that I am on the right tract).

3. Does anyone know how to to the VANOS test in DIS?

4. When I get there - is there a whole list of tests that can be done on various devices or will I have to program them myself?

Thanks.
 
#291 ·
The files were hosted on my personal server for over 2 years with direct links and uncapped download speeds. I did this because the previous location took me a week or longer to download the necessary files, and I thought I'd spare others the same paint.

I was not able to continue hosting them so I uploaded them to 2 different 4shared accounts, as well as a few offline backups for people local to Chicago.

If you are able to donate server space or have a suggesting for better storage, I'm all ears :)
 
#294 ·
The files were hosted on my personal server for over 2 years with direct links and uncapped download speeds. I did this because the previous location took me a week or longer to download the necessary files, and I thought I'd spare others the same paint.

I was not able to continue hosting them so I uploaded them to 2 different 4shared accounts, as well as a few offline backups for people local to Chicago.

If you are able to donate server space or have a suggesting for better storage, I'm all ears :)
I appreciate your effort and didn't mean to sound caviler. I just thought something like Dropbox would be easier.
 
#297 ·
Just for closure's sake. I have DIS running and spent a bit of time trying to check things out on my 1998 528i (E39 / M52, natch). What worked for me was disabling the USB serial port driver (which I had gotten from FTDI themselves) and reinstalling a driver from the provider of the 4-in-1. There was a small 2" CD that had some of the files on the larger CD (that had the virus), and it checked out clean.

After the re-install, my DME was read automatically by DIS. It seems that DIS won;t do much beyond the full diagnostic report unless you have faults. ie, I can't force a Vanos test. I can activate the Vanos and listen to the idle tone change but no test.

My next step is to try to get a printer working with DIS so I don't have to do 50 print screens / down arrow click (which takes forever) to get output from the diagnostic report. NOTHING was out of range. However, INPA says that my load (which I believe is just a calculated figure here and can be ignored), ICV air intake, and ignition angle are all out of range (I'm beginning to suspect that something might be amiss in the E39 information files, whatever they are and where ever they are, that INPA uses to decide what the ranges should be. Or INPA is reading something wrong, or DIS is the crazy one).

So, I'm in the process of uninstalling INPA 5.02 and installing an earlier version from the QUICK99Si files to see if that makes any difference.

Next up is to do the 20-pin round port hack to permit all data to come from the OBD port inside the car. Apparently, if I link pin 2 to pin 17 and pin 20, this does the trick. I've checked the diagrams for the port and this apparently will route the K-line stuff to where all the modules can be read.

I'll probably start a new thread entitled "gmak's adventures in Won-Dis-Land". Don't know whether to put it here or another forum.
 
#298 ·
I have INPA and DIS/GT1 installed. INPA runs fine. I can't get DIS/GT1 to work, however. I've double and triple checked all of the settings in the various files but can't get the connection to work. I get a message in DIS that says "There is no connection to a diagnostic head" when I try to run diagnostics in DIS. The cable is a FIDI FT232RL chipped cable with pins 7 & 8 bridged. APITEST works fine in DIS. I can ping 192.168.68.1 & 192.168.68.30 from Windows when DIS is up and running. So I'm thinking it's something with the cable itself, but not sure what. Any suggestions?
 
#301 · (Edited)
I've haed the mysterious mobilteil pop up

I've just ignoreed it.
:thumbup:
Sounds like you're good to go with Fister and VM. Let us know if that did the trick.

I'm looking for a way to get INPA 3.01 running at the same time as 5.02 so that I can see if they give me the same stuff. I migh upgrade DIS to v57 from v44 to see if that gives me an ad-hoc VANOS test.

good times.
 
#302 · (Edited)
I'm going to look into v57 once I tinker with v44 a little. Mainly just curious what it can do that v44 can't. I'm just interested in the diagnostic capabilities of the various software and won't be doing any programming to speak of.

I came across TIS 12/2007 if anyone wants it. I have installed it in DIS v44 and it works fine. Here is the link:
http://download.qclt.com/bigfiles/BMW.TIS.12.2007.English.iso
 
#306 ·
I'm going to look into v57 once I tinker with v44 a little. Mainly just curious what it can do that v44 can't. I'm just interested in the diagnostic capabilities of the various software and won't be doing any programming to speak of.
...
I've had V44 & V57 for a couple of years now. I've not noticed any difference between them on my 2003 530/E39 build date 9/02. However I haven't done any organized comparisions either, so there may well be some that I haven't seen.

But, V57 does have a least one advantage. It will identify and diagnose model years that V44 won't. For instance a friend with a late 2007 Z4/E85 needed help removing transport mode. V44 wouldn't identify and then diagnose his car (even with manual input), V57 did so without hitch.
 
#303 ·
TIS in DIS

Do you have to keep it linked via a virtual CD, as an .ISO file?
I set up a CD Rom in the Virtual machine and pointed it to the TIS .ISO file. Then I installed it through <Adminstration> on the DIS first screen.

However, I need to keep that CD existing or the TIS button turns off. Have you found an alternative to this?
 
#304 ·
No I do not have to keep the CD in or the ISO mounted to use it. When I installed it there was an option to install it to CD or Hard Disk. I chose Hard Disk, so I don't need the CD/ISO.

I mounted the ISO using DameonTools, then in DIS went into the Administration menu and activated the CD. Then under the TIS menu, I clicked on the installation button. Then there was a popup about installing it to hard disk or CD. I choose hard disk and then it ran it. It took probably 1.5 to 2 hours for the process to finish.
 
#307 ·
Thanks for the heads up, rdl. That saves me the trouble of setting up v57, as I won't be using on anything other than my '03 325i at this time.


SUCCESS!!! HUHRAY! It works! The combination of setting the protocol to fister, turning off vm, and installed NET Framework fixed it. Not sure which did the trick, could have been all 3, but she is working now. IDs the car and everything.

I must say, DIS is awesome. I should have set it up years ago. I'm going to have to spend some time learning how to use all of it's features but it seems pretty straight forward thus far. Thanks to everyone that has contributed to making this possible.
 
Top