Lexia Diagbox VCI Not Connected Issue: Solutions for Windows 7, Peugeot 308SW HDI & Citroen C3

Hello
I bought a Lexia interface from a Chinese.
General problem: in the diagbox, the message "VCI is not connected" after selecting any car.

Tested on 2 laptops - Windows 7 32bit and Windows 7 64bit
DB version 7.02, and probably 7.86 from the Chinese
Generally, when connecting the interface to USB, the LED will flash several times, then it will be lit continuously. In the device manager, the interface detects correctly (Actia USB devices > USB COM board Evolution Driver (UMDF)
When you try to connect the interface to the car, the effect is the same. You can't hear any relays ticking, etc. Tested on Peugeot 308SW HDI and Citroen C3 petrol. I tried different combinations and sequences, with the key in the pre-ignition position, with the car running, connecting the interface and starting the DB, and connecting to the already running DB.

I took apart the interface, no damage or cold solder is visible on it
The interface checker correctly detects Lexia as version 4.3.0 921815C
Something wrong with diagbox, is it interface fault? Can it be fixed somehow?

As far as I know, this hardware only works on Windows XP.

Hello
I had a similar problem, the interface bought from our colleagues who have everything for about $ 30 did not connect to my C5 2007, although the seller guaranteed that everything must be ok.
After disassembling the housing, it turns out that I had a LITE version interface without CAN bus support (only one white optoisolation system was inside).
I bought 9817A-2 (PS9817A-2) thinking that after soldering the interface will communicate with the car. Unfortunately not.
The solution was (proverb: he who buys cheap, buys twice) to buy a decent interface for $ 56.

Well, that's a curiosity. Diagbox 7.02 and 7.86, from 2 different sources. Both tested on different laptops, with Windows XP, Windows 7 32 bit, Windows 7 64 bit, not working anywhere.
I downloaded PP2000, installed XP on a virtual machine, it runs like this doll.

Personally, I have Diag installed on a separate removable drive.
I installed the program on clean XP without uploaded drivers for the network card and Wi-Fi card and without any antivirus.
If necessary, I replace the hard drive in the laptop and it's ok.
Laptop - old DELL Latitude D830
It also worked ok on Windows 7, but after a few months Diag refused to cooperate.

Currently, I have the cheaper interface in the litte version for sale, and I have a PCB board (with an optoisolator added) and a board with relays - the same interface without a housing.
This is the result of a long dispute with the seller at our majfrendów in the middle country.

1. Diagbox works on any Windows, I have it at home on Windows 10 64 bit, diagbox version 7.44

2. If you have the message "VCI is not connected" then:
If you have such a message drawn car = connect the interface to the car's ODB socket.
However, if you only have this inscription in the middle of the screen, you need to replace the interface firmware with another, preferably newer one. You can do this using the PSA interface checker program, you can find it easily on the net.
For my part, I recommend the Diagbox version from scarymistake and max to 7.44 or 7.58, unless you have a car from 2020. Scarymistake adds all the necessary files and firmware in the installation package.
Good luck

I also have the same problem. I connect the USB interface, the green LED lights up and then goes out. The diagbox displays connect VCI. I have Windows 7 and it worked before. Something happened to my connection once (I don't remember what it was about), I reinstalled Diagbox and it worked. Today I turn it on and it doesn't connect. Did your friend solve the problem? because he doesn't write anything.



I bought a second Lexia interface and it works. So that one just died

I have diagbox 9.146 running on Windows 11 without problem

Hello,
I have Diagbox version 9.91. A year ago, I was connecting to the car using it, and today I wanted to, but it does not automatically read the VIN number. Entering it manually does nothing because the interface does not connect to the calculators. From what I understand, is the interface broken? Additionally, about 2 years ago, I was connected via PP2000.
Is there any way out of this situation, or is there a new interface to buy? Have any of you solved it?

T5 wrote:

As far as I know, this hardware only works on Windows XP.

Depends on the "Chinese", I successfully use Diagbox with Chinese in Peugeot 207, 308. The problem with Windows 10 is only with older vehicles that require PeugeotPlanet / Lexia.

To the author: When you get the package (plate and interface) from a Chinese, the manual mentions a categorical ban on connecting to the Internet. Well... Diagbox, after detecting an Internet connection, checks the interface numbers, detects the clone and blocks it - as a result we have a bricked interface. I made this mistake with the first piece, I argued with the majfrend for a week and he sent me another one, this time without the disc etc because I had a complete set in the dead interface - in exchange for changing the rating from 1 to 5. This time I took an old laptop, Windows XP , no internet, I didn't even try to connect - it's been running for a long time.

And here's probably the reason, so far I've used PP2000 on the old computer without the net, and the last connection was made on the new one with the diagbox, because I connected the newer car 🤬
Well, then it remains to buy a new cable, thanks for the info.

I installed on Windows 10 and had problems because it didn't want to start at all. I uninstalled, reinstalled, and the program itself started, but it started to pop up "no card responsible for communication with the vehicle," and when ignored and connected to the car "no connection with the VCI." I've been fiddling around with drivers and messing around, but everything was fine. I finally downloaded PSA Interface Checker and changed the active version from the slightly older 4.3.0 to 2.2.9, and to my surprise, everything started working.

My problem is this: I have DB 9.9 (something) and it works on two of my cars. I downloaded an older version 7.7 (something) and this one "does not see" the cable, it shows "VCI not connected".
Sure and working version, used by the person from whom I downloaded it.
Where is the error and how to fix it?
Contact with the person from whom I downloaded DB has broken off because the forum where we contacted each other does not work.

Maybe this will help some people. I had such a problem with Diagbox that the first run of the program (after Windows start) also caused a connectivity error. Shutting down and restarting the program then helped.
Additionally, it should be mentioned that when there was a need for another startup, it would not boot. Then restarting Windows and on the second run Diagbox worked.

And for me everything generally works, no messages, but when I do a global test, there is no dialogue everywhere. C4 Picasso 2007

Buddy, did you manage to solve this problem? The same thing appears at my place.

Apologies for reheating the potato, is there anything I can do about the bricked cable? When I start the PSA checker and click Active, nothing happens, INIT OK pops up. No options can be loaded either. I read about adding the two files to the PSA Checker directory, also nothing. Anyone had a similar issue? Now these interfaces are no longer bought so cheaply .

>>21356085 send good quality photos of both sides of the plate, I'll think about something.

@kamaz8 Ok, thank you for your response 😉 I'll rest a while from the bigotry and write.

It seems that my cable is also locked. So I'm plugging the S8E in to ask if it can be unlocked.

maciek91ck44 wrote:

It looks like my cable is also locked, so I join in asking if it can be unlocked.

.

Without rebooting the software, unplug from the USB, plug it in and try again.

Good morning,
I've run into a similar problem, whereas it has slightly different symptoms. The cable is probably a WiFi quinol too, SuperCAN sees it and shows that there is voltage from the OBD. In DiagBox it also has no problem seeing that it has the VCI connected. On the other hand, it doesn't automatically find the VIN and when I type it in from my finger, when the two apps to choose Diag and PP2000 show up, neither works. I can click on it as much as I want and still nothing opens. The patient is a Peugeot 307 ~ 2003 - is there anything that can be done about this?

Jahowski wrote:

Good afternoon,
I ran into a similar problem, while it has slightly different symptoms. The cable is probably a WiFi quinol too, SuperCAN sees it and shows that there is voltage from the OBD. In DiagBox it also has no problem seeing that it has the VCI connected. On the other hand, it doesn't automatically find the VIN and when I type it in from my finger, when the two apps to choose Diag and PP2000 show up, neither works. I can click on it as much as I want and still nothing opens. The patient is a Peugeot 307 ~ 2003.Is there anything that can be done about it?

.

It can be done, you need to replace it with something that has the correct circuit boards inside and reports in the device manager as ACTIA not CH343. Some dealers write that it will work for cars after 2006, some omit this inconvenient fact. In addition, the fact that the PP2000 does not open is the fault of putting an old software version on a 64-bit system.

This version will work:
.

This one won't:

Hello,
How can you tell if a diag is blocked? I've been struggling with this Chinese crap for a long time and I don't know if maybe I got a return copy that was blocked or what. When plugged into the PC the light flashes a few times and is on continuously, the message "device not recognised" in the device manager "unknown device".
I opened it and it looks normal, full chip.
Tested on Win 7, Win 10, different versions of diagbox.
I bought a new USB cable but no improvement.
Any suggestions on how to bite this?
I installed XP but it doesn't recognise the device either, so what? Dead for amen?
What to do with it next, solder something, or is it too much trouble?

Pavololo wrote:

how to tell if the diag is locked?

.
There is no such thing as "blocked"-there is only a blacklist of serial numbers, but even then it should report correctly in the device manager.

Pavololo wrote:

When connected to the PC, the light flashes a few times and is on continuously

.
This is standard behaviour when connected.

Pavololo wrote:

I have opened it and it looks normal, ful chip.
Tested on Win 7, Win 10, different versions of diagbox.
I bought a new USB cable but no improvement.
Any suggestions on how to bite this?
I installed XP but it doesn't recognise the device either, so what? Dead on amen?

.
Connect via USB hub.

Ok, thanks for the hint, I'll try it today.

>>21450550 Using the USB hub did not yield positive results.
Is this a physical fault or a firmware fault for example?
Many years back someone had a similar problem here on the forum, only that on his two laptops Diagbox worked and on two it didn't, and also "unknown device". In the end it is not known what caused it, because the topic died.
Is there a possibility that this is the fault of a particular laptop?

.
Is this particular component the culprit? I know no one is clairvoyant, but maybe there is an electronics person here. I found a video on YouTube as some Romanian spec shows that replacing this component fixed the issue.

Pavololo wrote:

Is this a physical fault or e.g. a firmware fault?
Many years back someone had a similar problem here on the forum, only that on him on two laptops diagbox worked and on two did not, and also "unknown device," ultimately it is not known what was the cause because the topic died.
Is there a possibility that this is the fault of a particular laptop?

.
I know of several cases where the interface "didn't like" the laptop- but using a hub took care of the issue.

Pavololo wrote:

Is this component the culprit? I know no one is clairvoyant, but maybe there is an electronics person here. I found a video on YouTube how some Romanian spec shows that replacing this component fixed the issue.

.
This is a Statis RAM bone, there is no guarantee that it is the culprit.

>>21451083 Well, nothing, the service remains. Greetings