harryp wrote:Ah, Lexia! I now have one of my own.
Having struggled and read hundreds of posts on problems with Lexia, I do not know if my problem is related to software or the hardware supplied with the leads etc. I am using a s/h laptop bought for sole use of the lexia, 1Meg RAM with XP professional SP3 loaded. Eventually managed to get Diagbox loaded with help from both seller and this forum
![Smile :)](./images/smilies/icon_smile.gif)
. It is V7.02, and is not connected to the internet. Ign is fully on, all dash lights lit. Should I only have in the Aux position?
On starting asks for the VIN. Select Lexia, then select citroen, Xantia, Xantia2, asks for VIN to be input,VIN entered, asks to select application again. Select Lexia, ”Data access problem, you must close the applications in order to change vehicle”
Doesn't sound like the software is installed properly to me, as the sequence you describe above is not correct for Diagbox 7.02. It almost sounds like the standalone (older) version of Lexia has also been installed, which would probably clash with the version bundled with Diagbox.
The correct sequence for Diagbox 7.02 for a Xantia is:
1) Connect the interface to the USB port (the green light should come on)
2) Launch Diagbox, say no to "do you want to check for updates"
3) Choose Citroen, Xantia, Xantia 2, which will take you to a screen with two options, Lexia and Scantool.
4) Unplug the USB cable from the laptop, wait 5 seconds, plug it back in, wait 5 seconds.
5) Click Lexia and enter the VIN number of the car. This will now launch the Lexia app.
6) Before going to Diagnose turn the ignition key on or start the engine.
I've never seen the Lexia app itself ask for the VIN number, you should only get asked for the VIN number once before Lexia is launched. So either you have the old standalone version of Lexia installed (which did ask for the VIN number itself, as it ran by itself without any Diagbox app) or possibly Lexia is unable to communicate with the car so is asking to verify the VIN number again. (However I have not seen this happen even when I've had the cable from the interface to the car unplugged)
The svhost.exe then uses 100% cpu. Trying to exit, get the error msg, “the communication card is incorrectly initialised. Tool must be restarted” Validate to switch off tool. Can only exit by using Windows Task Manager to end task, which it does with great reluctance. All cables are tight into sockets etc. Have removed and re-connected usb as recommender in forum posts but to no avail. Seems stuck in a loop, lexia, vin, Data access problem. Svhost.exe still using 100% cpu, but strangely enough can start Diagbox easily, so reckon the task manager is caught up somewhere too.
The Lexia app will tend to hang and be difficult to end task if anything goes wrong with communication with the interface. The communication card error is worrying, first check in windows device manager that you have an ACTIA device without any errors displayed when the interface is connected and that you have a solid green light on the interface.
Any ideas as to whether it might be hardware or software related? I am beginning to fray a little at the edges, well quite a lot actually
![Crying or Very sad :cry:](./images/smilies/icon_cry.gif)
. My next port of call may be to get the vendor to load it again remotely as offered, but it seemed to load ok once I realised it needs to be done via the Demon.
I have to come to greatly value and respect the expertise available on this forum and wonder it anyone else has, or knows of, a solution? Thanks for any advice coming this way!
Really hard to know without seeing the hardware first hand, with another working system to compare with and swap to find out whether its hardware or software, as the Lexia software and hardware from different vendors does vary somewhat.
One other thing - have you tried it on another car or tried another Lexia on the same car ?