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
#128 ·
Hi all,

Newbie to Bimmerfest and BMW E39 ownership, but following this thread with massive interest.

Thought I'd chip in with a simple clarification about the difference between VMWare Player and Workstation.

Basically, as the name suggests, Player can only run an existing Virtual Machine whereas Workstation can create a new Virtual Machine.
Furthermore, Player will let you make changes within the contents of the VM itself but is limited to the extent of changes that can be made to the environment. So you can save files within the VM guest machine (to give it It's correct name) but you can't necessarily add new core hardware e.g additional CPUs.


A side note - bluebee, you are a superstar, nowhere have I come across anyone as thorough and pernickety as you. If ever you want to leave the horrible weather in CA and come to the luxury of Yorkshire over here in the UK, I have just the job for you :)

Quick99Si and RDL - you two also deserve praise for the contributions you have made

Thanks all
S
 
#129 ·
Hi all,

Thought I'd chip in with a simple clarification about the difference between VMWare Player and Workstation.

Basically, as the name suggests, Player can only run an existing Virtual Machine whereas Workstation can create a new Virtual Machine.

...stuff deleted
Thanks all
S
The EasyDIS that I sent to Quick99Si, which he then kindly made available for downloading, was created with Player 3.4.1. I've no knowledge of the capabilities of other versions.
 
#130 ·
EDIABAS 6.4.3 or 6.4.7 ?

Hi Guys,

Not sure if I should be asking this here or somewhere else, feel free to [tell me to] move it if inappropriate.
So I've just got a USB ODBII cable, gone through all the s/ware installs and I have communicatons with my vehicle - result :thumbup:

(INFO, maybe for bluebee - I'm actually running this in the "special" XP Mode on my Windows 7 x64-bit laptop. I believe that INPA 5.02 supports x64 natively, but I'm taking things one step at a time)

However, I need some guidance as to software versions and modules.

I started by trying to interrogate the LCM module (as I think my headlight adjuster wheel on the dash is faulty, so am hoping INPA can help - but that's for a further investigation!)
When loading, I get some warnings (rather than errors) about a module mismatch, or similar. It does eventually give me some info back, but I don't think I trust it.

Using INPA 4.4.7 by the way.....

So I followed Quick99si's postings #51 and #52, to get a list of all the modules that INPA thinks are installed. I see the following:-

control unit : LCM_IV
ID_BMW_NR : 6961142 ID_HW_NR : 7 ID_SW_NR : 77 ID_COD_INDEX : 24

So I reckon I have an LCM_IV with s/ware rel 24

When I load NCSDummy and select E39 and then look for the LCM modules, it only seems to go as far as LCM.C21

With the cable I acquired, there are instructions to download and update to EDIABAS 4.4.7 and INPA 5.02 (which are supposed to work with Win7 x64).
I've installed both of these and in the new NCSEXPER\DATEN\E39 folder, I now see LCM.C24 (as well as the older versions, up to LCM.C21 on 4.4.3)

Here's the question then - if I copy the new NCSEXPER\DATEN\E39 folder to my "working" installation, do you think the INPA will recognise the newer module definition?
[I am just about to go re-read the NCSDummy guide again to see if my question is answered in there - in which case I will take any replies of "RTFM" as deserved :) ]

Are there any issues mixing different versions of EDIABAS/INPA (and maybe NCSExpert)?

Incidentally, it seems that NCSExpert does NOT run in Win7 x64, looks like it is only EDIABAS and INPA that work.

The final piece of the equation to add, my vehicle is a late (October) 2003 530d Touring, so probably has the "latest" (or "last") relaease of the software/modules, any comments?

Looking forward to hearing from you gurus out there ......

Rgd
Simon
 
#131 ·
Hi Guys,

... stuff deleted ...
However, I need some guidance as to software versions and modules.

I started by trying to interrogate the LCM module (as I think my headlight adjuster wheel on the dash is faulty, so am hoping INPA can help - but that's for a further investigation!)
When loading, I get some warnings (rather than errors) about a module mismatch, or similar. It does eventually give me some info back, but I don't think I trust it.

Using INPA 4.4.7 by the way.....

So I followed Quick99si's postings #51 and #52, to get a list of all the modules that INPA thinks are installed. I see the following:-

control unit : LCM_IV
ID_BMW_NR : 6961142 ID_HW_NR : 7 ID_SW_NR : 77 ID_COD_INDEX : 24

So I reckon I have an LCM_IV with s/ware rel 24

When I load NCSDummy and select E39 and then look for the LCM modules, it only seems to go as far as LCM.C21

With the cable I acquired, there are instructions to download and update to EDIABAS 4.4.7 and INPA 5.02 (which are supposed to work with Win7 x64).
I've installed both of these and in the new NCSEXPER\DATEN\E39 folder, I now see LCM.C24 (as well as the older versions, up to LCM.C21 on 4.4.3)

Here's the question then - if I copy the new NCSEXPER\DATEN\E39 folder to my "working" installation, do you think the INPA will recognise the newer module definition?
[I am just about to go re-read the NCSDummy guide again to see if my question is answered in there - in which case I will take any replies of "RTFM" as deserved :) ]

... stuff deleted ...

Rgd
Simon
I can't answer your precise questions, but here is some background data that may help.

NCS Dummy reads from files in the path C:/NCSEXPER/. It doesn't check the version number. NCS Expert 3.0.8 goes up to LCM.C21. Ver 3.1.0 up to LCM.C24. I have both installed, each in a separate directory. I can switch from one to the other by simply renaming the directories: the "active" version is the one in directroy named C:/NCSEXPER.
(FWIW, I did this early on when I had other issues that I was trying to debug with Revtor's assistance. Nowadays I use V3.1.0 exclusively. Just haven't bothered to delete V3.0.8)
I don't know if the file contents are identical. It's probably safer to rename directories if you have both versions installed.

I vaugely recall reading that INPA 5.02 has problems with E39s, or perhaps with EasyDIS or Progman, I can't recall. Since INPA 4.4.7 works on my 09/02 build, I've left well enough alone.

If your issues continue, look to
http://forums.bimmerforums.com/forum/forumdisplay.php?f=233
for definitive answers.
 
#132 ·
Thanks for the rapid response.

I think I'm gonna try doing an update to NCS Expert and EDIABAS but not INPA on my working PC (rather than the Win7 x64, which is introducing too many variables at once!) and see if it then recognises the LCM without the warnings.

I think I can just copy / rename all the folders, I'm sure I read somewhere that the software installs don't write anything to the registry so can just move folders around as required.

Watch this space ..... :)

Rgds
S
 
#133 ·
For the record, this was posted today:
- E39 (1997 - 2003) > Look Inpa Videos for Beginners

Hi Guys
I am doing a bunch of short videos on how to use the Inpa Program for Basic stuff. I have been doing alot of research on the Program and after many weeks decided this could help others. I am no expert and don't claim to be I just would like to share what I have learnt so far and just how cool the Inpa program can work for you. Yesterday I went and looked at a E38 730iL and after getting permission to check out the codes on the car and do a live run I was so glad I had the program up and running. The car had 14 Faults and after a test drive and clearing the faults the Faults all came back plus 2 more. I also found quiet a few problem in the Live reading that frightened the **** out of me. The best part about it was the car salesman had no comeback and quickly dropped the price $2,000 if I would take the car. These videos are just to try to help someone out.
I hope this helps some one.
I will keep updating
Cheers
Addam

This Website has all the Codes that can be read and work with Inpa,
http://www.endtuning.com/bmwcodes.html#ecutop

Just make sure when starting up Inpa you use the correct settings of you car.
For Eg: My car has a M62TU Motor and was Built after 6th month 99 so I use
DME 7.2
The Bosch DME 7.2, also known as ME7.2, can be found on a number of V8 Petrol engines, used in the 5 and 7 Series amongst others. It uses Torque modeling to control the engine torque output depending on Throttle Pedal Position

Part 1:
How to Reset your Oil and Service lights on your console.
http://youtu.be/6sIgeP7fH_o

Part 2:
How to Check for Engine Fault Codes
http://youtu.be/MpfinqNSwYw

Part 3:
How to check Engine Live Analog Data
http://youtu.be/TfuBVk1GGAA
 
#134 ·
Hi Guys

New to this Forum but have been Member of various international ones for over 4 years.


I have a question its only short, I installed INPA EDIABAS over a year ago. When installing INPA i did not choose to install NCS expert as at the time i was merely using the Diagnostics to troubleshoot and reset /clear codes.

I now wish to code some minor items and was wondering the best way to get NCS installed. Do i have to overwrite the entire INPA install and select the NCS option or is their a shorter method?


Cheers! From Ireland
 
#135 ·
Hiya,

I think you'll find that if you re-run the installation program, there are options to tick a full install or update for each of the various components (INPA, NCS, WinKFP etc).

So just go ahead and select NCS, you should be fine.

(I'm no BMW/INPA/NCS specialist, but I am an IT professional, spent a lot of time recently experimenting with various installation/configuration options etc so I'm confident about my suggestion!)
Also, unless I'm mistaken, there is very little that could go wrong even if you do re-install INPA/EDIABAS again anyway - the worst you could do is over-write the .INI file, and that's not the end of the world to fix.

Enjoy :)
 
#136 ·
Hiya,

I think you'll find that if you re-run the installation program, there are options to tick a full install or update for each of the various components (INPA, NCS, WinKFP etc).

So just go ahead and select NCS, you should be fine.

(I'm no BMW/INPA/NCS specialist, but I am an IT professional, spent a lot of time recently experimenting with various installation/configuration options etc so I'm confident about my suggestion!)
Also, unless I'm mistaken, there is very little that could go wrong even if you do re-install INPA/EDIABAS again anyway - the worst you could do is over-write the .INI file, and that's not the end of the world to fix.

Enjoy :)
Much appreciated!

Im off to have a fun weekend in front of the laptop :D
 
#139 · (Edited)
Ok, I am having some trouble here and I am not too computer savvy but trying to learn as much as I can before asking dumb questions.

I am using a new laptop with Windows 7 and downloaded the INPA/EDIABAS.rar files and extracted them, used Daemon Tools and have installed INPA/EDIABAS using Quick99Si's guide but I am having trouble when I try to open the INPA (_.IPO) file. I get a message box that looks like this...

My largest area of trouble is understanding what VMware is used for and whether I need to download/buy UNIX/WindowsXP and whether I am running this separate operating system in VMware???
sorry if this is covered somewhere or maybe I just don't know enough about computers but I'm trying!
:cry:
 
#140 ·
INPA is designed to work on a 32-bit windows system. You're probably getting the error because you have a 64-bit version of Windows 7.

WMware is an emulation software (kernel) that allows a system (windows in this case) host one or more guest systems (Linux in this case). GT1 and EasyDIS only run on Linux.
 
#141 ·
As previous poster states, the file you are trying to run doesn't like your version of Windows 7, which is almost certainly going to be 64-bit. Check by finding the "My Computer" icon ( either on your Desktop already, or on the right hand side of the main Start menu)
Right click on My Computer, select Properties and have a look at the screen, somewhere in there it will tell you it is either a 32-bit or 64-bit operating system.

Regarding VMWare - this is a clever bit of software that allows you to run another "session" on the same computer. The session can be a different version of the operating system to the main laptop system. As an example, I have a Windows 7 64-bit laptop with VMWare installed. Using this I can run a copy of Windows Server 2003, or Linux Ubuntu, or Windows XP - or all at the same time!
Another way to think about it is a bit like running "Picture in Picture" on your TV, where you can keep an eye on the sports game while the Mrs is watching her favourite soap!

Be aware of licensing though - VMWare is NOT free (VMWare Player is, but that's a different story).
Also, if you use an operating system such as XP with VMWare, you need a license for that operating system as well, so to keep things legal it can get expensive.

The way round this with Win 7 is to use a feature called Windows XP Mode. This allows you to run an XP session inside your Win 7. If its not already installed on your laptop, it can be download for free from Microsoft.
Furthermore, you can then add NCS Expert to this XP session, you are then good to go!

If you get really stuck, you can try PMing me and I can try to help, bear in mind I am UK based though :)

Rgds
Simon

(in case there are any IT types out there, I know the use of the word session is not technically correct, but I find it the easiest way to explain it to non-techie folks.)
 
#142 ·
Oh, and just to confuse matters even further, there is a version of INPA that does run on Win 7 64-bit, but I have read that it isn't too friendly with earlier E39's. I can't comment as I tend to go straight to my XP mode as more than likely I will want use NCS as well, which is a definite no- no on Win 7-64.

S
 
#143 ·
I have working

Inpa Version 5.0 (David Mc Modified version)
NCS-Expert V3.1.0
NCS-Dummy 0.5.0.5
EDIABAS Toolset 32 Version 3.2.7
WinKFP Tool 32Bit-Version 5.1.0
GT1 DIS v44 Program
BMW TIS Technical Information System 12/2007
VmWare Workstation v6.0.4 Build 93057
BMW Wiring Diagram System

All loaded up and working great on my laptop :thumbup:.
If any Member here lives in South East Queensland needs to use my laptop please pm me and I will be only to happy to help
 
#144 · (Edited)
This is a great How to set up NCS, I can't remember where I got it from because I copy and pasted it to a notepad file.

Reading FSW/PSW trace files with NCS Expert
Despite people's claims of how dangerous NCS Expert is, reading FSW/PSW trace files from a car is perfectly safe as
long as you keep your head at the job. NCS Expert's default setting is to code, which we definitely don't want (at this
point), but once the job type is changed to reading the program is harmless. You don't need to take special
precautions for the car. Reading trace files takes just seconds, so there's absolutely no need for an external power
supply. Low battery voltages cannot cause damage, but may of course drop the connection so you are unable to
complete the trace file reading. So make sure your batteries are ok and properly charged.
Before you can start reading FSW/PSW trace files with NCS Expert you need a good profile. By default NCS Expert
comes with the "Expertenmodus" profile ("FZG2.PFL"), which despite the name is not that expert at all. You can
either use the "Fisterprofile" ("GOODFIST.PFL") from the founder of bmwecu.org, or my profile:
Unpack the zip archive and put the "REVTOR.PFL" profile file in the "EDIABAS\NCSEXPER\PFL\" folder.
Go to the "EDIABAS\NCSEXPER\WORK\" folder and (if not already existing) create a new empty text file called
"FSW_PSW.MAN".
Now connect your diagnostic interface to the car and turn the ignition to I. Test the connection with for example
INPA. Don't forget to close INPA before using NCS Expert. The interface throws errors when multiple applications try
to get access to it.
1. Once the profile is in the PFL folder and the diagnostic link ok, launch NCS Expert. At this moment no profile
is loaded, so the screen is quite empty.
2. From the "File" menu, choose "Load Profil".
3. In the "Choose profile" popup window, select "Fisterprofile" or "Revtor's NCS Expert Profile" and click
"OK". Nothing much happens, but you'll notice some of the buttons on the bottom now have labels.
4. Click the "VIN/ZCS/FA" button (F1). The button labels change once again.
5. Click the "ZCS/FA f. ECU" button (F3).
6. In the "Choose CHASSIS" popup window, select "E31" and click "OK".
7. In the "Choose ECU" popup window, select "EKM" and click "OK".
8. After a short moment, the top groupbox should now show information regarding your car.
9. Click the "Back" button (F6). The middle groupbox now shows the available modules and default job name.
The default is "SG_CODIEREN" which we definitely don't want, so pay attention what buttons you press
right now!
10. Click the "Process ECU" button (F4).
11. In the "Choose ECU" popup window, select the desired module and click "OK". If you want to read all
modules, you'll have to work module by module. Select for example the General Module ("GMII").
12.A popup window displaying the *.C??, *.IPO and *.PRG files for the chosen module is shown. Write these
filenames down as you may need it for NCS Dummy. Click "OK".
13. Click the "Change job" button (F2). If "JOBNAME" in the middle groupbox already reads
"CODIERDATEN_LESEN" you can skip the following steps and jump to 16.
14. In the "Choose job" popup window, select "CODIERDATEN_LESEN" and click "OK". The default job action is
now reading instead of coding. Note that NCS Expert will still say "get coded" in the middle groupbox and
during the read operation it says it's coding... but it will not. "CODIERDATEN_LESEN" is a safe read-only
operation.
15. Confirm "JOBNAME" in the middle groupbox says "CODIERDATEN_LESEN".
16. Click the "Execute job" button (F3). The process takes only a few seconds. As said, NCS Expert may indicate
it's coding but it's actually only reading.
Head over to the "EDIABAS\NCSEXPER\WORK\" folder. In it is now a file that interest us: "FSW_PSW.TRC". The first
is the human readable FSW/PSW trace file. Each time you read a module with NCS Expert this file is overwritten, so
you must move or rename it (no need to copy - if the original file is missing, NCS Expert will write a new one). For
example: "E31.GMII.FSW_PSW.TRC".
You have finished creating a FSW/PSW trace file for the GMII module.
If you want to read a FSW/PSW trace file from another module, head back to NCS Expert, click the "Change ECU"
button (F1) and repeat the steps starting from 11, but with a different module.
When finished, simply close NCS Expert.
You can open the "FSW_PSW.TRC" file (or whatever you renamed it to) in a plain text editor. The "FSW_PSW.TRC"
files are also the files used by NCS Dummy to create trace parameters or trace file differences.
Coding modules from an updated FSW/PSW trace file with NCS Expert
First of all make sure you have a good NCS Expert profile. Read the previous chapter for more information on
profiles.
Where little could go wrong with reading, coding is a different story. You don't want the battery voltage get too low
during coding as this may render the module dead. Luckily old bimmers like the E31 don't take long to code - just
seconds per module. So you don't need any special precautions if your batteries are good and properly charged.
Nevertheless it's recommended to attach a small 13.8 V power supply to keep the voltage well over 13 V. A simple
battery charger with power supply mode functionality and a current output of 5 A or better should be sufficient.
Note that newer bimmers may take a lot longer to code, with a much higher current draw. BMW recommends
power supplies that can deliver over 40 A for newer cars.
Make a copy of the FSW/PSW trace file you wish to make changes to. Open the copy in a plain text editor, make the
changes and save the file. Rename the copy to "FSW_PSW.MAN" and put it in the "EDIABAS\NCSEXPER\WORK\"
folder overwriting a previous version (if existing).
Connect your diagnostic interface to the car and turn the ignition to I. Test the connection with for example INPA.
Don't forget to close INPA before using NCS Expert. The interface throws errors when multiple applications try to get
access to it.
1. Launch NCS Expert. At this moment no profile is loaded, so the screen is quite empty.
2. From the "File" menu, choose "Load Profil".
3. In the "Choose profile" popup window, select "Fisterprofile" or "Revtor's NCS Expert Profile" and click
"OK". Nothing much happens, but you'll notice some of the buttons on the bottom now have labels.
4. Click the "VIN/ZCS/FA" button (F1). The button labels change once again.
5. Click the "ZCS/FA f. ECU" button (F3).
6. In the "Choose CHASSIS" popup window, select "E31" and click "OK".
7. In the "Choose ECU" popup window, select "EKM" and click "OK".
8. After a short moment, the top groupbox should now show information regarding your car.
9. Click the "Back" button (F6). The middle groupbox now shows the available modules and default job name.
10. Click the "Process ECU" button (F4).
11. In the "Choose ECU" popup window, select the desired module and click "OK". Make sure the updated
"FSW_PSW.MAN" trace file is for the same module.
12.A popup window displaying the *.C??, *.IPO and *.PRG files for the chosen module is shown. Click "OK".
13. Click the "Change job" button (F2). If "JOBNAME" in the middle groupbox already reads "SG_CODIEREN"
you can skip the following steps and jump to 16.
14. In the "Choose job" popup window, select "SG_CODIEREN" and click "OK". The default job action is now
coding.
15. Confirm "JOBNAME" in the middle groupbox says "SG_CODIEREN".
16. Click the "Execute job" button (F3). The process takes only a few seconds on older cars like the E31.
After NCS Expert has finished coding, close the application and turn the ignition back to off. That's all there is to it.
The car has been coded.
As stated before, this coding method does not change the ZCS. In other words, if you ever recode the car using the
ZCS all your changes will be lost. So if you are happy with the new coding, keep a backup of the "FSW_PSW.MAN"
file - just in case. I also recommend keeping a backup of the original unchanged "FSW_PSW.TRC" file.
 
#145 ·
Here is another cheap USB cable that I can confirm seems to work. (I may have missed it, but I don't think I've seen it mentioned before.)


I was a little reluctant at first, due to the really mangled product description:

"Reference Data 1.This cable can not work if your car uses a protocol ssystem like VPW,PWM or Can-bus. 2. Bus of communication 3.Terminal L= Ignition for waking up car computing system (ECU: Engine Control Unit) 4.Existed 3 different protocols with same OBD2 connector incl. ISO/KWP, VPW, PMW 5.This K/L Diaqnostic interface & cables work on ISO/KWP (Kev Word Protocol) Iaunched after 1996 only 6.Supported also ISO9141 protocol 7.The cables may work with some versions of the Carsoft, but carsoft used a lot of different intercaces during the different versions and also had some custom interfaces. 8.Product running as virtual comport, like many products it usees a USB to Rs232 converter chip .But under special circumstances this can give some problems regarding time especially on the handshake lines. 9.Read & erase error code, log data e. g. speed, gasoline, consume engine-rotating(RPM: Rotation Per Minutes). "

Bottom line is that I don't think it can handle all the possible ODB2 electrical interfaces (i.e. no GM, Ford, etc.), but it does do BMW E39. Out of the box it only works for engine and transmission, but you can very easily open it up and jumper the back side of pins 7 and 8 to be able to access all the other subsystems.

Testing was done on Windows7 64bit laptop. Per some other threads on interfaces based the FTDI chipset, I ignored the drivers that came with it. I was about to download the latest from their website, but instead I just let Windows sort it out on it's own, and it worked fine. Also, you have to install a newer update to the INPA Etc. suite of software before it will work with 64bit. Plenty of other helpful instructions on bimmerforums.com and e46fanatics.
 

Attachments

#146 ·
Hi Guys
If you are after ready to go Cables to suite your car contact Jimmy
http://bmwcables.moonfruit.com/
He supplies the Cables needed plus FREE all the software including Inpa,NCS,DIS and more on Disk.
The best part is they are USB and no need for serial port.
I have a 1999 Built E39 535i Msports with the OBD in the motor bay but I also have the 16 pin in the dash.
I bought the K-Line cable plus the 16 to 20 Pin adapter cable (second one from top) and this works straight off with Ingition and reads all modules.
Hope this helps someone.
 
#148 ·
BlueBee,

Where's your donate button? I've rummaged around to understand coding for some time now and it didn't all come together for me until discovering your post. Since discovering your post, I've managed to install and validate settings on all programs up to but not including "Progman" and am currently now only waiting on my cable to arrive to test. So, I feel very appreciative! :) Thnx!!!
 
#149 ·
Where's your donate button?
I wish I had one! :)

Lord knows, I could use it now.

But this thread was/is the effort of quite a few people, so they'd all get a fair share of the winnings! :)

Glad it helped you. What you should do for payback is write up a vignette for others to follow on performing a task with the tools.

Good luck!
 
#152 · (Edited)
OK. Well, I thought I set everything up correctly including successful ATI test; however, on my first attempt I couldn't even read the car. I read somewhere about modifying latency and com settings for OBD cable with directions in this folder C:\EDIABAS\Hardware\OBD; however, my directions are in German and can't figure out how to translate them.

What happens is I plug the cable into my computer and open INPA. I get the fast blinking circles on the left but the battery/ignition circles remain unfilled. Thoughts?

Update: Figured it out. Plugged in cable. Then right-clicked on computer, selected manager and then selected USB (?) for the cable. Went to properties, select advanced and changed latency to 1 and selected com1. Now black circles. Tried opening up NCS expert and when I went to load profile I got a pop-up saying application stopped working and to close or close and look for solution online. Specifically, NTVDM.exe has stopped working. I'm not making headway in finding an answer but still looking...

Update 2: Needed to use "Windows XP mode" in virtual operating machine.
 
#153 ·
INPA for E92

Hi Guys,

Hats off for a lot of useful information. I could not have even thought about messing with my bmw without forums like these.

I just bought the DCAN/KCAN (inpa compatible) cable. I can see that INPA can see the ingition when I switch the car on. However version 4.4.7 of INPA does not have support for E9X.

I have tried running some of the other diagnostic options such as special tests but it errors out.

What are my options at this time to get INPA to work?
1) Update INPA with the datens files for E92(where do I get these from and how do I update them)
2) Update INPA to a newer version and hope that it has the daten files for E92 in it.

Please help. Have spent a huge amount of time already without much success. I know this forum is for E39's. Unfortunately I haven't found much information about E92's anywhere :(
 
#154 ·
#157 · (Edited by Moderator)
Starting DIS v57

Hi - I have installed DIS v57 and SSS v32 but can't get them to start. According to my installation instructions the file 'other.vmx' should start DIS v57 and the file 'Windows XP Professional.vmx' should start SSS v32 in VMWare, but when I try to open these files I get the message 'Windows cannot open the file 'other.vmx' it needs to know what program created it. What am I doing wrong? Thanks
 
#158 ·
Hi - I have installed DIS v57 and SSS v32 but can't get them to start. According to my installation instructions the file 'other.vmx' should start DIS v57 and the file 'Windows XP Professional.vmx' should start SSS v32 in VMWare, but when I try to open these files I get the message 'Windows cannot open the file 'other.vmx' it needs to know what program created it. What am I doing wrong? Thanks
Did you download those VM files or did you make your own using the files and instructions in the first post titled "3rd EasyDIS 1.0 (which is DIS v44) and the READTHISFIRST document from DavidMC" (under heading #4)?
 
Top