Merged Lexia & Diagbox threads

[GiveMeABreak]

What version of Windows are you using and is it a 32 or 64 bit version?

[sonoramicommando]

I'm pretty sure 32 bit version (the laptop is pretty old) but I'll have to check.

[GiveMeABreak]

XP? Win 7?

[sonoramicommando]

Sorry - XP.

[sonoramicommando]

It's XP professional 32-bit version. (well, it is pro and doesn't say 64-bit, so I gather that implies it is 32-bit)
All USB root hubs (all four of them) have the power save disabled.
There are a few "other devices" with yellow "?" in the Device Manager, which I'm guess don't have correct drivers and not installed right. They are bludetooth module, PCI simple communication controller, unknown device & mass storage controller.

[GiveMeABreak]

Well that should be the starting point, get the drivers installed for the hardware first. Sounds like you are missing the Intel chipset drivers for your motherboard. The Bluetooth module may be independent or may be part of your network or communication hardware depending on your Laptop make and model.

Dig out your OEM driver CD / DVD and get those installed first so there are no yellow exclamation marks. unfortunately Windows XP is now unsupported by Microsoft so you can’t get updates now. You should really have XP patched to service pack 3. If you have the option I would personally get Windows 7 installed instead.

I’m not sure what your IT skills are like, but if you have internet access and need a hand let me know and I might be able to source the files and remote into your laptop and see if we can’t get all the drivers on. I think unless you get all the hardware drivers on first, there is little chance of getting Lexia working. Let me know if you want a hand.

[Hell Razor5543]

What make/model of laptop is it? You may well find that (despite its' age) you are able to get the device drivers directly from the manufacturers. I would (assuming you can get them) download and install all of the relevant ones for the laptop (some my be specific to different countries around the world). At the moment Windows is trying to 'guess' how to use some of the hardware. The device drivers 'tell' the O/S exactly how to use the hardware, and what it can do.

[sonoramicommando]

It's an old (and huge) HP laptop.
I downloaded a whole bunch of drivers off HP website for the laptop last night, will install drivers and see how it goes.
Cheers.

[GiveMeABreak]

Make sure you install the inter chipset driver first - as then once this is done and the laptop is restarted it will allow the installation of the other drivers now that they have been recognised - trying to install the actual component device drivers (especially PCI comms drivers, audio and some network adapters) first won't always work.

[ekjdm14]

EDIT- opening up the VCI was the first thing I should have done, hindsight being 20/20 and all that... Bad connection on one of the internal plugs I think since it's working now! Think I might upgrade my Diagbox laptop at some point though as it's still old, slow and has damaged keyboard and screen. Off to find the cause of an Antipollution fault now fingers crossed!


OK further to my post earlier reminding someone about making sure the COM board evolution driver (multi instance) was installed & this temporarily at least making my VCI work.

Now I'm having an issue again with it, when I plug in the VCI I get a few seconds of green light then nothing (whereas I should get 3 flashes and stay lit). Just wondering if there's anything I'm missing here, when I go into the interface checker app and click activate, it shows as having firmware V4.3.2 installed.

Something I noticed that maybe of consequence is, no matter which previous firmware version I try to downgrade to it still shows up on the checker as V4.3.2 no matter what I try (I do get the "telechargement OK" message each time as well, and ive double checked it's not saying "KO"). If I click around the Interface Checker enough after supposedly downgrading the green light does come on, but still no contact with Diagbox and if I unplug/replug it still fails to activate correctly.

So far I've swapped my serial adapter lead from the long one to the short one with no change, fiddled with the plug numerous times, done a reinstall of Windows 7 starter (x86), clean reinstall of diagbox 7.01/02 with all associated drivers and still no joy, updated to 7.57 still with no green light and no contact between Diagbox and the VCI, just now I've RE-reinstalled the driver (ACTIAPnPinstaller.exe) and still the same. Also, no matter what firmware version I purportedly have on said VCI at launch, and regardless of whether I launch with the green light showing or now, Diagbox launcher races through the check of interface version/makes no attempt to update it.

Just wondering what I might have missed here, and if the failure of the Interface Checker to show downgrades of firmware could be indicative of a fault with the VCI unit itself or perhaps with my laptop (it is pretty beat up and slow so might try and find a better one anyway).

Pleeeeease has anyone got any suggestions that don't involve huge financial outlay! even if it takes a while... I'm at the point of physically opening up the VCI and checking for dry solder joints otherwise lol... I should add that it has worked previously, although I'd had a bit of a faff with the USB driver reverting back to UMDS instead of multi instance in the beginning, but I had worked through this last year and had it talking happily with the 206, as well as partial comms with S1 Xantia only last month.

[GiveMeABreak]

Excellent - I treat mine like a baby as I know how sensitive these things are! Good luck troubleshooting the AP fault.

[Gibbo2286]

Any opinions on this being offered now on the easydiagnostics site?

http://www.easydiagnostics.co.uk/shop/ ... /11261316

[Paul-R]

Looks interesting. At least you'd be able to use a more modern (faster!) computer.

They don't mention the actual software though, do they?

[Gibbo2286]

They seem to be suggesting that it will do all that the damned Lexia will do.

[MikeT]

Without knowing, I'm guessing that's simply a wireless (bluetooth, in this case) VCI that connects Diagbox instead of the more commonly-known USB-wired VCI we all use?