You are welcome,
I will change latency and let you know
Will take good picture of my cable too.
Windows does not stop rolling up when door opens ! Great.
My car has electronic side-view mirrors , any clue to fold them with lock on keyfob.

 

If you have a green working cable then disregard the Latency part. This is only for people who have a non-working white cable.

 

Here is the error message for me.

I did not reinstall the software yet. I had everything working for the E60 platform.
I did updated the filed in folders per the instructions and have the latest daten files.

I do get two black circles in INAP. The error message pops up when I hit F3 to read the ECU.

I am going to redo the process again and recheck my software versions.

 

Your cable most likely does not work on DCAN vehicles. You have one of the faulty ones (only works on k-line).

Just to confirm, make sure pins 7 & 8 are disconnected and then change Latency to 2 and also 4 and try again. If you do not have success, you need a new cable.

 

I do not see a setting for Latency. I have "receive buffer" and "Transmit buffer". Both are at 8
Edit: I was looking at the wrong device in the device manager.

 

I also reinstalled everything. When I went to update the datan files the NCSExpert daten folder was empty. I created a R56 folder an placed the latest daten files in it.

I was expecting the daten folder to have files in it from the main installation.

 

I got further after I reinstalled everything. I can now make contact with my ECU and pull the vin and other info. No error messages.

I haven't tried to code yet but things look good to this point.

:-)

 

Glad to hear it! That cable is identical to mine, so you should be in good shape.

Sometimes a full re-install just clears out the demons.

 

Question....
When you read the different modules do you save the TRC file created as a backup in a different folder? I created a folder and named it the same as the modual "CAS" and put the TRC in this folder. When I read the FRM I put that TRC in a "FRM" folder.

Is this needed? Or is it over kill?.

 

Yep. I use the following methodology:

Create WORK folder. Create subdirs for CAS,ABG,KOMBI,FRM, etc....

Read all modules, move files to appropriate folders (incl nettodat). Copy folders into WORK_BACKUP folder. Make coding changes to folders under original WORK directory. Drag files back to main flash directory one-by-one to flash.

Not overly complicated. Takes a bit longer, but completely foolproof and safe.

 

TRIPLE_O
With my R60, mini countryman cooper s all4, 09/22/2012
I checked faulty cable ( pic as cm.d mentioned in post 568, left white one)
Change latency to 2 or 4 , help INPA to read right status of ignition.
If latency = 1, INPA always reports ignition on no matter that is car ignition status

But NCS can not read anything, shows:
vin is faulty ,
COAPI-2020, no answer from ECU
IFH-0009, ECU not connected or doesn't answer

 

Forgive me! I was too exciting to search rightly.
Holding Fob Trunk Button Sounds Panic Alarm ** Works only on models w/ Alarm Package!
This worked!
Edited SPEG module to make a sound when car locked or unlocked, success! The sound is too low! Maybe there is a field to make it louder?
Bluetooth audio apprears in CD media but no Bluetooth music source to test.
Will update soon, wife called for a ride

 

Today is coding day!

I am planning on reading a few modules, save the TRC files in different folders, and then come back into the house to make the coding changes (in each module folder).

I then plan on going back out to the garage and coding each module (as Theta noted) one at a time until they are all coded. Question: When coding more then one module, do you guys close the program, disconnect, and full test each module after you code it before you move on to the next?

 

I'm a little methodical (where "methodic" == "an") when it comes to coding my car. I like to close the program and go back through my steps. There are easier ways, but I've found that while forcing myself to go through the steps every time takes a little bit longer, it decreases the chance for errors.

 

Has anyone had an issue with the one touch sunroof mod?
I coded the four lines of code as described but the one touch close doesn't work. When I try to close the roof the panels only move 6" and stop. I then toggle the switch again and it moves another 6" I does this each time until it is closed.
The one touch open seems to work okay.

I will let the car sit a few to see if the ecu needs some time to accept the change.

Cheers

 

I had the same issue with the sunroof. All you have to do is put the key in and turn on the ignition. Press the sunroof button to the first click and hold for about 20-30 seconds. The roof will open and then close. Wait till it closes and it will be fixed.

 

Yep. That is what I ended up doing. After that I recoded the one touch and everything works fine.

Cheers.

 

Agreed totally, I did meet a case that the new codes were not written in if I did not close ncsexpert and open it again.

 

Awesome so you got a non defective cable!

I think it is overkill. Some people take multiple backups, some do not. Both ways are fine for multiple reasons.

Although this is good so you can read your files offline.

Thanks mikecalgon for checking. Just to confirm, pins 7 & 8 were disconnected from eachother right? I'm trying to see if maybe we can get these faulty cables to work (not recommending people to buy them, but since some have them it is worth a shot).

You do not need to close the program or disconnect anything when you turn off the car, etc. You can just pickup where you left off. As you code more you will find yourself just coding all the changes at once and then test at the end.

For some later model R56's and R60's the one touch sunroof mod does not work right after coding. The module needs to go through a full reset before the one touch operation starts to work. It usually only takes 10 minutes, but just power the car down and power it back up after that time. The Fxx chassis BMW's are the same way with the rear hatch module.

Again, you never need to close NCS and re-open it. Once the codes are written to the car, they're in. Occasionally the module itself just needs to reset.

 

TRIPLE_O
the faulty cable pin7/8 soldered originally, I disconnected them before the test of change latency. It seems like that the good cable is older version. Could be a software merged into circuits.

 

Hello,
TRIPLE_O
mikecalgon
cm.d
THETA
kerrys914
great talks on cable.
I own a blue PCB cable that doesn't work. I compared with Hi-res pictures posted here up but I didn't find any macroscopic differences from THETA and cm.d ones.
I REMOVED also the pin 8 from OBD connector because pin 7&8 were shorted together on the back PCB, and when I try to connect the PC with my MC Cooper D 4/1012, Ediabas reports correctly battery and ignition on/off sensing. Although it seems work fine I'm not able to read any ECU's.
The cable's supplier with the cable included also the following programs for setting the cable modes:

D-CAN.exe (windows)
DCAN.exe (dos shell)
L_timer.JPG
Number.JPG
OBDSetup.exe (dos shell)

When I launch D-CAN (or DCAN) and I set the "D-CAN" mode the led on cable switch off and after few seconds the software reports an error code.
Have you got any experiences on this setup?

Here I attach the HR picture of my cable.
Thanks a lot for your attention,
Silvio.

 

I have to say that the only blue PCBs I've seen were in the older blue cables (Pre-K+DCAN).

If this is indeed the case, the hardware, itself, will not allow for DCAN communication.

 

Good issue THETA.
Since it seems identical, can you help me to compare the blue hardware with both white and green?

 

Looks like the pins are bridged on the IC chip. I don't know if that's your problem though. I don't know much about how these circuits work.... but I can build them.

 

Thanks for the feedback. It looks like no matter what, drivers, pins, latency, etc that this cable is in fact faulty.

Correct. I have never seen a blue board cable work for a DCAN vehicle. I have seen others order them with no success.