Cable to work with NCSExpert

V

v8z4

Member
 Fountain Hills, AZ
Hi all,
I tried downloading and working with NCSExpert, however I cannot get it to work with my BMW Scanner 1.4.0 cable/module. When I try to connect, the battery/ignition lights remain white (never connects up) . Perhaps the BMW Scanner module is only useable with the BMW Scanner software? Anyways, I need to find a known compatible cable to use with NCSExpert.

Thanks,
Chris
 
http://www.ebay.co.uk/itm/BMW-USB-Diagnostics-OBD-Cable-Interface-lead-Ediabas-Inpa-DIS-SSS-Progman-GT1-/110953205588?pt=UK_Diagnostic_Tools_Equipment&hash=item19d5538f54
 
mac27040 said:
http://www.ebay.co.uk/itm/BMW-USB-Diagnostics-OBD-Cable-Interface-lead-Ediabas-Inpa-DIS-SSS-Progman-GT1-/110953205588?pt=UK_Diagnostic_Tools_Equipment&hash=item19d5538f54
Click to expand...

:thumbsdown: How can you recommend that tripe? Biggest piece of junk I have ever bought.

FIRST, installation .. it comes with a 55 page installation manual ... yes - all that just for installation. And I'm a computer programmer, and it is the most difficult cumbersome install I have ever ever ever encountered. Takes maybe 20 hours to install, installing about 50 gig of virtual machines, ... this emulating that emulating that. Just crap. And the installation manual is full of errors.

SECOND, it doesn't even work with the newer facelift Z4s. The software it comes with doesn't even know what an N52 motor is ... it doesn't even recognise a facelift Z4 ... doesn't know what an E86 is ... it is just CRAP.

THIRD, when you complain to the people who sell the junk ... they just ignore you ... they don't even update their web page to state it doesn't work on facelift models.

So ... I have this cable now ... and software that doesn't even recognise my car. Anyone know where I can get some software that will work with that cable? And recognise an E86?
 
Funny as the instruction PDF is 55 pages and yes is comprehensive install but if you following the process easy to install, it took me 3-4 hours to install.

As for facelift I have coded many facelift e86 cars along with pre-facelift,so dont no what your problem is.


Sent from my iPad using Tapatalk HD
 
For example, on p.26 of the instructions, the engine types provided include the pre-facelift M54 engine (used in the E85 Z4 up to 2005), but do NOT include the N52 engine used in the Z4 from 2006-2008. There is NO N52 engine provided to choose from!?


When I get to p.46 of the instructions, with the cable connected to my E86 Z4 coupe, the software first does a hunt:

"The vehicle order is being determined"

... as per your instructions, and then returns the message:

"Information on a vehicle for the model series E85 could not be determined.
Use the diagnosis to make sure that access is possible."

I would be so very interested to hear where your N52 engine files are located? When I contacted the 'seller' on ebay, they didn't even dispute the fact that it doesn't work with the E86, nor that it doesn't know what an N52 engine is. :thumbsdown: :thumbsdown: :thumbsdown:
 
Which part of the software pack are you using, sssv32, dis 57 or INPA.

I have coded many E86 face lifts with SSS to switch on the triple blink indicator and auto lock after pulling off.



Sent from my iPad using Tapatalk HD
 
krusty said:
For example, on p.26 of the instructions, the engine types provided include the pre-facelift M54 engine (used in the E85 Z4 up to 2005), but do NOT include the N52 engine used in the Z4 from 2006-2008. There is NO N52 engine provided to choose from!?


When I get to p.46 of the instructions, with the cable connected to my E86 Z4 coupe, the software first does a hunt:

"The vehicle order is being determined"

... as per your instructions, and then returns the message:

"Information on a vehicle for the model series E85 could not be determined.
Use the diagnosis to make sure that access is possible."

Try checking your settings in VMware and set memory to recommend.



Sent from my iPad using Tapatalk HD
Click to expand...
 
The problem isn't VMware ... it's not a memory problem ... it doesn't even know what an N52 engine is. It doesn't have it. It's got the olde M54 whatever ... but not the N52. End of story. It's crap, and if I knew what junk it is /// like some archaic 1980s ZX80 emulating a toad through an RS232 port, ... I would never ever ever have bought such an EPIC waste of time. :headbang:
 
Well you must be doing something wrong, I bought cable and can code facelift e85 /86 cars



Sent from my iPad using Tapatalk HD
 
Here's a typical extract from the install manual to the crappy BMW Cables 'product':

-------------------------------------------------------------

From p.12 of the installation 'guide':

In the "variable value:" box, add ";c:\ediabas\bin" to the end of the list of folders e.g.:

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;c:\ediabas\bin

:rofl: That goes on for 55 pages.
 
krusty said:
Here's a typical extract from the install manual to the crappy BMW Cables 'product':

-------------------------------------------------------------

From p.12 of the installation 'guide':

In the "variable value:" box, add ";c:\ediabas\bin" to the end of the list of folders e.g.:

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;c:\ediabas\bin

:rofl:
Click to expand...

What difficult with that, I thought you did computer programming.


Sent from my iPad using Tapatalk HD
 
Only nightmare is that a computer programmer cannot install software correctly.
Check the Internet an lots of people have coded n52 engines with this software.

I did 3 on our last midland meet.
 
No problems so far, I'm on page 25 and calling it a night, lets see if I run into krustys page 26 problem tommorow as I have the n52 engine.
 
Did page 24 go ok and the results are as per the document, if you get any different other than "ok" then either go back and change settings or follow instructions.


Sent from my iPad using Tapatalk HD
 
Yes that all went fine, I had to go nd change settings but then re ran it and it all came back as ok :thumbsup: :D
 
I was going insane over the software, then as a last resort, took the cable apart and realised what a bodge job it is. I believe he takes a vagcom cable and bridges two pins to make it work with a BMW. He does this with a wodging great lump of solder, not even a link wire, and I found it was a dry joint. Fixed and everything came to life

Over on the bmwcoders forum there is a utility to update all of the inpa files automatically. I've not tried this but it seems popular. After buying this dodgy cable, I got what I wanted via my Intravee!
 
You must log in or register to reply here.
Back
Top Bottom