( 10:44 PM)Simple Wrote: Why do you install 7.7 or 7.11 or 7.40, when you can install 7.xx-7.57 in one go??, please search for 7.xx-7.57 (one update file). The sequence is mentioned here: Simple. I was not aware that there was a 7.xx-7.57 file. I downloaded the software and updates from the link in the first post of this thread. The update sequence in that download and the torrent file is 7.01-7.02-7.06-7.11-7.16-7.24-7.40-7.58-7.62-7.66.
With no mention of 7.xx-7.57 ( I'm Still looking for it) David Rossi46, proud to be a member of GarageForum since Mar 2015. Difference between ucs and wcs.
I've tested a few cars with this latest version, everything works great, I can even read ABS with updated interface firmware (4.3.2), before it didn't read ABS and even BSI on some cars. Telecoding works as well, it didn't with the old software and interface I had. I've tried ECU updating, but it asks for network connection. Aren't the ECU firmwares already in the program? Or does it only ask for connection to validate the account? Basically, what I wanted to ask, is there any way of ECU updating in Lexia/pp2000 with this version or does it only work with older v6 diagbox?
I need to update ECU on a 2001 Pug 206 S16 and a 2010 Citroen C4. Cheers Atrax, proud to be a member of GarageForum since Nov 2017. ( 03:26 PM)Atrax Wrote: I've tested a few cars with this latest version, everything works great, I can even read ABS with updated interface firmware (4.3.2), before it didn't read ABS and even BSI on some cars. Telecoding works as well, it didn't with the old software and interface I had. I've tried ECU updating, but it asks for network connection.
Aren't the ECU firmwares already in the program? Or does it only ask for connection to validate the account? Basically, what I wanted to ask, is there any way of ECU updating in Lexia/pp2000 with this version or does it only work with older v6 diagbox? I need to update ECU on a 2001 Pug 206 S16 and a 2010 Citroen C4. Cheers ( 03:26 PM)Atrax Wrote: You can't downloading a update for ecu with diagbox,for me not working. But with lexia you cant. Kyturelm, proud to be a member of GarageForum since Apr 2014.
I have tried now three times to install this software. I am running VM Virtualbox with Windows XP with SP3 installed but about v7.58 or so I get Microsoft message that psaAgent.exe has encounterd a problem and needs to close. I have spent a considerable time with this installation and updates as it takes ages for diagbox to shut down. I have used the tool to remove all traces of diagbox and rebooted after every installation. Any idea what could be going wrong? Thanks David Rossi46, proud to be a member of GarageForum since Mar 2015.
Ok thanks for that but it does not appear to have worked. All looks fine, but ensure your CMD is run as Administrator and the text is case sensitive. You can view the 'Windows XP.vbox' file and check if the line you entered has been included under ExtraData exactly as shown below. The SystemSerial can be any text, I cut it short. If not, you can enter the value manually. If it does not happen, then you may have a problem with the installation, like skipping an update or some corruption. Simple, proud to be a member of GarageForum since Dec 2014.
Copied from Windows XP.VBox (First Character Edited) (ExtraDataItem name='VBoxInternal/Devices/pcbios/0/config/DmiSystemSerial' value='F3N0CV38496013E'/ Copied from Powershell Bios Query SMBIOSBIOSVersion: X555LA.309 Manufacturer: American Megatrends Inc. Name: X555LA.309 SerialNumber: F3N0CV38496013E Version: ASUS - 1072009 I'm fairly sure I have not missed the correct update sequence. I has happened 4 times now.
It seems to occur at Update 7.58 Where to now? Thanks David Rossi46, proud to be a member of GarageForum since Mar 2015.
I assume you have Windows XP 32bit, VirtualBox with Extension Pack and Guest Additions installed, a network card and USB 2.0 device are enabled. You also have Virtualisation enabled in the ASUS Laptop BIOS. You may make a change to the SystemSerial 'F3N0CV38496013E', in case it is being used somewhere else (unlikely, but a precaution). If you have installed any Java Run Time, please uninstall it/them, DiagBox automatically installs Java 6.xx If all the above is done and you are on DiagBox v7.58, reinstal update 7.58 again and run DiagBox as Administrator (you may have to download 7.58 again from another source!!, Check here: ).
Simple, proud to be a member of GarageForum since Dec 2014. ( 06:21 PM)Simple Wrote: I assume you have Windows XP 32bit, VirtualBox with Extension Pack and Guest Additions installed, a network card and USB 2.0 device are enabled. You also have Virtualisation enabled in the ASUS Laptop BIOS. You may make a change to the SystemSerial 'F3N0CV38496013E', in case it is being used somewhere else (unlikely, but a precaution). If you have installed any Java Run Time, please uninstall it/them, DiagBox automatically installs Java 6.xx If all the above is done and you are on DiagBox v7.58, reinstal update 7.58 again and run DiagBox as Administrator (you may have to download 7.58 again from another source!!, Check here: ). Yes I have checked all that.
font=Tahoma, Verdana, Arial, sans-serif /font I cannot reinstall v7.58. I downloaded the version in the link you gave but it will not allow you to do a reinstall.
It seems the process of installation checks to see which version you have installed to make sure that you are applying the correct update. I assume from this that it is not possible to update in the wrong sequence. I have re-installed to version 7.40 to see if I can use that in the meantime. Is there a list somewhere that gives the changes that are applied with each Update? (I did find a link somewhere but the link was dead.) In particular what vehicles are covered with update v7.40? My present task is trying to see if I can enable Cruise Control on a 2014 Citroen Relay Enterprise 130 (2006-2014 model) With regard to changing the SystemSerial is there a format that needs to be used?
Could I enter zero for example? Seems odd to make a point of entering some information and then using the wrong details. (Don't try to explain.
It's all beyond me) I have tried to Install the software on my older Windows XP notebook but when I get to update v7.7 - v7.11 I get an error 'Impossible de creer sim.exe' so not having much luck there either. I had hoped that even though it is a lot slower there would be less problems as it is a proper Windows XP installation rather than a Virtual Installation. Thanks for your help David Rossi46, proud to be a member of GarageForum since Mar 2015.
If you have clone with Lexia/PP2000/Diagbox software is not compatible with diagbox version greater than 7.02. You probably know that we must re-flash the MCU internal EEPROM and the SPI that contains no problematic series. Here is the DIY tutorial on how to reflash your lexia3. So far the only solution was to make a programming interface to reflash the MCU and desoldering SPI EEPROM to be able to reprogram on an EEPROM programmer. You could do it yourself, but it is not accessible to everyone, and send it to someone who updates your interface to cost money.
As electronics and have already developed on the MCU used in this interface (MB90F546), I developed a special program which is injected into the interface through USB with PSA Interface Checker and allows the upgrade for it to be recognized usb com Evolution board and also change the serial number for a No. Non blacklisted series. The interface then becomes compatible with the latest versions of diagbox 8) If you are confronted with the version on your clamping interface and want the ‘upgrade, the procedure is as follows: – You made me demand by private message, giving me your full personal details: name, address, and ideally the email address provided by your ISP. This personal information I care little, but I need to put them in the file that I send you by email. The customization file with your personal information is used only to deter move the file to someone else, to avoid the spread of wild file on the Internet and prevent profiteers steal my work. 1) Once I have received your application and personal information, I prepare your custom upgrade file and I send it to you by email with the explanations to make updating your interface. 2) Upon receiving my file ‘upgrade in a few mouse clicks, your interface will be updated and compatible with diagbox 7.xx! You probably read right or left this method update by USB is not good. It’s hype. Once the interface update by yourself with my method, it contains exactly the same firmware (4.3.0 + bootloader Board Com Evolution) by making hardware update (disassembly, reprogramming MCU, desoldering / reprogramming / ressoudage EEPROM). Regarding the serial number, I provided you a No random series that is different for everyone.
Psa Diagbox Serial Numbers
Psa Diagbox Serial Number
This is much better than no single series for everyone, even if existing, for if one day the manufacturer decides to blacklist the serial number, then all these interfaces are found inconsistent with the future versions diagbox!! And at worst, if one day the serial number that I provided you can no longer work correctly with future versions of diagbox, and although it will be enough to remake me a request and I will provide a new update file to change by the usb serial number in eeprom, always without removing the interface Ceci est du support technique du site Web.