Conseil d'achat

[mista]

pourrais tu me faire un print screen de ton interface checker stp avec ton interface connecter l as tu flasher avec le fichier de nlc ?
merci

[Walid25]

oui g entendu bcp de probleme de connection avec les c4 aurais tu essaye sur d autre vehicule ? mise a part la c4 picasso?

Slt Mista ;

J'ai flashé ma VCI avec le fichier de " nlc ", elle est désormais reconnue en Evolution dans le gestionnaire des périphériques; néanmoins, le problème est toujours d'actualité, pour avoir le coeur net, je vais tester mon interface sur une Peugeot dans les jours qui viennent et te tiens au courant.
Mais, je reste persuadé que c'est un problème " hardware ", il faut modifier certains composants de l'interface ( http://www.lesamisdudiag.com/diagbox...originale.html) et ( http://www.lesamisdudiag.com/diagbox...aleatoire.html ),

@+++

[mista]

ok e avant que tu la flashhh tu avait le meme souci je suppose ?
fais moi un print screen une fois de ton interface checker avec la vci connecte et active avec numero de reference je dois checker un truc

[Walid25]

Salut Mista,

J'ai tout désinstallé hier soir et un ami à modifier mon interface. Je réinstalle Diagbox, je fais un test et te tiens au courant.
Le test sur une Peugeot est négatif aussi, dialogue impossible avec les calculateurs.

[Simple]

@Walid25,
Can you take photos of the boards inside the VCI to see the components?
Is your VCI Full Chip? and is the 10K resistor on the back of one board missing?

[Walid25]

Hello Simple ;


Here are pictures of my VCI, it is clear that lack the 10K resistor .

[Walid25]

ok e avant que tu la flashhh tu avait le meme souci je suppose ?
fais moi un print screen une fois de ton interface checker avec la vci connecte et active avec numero de reference je dois checker un truc

Slt Mista ;

Effectivement, même avant le flash de " nlc ", je n'avais aucun dialogue avec les calculateurs de mon C4, j'ai testé sur une Peugeot 407, idem, aucun dialogue avec les calculateurs.
Actuellement, l'interface est sous la version 4.3.0, je vais mettre la version 4.2.4db et faire un test et te tiens au courant, mais je reste persuadé que c'est un problème " hardware ", déjà sur ma VCI, il manque la résistance 10K dont parle Simple dans sa réponse plus bas.

[Walid25]

Slt Mista ;

J'ai mis le firmware 4.2.4db pour tester et toujours pareil, absence de dialogue, en ce moment je suis sous DB 7.02, je vais essayer de faire les mise à jour jusqu'à la version 7.57 et faire un autre test.

[Simple]

@walid,
From what you have described, it looks like it is hardware issue... but it may as well be software issue.. lets clear the software issue first..
Lets work this one out.... I will give you links to download:
1- en_windows_xp_professional_sp3_x86_cd_x14-80428.iso
2- VMware-player-12.0.0-2985596.exe
3- DiagBox suite 7.01 - 7.76
I will send you a private mail
Sloan,

[Simple]

This is a manual I wrote last year, Please read it...

For DiagBox 7.xx, you can use your name or any other name, but if you have had the previous failures on the same Windows XP installation, I would strongly advise you to use "DBCleaner v101a" making sure you run it as Administrator.

If your notebook currently runs Windows XP 32 bit, you can install Evolution XS (Lexia) applications directly on it. However, many of the currently available notebooks are unlikely to come with Windows XP; in which case the best way would be to shrink your last partition by about 40 GB and create a new partition to install windows XP 32 bit on it, then the Lexia application. Nevertheless, you can run Windows XP (and many other operating systems) within a Virtual Machine installed on your current notebook’s OS; luckily, they are mostly free and readily available. I have tried both methodologies and both work well, I have preference to the Virtual Machine because I still have access to my other operating system (in fact I am writing this whilst performing another test). One can also change the amount of memory (RAM) or computation power (CPU) as need be, you can clone it, and if you do not like it, you can delete it.

Let’s Start:

Ensure that all files and folders names do NOT include spaces or funny characters, example: “Folder_1or_file_5” and not “Folder 1 or file 5”. If possible, convert all your media to ISO format ensuring the media is laid at the root directory and NOT inside another folder, Example: if you mount the DVD ISO it should be “G:\installation_material” and NOT “G:\Lexia 3\Diagbox\installation material” (where G is the arbitrary DVD drive letter).
1- Install VirtualBox, the Extensions and Guest Additions, ensuring the following:
a) The Hard Drive controller must be IDE.
b) Create a preferably fixed hard drive more than 24GB. Dynamic also works.
c) Connect the Windows ISO through the Settings -> Storage -> Optical Drive.

2- Install a clean Windows XP Pro SP3 and activate it and install the following tools:
a) All necessary drivers.
b) Setup a network adaptor
c) Install Mozilla Firefox
d) Java 7
e) Winrar or 7zip
f) Virtual Clonedrive (not needed for VirtualBox)

3- Connect the Lexia USB interface to the computer so that VirtualBox identifies it:
1. Click on VirtualBox Settings, USB, Add a new USB filter and choose the code representing Lexia interface.
2. Leave the Lexia interface connected throughout the whole installation process, if Windows asks to look for drivers then just cancel for now.
4. Disconnect the network cable.
5. Create a blank file named version.txt in C:\ i.e “C:\version.txt” (This step may not be necessary with newer DiagBox versions).
6. Mount the DiagBox 7.02 ISO and run the setup, go through the process. At some stage, "new hardware found" window will appear, do not choose to search automatically for drivers, you may cancel it or just manually select the driver that should now be available.
7. Once done, start DiagBox and when prompted for activation, choose the "manual activation" option, fill-in information as per the provided instructions, usually (Customer Code, Address, Post Code and Car Phone) you can enter any characters or numbers.
8. Start DiagBox again it will run the update for 7.02.
9. Install the update package/s – I prefer the 7.xx to 7.57. Please note after installing the update you will need to reboot then run DiagBox for the update to be fully installed. At some stage, the drivers may install (if not already installed) where you will get "New hardware found" wizard again.
10. DiagBox (the latest version installed) is now operational.
Connect the USB interface to the OBD-II port on your car, turn on the ignition, and in DiagBox choose your car, insert your RPO and work away.

[Simple]

Please update the message about your current setup:
1- What is your Computer Hardware and the size of RAM and Hard Disk ?
2- What is your main Windows os version and is it x64 or x86 ?
3- What Virtual Machine is used and Which Windows is installed on it ?
4- Do you use DBCleaner v101 to completely uninstall DiagBox before re-installing again ?
5- Do you see the VCI with the proper drivers installed in the Device Manager of Windows 64bit or Windows 32bit inside the Virtual Machine ?

I think I have an idea of what your problem is!!

[Walid25]

Hello Simple ;

The interface is recognized by PSA Peugeot Interface Checker as USB Board Com Evolution Driver (Multi-instance) in the Device Manager, she was recognized front (UDMF).
The firmware version is 4.3.0, Diagbox is installed on a laptop with Windows 7 Ultimate 32-bit.
When I run a comprehensive test either by diagbox or by Lexia (C4 Grand Picasso on 2007) or on a PP2000 Peugeot 407, there is no dialogue with the computers.
I changed the firmware of the IVC in 4.2.4 DB and blocked its update, when I do a test, the VCI is not connected at all, so I went back to the 4.3.0 firmware, recognized VCI but still lack of dialogue with computers, I do control the interface by a friend electronics, welds and connections are OK, the cables also.
I am currently in diagbox 7.02, I have already tested with the versions 7.44 and 7.57 but with no results, I uninstalled and re diagbox several times, always with DBCleaner uninstaller.

P.S:
Whenever I do a test, the VIN is never automatically recognized by the VCI, I have to go manually, again, I saw that there is a LED on the connector (16-pin socket) that going on ODB, the famous LED never lights.

[Simple]

Can you show clear photos of the 4 sides of the boards you have, please.
May be devildante007 can participate in solving this problem.

[Walid25]

Hello Simple,

I have already send a private message to Devildante, but i have not any answer. I add the famous 10K resistor, but i have not any good results.

[Simple]

Review these photos to see if your device is missing a component, find one that identical to your..

Regrettably, your device is missing the base for the TDK chip, I don't think it could even become a full chip.

You need someone with an oscilloscope to check the signals ad compare them to the results in devildante07 post.

http://www.lesamisdudiag.com/diagbox/43058-photos-de-vos-interfaces.html#post67121

http://www.lesamisdudiag.com/diagbox/43058-photos-de-vos-interfaces.html#post70161

http://www.lesamisdudiag.com/diagbox/43058-photos-de-vos-interfaces.html#post64185

http://www.lesamisdudiag.com/diagbox/43058-photos-de-vos-interfaces.html#post64670