Evening all,

This is my last ditch attempt to get my OBD reader to be seen by the laptop. I'm running Windows 7 and although the device appears in the Device Manager, it is not recognised by my Digimoto, Scantool 1.13 or by using Hyperterminal to try and communicate directly with the device.

I get the following error in the Device Manager details window:
This device is not configured correctly. (Code 1)

To find a driver for this device, click Update Driver.

And my hardware ID for the OBD Reader (ELM327 by the way) is:
FTDIBUS\COMPORT&VID_0403&PID_6001

Any help as always would be greatly apprieciated. I've been at this since 6pm tonight and have well and truly given up now...

Thanks,
A Grumpy, tired Kris

I take it you ran the installation CD for program?

There wasn't one

You just have to direct the update driver location to the CD drive which I have done and I get the error that the drivers were not installed correctly...

Very annoying

Without installing the software how can you expect it to work? There has to be a related program to read the data?

OK, which version of Windows 7, specifically is it 32 or 64 bit ????

Odds are that the driver is a 32 bit one for Windows XP. Some of these drivers work OK on Win-7 but only the 32 bit version. Otherwise you either need a different driver or a different operating system.

This is a massive ongoing problem with many software packages and if you're old enough to remember the Windows 3.1 to Windows 95 debacle it will seem very familiar.

The best solution I offer is one I use myself. Get a copy of VMware Workstation and build a Windows XP 32 bit Virtual Machine. That way you can use the VM for any legacy stuff which won't run under 7.

Dom

Thanks Dom.

I'm running 32bit version.

I'll look onto this virtual xp, sure I have a copy of it already

I'm with Gaz on this one, regardless of your system, if you don't have the correct drivers (and Windows 7 doesn't appear to have them on board, which means XP is everso less likely to have have them) you won't get a proper connection. Go back to your supplier, or check out their website for the drivers for your device. .
Experience is the only genuine knowledge, but as time passes, I have forgotten more than I can remember
Volvo V70 P2 2006 2.4 Petrol 170bhp Estate SE
MG Midget Mk1 1962

Previous: L322 Range Rover TDV8 3.6 2008; L322 Range Rover TD6 3.0 2002; P38A Range Rover V8 1999

If you think it's a compatibility issue, you just copy any related software into a folder and right click on the 'exe' program and select 'test compatibility' and Windows 7 will check program /drivers and choose a compatability mode (bit like on XP where you could choose to run a program as win 95 /98 ME etc). May help you and saves running XP under VM Ware Steve

Main car : FFRR L405 Vogue SDV8
Other car : Vauxhall Lotus Carlton
Past cars : FFRR L322 Vogue TD6 SE (Sept 2006 MY07) ; LandCruiser SWB ; 4-Runner ; Supras; XJS V12 LeMans

I've tried the interface now on 3 different machines, Windows7, XP and Vista and every machine see's the hardware but when loading Digimoto or Scantool i get the "interface not found" message.

I've concluded i've bought a dud. I've emailled the company and informed them the device is faulty. Will give them a few days and if i've not heard anything i'll dispute the case with Paypal.

Cheers for all your help!
Kris

OK, you might be right in assuming it's duff.

But, the message about it not being configured correctly smacks of a driver incompatibility. Not knowing much about the actual unit, perhaps you can tell us how it connects to the PC. Is it USB or Serial, or one of those USB to Serial dongle things?

Reason I ask is that the Blackbox Faultmate uses a serial port which is fine. But if you are forced to use one of those USB to serial converter things it can come in on a very high COM port number which can cause issues. A genuine serial port is always better since it comes in at COM2 usually (address 02F8) or sometimes COM1 (03F8). The higher (emulated) COM ports come in at addresses which were never issued (or reserved in memory) in the days of DOS and a lot of these programs talk in low level DOS terms to the hardware, hence the issues with high COM ports. Ask any Cisco guy who needs a console cable to a router - he will know this pain very well. If this is what you have then try and hard configure the COM port to COM 2, 3 or 4. No higher than 4 but avoid COM1 since that's normally allocated to internal modems (fitted or not)

If it's a USB connection then I would guess you are correct in thinking it's duff. Again though, I've seen USB cables to boxes (Autogas programmers) which have the USB to Serial bit built into the box so that's something to look at as well. Make sure it is actually USB if that's what you have.

Failing all that, it could be a driver issue but it sounds more like misconfigured ports to me from what I read above.