Electrical NCSExpert for beginners
PC: Win 7 - 64 bit, windows virtual pc: xp mode
Mini OneD Dec 2011.
Needed to load the V45 datens.
A few observations:
1. INPA showed power, but it offered no chassis to select. Is this standard? Or have I got some files missing? I haven't tried the Ediabas update metioned later in the thread.
2. I looked at various methods to update the VO (as above) and tried the CAS write followed by LM. But I could not see the 2nd module (LM?) and the change didn't appear to take effect.
3. So with some reservation I hit code Car. A long time past with displays flashing and changing... eventually NCSExpert reported an error and aborted.

But so far it looks like it worked I now have MPG and miles to empty displayed
And the car still starts 
So thanks... but I haven't quite got it right yet!
Cheers,
Tim.
Yeah, I'll need to figure out what I did to INPA...Somewhere a few months back I found an updated package that got pretty much every module (except engine) to work with INPA! It really is so quick compared to DIS for most functions. I bet I got it on bmwcoding.com.
http://www.4shared.com/folder/hX4ohKra/INPA_2010.html
this is the link for the updated inpa.
http://forums.bimmerforums.com/forum....php?t=1673155
this is the link for the updated inpa.
http://forums.bimmerforums.com/forum....php?t=1673155
Ok guys, got my cable:
http://www.autoscannertool.com/china...an-112144.html
I installed everything perfectly as instructed in the "Mini Cooper Coding" folder downloaded from the first page of this thread.
I'm using a fully updated Mac with fully updated WinXP running via Parallels 7.0.15. Everything is totally fine with the program until it is time for NCS Expert to read the VIN. INPA sees the battery and ignition as on but NCS Expert fails to read the VIN with the error box:

VIN is faulty
COAIP-2020: no answer from ECU
IFH-0009: ECU not connected or doesn't answer
I've installed with dates V38 as well as V40 both with the same results.
Versions:
INPA: 5.0
NCS Expert: 3.1.0
EDIBAS: 6.4.7
Does anybody know what's going on? I'm trying to modify the 2011 R56 S in my signature.
http://www.autoscannertool.com/china...an-112144.html
I installed everything perfectly as instructed in the "Mini Cooper Coding" folder downloaded from the first page of this thread.
I'm using a fully updated Mac with fully updated WinXP running via Parallels 7.0.15. Everything is totally fine with the program until it is time for NCS Expert to read the VIN. INPA sees the battery and ignition as on but NCS Expert fails to read the VIN with the error box:

VIN is faulty
COAIP-2020: no answer from ECU
IFH-0009: ECU not connected or doesn't answer
I've installed with dates V38 as well as V40 both with the same results.
Versions:
INPA: 5.0
NCS Expert: 3.1.0
EDIBAS: 6.4.7
Does anybody know what's going on? I'm trying to modify the 2011 R56 S in my signature.
Well as you've a 2011, then you could try updating your datens to v45 - worked for me.
http://www.bmwcoding.com/showthread....6X-E7X-E9X-E46
R56 http://www.mediafire.com/download.php?jw5iktfjjd6ac3z
If that fails you'll have to wait for the experts ;-)
http://www.bmwcoding.com/showthread....6X-E7X-E9X-E46
R56 http://www.mediafire.com/download.php?jw5iktfjjd6ac3z
If that fails you'll have to wait for the experts ;-)
Ok guys, got my cable:
http://www.autoscannertool.com/china...an-112144.html
I installed everything perfectly as instructed in the "Mini Cooper Coding" folder downloaded from the first page of this thread.
I'm using a fully updated Mac with fully updated WinXP running via Parallels 7.0.15. Everything is totally fine with the program until it is time for NCS Expert to read the VIN. INPA sees the battery and ignition as on but NCS Expert fails to read the VIN with the error box:

VIN is faulty
COAIP-2020: no answer from ECU
IFH-0009: ECU not connected or doesn't answer
I've installed with dates V38 as well as V40 both with the same results.
Versions:
INPA: 5.0
NCS Expert: 3.1.0
EDIBAS: 6.4.7
Does anybody know what's going on? I'm trying to modify the 2011 R56 S in my signature.
http://www.autoscannertool.com/china...an-112144.html
I installed everything perfectly as instructed in the "Mini Cooper Coding" folder downloaded from the first page of this thread.
I'm using a fully updated Mac with fully updated WinXP running via Parallels 7.0.15. Everything is totally fine with the program until it is time for NCS Expert to read the VIN. INPA sees the battery and ignition as on but NCS Expert fails to read the VIN with the error box:

VIN is faulty
COAIP-2020: no answer from ECU
IFH-0009: ECU not connected or doesn't answer
I've installed with dates V38 as well as V40 both with the same results.
Versions:
INPA: 5.0
NCS Expert: 3.1.0
EDIBAS: 6.4.7
Does anybody know what's going on? I'm trying to modify the 2011 R56 S in my signature.
Thanks,
Danny
You can find the BMW tools with Ediabas 7.5.2 and an easy install at www.bmwcoders.com (two different sites). I would reinstall everything (that is what I did) and it should work.
Also, Parallels seems to work just fine, sans this huge error.
Last edited by calforhelp; Jun 9, 2012 at 11:26 AM.
I've noticed a lot of the BMW folks saying that pin 8 on their cable has to be disconnected. Something about the car uses pin 8 for ethernet or something and that it messes up the programs if it is connected.
Does anyone have any information on this?
Does anyone have any information on this?
Not sure why people keep trying to buy a cheap cable on Enay for a $25,000+ car. Folks, the wrong cable can damage your car! Why skimp on this? One stop cables have been proven time and again, cs. Cheaper other ones that don't work or could damage modules.
Many thanks for GTECKO for the excellent guide. I got the cable, installed without an issue and coded quite a few things yesterday in my 2010 MCS (comfort close, one-touch sunroof, always display speed).
I have an issue with FRM2 but I saw some options here that I will try today. I still want to prevent window-roll-stop when you open the door and possibly the alarm heartbeat.
I have an issue with FRM2 but I saw some options here that I will try today. I still want to prevent window-roll-stop when you open the door and possibly the alarm heartbeat.
I've never been able to get the change to prevent window roll-up to stop when opening the doors to work, nor the change to allow both high beams and fog lights to be on (in KOMBI, I think). I do have the comfort close and one-touch sunroof changes coded though and I like those changes very much.
I would appreciate anyone who have access to the spreadsheet to limit themselves with the editing. Basically there is on the year column you should be touching (if its there already, it means it have already tried and it works)
If you have find a new mod and it works, great, feel free to add it.
Please stop deleting my work and the work ppl put in the this spreadsheet, stop edition the wording, the size of the column and all ... it is meant to be that way. I would hate to lock all the cells and have this file only read.
If you want to edit it YOUR way, download it and do what you want on it.
Respect others work.
Thanks
If you have find a new mod and it works, great, feel free to add it.
Please stop deleting my work and the work ppl put in the this spreadsheet, stop edition the wording, the size of the column and all ... it is meant to be that way. I would hate to lock all the cells and have this file only read.
If you want to edit it YOUR way, download it and do what you want on it.
Respect others work.
Thanks
So I posted a week or so ago and was suggested a new cable. I bought the forum recommended cable.
After getting the new cable, the first attempt to communicate with NCSExpert was slightly better. The program read the VIN but afterwards brought up the error below:

Every attempt after this resulted in the error below:

I get these errors wether I have the included adapter on the cable or not.
The cable is the recommended one.
INPA: V5.0.6
NCS-Expert: V3.1.0
EDIBAS: V7.2.0
DATENS: V46.3
Revtor's NCS Profile
Setup instructions I found in the first post of this thread.
Cable is set to port 4 and 1 for latency, while setting up BMW Tools, I selected port 4.
Any recommendations?
Or is there anyone who would be willing to set BMW Tools up for me via remote desktop?
EDIT:
I just tried again. The only change I made was to add the daten files into a folder named "R56" inside the datens folder on the C drive. I did this and the computer read the car and actually processed the ECU and gave me a FSW_PSW file. I turned the ignition off, in accordance with the instructions, then when trying to connect for a second time in a row to write to the car I, again get the "VIN Faulty" errors.
I did every combination of changing files, uninstalling everything and reinstalling, restarting the computer, EVERYTHING! Absolutely nothing allowed me to reconnect to the car :( This is so frustrating.
After getting the new cable, the first attempt to communicate with NCSExpert was slightly better. The program read the VIN but afterwards brought up the error below:

Every attempt after this resulted in the error below:

I get these errors wether I have the included adapter on the cable or not.
The cable is the recommended one.
INPA: V5.0.6
NCS-Expert: V3.1.0
EDIBAS: V7.2.0
DATENS: V46.3
Revtor's NCS Profile
Setup instructions I found in the first post of this thread.
Cable is set to port 4 and 1 for latency, while setting up BMW Tools, I selected port 4.
Any recommendations?
Or is there anyone who would be willing to set BMW Tools up for me via remote desktop?
EDIT:
I just tried again. The only change I made was to add the daten files into a folder named "R56" inside the datens folder on the C drive. I did this and the computer read the car and actually processed the ECU and gave me a FSW_PSW file. I turned the ignition off, in accordance with the instructions, then when trying to connect for a second time in a row to write to the car I, again get the "VIN Faulty" errors.
I did every combination of changing files, uninstalling everything and reinstalling, restarting the computer, EVERYTHING! Absolutely nothing allowed me to reconnect to the car :( This is so frustrating.
Last edited by calforhelp; Jun 20, 2012 at 09:23 PM.
Ok, so I deleted the virtual XP machine and reinstalled it from scratch thinking all of this messing around has messed up some files. I also re-downloaded all of my NCS installation files just to be safe.
So once a fresh version of XP was installed and updated, I followed guide posted HERE word-for-word, very, very carefully.
Still getting the same error:

Does ANYONE have any idea?! I would love to do a remote desktop session with someone who would be willing to set this up on my computer.
PLEASE HELP MEEEEE!!!!!
So once a fresh version of XP was installed and updated, I followed guide posted HERE word-for-word, very, very carefully.
Still getting the same error:

Does ANYONE have any idea?! I would love to do a remote desktop session with someone who would be willing to set this up on my computer.
PLEASE HELP MEEEEE!!!!!
I saw your post saying that it works on a Mac with Parallels "sans this huge error". I do not remember ever seeing any authoritative posts saying that the coding software actually works on a Mac with Parallels. In fact, I seem to remember seeing posts saying that it wouldn't work because the software couldn't get to the COM port. Maybe this is actually your problem.
When you install all the software, there is a program called INPA that you start by running INPALOAD.exe. One of the guides I used had instructions for creating a shortcut to this program. Have you launched this program and verified that it can actually communicate to the car? If you load this program and it indicates that it can not connect to the car, then NCSExpert is not going to work either. Aside from the question about using Parallels, are you certain that you have made the appropriate COM port available to the VM and configured the coding software to use that same COM port?
Danny
When you install all the software, there is a program called INPA that you start by running INPALOAD.exe. One of the guides I used had instructions for creating a shortcut to this program. Have you launched this program and verified that it can actually communicate to the car? If you load this program and it indicates that it can not connect to the car, then NCSExpert is not going to work either. Aside from the question about using Parallels, are you certain that you have made the appropriate COM port available to the VM and configured the coding software to use that same COM port?
Danny
I'm hoping that using an actual windows machine will work. I'm going to try bootcamp first since that's a little easier for me.
INPA sees the vehicle's battery and ignition as on. I'm 100% sure that the COM ports are set up correctly on the windows side and that when plugging in the cable, it is made available to the VM and not OS X.
I'll try out bootcamp then a PC. I'll report back with my, hopefully positive, findings.
Thanks for the help!
INPA sees the vehicle's battery and ignition as on. I'm 100% sure that the COM ports are set up correctly on the windows side and that when plugging in the cable, it is made available to the VM and not OS X.
I'll try out bootcamp then a PC. I'll report back with my, hopefully positive, findings.
Thanks for the help!
Ok, so I setup bootcamp on my MacBook Air with XP SP3 and set everything up exactly as the instructions on the first page of this thread advise. I used BMW Tools 5.0 and datens V46.3.
On the very first attempt to read and code everything was perfect, the car read perfectly, and it wrote to the .MAN file. But part way through, the car lost connection and when I tried to click, I received the "no answer from ECU" error above. Every further attempt to communicate with the car completely failed and I received the error when trying to read the VIN for the first time.
INPA still reads battery and ignition but NCS Expert has nothing.
Why is this working perfectly the very first time I try it and then dying part way through then never working again!?! It's all just making me unbelievably angry.
Everything HAS to be set up correctly, otherwise I'd never even get it to connect the first time. All of my software HAS to be compatible, otherwise I'd never get it to connect the first time. The computer and car HAVE to be compatible, otherwise I'd never get it to connect the first time. Is there some file that gets created that needs to be deleted every time NCS tries to communicate with the car?
I did notice that when running the laden.bat file most of the commands were giving errors such as "Cannot overwrite file with same name" but I do notice 5 or 6 new files created in the datens folder after running the laden.bat file.
On the very first attempt to read and code everything was perfect, the car read perfectly, and it wrote to the .MAN file. But part way through, the car lost connection and when I tried to click, I received the "no answer from ECU" error above. Every further attempt to communicate with the car completely failed and I received the error when trying to read the VIN for the first time.
INPA still reads battery and ignition but NCS Expert has nothing.
Why is this working perfectly the very first time I try it and then dying part way through then never working again!?! It's all just making me unbelievably angry.
Everything HAS to be set up correctly, otherwise I'd never even get it to connect the first time. All of my software HAS to be compatible, otherwise I'd never get it to connect the first time. The computer and car HAVE to be compatible, otherwise I'd never get it to connect the first time. Is there some file that gets created that needs to be deleted every time NCS tries to communicate with the car?
I did notice that when running the laden.bat file most of the commands were giving errors such as "Cannot overwrite file with same name" but I do notice 5 or 6 new files created in the datens folder after running the laden.bat file.
Unfortunately, I've got nothing else except to say that I am watching this thread with interest. When I coded my car about a year ago, I used XP mode on a ThinkPad running Windows 7. I had occasional communications errors that I could never figure out, but I was able to code most of the things I wanted to customize. Since then, I have started using a MacBook Pro for my personal machine, so I am interested to see if it is actually possible to run the coding tools in a VM on a Mac. As I said in a previous post, I do not remember ever seeing a definitive post from anybody stating that this will work on a Mac.
Last Step , Installing software
Ok , I got to the last step .
4. Finally , copy "REVTOR.PFL" from the "Profile" folder in your working directory into "C:\NCSECPER\PFL" .
I cannot find this REVTOR.PFL file .
The only thing I did different from directions was in Datens , using V38 . After installing . It stated do not copy folders just files inside folder . Well that worked for ECU and SGDAT , but I did not have a folder XXX ( R56) so in this instance I created the folder R56 then copied and pasted the files into this newly created folder so I had the proper string C:\NCSEXPER\DATEN\R56
Ran the LADEN.BAT file . So can anyone tell me what went wrong or where can I find REVTOR.PFL file
Thanks
Update : Think I found it by searching all files . Was in the initial folder created when unrar the NCSexpert program . Done for today will try again when I have some more time.
4. Finally , copy "REVTOR.PFL" from the "Profile" folder in your working directory into "C:\NCSECPER\PFL" .
I cannot find this REVTOR.PFL file .
The only thing I did different from directions was in Datens , using V38 . After installing . It stated do not copy folders just files inside folder . Well that worked for ECU and SGDAT , but I did not have a folder XXX ( R56) so in this instance I created the folder R56 then copied and pasted the files into this newly created folder so I had the proper string C:\NCSEXPER\DATEN\R56
Ran the LADEN.BAT file . So can anyone tell me what went wrong or where can I find REVTOR.PFL file
Thanks
Update : Think I found it by searching all files . Was in the initial folder created when unrar the NCSexpert program . Done for today will try again when I have some more time.
Last edited by Hubs; Jul 4, 2012 at 11:48 AM. Reason: update



Cheers.