Electrical The [Complete] NCS Expert DIY
#126
- Does your MINI have comfort access?
#127
#128
#129
What great DIY info!
__________________
Your Trusted Source For DIY and Parts
FREE SHIPPING over $99 click here
MINI Parts | DIY Help | Facebook | Twitter | Instagram | YouTube | Promos
888.280.7799 | 6am - 5pm PST
FREE SHIPPING over $99 click here
MINI Parts | DIY Help | Facebook | Twitter | Instagram | YouTube | Promos
888.280.7799 | 6am - 5pm PST
#130
EDIABAS Server 7.2 Quitting when INPA closes
Hey NAM!
First-time poster! After a couple years of learning through various forums, I finally was brave enough to try NCSExpert and was able to code the one-touch sunroof and the remote closing windows using NCSExpert with Ediabas 6.4.7 in WinXP via Virtual Machine with no problems until I received a Fault BEST error so I stopped . Did a search on the Interwebz and found the solution to be to update to Ediabas 7.2 and to update my datens, as well . I installed Standard Tools 2.10 with Ediabas 7.2 and using the v41 datens. In the older version, when I ran INPA to see if the vehicle is responsive, I would have an Ediabas server running even after I close out INPA . With the new install, when I run INPA, it will run Ediabas server but will also quit when I close INPA . So, I'm trying to find out if its crucial that I have the Ediabas server running while working with NCSExpert to code. If so, how can I prevent Ediabas from quitting with INPA? - should I keep INPA open?, I also have Standard Tools 2.12 and v.53.05 & v.55 datens, should I just go ahead and install that and use the most recent datens (v.55)?
Any input would be appreciated. Thank you!
First-time poster! After a couple years of learning through various forums, I finally was brave enough to try NCSExpert and was able to code the one-touch sunroof and the remote closing windows using NCSExpert with Ediabas 6.4.7 in WinXP via Virtual Machine with no problems until I received a Fault BEST error so I stopped . Did a search on the Interwebz and found the solution to be to update to Ediabas 7.2 and to update my datens, as well . I installed Standard Tools 2.10 with Ediabas 7.2 and using the v41 datens. In the older version, when I ran INPA to see if the vehicle is responsive, I would have an Ediabas server running even after I close out INPA . With the new install, when I run INPA, it will run Ediabas server but will also quit when I close INPA . So, I'm trying to find out if its crucial that I have the Ediabas server running while working with NCSExpert to code. If so, how can I prevent Ediabas from quitting with INPA? - should I keep INPA open?, I also have Standard Tools 2.12 and v.53.05 & v.55 datens, should I just go ahead and install that and use the most recent datens (v.55)?
Any input would be appreciated. Thank you!
#134
Anyone else having issues with INPA having no menus? For example, the only menus I have are: Info, Script, and Exit...with F3-F9 being blank.
I'd really like to be able to use it for diagnostic purposes and clearing CEL if/when they pop up.
I followed the instructions to a T and even reinstalled everything with no luck.
I'd really like to be able to use it for diagnostic purposes and clearing CEL if/when they pop up.
I followed the instructions to a T and even reinstalled everything with no luck.
#135
Update:
After hours of digging through NAM and several Bimmer forums I've come to the conclusion that with the version of INPA offered here I was getting half-installed configs and files. Browsing to the EC-APPS\INPA\CFGDAT folder, I could find almost no files at all. A correct installation should have files ending in .ENG and .GER for the respective English and German language versions of that chassis. I had NONE of these files until I completely removed everything and reinstalled INPA from another source. The other odd thing is the INPA config file had 0 entries in it. Adding the entries found in a Bimmer forum gave me the context menus within INPA but then threw errors when trying to find the related file.
For anyone else running into this issue I highly recommend downloading and installing from this link. The main link provided in the first post no longer works but someone in the thread has posted a new one for the file BMW_INPA_5.0.2 (download is super slow so be patient): http://bmwcoders.com/forum/bmw-gt1-o...-software-328/
The last step of the process is changing the INPA config file slightly. If you install as the directions guide you, you'll wind up with a perfectly good and functioning install but you won't have a menu option for R56. For that, you need to simply open the INPA config file in EC-APPS\INPA\CFGDAT and just replace one of the other chassis codes with R56.
I'm also thinking that those of us with incomplete installations could simply change the INPA config file's contents and place the .ENG chassis data files into the same folder and have it up and running with fully working menus (I have NOT tested this but may in the future).
If anyone has any questions or has experienced this I can attempt to answer questions as best as possible or provide the needed files/configs.
After hours of digging through NAM and several Bimmer forums I've come to the conclusion that with the version of INPA offered here I was getting half-installed configs and files. Browsing to the EC-APPS\INPA\CFGDAT folder, I could find almost no files at all. A correct installation should have files ending in .ENG and .GER for the respective English and German language versions of that chassis. I had NONE of these files until I completely removed everything and reinstalled INPA from another source. The other odd thing is the INPA config file had 0 entries in it. Adding the entries found in a Bimmer forum gave me the context menus within INPA but then threw errors when trying to find the related file.
For anyone else running into this issue I highly recommend downloading and installing from this link. The main link provided in the first post no longer works but someone in the thread has posted a new one for the file BMW_INPA_5.0.2 (download is super slow so be patient): http://bmwcoders.com/forum/bmw-gt1-o...-software-328/
The last step of the process is changing the INPA config file slightly. If you install as the directions guide you, you'll wind up with a perfectly good and functioning install but you won't have a menu option for R56. For that, you need to simply open the INPA config file in EC-APPS\INPA\CFGDAT and just replace one of the other chassis codes with R56.
I'm also thinking that those of us with incomplete installations could simply change the INPA config file's contents and place the .ENG chassis data files into the same folder and have it up and running with fully working menus (I have NOT tested this but may in the future).
If anyone has any questions or has experienced this I can attempt to answer questions as best as possible or provide the needed files/configs.
The following users liked this post:
ItalianJobR53 (11-28-2018)
#136
Great tut very very helpful and easy to read. Im getting the following problems and dont know if anyone can help me out:
1) When I load INPA, EDIABAS loads in the background but when i exit INPA, EDIABAS also closes.
2) Revtor's profile isnt in the list of the available profiles to choose from in EDIABAS
3) I primarily need the E89 daten for my e93 MY2007. When I select this chasis in EDIABAS i get the error "CHASSIS is faulty"
Does anyone know ways around to solve these?
1) When I load INPA, EDIABAS loads in the background but when i exit INPA, EDIABAS also closes.
2) Revtor's profile isnt in the list of the available profiles to choose from in EDIABAS
3) I primarily need the E89 daten for my e93 MY2007. When I select this chasis in EDIABAS i get the error "CHASSIS is faulty"
Does anyone know ways around to solve these?
#137
Coding error
Hello I am brand new to this. I got software and cable from Cable Shack in UK. Everything installs and looks like I can read the car, not sure how all the diagnostic software works yet. I am trying to add the retrofit bluetooth and rear fog light to my 2010 R55 and I get a COAPI -1000 error after at the $6ND code to the CAS for VO update and hitting the F6 or back key in NCSEXPERT. Any idea what I might be doing wrong?
Thanks
Thanks
#138
James
#139
I'm not entirely sure how the R53 chassis is under this program unfortunately. I know that for my issue the R56 chassis code was missing completely until I went through a whole load of shenanigans and even then I ran into issues down the road trying to access certain menus.
As for the R53 and as far as I know, once the programs are installed it should work properly. Again, I have 0 experience with that chassis but even with a plain jane install I did have the R53 chassis available in the program. Being that I don't have an R53 I didn't really have a reason or opportunity to dig through that portion.
Somebody else might be able to chime in here for this.
P.S. This is in the 2nd gen thread...might be worth digging through the 1st gen section to see if anyone there has a guide and/or some advice.
As for the R53 and as far as I know, once the programs are installed it should work properly. Again, I have 0 experience with that chassis but even with a plain jane install I did have the R53 chassis available in the program. Being that I don't have an R53 I didn't really have a reason or opportunity to dig through that portion.
Somebody else might be able to chime in here for this.
P.S. This is in the 2nd gen thread...might be worth digging through the 1st gen section to see if anyone there has a guide and/or some advice.
#140
#141
2008 Clubman HPFP test which item?
I have a working INPA/NCS Expert/EDIABAS set up on a dedicated XP laptop (HP 630 I bought for $100). I do not know which ECU or CAS to test the pressure differential on the HPFP. I did search the forum but did not find a piece I thought I'd read here a while back.
Thanks to anyone who may be able to shed some light on this.
Thanks to anyone who may be able to shed some light on this.
#142
#143
Dead and cold MINI after Airbag recall
Because the airbag seat sensor failed and the airbag light came on and Mini wouldn't fix it, using NCS Expert, I reprogrammed the computer to not look for the sensor.
When Mini finally admitted to the problem and had a recall, I took it in for the work. The mechanic swapped the bad part out but the airbag light stayed on. He said I would have to bring it back and they would give me a loaner car and a guy in New Jersey would need to reprogram it remotely.
I took the car home and decided maybe I could reprogram it back myself but I accidentally erased the program and now it won't listen to my computer. It also won't run. It just shudders constantly regardless of key position until I moved the battery terminal.
I think I need to let the guy in New Jersey do his thing after all. Unfortunately, I'll need a tow truck to get it back to the dealer.
Because the airbag seat sensor failed and the airbag light came on and Mini wouldn't fix it, using NCS Expert, I reprogrammed the computer to not look for the sensor.
When Mini finally admitted to the problem and had a recall, I took it in for the work. The mechanic swapped the bad part out but the airbag light stayed on. He said I would have to bring it back and they would give me a loaner car and a guy in New Jersey would need to reprogram it remotely.
I took the car home and decided maybe I could reprogram it back myself but I accidentally erased the program and now it won't listen to my computer. It also won't run. It just shudders constantly regardless of key position until I moved the battery terminal.
I think I need to let the guy in New Jersey do his thing after all. Unfortunately, I'll need a tow truck to get it back to the dealer.
#144
Hello everyone,
I need some assistance if possible. I have a 2008 Cooper Non-s. I have successfully coded everything I wanted to. Recently trying to cure a transmission issue, I gave my car into a shop to reflash the TCM. They updated all the modules which I did not have a problem with. After getting the car back, I discovered some of my coding returned to its original status. I was able to recode CAS, but when I went to reprogram the FRM I got a code COAPI-1043 error. I can read the module but when I go to reprogram I get that code. If I read the module after, my changes are present, but they are not functioning as programmed. I presume my Daten files are too old for the newly flashed modules. I have Daten 51.2. I need newer but don't know how new I need. I also am having difficulty finding a source to download new Daten files.
Any assistance is appreciated!
All figured out. I figure I would share. I updated my Daten files to 55.3 and still had the problems. I notices some discussion about the file size after reading a module. I looked and saw my file size was the same size as in the discussion. I decided to erase everything in that file. When I reread the file, I looked in my trace file and it was still empty. I noticed under VIEW in NCS Expert, I could view the Trace file. I saw it edited it and saved it from that location to the MAN file. BOOM everything worked. I don't know why the destinations changed but all is good now.
Ivan
I need some assistance if possible. I have a 2008 Cooper Non-s. I have successfully coded everything I wanted to. Recently trying to cure a transmission issue, I gave my car into a shop to reflash the TCM. They updated all the modules which I did not have a problem with. After getting the car back, I discovered some of my coding returned to its original status. I was able to recode CAS, but when I went to reprogram the FRM I got a code COAPI-1043 error. I can read the module but when I go to reprogram I get that code. If I read the module after, my changes are present, but they are not functioning as programmed. I presume my Daten files are too old for the newly flashed modules. I have Daten 51.2. I need newer but don't know how new I need. I also am having difficulty finding a source to download new Daten files.
Any assistance is appreciated!
All figured out. I figure I would share. I updated my Daten files to 55.3 and still had the problems. I notices some discussion about the file size after reading a module. I looked and saw my file size was the same size as in the discussion. I decided to erase everything in that file. When I reread the file, I looked in my trace file and it was still empty. I noticed under VIEW in NCS Expert, I could view the Trace file. I saw it edited it and saved it from that location to the MAN file. BOOM everything worked. I don't know why the destinations changed but all is good now.
Ivan
Last edited by Ive's Mini; 11-21-2016 at 06:37 PM. Reason: Updated information
#145
Not so dead Mini
So after I killed my daughters car, this morning I noticed I had the original files. And after spending the night with the battery on a charger everything seemed much better this morning. If I tried something like starting the car, it would crap out but if I just carefully went into NCSExpert I was able to load the old files back into the brainbox.
Even then it would crap out and go crazy so I unplugged the battery and put it on a charger.
After dinner, I connected the battery and voila, car is happy.
I drove it around and it is happy and there are no airbag lights.
Hurray,
Peter
Even then it would crap out and go crazy so I unplugged the battery and put it on a charger.
After dinner, I connected the battery and voila, car is happy.
I drove it around and it is happy and there are no airbag lights.
Hurray,
Peter
#146
NCSExpert not running in Windows 10 64
I installed per the instructions posted here and INPA runs and shows battery and ignition status. The EDIABAS server stays active but NCSExpert will not run - I get an error "This app cannot run on your PC". I have tried a variety of windows security changes and compatibility mode changes with no effect. Any thoughts? I have tried several searches on various forums and it seems like others have seen this as well but I cannot find a solution. NCSExpert is v3.1.0 and INPA is v5.0.1.
One odd thing I did notice is that when I launch INPA, there are no vehicle platforms listed like I see on some of the posted screenshots - maybe it did not install completely?
Thanks for your help.
One odd thing I did notice is that when I launch INPA, there are no vehicle platforms listed like I see on some of the posted screenshots - maybe it did not install completely?
Thanks for your help.
#147
Update:
After hours of digging through NAM and several Bimmer forums I've come to the conclusion that with the version of INPA offered here I was getting half-installed configs and files. Browsing to the EC-APPS\INPA\CFGDAT folder, I could find almost no files at all. A correct installation should have files ending in .ENG and .GER for the respective English and German language versions of that chassis. I had NONE of these files until I completely removed everything and reinstalled INPA from another source. The other odd thing is the INPA config file had 0 entries in it. Adding the entries found in a Bimmer forum gave me the context menus within INPA but then threw errors when trying to find the related file.
For anyone else running into this issue I highly recommend downloading and installing from this link. The main link provided in the first post no longer works but someone in the thread has posted a new one for the file BMW_INPA_5.0.2 (download is super slow so be patient): http://bmwcoders.com/forum/bmw-gt1-o...-software-328/
The last step of the process is changing the INPA config file slightly. If you install as the directions guide you, you'll wind up with a perfectly good and functioning install but you won't have a menu option for R56. For that, you need to simply open the INPA config file in EC-APPS\INPA\CFGDAT and just replace one of the other chassis codes with R56.
I'm also thinking that those of us with incomplete installations could simply change the INPA config file's contents and place the .ENG chassis data files into the same folder and have it up and running with fully working menus (I have NOT tested this but may in the future).
If anyone has any questions or has experienced this I can attempt to answer questions as best as possible or provide the needed files/configs.
After hours of digging through NAM and several Bimmer forums I've come to the conclusion that with the version of INPA offered here I was getting half-installed configs and files. Browsing to the EC-APPS\INPA\CFGDAT folder, I could find almost no files at all. A correct installation should have files ending in .ENG and .GER for the respective English and German language versions of that chassis. I had NONE of these files until I completely removed everything and reinstalled INPA from another source. The other odd thing is the INPA config file had 0 entries in it. Adding the entries found in a Bimmer forum gave me the context menus within INPA but then threw errors when trying to find the related file.
For anyone else running into this issue I highly recommend downloading and installing from this link. The main link provided in the first post no longer works but someone in the thread has posted a new one for the file BMW_INPA_5.0.2 (download is super slow so be patient): http://bmwcoders.com/forum/bmw-gt1-o...-software-328/
The last step of the process is changing the INPA config file slightly. If you install as the directions guide you, you'll wind up with a perfectly good and functioning install but you won't have a menu option for R56. For that, you need to simply open the INPA config file in EC-APPS\INPA\CFGDAT and just replace one of the other chassis codes with R56.
I'm also thinking that those of us with incomplete installations could simply change the INPA config file's contents and place the .ENG chassis data files into the same folder and have it up and running with fully working menus (I have NOT tested this but may in the future).
If anyone has any questions or has experienced this I can attempt to answer questions as best as possible or provide the needed files/configs.
EDIT: NVM, I was using a shortcut that linked to INPALOAD.exe Apparently, I need to open INPA.exe for it to work.
Thread
Thread Starter
Forum
Replies
Last Post
Interior/Exterior Must see: Liberty Walk body kit for Mini Cooper R56
carid
Interior/Exterior
13
09-02-2021 07:22 AM
Sc00terbum
R50/R53 :: Hatch Talk (2002-2006)
6
09-11-2015 07:17 AM
bbak11010
MINI Parts for Sale
0
09-07-2015 08:08 PM
bbak11010
MINI Parts for Sale
0
09-07-2015 08:03 PM