Lexia no longer recognized by the laptop

[Cristache39]

Hi all,

I bought an year ago a clone Lexia interface, A.1281 Z and a few days ago, for the 1st time I couldn't connect it to the car. I noticed then that the interface's led stayed open for 2-3 seconds and then shut off. It was not reading the VIN's car, then i was receiving the following message : "Currently updating communication interface software, please wait..". After, i wrote the VIN but still no connection with the car.
I decided to reinstall the DiagBox, I'm using it on Windows 7 with VMware. I want to highlight that the interface was recognized by both devices, host and VMware.
After reinstalling the virtual machine (the same that i've received when i bought the interface) I've connected Lexia again to the laptop, the led remained ON but the issue now is no visibility from both devices, Windows 10 and VMware.

I read somewhere that maybe the Actia driver should be installed. I looked in C:\AWroot\bin\fi and all I saw regarding Actia (which helps reading the interface from what I understood) is actiadc.dll.
Can somebody guide me with this, please?

Cheers!

[Mihael_M]

Hello, which Diagbox are you using? Generally, during installation, the Driver icon appears and then you have to click on it to install the drivers. After that, there is the PSA Interface checker icon. If you click on it, the Lexia interface is tested.

[Cristache39]

Hello, which Diagbox are you using? Generally, during installation, the Driver icon appears and then you have to click on it to install the drivers. After that, there is the PSA Interface checker icon. If you click on it, the Lexia interface is tested.

Hello,

I'm using the version 9.91. When I open it from VMware in order to install I receive only one pop-up ("This virtual machine might have been moved or copied. ...") and that's it. I think that first time something came with removable devices that can be connected with the virtual machine.
Regarding PSA Interface Checker, that is not working. I checked, but because Lexia is not seen by laptop nothing happens.

[Mihael_M]

Why do you use virtual machines? Find version 9.85 and install it directly on Win 10. Before installation, turn off antivirus and windows defender. If you use the existing laptop for other things, get a smaller SSD drive (128 GB is enough) and try to install Diagbox on it. When you connect Lexia and run Interface Checker, then you are sure that the driver and Lexia are fine.

[Cristache39]

Why do you use virtual machines? Find version 9.85 and install it directly on Win 10. Before installation, turn off antivirus and windows defender. If you use the existing laptop for other things, get a smaller SSD drive (128 GB is enough) and try to install Diagbox on it. When you connect Lexia and run Interface Checker, then you are sure that the driver and Lexia are fine.

That's what I've received when I bought the interface and precisely because it's my personal laptop I decided not to use the native DiagBox, which requires disabling the antivirus.
It's working fine also through virtual machine but now the problem is that I don't known how to make the interface visible again.
After reinstalling DiagBox, the interface is suddenly no longer recognized.

[Mihael_M]

Do you have ACTIA USB Devices in the Device Manager? Below is the USB Com Board Evolution Driver (UMDF). It appears when you connect the Lexiu device. If it is not there, the Driver is not installed properly. You can repeat the installation of the driver. If the drivers are there, try Interface Checker. You have to press Activate and Version. If it doesn't show the version, something is wrongly installed.

[Cristache39]

Do you have ACTIA USB Devices in the Device Manager? Below is the USB Com Board Evolution Driver (UMDF). It appears when you connect the Lexiu device. If it is not there, the Driver is not installed properly. You can repeat the installation of the driver. If the drivers are there, try Interface Checker. You have to press Activate and Version. If it doesn't show the version, something is wrongly installed.

When I installed DiagBox the driver was not there, i mean in VMware. Then i selected "Add old driver" and add it, but bellow, USB BBP Driver (UMDF) has the exclamation mark with the details "This device can not start (Code 10)".
On host in Device Manager when I connect the interface nothing changes, in Universal Serial Bus Controllers.

How can I repeat the installation of the driver? Any clue?

[Mihael_M]

I am not familiar with VMware .I would delete the Diagbox installation and delete the Actia driver , and then start the Diagbox installation again.
You have this instruction on Youtube from romenian site.
Tutorial instalare Diagbox 9 91 VMWare Windows 10 64 bit

[Cristache39]

I am not familiar with VMware .I would delete the Diagbox installation and delete the Actia driver , and then start the Diagbox installation again.
You have this instruction on Youtube from romenian site.
Tutorial instalare Diagbox 9 91 VMWare Windows 10 64 bit

Yes, I saw it. I’ve deleted and reinstalled DiagBox yesterday multiple times exactly like that but nothing. I don’t get why the driver is not being installed directly with DiagBox.

Thank you anyway Mihael for your time!

[cit-rotti]

Please use a different software version.
The 9.91 is not very stable.
If you perform a native installation, there must be no virus program, not even Defender.
The conditions must also be met for a VM installation.
An optimal native software is available e.g. from Robert in the Spanish forum - but the activation costs 20€.
However, free software versions are also offered and there are the necessary accompanying programmes and many tips.
Google Chrome can translate all this sufficiently.

Link: https://guiapsa.foroactivo.com/login

[Cristache39]

Please use a different software version.
The 9.91 is not very stable.
If you perform a native installation, there must be no virus program, not even Defender.
The conditions must also be met for a VM installation.
An optimal native software is available e.g. from Robert in the Spanish forum - but the activation costs 20€.
However, free software versions are also offered and there are the necessary accompanying programmes and many tips.
Google Chrome can translate all this sufficiently.

Link: https://guiapsa.foroactivo.com/login

Hello,

Ok, I will try to find another version. But this will fix the visibility issue of the interface?
The fact that 9.91 is not stable could be the reason why the interface is not recognized anymore?

[cit-rotti]

can't judge that because I prefer to use native installations and work with an original VCI.

With a VM installation, the configuration of the software (in this case probably WIN 7 64 bit pro) must also be suitable for the VM used and the correct VM programme must be used.
During the VM installation, you are also asked whether the driver for the VCI should be installed and always remain usable.

It can therefore be due to a failed VM installation - but a bad China clone is also conceivable. Especially after the VCI has been updated, it is very likely that it is faulty. Normally the VCI flashes 3 times and then lights up constantly. Connected to the vehicle - ignition switched on - the VIN should always be read.

Even without being connected to a car, the function of the VCI can always be checked.
Start the laptop and start the DB - connect the VCI to the correct USB port - the VCI must flash 3 times and then continue to light up green - select the vehicle and then enter A111..... instead of a VIN (as many ‘1s’ until none are accepted) and then continue to select - after no vehicle is connected, of course, no control units are recognised - then return with F2 and F9.

If there is no helper nearby to test the VCI, I have recommended a native installation because it is easier to check whether the VCI is installed.

[Mihael_M]

Cristache : Your problem is probably not a defective device, but a conflict with the drivers. I told you to get an SSD (128 GB is enough) and install everything again. I have done this with my laptop and installed various versions over 20 times. I tried 9.85, 9.150, 9.186 and 9.208. These are all free versions and 9.85 suits me best. And if you want to fix the existing one, you have to delete the Actia driver in Device Manager, as well as Diagbox. After that, reinstall Diagbox, which will install the drivers again.

[Cristache39]

can't judge that because I prefer to use native installations and work with an original VCI.

With a VM installation, the configuration of the software (in this case probably WIN 7 64 bit pro) must also be suitable for the VM used and the correct VM programme must be used.
During the VM installation, you are also asked whether the driver for the VCI should be installed and always remain usable.

It can therefore be due to a failed VM installation - but a bad China clone is also conceivable. Especially after the VCI has been updated, it is very likely that it is faulty. Normally the VCI flashes 3 times and then lights up constantly. Connected to the vehicle - ignition switched on - the VIN should always be read.

Even without being connected to a car, the function of the VCI can always be checked.
Start the laptop and start the DB - connect the VCI to the correct USB port - the VCI must flash 3 times and then continue to light up green - select the vehicle and then enter A111..... instead of a VIN (as many ‘1s’ until none are accepted) and then continue to select - after no vehicle is connected, of course, no control units are recognised - then return with F2 and F9.

If there is no helper nearby to test the VCI, I have recommended a native installation because it is easier to check whether the VCI is installed.

I bought the interface from my country and with it I received also instructions for installation. It came with VMware Workstation 16 Player and indeed the software is a WIN 7 64 bit pro. During installation I receive only 2 pop-ups, "This virtual machine might have been moved or copied" where I select "I moved it" and "Removable Devices can be connected to the virtual machine". That's it. Now, i noticed that VMware tools is not being installed and from what I read the tool provides the pack with all drivers.
Regarding the flashes of VCI at connection, it never did that, neither when it was working, just lights up and stays like that.
I will try with a native installation to see if it will be recognized. I installed also Actia drivers but without success.

[Cristache39]

Cristache : Your problem is probably not a defective device, but a conflict with the drivers. I told you to get an SSD (128 GB is enough) and install everything again. I have done this with my laptop and installed various versions over 20 times. I tried 9.85, 9.150, 9.186 and 9.208. These are all free versions and 9.85 suits me best. And if you want to fix the existing one, you have to delete the Actia driver in Device Manager, as well as Diagbox. After that, reinstall Diagbox, which will install the drivers again.

Yes, but until I will get a SSD I was thinking to repair this one with VMware but it's driving me crazy.
The Actia driver is not present on Device Manager from host but I deleted the Diagbox, all drivers from Universal Serial Bus controllers on host, reinstall VMware 16, open again the virtual machine for further installation of Diagbox and still nothing. I noticed that VMware Tools is not being installed which I read that it should provide the pack with all drivers.
I guess that the only chance is checking with a native installation.