Ediabas Inpa Software Installieren Spiel

System Software; Rating and Stats. 0.0 (0) Document Actions. Share or Embed Document. Sharing Options. Bevor Sie EDIABAS / INPA installieren. Find great deals on eBay for BMW GT1 in Other Diagnostic Service Tools. With Ediabas - INPA. Fit IBM T30 is the latest software for BMW GT1 and OPS.It can.

Quote: I am very grateful to your time and organization for this thread. I was able to install and run on my 05 X5 DIS and inpa. I am running INPA 447 and EASYDIS v44. I was able to install the programs on my 2009 MacBook pro running Lion. I installed it two different ways.

One is through VMware Fusion running XP and the other with Bootcamp running native XP. I did an easier install which worked for me. • Instead of using VMware Workstation, I installed the VMware Player- which is free. • I also installed the pre-built GT1 VMware image (3.6gb). It is very easy to install and you don't have the issues with base and program iso, etc.

The only thing I had to do in VMware player inside DIS was to remove and replace the LAN adapter. I think everything else was already set in the image. There is one trick to VMware player. You have to go to Windows XP and run 'c: vmwareplayerxx.exe -/e c: temp. This extracts a bunch of files to the temp folder.

You double click on the network.cab file and it will ask you to extract vmnetcf.exe to the c: programfiles vmware player directory. You have to run vmnetcfg.exe and change vmnet1 and vmnet8 to the ip values listed in the guides. For anyone having trouble with VMware workstation or if they are running on a Mac, this information might be helpful to the thread. 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. 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 (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. Star Sports 3 Channel Free Download For Pc. 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. 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 for definitive answers. 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, 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. Part 2: How to Check for Engine Fault Codes Part 3: How to check Engine Live Analog Data. 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? From Ireland. 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. 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. 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! 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! 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. 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.).

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'. Full Futura Font Family Nov 2013 on this page.

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. 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. From the 'File' menu, choose 'Load Profil'. 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.

Click the 'VIN/ZCS/FA' button (F1). The button labels change once again. Click the 'ZCS/FA f. ECU' button (F3). In the 'Choose CHASSIS' popup window, select 'E31' and click 'OK'.

In the 'Choose ECU' popup window, select 'EKM' and click 'OK'. After a short moment, the top groupbox should now show information regarding your car. 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! Click the 'Process ECU' button (F4). 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 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. 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. Confirm 'JOBNAME' in the middle groupbox says 'CODIERDATEN_LESEN'. 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.

Launch NCS Expert. At this moment no profile is loaded, so the screen is quite empty. From the 'File' menu, choose 'Load Profil'. 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. Click the 'VIN/ZCS/FA' button (F1).

The button labels change once again. Click the 'ZCS/FA f. ECU' button (F3). In the 'Choose CHASSIS' popup window, select 'E31' and click 'OK'.

In the 'Choose ECU' popup window, select 'EKM' and click 'OK'. After a short moment, the top groupbox should now show information regarding your car.

Click the 'Back' button (F6). The middle groupbox now shows the available modules and default job name. Click the 'Process ECU' button (F4).

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 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. In the 'Choose job' popup window, select 'SG_CODIEREN' and click 'OK'. The default job action is now coding. Confirm 'JOBNAME' in the middle groupbox says 'SG_CODIEREN'. 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. 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. 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.

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.

Hi Guys If you are after ready to go Cables to suite your car contact Jimmy 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.

Several versions of BMW INPA diagnostic software are available on the aftermarket. Here obdii365.com share INPA 6.4.3, 5.0.6 and 5.02 free download links with you all. Free download BMW INPA (tested) + NOTE: Most INPA software above are shared by forum members.