Bmw Diagnostic Software

Posted on by

This is a great write-up of INPA BMW software and hardware (K+DCAN interface), incl.:

Description: Bmw diagnostic tool BMW ICOM A2+B+C Diagnostic & Programming TOOL supports BMW All series diagnose and programming,The best bmw scanner or BMW, MINI, Rolls-Royce BMW-Model Item No. We provide the software you provide computer and diagnostic interface! Our system includes the BMW 'Dealer Information System' (DIS), 'Software Service Station with Progman' (SSS Progman) and the tools the factory used to program your car to start with - the EDIABAS tool set. Autohex BMW Diagnostic Software provides two different channels of CAN BUS acting like a Gateway, this Gateway simulation will allow you to connect both DME (or DDE) and CAS together to Autohex II WVCI and then you can do all required jobs like key programming, ISN matching, Ecu programming and coding simultaneously on both Ecus in one session.

– inpa bmw definition

– inpa 5.0.2 & 5.0.6 download

– inpa software install (windows XP/7/8/10)

– inpa driver software installation

– inpa bmw how to use

– inpa k+dcan cable website

– k+dcan cable advantage & disadvantage

– k+dcan cable how to use

– inpa vehicle coverage

– protocols support

1.Driver Error

2.EDIABAS Error 126 (only up to Ediabas V6.4.x)

3.ToolSet Error: Runtime error ’372’

4.INPA: vehicle could not be identified

5.INPA Error IFH-0009: NO RESPONSE FROM CONTROL UNIT

6. BMW INPA Edibas IFH-0018: INITIALIZATION ERROR

in detail…

Part 1: INPA software

– inpa bmw definition

INPA is used for BMW diagnostic & coding software, working with INPA/Ediabas K+DCAN USB interface for E-Chassis vehicles from 1998 to 2008.

– inpa software download

inpa 5.0.2 download:

inpa 5.0.6 download:

Software Version: 5.0.2 and 5.0.6

Operating System: Windows 7/10/XP

Language: English

Update: Can NOT update

Car: BMW E-Chassis vehicles from 1998 to 2008

Compatible Hardware:INPA/Ediabas K+DCAN USB Interface

– inpa software Windows 7 install

VERY IMPORTANT:

1.Close anti-virus software

  1. INPA BMW software must extract to the local desk (System C), or it would be reported to the error
  2. Never update the software

Main steps to install inpa:

Step 1: Install INPA software

Step 2: Connect Inpa cable with the laptop

Step 3: Install INPA software driver

inpa installation instruction in detail:

Free Download Inpa BMW Software from the CD off obdii365.com

(it’s good to get the free software on the web, but do confirm it’s security and functionality before download. if not, obdii365 is your way to go. inpa software is tested successfully by thousands of and millions of professionals)

Extract “BMW Inpa” to desktop, then Double-click on “Inpa V5.02″, and extract ” cicdaten” “ediabas_7.2.0.504_” “NCSEXPER” these three compressed packages at the same time to “local desk C (System C)”

Click on “Extact to”, then choose “System C” , after that, click on “OK”.

Click on “Yes to All”.

Open “My computer” then find Bin folder, and choose and right click on ” INPALOAD”, then send it to Desktop (create shortcut).

Choose My computer, right click on and choose “Properties”.

Choose and click on “Advance system settings” to open System Properties

Choose “Advanced” , then click on “Environment Variables” button

Choose “path” then click on “New” button

Enter the “path” to Variable name, and enter the Bin location to Variable Value.

Click on the “OK” button.

Double-click on “INPALOAD_Shortcut” button to open INPA program.

INPA BMW software installation success!

Tips: for more tips of inpa install, pls click on operation system below to get the installation instruction

Windows XP, Windows Vista 32bit, Windows 7 32, Windwos 7 64bit, Windows 8, Windows 10

– inpa driver software installation

k+dcan interface is connected to the laptop thru the USB port

Choose My computer, then right click on “Manage” button after connect with INPA BMW cable.

Choose and click on “Device Manager” button, then choose and right click on “USB Serial Port(COM6) Properties” button, and click on “Properties” button.

Choose and click on “Port Settings” button then click on “Advanced” button.

For ” COM Port Number” choose “COM1”, for “Latency Timer(msec)” choose “1”, then click on “OK” button.

inpa driver sw is installed!

– INPA BMW how to use

How do I start INPA?

Start Inpa using Inpaload.exe in C:InpaBin or alternatively C:EC-AppsInpaBin or use Start All Programs EDIABAS INPA ELDI NCS NFS INPA(_.IPO) to start the general reworking programme. This corresponds to calling Inpaload.exe under smuc0900sgInpaBin or alternatively C:InpaBin.

How do I find out what EDIABAS package is installed?

The version of the currently installed Ediabas package can be seen in the files C:EDIABASversion.txt or C:EDIABASpackage.pdf.

How can I uninstall EDIABAS or INPA?

You uninstall INPA by deleting the Ediabas and Inpa folders under C:. Reason: No registry entries are made during the installation.

What is the difference between EDIABASbinToolSet.exe andEDIABAbinTool32.exe?

Tool32.exe is current and when it is started, the Ediabas server will start as a 32-bit application. ToolSet.exe is an old version and is required under Windows 3.11.

What do SGBDs with the name _xxx mean?

SGBDs that begin with “_” (e.g. _LWS5), contain jobs that are only intended for development (e.g.: writing the ident data). These SGBDs are not used in production or in customer service.

What is the KVP Editor?

KVP stands for continuous improvement process. The KVP Editor can be called when using the INPA Tool. This is mainly used in reworking and in the plant. Here, the user has the possibility to enter his name and telephone number and then enter an error description and improvement request and then to send the form directly to the person responsible at BMW.

Part 2: INPA cable

– inpa k+dcan cable website

k+dcan cable price: 17.99

Good to know: Is K+Dcan cable is the right one you need?

K+Dcan cable and ENET Esys cable and ICOM Next, which one should you have?

Look here: http://blog.obdii365.com/2017/09/13/k-dcan-cable-vs-enet-cable-vs-bmw-icom/

It depends on your purpose (diagnostic or coding or programming) and model (Exx or Fxx or others).

For Coding, you need different Tools, NCS Expert / SP-Daten for E-Series and E-Sys / PSdZData for F-Series.

All Diagnosis and Coding can be done with cheap DCAN Cable for E-Series and cheap ENET Cable for F-Series.

For Programming (Flashing ECU’s with new Firmware), then you need ISTA/P for for both E-Series and F-Series cars, or you can use WinKFP for E-Series and E-Sys for F-Series. For E-Series Programming, you will need an ICOM, but for F-Series Programming, you can use ENET Cable.

– k+dcan cable advantage & disadvantage

Connection by soldering is a bad option as it limits the usefulness of the interface, I have an adapter but consider a switch to be a better option

With these K+DCAN cables there are two subtle different versions, one with pin 8 enabled, one with it disabled. The one with it disabled is ideal for e90 newer than 03/07 & that era, these leads often come with a black adapter to re-enable the pin 8 (by just tying it to pin 9) so it will also be suitable for e46/e39/e63 etc. The ones with pin 8 active are just older versions of the cable. Worst cast scenario you just need to modify the cable & stuck a switch on it to toggle pin 8 on/off as needed.

The reasons being that on DCAN cars one pin is used for a ethernet connection and the other to the K data line – on K line cars, both pins are connected to K data lines and that creating a switch mode circuit would cost more than the interface is worth. The 2 most sensible options are both hardware-related:-

– Use an adapter (such as the one sold by One Stop electronics) which internally bridges pins 7 & 8 or…

– Mount a small switch on the OBD plug end of your adapter, which can bridge (for K line) or separate (for DCAN) the connection between pins 7 & 8.

As soon as you connect the interface to the car and your computer, run DCAN.exe to configure the comms rate. I have only used the K+DCAN interface with DCAN cars.

Fyi, You only need to run DCAN.exe when you are switching between modes. If you run it the first time you connect to a DCAN car, your computer will retain the settings.

Switch K+D CAN adapter between K and D CAN protocols for use, depends on the car that is connected.

The last, K+DCAN cable you see the PCB
Very fine work, bridged soldering of 2 pins is intentional.

source: http://www.obdii365.com/wholesale/bmw-inpa-k-can-with-ft232rq-chip.html

– k+dcan inpa cable how to use

A lot of questions and answers here will help use/switch/connect to K-Line or Dcan pin 7&8?

Q: So you have to physically connect (K-Line) or disconnect (DCAN) pin 7&8?

A: Yes, I think connection by soldering is a bad option as it limits the usefulness of the interface, I have an adapter but consider a switch to be a better option.

Q: Is there anything else to do for switching from K-Line to DCAN then disconnecting pin 7&8? Unfortunately I don’t have a DCAN model available.

A: As soon as you connect the interface to the car and your computer, run DCAN.exe to configure the comms rate. I have only used my K+DCAN interface with DCAN cars.

Q: Is it necessary to do so every time I want to use DCAN or is the interface staying in DCAN mode once I ran DCAN.exe?

A: You only need to run it when you are switching between modes. If you run it the first time you connect to a DCAN car, your computer will retain the settings.

Q: How do I switch back to K-Line? Just by connecting the two pins or is further action on the computer required?

A: Earlier e39 had both the OBD port in the cabin and the round 20 pin connector under the hood.

The OBD port only allowed access to limited modules, I think only the DME in fact.

I always switch my K+D CAN adapter between K and D CAN protocols as I need to, depending on the car that I’m connecting to.

I use the DOS version of the DCAN utility. As mentioned if you only use the adapter on the e39, run the utility once and set the adapter to K CAN and leave it at that.

In fact thinking about it I use the same adapter for INPA, DIS and ISID.

With these K DCAN cables there are two subtle different versions, one with pin 8 enabled, one with it disabled. The one with it disabled is ideal for e90 newer than 03/07 & that era, these leads often come with a black adapter to re-enable the pin 8 (by just tying it to pin 9) so it will also be suitable for e46/e39/e63 etc. The ones with pin 8 active are just older versions of the cable. Worst cast scenario you just need to modify the cable & stuck a switch on it to toggle pin 8 on/off as needed.

Finally there are a lot of rubbish adapter cables out there. Finding a good one can be tricky.

Q: I have a 2003 E39 so there is no OBD1 anymore. How do you switch the modes physically? Do you use such a adapter to connect Pin 7&8?

A: If you don‘t plan to use the cable on any cars that have DCAN(2007+) then you can pop open the case and solder a jumper between them. When you do this the DCAN functionality will no longer work though.

source: http://blog.obdii365.com/2018/02/04/k-dcan-cable-with-switch-pin-7-8-good-or-not/

Part 3: INPA vehicle &protocol

– INPA vehicle coverage

For BMW 1-Series : E81, E82, E83, E87, E88 (2004-2011)

For BMW 3-Series: E90, E91, E92, E93 (2006-2011)

For BMW 5-Series: E60 (2004-2009)

For BMW Z4 : E85, E86 (2002-2008) E89 (2009-present)

For BMW X1: E84

For BMW X5: E70

For BMW X6: E71

– Protocols support

1)Fast magistral D-CAN and PT-CAN (500 kbit/s)

2)Slow magistral K-CAN (100 kbit/s)

3) Standard for BM-W protocol (for BMW OBD interface).

D-CAN for:

1)E60, E61 od 03/2007

2)E83 od 09/2006

3)E81, E87 od 03/2007

4)E90, E91, E92, E93 od 03/2007

5)E70 (new model X5)

6)R56 (new model MINI)

PT-CAN

K-CAN-fully

a switchable speed of magisterial CAN – you can diagnose driver without any car

Protocol “For B-MW OBD interface” for older cars:

1)from 1995 to 1998 (don’t need K-line).

2)from 1998 to 03/2008 (all models)

Part 4: INPA BMW software troubleshooting

1.Driver Error

Message comes along with an ADS or OBD connector.

This error occurs if another program or device has taken the COM1 port of your PC.

If you want to work with EDIABAS or INPA, please make sure that the COM1 port is not taken.

2.EDIABAS Error 126 (only up to Ediabas V6.4.x)

Reason: This error message appears if you start the Tool Set while an INPA script is running. This is also true the other way round. The reason for this is that only one programme can access EDIABAS at a time.

Solution: Therefore, before you start the ToolSet, you must exit INPA!!!

3.ToolSet Error: Runtime error ’372’

The following error message appears.

Reason: The old version msflxgrd.ocx exists under c:winntsystem32.

Solution: msflxgrd.ocx under c:Ediabasbin must be registered. To do this, select “Start” “Run…” and execute regsvr32: ediabasbinmsflxgrd.ocx in the window and confirm with “OK“. The following must be entered for Windows XP: “regsvr32 c:ediabasbin msflxgrd.ocx“

  1. INPA: vehicle could not be identified

Solution:

– uninstall supplemental Ediabas altogether (right click/uninstall on Ediabas MSI file if it’s the one that’s currently installed)
– in your main ISTA/D deployment directory, rename C:RheingoldEdiabasBIN to C:RheingoldEdiabasOLD_BIN
– reinstall Ediabas MSI package, changing its install path to C:RheingoldEdiabas during installation
– this will create a new C:RheingoldEdiabasBIN directory containing all Ediabas binaries + DLLs + INI files
– the rest of Ediabas package (docs, helper files, sim files, etc ….) will be installed in C:EDIABAS as usual
– modify EcuPath parameter inside C:RheingoldEdiabasBINEDIABAS.INI to C:RheingoldEcu

Then, you can redo your other settings :
– C:RheingoldEdiabasBINEDIABAS.INI
Interface = STD:OBD
You don’t care about anything TCP or Ethernet here as you’ll be using an USB K+DCAN cable if I’m correct (=> nothing to do with a network connection).

– C:RheingoldEdiabasBINOBD.INI
[OBD]
Port=Com9
Hardware=OBD

You also don’t have to care about ifhsrv32, which is a network proxy for Ediabas. It’s used when ISTA (or any BMW diag software needing Ediabas to connect to car), is run from another PC than the one where Ediabas itself is installed, and “discusses” remotely with it over a network.
Guess it’s not the classic case for DIYers

  1. INPA Error IFH-0009: NO RESPONSE FROM CONTROL UNIT

The hardware for INPA can be:

BMW ICOM A2/ICOM Next;

INPA KDCAN USB cable;

EDIABAS OBDII interface;

Reason:

1) Poor quality, or incorrectly wired interfaces. IFH-0009 errors are the most common in D-Can+K usb interface leads. Often these low-quality can be badly constructed, incorrectly wired, or contain the wrong chip set drivers or come with no drivers at all!. Whilst not all Chinese interfaces are poor quality, buying cheap imported leads is a gamble and when problems occur the seller probably won’t be interested. It is therefore important that you buy an interface lead from a good quality, reputable Vendor.

2) Wrong or Incorrect Interface Drivers. Again, mass produced interfaces can often contain cd’s with the wrong chipset drivers or come with no CD at all. Without the correct (latest) USB drivers, your interface lead will not install under windows properly. Our software package comes complete with a popular driver which is compatible with most Chinese and Western produced USB Interfaces, which will often work if the one supplied from your interface lead vendor doesn’t or hasn’t been included.

3) Incorrectly configured interface lead. Again, one of the most common problems with USB type leads. When installing a D-Can or Usb Interface lead, you will need to reconfigure the Windows based com port settings, so that the USB lead, appears to replicate an old RS-232 serial port. To replicate the port correctly, you need to change the existing Com port setting of the USB interface within Windows to Com Port 1 and change the latency setting to ‘1′ and check any ‘Fifo’ box

4) Incorrectly wired interface. Once again, there is no set standard as to the wiring pin configurations used within D-Can + K interfaces, by the various manufacturers. Some interface leads have pin 8 disconnected, some have pin 8 physically linked (bridged) to Pin 7, and some have pin 7 & 8 connected individually with no bridge link. If you still have problems connecting to the vehicle, and still get ‘IFH’ style errors then you should open the OBD Socket of the lead and check the pin wiring to see which type of interface you have. You should consider trying your interface lead, with the following configurations….

i) Pin 8 joined to Pin 7 using a small wire link

ii) Pin 8 physically disconnected

iii) Pin 7 and Pin 8 individually connected to their own pins with no link.

More often than not, one of these configurations will work with your vehicle, I recommend trying it with pins 7 & 8 linked together first, as this is by far the most popular vehicle configuration.

Also don’t assume that once you have found the pin 8 solution which works with one vehicle, that it will automatically work with a different model. If you have more than one D-Can equipped vehicle, you may need to obtain a second interface lead and configure ‘pin 8′ differently.

Bmw

If you don’t own a soldering iron, or if you don’t feel confident about soldering electrical connectors, then there are adaptors available which will bridge pins 7 & 8 together, without any need to open the OBD socket or solder.

5) Incomplete Versions of INPA. There are many versions of Inpa around, many of which are incomplete or simply lack the various configuration files in which to work correctly. If you try all of the above and the IFH-0009 problem still remains, then you will need to consider buying and installing the full version of Inpa which includes Ediabas and BMW Standard Tools

Solution:

Real case solved by one of solutions above:

Background:

  1. I have a 2004 325ci2. I purchased the k+dcan cable. It is an under-the-dash OBD to USB cable.3. It came with what was described as INPA 5.02 and EDIABAS 6.4.7. You have to install BMW Tools first, and then update. (Updating INPA, it shows a check mark next to INPA 5.01 “update,” and loading INPA, it says version 5.00 at the top bar.) I also installed NCSExpert.4. I am using windows XP SP3 32 bit. Firewall disabled, no anti-virus. No other software is installed. (I’ve had the same problem using Win 7 and Vista).

    5. C:Ediabasbin is in the path.

    6. Installed the USB cable and set the COM port to 1. Latency is set to 1ms. There is no option to use FIFO buffer.

    7. Ediabas.ini has STD:OBD as interface. It is also set so loadwinxp = 1

    8. OBD.INI is in C:ediabasbin and system32. COM port is set to 1 and hardware = USB (when hardware = OBD the battery circle is black even when not plugged into the car).

    9. When loading INPA, I get black battery and ignition when plugged in and starting car.

    10. I can successfully read the ECU. I can read and clear errors.

    11. When trying to read any other module, I get the IFH 0009 No Response From Control Unit.

How to solved:

I took about the connector and pins 7 and 8 are indeed soldered together!

I verified that both pins 7 and 8 had voltage and that the connection from the chassis wires to the obd plug under the dash were solid.

I then looked closely at pin #8 on the OBD/USB wire and noticed that it was bent slightly. It was not lining up in the pin #8 slot! I straightened it out and it worked!

  1. BMW INPA Edibas IFH-0018: INITIALIZATION ERROR

Solution: http://blog.obdii365.com/2016/06/26/inpa-edibas-ifh-0018-initialization-error/

Keep updating…

Related posts:

INPA, is BMW Factory-Level Diagnostic Software included in BMW Standard Tools. It is very powerful, but many/ Most ALL versions I have seen, are in German with LITTLE Translation to English, other than Menus.

TL;DNR Types: LOOK at the attached INPA Screens FIRST before you dismiss.

  1. F6, F1, F4 VANOS Activation, En
  1. F9, F5 Adjust Idle Speed, En
  1. F9, F5, F6 Set RPM Below 2K, En

Specific steps to save & attach INPA Screens are described in attached in the last paragraph (INPA Tutorial Quickstart (Functional Jobs examples). Generally, N51 & N52 Engines use either MSV70 or MSV80 (2007 & Later) DME Variants; N54 Engine uses mostly MSD80 DME Variant, and Later N55 Engine used MEVD17x Variant. To connect with ANY module, you need to know the VARIANT to make proper selection from the Right-hand Listbox.

  1. Change Idle Speed Setpoint: DME > F9 > F5 Idle Speed Adjustment:
    Some Functions or Activations, such as VANOS Activation described below, require a certain Idle Speed. Also, you may want to reset your idle speed (Setpoint or Target Speed) if you find your warm engine idle too High/too Low. With INPA, it’s so simple, even I can do it.A. Open DME > F9 System Diagnosis > F5 Increase Idle Speed:
    When you press/click that Menu Selection sequence you should see the First Screen attached Below, which simply shows the current ACTUAL RPM, and the Setpoint or Requested speed: 664 & 660 RPM respectively in my case. This screen as opened allows you to simply OBSERVE or view current setpoint & Actual Idle Speed (Live Data), BUT if you see the Submenu choices you can click on in the INPA “Taskbar”, you see you can add or subtract in increments of 10 or 100 RPM by simply clicking the buttons. OR, you can select F6 Auswahl (Selection) as described below.B. Enter Specific Desired RPM: DME > F9 > F5 > F6 Auswahl “Selection”:
    When you select the Auswahl/ Selection Button, a Dialog box is opened into which you can type ANY value between 0 and 2,000. See the 2nd attached INPA Screen for what that looks like. If you Enter 1020 and click OK (so you can Test VANOS as described below), that will remain the idle speed maintained UNTIL you return to this screen and enter a different speed, OR use the F1 thru F4 buttons to change speed. You can leave this menu (F10 Zuruck/ Go Back) to go to VANOS Screen, and newly-selected idle speed is maintained.

    III. Control VANOS Solenoids & View Actual Cam Advance: DME > F6 > F1 > F4 VANOS:
    When you press that Menu Selection sequence, you will see a screen like the THIRD attached screen. (WITHOUT the Red English Translation/Notes 😉 Some IMPORTANT things to note about ANY “F6 Activations” Screen. ALWAYS read and understand the “Control Conditions”/ “Ansteuerbedingung” which in this case say “Drehzahl > 1000 1/min = Rotational Speed (RPM) Greater Than 1,000 RPM. In this case, if you did NOT use the steps explained above to get RPM > 1000, INPA would simply tell you “test conditions NOT met” and nothing would happen, but DON’T press your luck and just randomly push buttons without translating/ understanding the “conditions”.

    When I first saw the Instruction: “Increase above Idle Speed WITHOUT pressing Accelerator Pedal”, I wondered: HOW can you do THAT? Some INPA engineer must have had a LOT of chuckles over that one. :tsk: I had to go through ALL the DME INPA Screens to see what each showed, and translate/ experiment with each to find the “key”. My version of INPA still has the Menus in German, and the Menu choice for this screen is “EOL LL-Erhöhung Bandende”. So after opening that screen and seeing Idle (Leerlauf) values, I had an epiphany. So THAT’s WHAT LL Stands for?!? I’m sure those sneaky

German guys had “Hidden” a LOT of other good Info. :thumbup: It’s AMAZING what you miss when you don’t speak German and don’t understand the German abbreviations. The TIS wiring diagrams are FULL of those abbreviations, beginning with wire colors, but that’s JUST the beginning.

You can use ANY “F6 Activation” Screen to simply Monitor system conditions in Real Time, or as Live Data, WITHOUT Over-riding DME Control of the Component. That is True for any electrically-controlled component, such as VANOS Solenoids, Coolant Pump, Fuel Pump, Thermostat, etc. OR, you can choose to Activate the Component using INPA or ISTA, and see if THAT Component, Solenoid, Motor, etc, responds as it should.

You can use this VANOS Solenoid Activation Screen to test Solenoid oil supply to the VANOS Units and corresponding Cam Position Sensor Readout to see if each Cam Advances as it should. In the 3+ years that I have followed Forums, it appears that MANY people unnecessarily replace VANOS Solenoids, often at a cost of ~ $200 each, ONLY to find that does NOT correct the issue which caused them to believe a Solenoid needed Replacing.

INPA Tutorial Quickstart (Functional Jobs examples):

  1. Procedure: Setup Hardware, Windows 10 OS:

AFTER Downloading & Installing Software: Set to Com Port 1, Latency 1

1) Attach K+DCAN Cable to computer USB Port (but NOT OBD II Socket)

2) Open Control Panel & Select Device Manager

3) In Device Manager, Select “Ports (COM & LPT)” which ONLY appears if Cable connected

4) DoubleClick USB Serial Port & select Port Settings Tab & click “Advanced” box

5) Set Com Port # = “COM1” & set Latency Timer (msec) = “1”

6) If your Cable has a slide switch on the Large Connector which attaches to the OBD II Socket, check to make sure it is in correct position. For example, BimmerGeeks Pro cable, proper position is to right as you hold pins UP with switch facing you. This is a pin bridge, and correct switch position varies between models.

NOTE: Check these settings if you can’t connect to a module, or have program STOP a function after a screen has opened, or if only part of a screen opens or displays.

  1. Functional Jobs:
  2. Primary Uses, F2, Identification, and F4, Fault Memory, ALL Modules:

F2, Identification: provides identification of EACH of the ~ 20 modules in your vehicle (some more, some less, depending upon optional equipment) including SGBD ID Code for module. Recommended that you SAVE that screen for future reference.

F4, Fault Memory, All Modules: provides a quick readout of status of Fault Memory of each Module, listing any Fault Code found in any module; stating No error registered (Kein Fehler eingetragen), if NONE for that Module. This is ONLY the code, NO Fault Code Definition.

  1. Procedure to Display F2 or F4 Screens:

1) At INPA opening screen, Select E90 (E91/E92/E93) Function key varies between Versions;

2) Script Selection Box appears, with Left & Right Listboxes;

3) “Select E90 V1.xx” highlighted in Left Listbox at open; Press Tab to move to Right Listbox;

4) Press Cursor Down Arrow to Highlight “Functional Jobs” in Right Listbox; Press Enter;

5) Functional Jobs Menu, Press < F2 > Identification or < F4 > Fault Memory (Fehlerspeicher);

  1. Saving Screens; Uses & Procedure:

You will almost certainly find that you want to save an INPA screen: (1) to have a historical record of faults, (2) to be able to post a screen on a Forum, (3) to translate it, or even (4) to keep some or all screens you open in a folder named for that Module, so you have a reference for what INPA can do or show you related to that Module. ONE WAY to do that (there are others):

1) Have a photo editor (such as “Paint” – Windows Accessory) open & running in background BEFORE you open INPA;

2) Open INPA screen to be Saved; press Shft+PrtSc to “print screen”/save it in temp memory;

3) Alt+Tab to navigate to Paint; Ctrl+V to paste screenprint to Paint;

4) SaveAs jpg file format in Folder/Subfolder of your choice, with helpful descriptive name.

5) In Paint, press Ctrl+N to clear screen to be ready for NEW “Paste & SaveAs.

Bmw Diagnostic Software Ista Free Download

Example of Filename & Folder Format: I do a “Functional Jobs” check for Fault Codes in ALL Modules ~ every 3 months. To maintain an historical record of Faults (or hopefully Lack Thereof 😉 I SAVE the screen each time in a Subfolder “Functional Jobs” where the other subfolders are named for each Module, such as DME, EGS, FRM, etc. When I last saved a screenprint of Fault Memory, ALL modules, on June 5, 2019, I gave it a FileName: 190606 FS1 or FS2 (two pages due to short screen). That yymmdd first name results in automatic sorting by date, and the FS1 stands for Fehlerspeicher1 or 1st page of Fault Memory. NOTE: I have Fluid Wear Faults in BOTH EGS & VGSG.

Whatever works for YOU, but keeping records of stuff is important, and how you keep them becomes MORE important the More Stuff you keep. One of the BIGGEST advantages of a computer-based software vs. Carly or such is the ability to EASILY & Quickly save a copy of a screen. INPA automatically saves some screens in temporary txt files in the “BIN” folder which you can retrieve BEFORE they get overwritten, but since electronic file storage is cheap these days, it really becomes what is quicker & easier, and the jpg file works for bar graphs & other graphics in F5 (Status) screens (See Below).

III. Connecting to Modules:

Bmw diagnostic software ista
  1. Why Connect to a Single Module?

Functional Jobs – a Starting Point ONLY: There are NO Fault Code DEFINITIONS, Freeze Frame Data or Fault Details, PLUS there is a LOT more to INPA than just Fault Codes (summarized below). There’s NOT much diagnostic information in a 4-character code that means NOTHING without a definition.

So you have to connect to a single Module: to find out what is going on NOW, or has gone on in the past, and to be able to see Parameters or PIDs (Inputs to that Module in Real Time), or to do “Activations” or tests of Outputs from the Module to a Motor or other component.

  1. What Information is Available when you Connect to a Single Module?
  2. F1: Information about Module; F2: Identification of the Module:

Press F1 & F2: at Main Menu for any Module and see/Save data about that module from Part#, Name of Supplier, Variant Information, etc. Suggest Saving F1 & F2 screens as reference for each module in your vehicle.

  1. F4: Fehlerspeicher; Fault Memory & Memory History:

Fault Codes: both in P-code format & in BMW FC format

Fault Code DEFINITIONS: often in German requiring translation

Fault Code Details: such as whether or not the fault is currently present or would light a warning lamp; the mileage/km at which the fault code was saved; other conditions such as Voltage or Temperature when fault was saved; the type of signal fault (high/low/none), etc.

Freeze Frame Data: in DME faults you will see a snapshot of Parameters at the moment the fault code was saved, such as Engine Temp, RPM, Load, System Voltage, etc.

History speicher or Memory History in DME: where Fault Codes that happened years ago and were cleared are still recorded, along with mileage/km when saved, and other details

Bmw Diagnostic Software Free

Faults that do NOT light a warning lamp: such as Oil Wear Faults in Transmission or Transfer Case. Actually, these appear in Functional Jobs but without Definition or Details

  1. F5: Status; Parameters; Live Data; Inputs to Modules from Sensors/Switches:
  2. F6: Activations (Steuern); Test/Activate Module Outputs & Attached Motors:

Examples of F5 & F6 functions for Each Module will be provided, beginning with DME & IHKA Modules. WATCH THIS SPACE

  1. Functional Jobs Screens, Example Screens for my 2007 328xi:

Screens will vary depending upon Equipment/Modules/Variants/Options on YOUR vehicle

  1. Functional Jobs Main Menu: How to Select:

Screen below appears when E90 selected; press Tab & Down (scroll) Arrow; Press Enter

  1. Functional Jobs, Main Menu (Hauptmenu):
  1. Functional Jobs | F2, Identification, Identifying ALL Modules in Vehicle:

Suggest save & use as reference; NOTE “SGBD” Module Variant, 4th Column

  1. Functional Jobs | F4 | F1, Fault Memory, ALL Modules (page 1 of 2):

Kein Fehler eingetragen = No error entered = what you WANT to see

That’s all!

INPA K+DCAN cable source:

Bmw Diagnostic software, free download

Related posts: