[mkoehnE90]

Thanks *******_! I didn't want to buy the cable until I got the program downloaded. On to phase II.

I tend to jump right into things

[joshuaacook]

Alright guys, hopefully someone can give me a hand here. Ive been frying my brain cells trying to search and figure this NCS error out. This forum has helped me tons. I have INPA working fine... I have the 2 black dots, I can read errors, clear them... etc. I was not able to do the airbag test with INPA though... and I have read that many others couldnt either and skipped this step. MY INPA is V5.0.2. The EDIABAS I have is V6.4.7. and the NCS I am using is V3.1.0.

I have updated my daten files by running the laden from within the e89 file of NCS. Whenever I go into NCS and load my profile, I do F1, F3, chasis - e89... wait... then F6 for "back". I can get through all these steps fine. Whenever I tell NCS to process ecu, I then select CAS, then read ecu... and this is when I get this error "data transfer interface/ECU disturbed" However, I can continue to to click read ECU multiple times and eventually it will read and give me the window that you close out. I have gotten that far maybe 4 times. I think after the 4th time NCS finally saved my CAS and modules into FSW_PSW of the work folder. I have also been able to get as far as clicking execute job trying to program the BV_DIGITAL speed but with no luck. I had to click execute job several times before I could get past said error and begin the programming. The programming completed and said "coding ended" but the digital speed in the cluster didnt become a option so I was unsuccessful...


This is my error. Can anyone tell me what the deal is?

I have a 2009 e90LCI 328i

I have this cable:
http://www.ebay.com/itm/BMW-USB-OBD-...79803103410109


which has a switch on the side which jumpers the pins when needed.

I have been following Junior's DIY. I have an old winXP laptop I installed these programs on and got that error... I also have a windows7 ultimate that I installed it on and I was more likely to get through the ncs steps easier than the xp...

I think Ive given all the info needed. If not, I will be glad to supply. Please help . Oh, and Im a beginner here...

[joshuaacook]

Oh, I forgot... My latency is set to 1, the port is set to COM1, I have also gone into the registry and verified that the fifo buffers were set to 8.

[jphughan]

Originally Posted by joshuaacook

Oh, I forgot... My latency is set to 1, the port is set to COM1, I have also gone into the registry and verified that the fifo buffers were set to 8.

Your car would likely need Pin 8 inactive to work properly given its model year. Assuming that's the pin the switch you have controls and you've tried it both ways though, the only remaining thing I can think of would be making sure you have the latest drivers -- but given that you have the Latency option you probably do. Other than that, the only other cause I've seen for those data transmission disturbed errors are faulty cables.

[joshuaacook]

Originally Posted by jphughan

Your car would likely need Pin 8 inactive to work properly given its model year. Assuming that's the pin the switch you have controls and you've tried it both ways though, the only remaining thing I can think of would be making sure you have the latest drivers -- but given that you have the Latency option you probably do. Other than that, the only other cause I've seen for those data transmission disturbed errors are faulty cables.

Cool man, thanks for the reply.i. I was kinda thinking the same thing. I emailed the dude and asked for a replacement... I guess now I have to wait 3 more weeks . I used to have VW and used the vag with it. I could try and take the 8 pin out of that cable maybe just to test the theory. Which one is pin 8 just to be sure... If I hold the connector with the wider side on top?

[JimVR4]

Originally Posted by jphughan

Your car would likely need Pin 8 inactive to work properly given its model year. Assuming that's the pin the switch you have controls and you've tried it both ways though, the only remaining thing I can think of would be making sure you have the latest drivers -- but given that you have the Latency option you probably do. Other than that, the only other cause I've seen for those data transmission disturbed errors are faulty cables.

I don't think that's the reason. I have a 2009 328i and my cable has pin 7 and 8 shorted and I can code with no problems.

Originally Posted by joshuaacook

Cool man, thanks for the reply.i. I was kinda thinking the same thing. I emailed the dude and asked for a replacement... I guess now I have to wait 3 more weeks . I used to have VW and used the vag with it. I could try and take the 8 pin out of that cable maybe just to test the theory. Which one is pin 8 just to be sure... If I hold the connector with the wider side on top?

I think your problem is out of date files. Junior's pack is not sufficient for newer cars like ours. You need EDIABAS v7.2 files and the Daten files might have to be updated as well. Search for the Phil Harlow DIY post as his pack has later files.

[jphughan]

Originally Posted by JimVR4

I don't think that's the reason. I have a 2009 328i and my cable has pin 7 and 8 shorted and I can code with no problems.



I think your problem is out of date files. Junior's pack is not sufficient for newer cars like ours. You need EDIABAS v7.2 files and the Daten files might have to be updated as well. Search for the Phil Harlow DIY post as his pack has later files.

EDIABAS 7.2 isn't necessary but it can help because some modules require OLDER files in the ECU directory to code (like FRM/NFRM) when running earlier versions of EDIABAS. With 7.2 you can use the new ECU files for everything. As for the Pin 8 debacle, it's an issue on cars produced 3/2009 or later, which is when the Ethernet interface was added. Prior to that, it doesn't matter whether or not Pin 8 is active. From 3/09 on, it has to be disabled. I don't have the cable right now so unfortunately I can't take a picture to show which pin is 8, but if memory serves I believe Pins 1 and 16 are stamped in the plastic, so you should be able to figure out which one it is.

[joshuaacook]

Originally Posted by JimVR4

I don't think that's the reason. I have a 2009 328i and my cable has pin 7 and 8 shorted and I can code with no problems.



I think your problem is out of date files. Junior's pack is not sufficient for newer cars like ours. You need EDIABAS v7.2 files and the Daten files might have to be updated as well. Search for the Phil Harlow DIY post as his pack has later files.

I will look up his DIY this afternoon when I get home and see if that resolves the issue.

My car prod month was 02/2009... So I just cleared that issue

Thanks!

[joshuaacook]

Originally Posted by JimVR4

I don't think that's the reason. I have a 2009 328i and my cable has pin 7 and 8 shorted and I can code with no problems.



I think your problem is out of date files. Junior's pack is not sufficient for newer cars like ours. You need EDIABAS v7.2 files and the Daten files might have to be updated as well. Search for the Phil Harlow DIY post as his pack has later files.

Is this the DIY your referencing?
http://www.e90post.com/forums/showthread.php?t=588311

If so, I think I downloaded that before and just updated my daten files with the daten from that zip file and left it at that. I will verify to make sure it was this particular zip file and install the EDIAVAS v7.2 from it...

[JimVR4]

Originally Posted by jphughan

EDIABAS 7.2 isn't necessary but it can help because some modules require OLDER files in the ECU directory to code (like FRM/NFRM) when running earlier versions of EDIABAS. With 7.2 you can use the new ECU files for everything. As for the Pin 8 debacle, it's an issue on cars produced 3/2009 or later, which is when the Ethernet interface was added. Prior to that, it doesn't matter whether or not Pin 8 is active. From 3/09 on, it has to be disabled. I don't have the cable right now so unfortunately I can't take a picture to show which pin is 8, but if memory serves I believe Pins 1 and 16 are stamped in the plastic, so you should be able to figure out which one it is.

Sorry I rechecked my cable and it appears pin 8 is floating, non connected. My production date is 07/2009. I have coded CAS, KOMBI and NFRM with a cable.

Originally Posted by joshuaacook

Is this the DIY your referencing?
http://www.e90post.com/forums/showthread.php?t=588311

If so, I think I downloaded that before and just updated my daten files with the daten from that zip file and left it at that. I will verify to make sure it was this particular zip file and install the EDIAVAS v7.2 from it...

That's the thread I was referring to.

[joshuaacook]

Originally Posted by JimVR4

Sorry I rechecked my cable and it appears pin 8 is floating, non connected. My production date is 07/2009. I have coded CAS, KOMBI and NFRM with a cable.



That's the thread I was referring to.

awesome! I'm gonna work on downloading that and update daten, run laden then try it again :-D. We'll see how it goes. Also the seller informed me the particular cable I have is most likely non defective as he's had that particular cable in production for 2 years and never had a bad one... But, there's a first time for everything. I'll keep my fingers crossed and he's offered to remote connect with me to check it. Hopefully all will be well after this update

[FlowState]

Originally Posted by Trevendous03

I can vouch for this... it does take a bit to get everything set up, but the coding part itself takes no time at all. I took a couple days at like 3 hours per day, but that's because I was stuck trying to figure out why the car on lift error was appearing. Everything else took about a half hour. Since I figured out why that specific error was coming about, and now that we have posted how to resolve it, it should seriously take you guys no time to resolve all your errors via coding. Def the proper way to do things! Just always, always code for xenon first before doing the rest of the FRM or CAS codes, because coding for xenon requires a reset of both of those submodules.

Can someone clarify this?

The only way to get rid of the bulb warning (yellow light indicator) and low beam failure (red car on lift indicator) is to first code for Xenons, and THEN change the settings for the headlights?

I'm having my car coded on Thursday and would just like a final confirmation on this. I don't have the Bi-Xenon setup. Can I still code my aftermarket lights to Xenon's in my cars computer? I am really tired of the annoying light out chime and red car on lift symbol on my dash.

2006 325i

[strams]

New to this board but done some coding on my car and wanted to say Hi to everyone.

[Tru3Story]

question, yes im a newb, i have an 08 328i with xenon. i just purchased the lux angel eyes v5.1 for my e90...do i need to be coded before installing them?

also, im getting fog HIDs with cancelors, do i gotta code for those too?

[BMW-335i-07]

Originally Posted by Tru3Story

question, yes im a newb, i have an 08 328i with xenon. i just purchased the lux angel eyes v5.1 for my e90...do i need to be coded before installing them?

also, im getting fog HIDs with cancelors, do i gotta code for those too?

no and no

[Tru3Story]

Originally Posted by BMW-335i-07

no and no

thank you sir! have made my first 2 mods easy

[FlowState]

Originally Posted by DUI Elite

Can someone clarify this?

The only way to get rid of the bulb warning (yellow light indicator) and low beam failure (red car on lift indicator) is to first code for Xenons, and THEN change the settings for the headlights?

I'm having my car coded on Thursday and would just like a final confirmation on this. I don't have the Bi-Xenon setup. Can I still code my aftermarket lights to Xenon's in my cars computer? I am really tired of the annoying light out chime and red car on lift symbol on my dash.

2006 325i

Bump for answer

[hiter202]

anyway to get it to work on windows 7 64bit?

[jphughan]

Originally Posted by elitefusion

anyway to get it to work on windows 7 64bit?

Not unless you can decompile NCS and do some reprogramming.

[joshuaacook]

[IMG]

Uploaded with ImageShack.us[/IMG]

Anyone able to help me figure this one out? 9 times out of 10 I get this issue. I have been able to get as far as "read ecu" and have the window pop up that you can just close out, even get to the trc file, save it as a man, then try and process ecu but get this datatransmission to interface disturbed error. I have gotten an fa fehler error before too. I have win 7 ultimate. Ive checked the obdsetup.exe file and all seems to be OK. Latency is 1, fifo buffers are 8. I can get the datatransmission error at any point throughout the steps to process car... its not at just any given step...

My hair is prematurely going grey from it...

any ideas?

its an 09 328i (02/2009).

[Dziqsek_]

Lokk like you have interface problem, did you have dcan cable and updated ncs and ediabas ?

[joshuaacook]

Originally Posted by *******_

Lokk like you have interface problem, did you have dcan cable and updated ncs and ediabas ?

Yeah I think so. Is that my problem? It says K+Dcan INPA compatible.

It's this cable
http://www.ebay.com/itm/BMW-USB-OBD-...item3cc3966610

Yes I updated the ncs that was shipped with the cable and the edibias...

What should I do to fix it?