When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
ElectricalFor discussions regarding wiring up electrical modifications such as radar detectors, brake light mods, power sockets, and driving lights in Clubman (R55), Cooper and Cooper S (R56), and Cabrio (R57) MINIs.
I have been trying for two days to get INPA working on my Windows 10 64 bit laptop from the files in the first post. I have been all over this site and the internet looking for a solution. I can install everything but when I open INPA I don't have any chassis selections.
I'm thinking it may have something to do with these steps: ● All files in “daten” → C:\NCSEXPER\DATEN\XXX (where XXX is your
chassis code)
● All files in “sgdat” → C:\NCSEXPER\SGDAT
● All files in “ecu” → C:\EDIABAS\ECU
Do not copy the folders themselves, only the files inside them. Choose “Copy
and Replace” to resolve conflicts.
Or the INPA.ini file??
Any thoughts or suggestions would be greatly appreciated
Last edited by cosmo727; Oct 24, 2018 at 07:32 PM.
Cosmo727, have you searched bimmerforums.com? There is a LOT more information there on INPA than here. Although there is a lot here, there is even more there. They might have a little more info on win 10. I set mine up on an XP machine all by itself. Worked through a lot of issues right at first but it's been far too long ago for me to be very useful to you. Sorry, I can't tell you more!
I have been to bimmerforums and have tried a few things from there with no luck. I even installed Mike's Easy BMW Tools. It was an extremely easy installation. The problem with that one was that there were no MINI chassis installed, just BMWs. I then tried to copy the Datens from the first post in this thread into Mike's Easy BMW Tools. I'm not sure if I was doing it right because every time I made a change the program seemed to re-install itself back to original.
Still looking for suggestions to get INPA working on my Windows 10 64 bit laptop.
I remember when I installed, you must run it in 'compatibility mode' for Windows.
Right click on the programme or exe file
Click on properties
Compatibility Tab
Check, run this programme in compatibility mode.
I finally got it going!! Thanks to all for the replies!! I found another installation file on bimmerforums which was relatively painless to install.
Special thanks to thewizz for mentioning bimmerforums so that I could revisit there to get this thing going.
My next task will be to get DIS/GT1 working....wish me luck!!!
Hi. .I've been lurking for a while.. And I used the guilde on this post to code my R56 non s with the sunroof etc.. But I'm having trouble accessing the FRM module.. I want to disable the bulb check and retrofit the sport button..
This is the msg I got
Error in CABD! Look at CABI.ERR and ERROR.LOG
BIP-0009: Faulty BEST version of description file
I read numerous post and it mention I need a differnt detens
. I've try V 38, 40 49, 53 ,60 with no success. . I read I need a a older datens of V32 and V40 mix...
I was wondering if anyone would have a copy of it.
I finally got it going!! Thanks to all for the replies!! I found another installation file on bimmerforums which was relatively painless to install.
Special thanks to thewizz for mentioning bimmerforums so that I could revisit there to get this thing going.
My next task will be to get DIS/GT1 working....wish me luck!!!
Any way you could send me that forum link? I've been searching and can't find one that will work. Also did you get NCSExpert to work on windows 10? I'm running a x64 OS so I know it might not, but I have a separate computer with xp on it where I could install it again.
I installed NCSExpert on my laptop (Windows 10, 64bit), and yes, I know they say NCS wont work on 64bit but I thought i'd give it a go anyways.
The install process went fine and exactly as described in the manual, but NCS would not load saying it is not the right software for my operating system.
OK, thats probably why they say it wont work on 64bit.
So I tried running INPA.
It seems to connect with my car as I can see the 2 black circles of battery and ignition and they respond when I turn the car on or off.
But, I cant connect to any of the modules. keeps giving me an error saying "ÏFH-0009 No response from control unit".
Is this also affected by the operating system? or is it something else?
Vehicle is Cooper S 2012 LCI
Cable is the recommended one from ecutool.com
Im trying to program the car work with the xenon retrofit kit.
Any help would be appreciated.
Maybe someone knows of another software that could help me program what I want and would work on Windows 10 64 bit.
Or maybe a better cable?
hey guys
i am new in coding, last night i face some error that when i choose ecu e60 cas and then capp it selected and then when i read ecu its says error COAPI_2041 wrong coding index ?
i dont understand what is this and how to fix this please if anyonwe who help me .
Does anyone have a cheat sheet for the R52? I want to add rear fog lights and a few other mods. I am not sure what modules need coding for that. I have successfully coded my R56 with a cheat sheet that I found online, but I cant find anything for Gen1. Thanks!
So travelling down this coding avenue, using Windows 10 64bit, I ran into problems that took some time to resolve. I'm documenting it here as over the last few weeks I've never seen this recommended before. Background:
The K+DCAN cable refused to be acknowledged by Windows. It kept coming in as an "other" device in Device Manager, and no "update driver" method worked on the item itself. Windows continually told me "The device is not working" and then when trying to update the driver "Windows is using the newest driver".
The cable I bought was a switch enabled unit from Amazon with a good rating, a clear one with INPA sticker, and CD. But the CD is useless in this house as there's no drives here, and there's no driver on the CD anyway.
I gave up and ordered a cable from BimmerGeeks directly. Having texted with them via FB messenger, they confirmed the driver was in their package and it works on W10 64bit. Waited a few weeks for it to arrive, and when I plugged it in... Same damn result. They tried to give me some direction via messenger - but I had already done those items.
Turns out, I got lucky.
Solution:
I went to Windows update *with the cable plugged in* and it found an optional driver update for the FTDI Port (which is what these cables use). I had previously attempted to use similar drivers before, but THIS time it worked.
The cable plugs in, picks up as a COM port. Changed it to COM1 and latency of 1. INPA picks it up as a connected cable.
This afternoon will be the real test when I plug it into an R53.
So travelling down this coding avenue, using Windows 10 64bit, I ran into problems that took some time to resolve. I'm documenting it here as over the last few weeks I've never seen this recommended before. Background:
The K+DCAN cable refused to be acknowledged by Windows. It kept coming in as an "other" device in Device Manager, and no "update driver" method worked on the item itself. Windows continually told me "The device is not working" and then when trying to update the driver "Windows is using the newest driver".
The cable I bought was a switch enabled unit from Amazon with a good rating, a clear one with INPA sticker, and CD. But the CD is useless in this house as there's no drives here, and there's no driver on the CD anyway.
I gave up and ordered a cable from BimmerGeeks directly. Having texted with them via FB messenger, they confirmed the driver was in their package and it works on W10 64bit. Waited a few weeks for it to arrive, and when I plugged it in... Same damn result. They tried to give me some direction via messenger - but I had already done those items.
Turns out, I got lucky.
Solution:
I went to Windows update *with the cable plugged in* and it found an optional driver update for the FTDI Port (which is what these cables use). I had previously attempted to use similar drivers before, but THIS time it worked.
The cable plugs in, picks up as a COM port. Changed it to COM1 and latency of 1. INPA picks it up as a connected cable.
This afternoon will be the real test when I plug it into an R53.
The Bimmergeeks cable is pretty great, and their coding app is amazing. Too bad that the 1st gen is a little limited in that regard. Did you order the Double K-Line Adapter? You're going to need that with an R53.
The Bimmergeeks cable is pretty great, and their coding app is amazing. Too bad that the 1st gen is a little limited in that regard. Did you order the Double K-Line Adapter? You're going to need that with an R53.
Yeup, got it. Thanks for pointing that out.
I’m planning on working on a lot of cars for my parts business, so I got the pro cable, warranty and the adapter.
I’ll be using it for second gen’s and I have my Ethernet cable for third gens.
Hoping to avoid buying an ICOM NEXT, but it may be inevitable.
Yeup, got it. Thanks for pointing that out.
I’m planning on working on a lot of cars for my parts business, so I got the pro cable, warranty and the adapter.
I’ll be using it for second gen’s and I have my Ethernet cable for third gens.
Hoping to avoid buying an ICOM NEXT, but it may be inevitable.
Sounds like you're set. I feel your pain on the ICOM, I've been putting that off.
Not sure how many people are still using NCS, especially the R56+ cars that have easy to use smartphone app options now, but I dove into this process last week as I needed to update an R53. Helpful info here but it is a steep learning curve and I found the old versions in this thread just didn't get the job done. I could not connect to my car (VIN is faulty), ultimately went for a newer version a from Bimmergeeks (https://www.bimmergeeks.net/) on a Windows 7 x86 (important) VM, and everything worked first try. I'm using a cheap Amazon cable with a switch (
So i have swapped out the BC1 on Mini r50 2001, I coded the Key so now the C entral locking is working again from the key, and i have used NCS to turn on Basic Air Con however when i try and write back i am getting this error...========================================== ======================================(3)
R58 CAS Error while trying to program with NCS Expert
I messed something up and don't know what I did. I am using ICOM on NCS Expert. I am able to program every other module except CAS. Everything seems to be working fine, just pops up the errors. I would appreciate help if you can!
