View Single Post
      07-11-2014, 01:57 PM   #1
MineralweissIS
Second Lieutenant
MineralweissIS's Avatar
47
Rep
201
Posts

Drives: 2012 Mineral White 335is
Join Date: Aug 2013
Location: Miami, FL

iTrader: (2)

Garage List
2012 BMW 335is  [0.00]
Should I toss my BM Technic cable?

Late last year I purchased the cable/software package from BM Technic just before they went under. At the time it was a $100 investment and included all the software under one roof and self-installed. Easy, I thought. In hindsight, I wish I had not.

First time using their cable was with their bundled software installed on a Win 7 64 bit machine. Once in NCS expert I got an error stating "VIN is faulty" (IFH-0003). This error comes up after I load the profile, select F1, then F3, chassis and module. I get a different error altogether if the cable is not connected to the OBD port so I know something is happening with it connected.

I did some reading and concluded 64 bit was the problem. So I installed a clean copy of Win 7 32 bit. Much to my surprise I was no longer able to install the BM bundled software because it requires on-line activation and since is BM Technic is no longer around I was SOL.

Since I was back at square one I decided to follow the sourcing and install of the software using the DIY found in this forum:

http://www.e90post.com/forums/showthread.php?t=918608

It is quite involved but I am still thankful for the efforts made by member 808AWD325xi.

Tried the cable again. Same error. Tried to launch NCS Expert in XP compatibility mode. Same error.

Finally installed Win XP using VM Ware and followed a simpler installation DIY found here:

http://www.northamericanmotoring.com...xpert-diy.html

Tried the cable again. Same error.

Moved the virtual machine to another laptop and tried the cable again. Same error.

I have double and triple checked all communication settings and have even followed BMW's published INPA/NCS Expert FAQ, which states all possible errors and fixes.

After trying two different machines and three different operating systems, I think its safe to say the cable is the problem.

I'm an IT guy so this stuff comes easy to me but throwing away what appears to be a well made cable that will not communicate irks me.

I will invest in another cable if i have to but want to get feedback from others here before I do that.

Does anyone have any ideas before I go shopping? Thanks.

Last edited by MineralweissIS; 07-11-2014 at 02:09 PM..
Appreciate 0