Merged Lexia & Diagbox threads

[renagade]

Hi ,well have just install a fresh copy of win 7 32bit and just finishing all the updates then I am going to take a deep breath and start installing the Lexia. Did you say that I have to install Diagbox first and then Lexia.??

[GiveMeABreak]

No, both the Lexia and Peugeot Planet programmes are installed as part of the main Diagbox programme. I'm assuming you have Diagbox 7? Run the programme in XP Service Pack 3 compatibility mode and run as Administrator (right click the install file, choose properties and compatibility tab). If you get stuck send me a PM and I'll dial in if you need a hand.

[Peugeoholic]

Hi Thanks for that info.I have been offered a 32 bit install of win 7 by the shop that put 64 bit win 7 so I think this would be the way to go. am I doing the right thing. Is this lexia worth all this trouble?????
Thanks again

I had diagbox running on a 64bit Win7 Pro laptop by creating a WinXP mode virtual machine and installing and runing diagbox inside that.
The 'had' is because that laptop is now upgraded to Win10 and I have yet to try installing XPmode (http://www.download3k.com/articles/How- ... er-V-00770)

[GiveMeABreak]

I had diagbox running on a 64bit Win7 Pro laptop by creating a WinXP mode virtual machine and installing and runing diagbox inside that.
The 'had' is because that laptop is now upgraded to Win10 and I have yet to try installing XPmode (http://www.download3k.com/articles/How- ... er-V-00770)

I think you may have problems with that - certainly with Hyper V under Windows 10 - as it won't install drivers like under a native OS. I use Hyper V under Windows 10 (not for Diagbox) and it won't even detect some USB flash drives or other USB devices, making the drives unavailable to be seen on the system. So there may be little chance that it is going to detect and allow the Evolution Drivers to instal, which are lneeded for the Actia Hardware. Also, the system overheads in running a VM on a laptop are likely to make it so slow as to be unusable...

I would recommend that all you need to do is get Windows 7 32 Bit installed on your laptop and you'll be fine and able to install Diagbox directly - no need to faff with a VM - I think you are just creating more work for yourself here

[Mandrake]

It should be pointed out that the 32 bit version of windows can only address 4GB of ram, and typically no more than 3GB of that will be available for applications. So if the laptop has 4GB or more ram then some of it will be wasted...

The ideal Diagbox/Lexia machine is one that has around 2 to 4GB of ram - enough ram to run Windows 7 well, (less than 2GB is not recommended) but not so much that you are losing the use of a significant chunk of ram by running the 32 bit version of windows, especially if you were also using the Laptop for other purposes.

[RichardW]

I'm running Diagbox inside a Vista virtual machine using virtual box on a Win 10 machine - it runs fine (the lappy is Core I5 with 8Gb ram). It's a slight faff to set up the pass through for the USB device, but it can be done. It was crocked by the Win10 anniversary update, but I managed to get it going again. The advantage to this set up is you can save the virtual machine whilst it's running, so it only takes a few seconds to start and diagbox and service box are already loaded - which otherwise takes an appreciable amount of time.

[GiveMeABreak]

Yes the win 10 anniversary has stuffed a lot of my previous customised settings - gradually getting them back now... I have a separate laptop just for Diagbox, but run the VM on the main rig for older software. I found is was a lot less costly to use an older laptop for the diagnostics and service doc software - keeps those glitchy programmes off the main system.

[kitchD6C]

I'm having all sorts of fun and games trying to install Diagbox on an old laptop (32bit XP). It's one of the £60 ebay ones - am I wasting my time? It's failed to install once already (programme etc on there, but wouldn't communicate with car).

[GiveMeABreak]

XP is really no longer supported as you probably know. You can safely install it on Windows 7 - if you have Windows 7 install media, just buy a licence key from a disposed laptop from the bay. As for your communications issues - this will depend on the car you are trying to communicate with, the Lexia hardware revision and firmware of the software and of course ensuring it is installed and activated properly.

[kitchD6C]

Ok, so had a more serious go at this, this afternoon.

The laptop is an old IBM Thinkpad running XP. I don't have anything with Windows 7 on it, only Windows 10.

The version of Diagbox V7 came from eBay. I think it's a Russian-translated copy! The instructions are about as clear as mud, but so far I've worked out you can't have the laptop connected to the internet at all, which seems daft as the program says it needs the internet.

Anyway, originally this software was installed onto the laptop by my colleague. He managed to get it working and communicating with the car, but it couldn't actually diagnose and faults or clear any codes. For some reason, I decided to try and remove this copy first, and just took his word it didn't work. I should probably have tried it myself.

Tried removing and reinstalling today. The only option is to install using the Daemon Lite program, and in doing this it detects the previous version and says it needs to remove that first before continuing. Fair enough. It then took nearly an hour to remove this, and died halfway through. Eventually it completed the removal, and declared the installation successful. I tried hooking it up to the car, but it wasn't connecting properly. It read the ID of the car etc., but the fault-finding part wasn't working.
I tried to update it as I realised the CD came with the latest updates, but didn't spot the bit saying I needed to move a file out of the installation folder before updating, and consequently updated with all the stuff still in place. Now, when I try to run Diagbox, it says "If you bought this on ebay, you've been ROBBED" or something like that.

So at the moment, I'm trying to remove it and do it again, only this time following the muddled broken English instructions. It takes FOREVER to do anything when installing, so I'll see how far my patience goes before writing the idea off! So far, it's done the same crash midway through the uninstall as it did before, and is currently finishing uninstalling and the installation of the new software. It'll be going until 11pm or so I expect.

[GiveMeABreak]

Ok, so had a more serious go at this, this afternoon.

The laptop is an old IBM Thinkpad running XP. I don't have anything with Windows 7 on it, only Windows 10.
OK stick with XP - your older hardware might not support Windows 10 and Diagbox is funny about Windows 10

The version of Diagbox V7 came from eBay. I think it's a Russian-translated copy! The instructions are about as clear as mud, but so far I've worked out you can't have the laptop connected to the internet at all, which seems daft as the program says it needs the internet.
You must have all the drivers installed on your Laptop and the network adapter should be activated even if not actually connected to the Internet for Activation

Anyway, originally this software was installed onto the laptop by my colleague. He managed to get it working and communicating with the car, but it couldn't actually diagnose and faults or clear any codes. For some reason, I decided to try and remove this copy first, and just took his word it didn't work. I should probably have tried it myself.
Previous versions will not fully install just by using Add/Remove Programmes. You will need the Diagbox Uninstaller Programme. (PM me if you don't have this).

Tried removing and reinstalling today. The only option is to install using the Daemon Lite program, and in doing this it detects the previous version and says it needs to remove that first before continuing. Fair enough. It then took nearly an hour to remove this, and died halfway through. Eventually it completed the removal, and declared the installation successful. I tried hooking it up to the car, but it wasn't connecting properly. It read the ID of the car etc., but the fault-finding part wasn't working.
See last point - programme not properly uninstalled and you can't install over an old copy - it will just not work.

I tried to update it as I realised the CD came with the latest updates, but didn't spot the bit saying I needed to move a file out of the installation folder before updating, and consequently updated with all the stuff still in place. Now, when I try to run Diagbox, it says "If you bought this on ebay, you've been ROBBED" or something like that.
The 'You've been robbed' is fine. What is happening is that when you close and restart Diagbox it applies the patch (7.0 to 7.01) and this message appears - it just means the software is freely available and if you've paid for it from 'The Bay of Evil' or elsewhere, then literally 'You've been Robbed!

So at the moment, I'm trying to remove it and do it again, only this time following the muddled broken English instructions. It takes FOREVER to do anything when installing, so I'll see how far my patience goes before writing the idea off! So far, it's done the same crash midway through the uninstall as it did before, and is currently finishing uninstalling and the installation of the new software. It'll be going until 11pm or so I expect.

There are too many things to repeat here that have already been mentioned in this huge thread - so you can be forgiven if you can't find the specifics as it is a massive topic!

Essentially -

• Thoroughly uninstall Diagbox from Add / Remove Programmes.
• Restart Laptop. Run Diagbox Cleaner, ensuring all relevant directories are removed. Then restart the Laptop again and run the Diagbox Cleaner software AGAIN to ensure any remnants are fully removed as some services can't be removed until the system has restarted.
• Ensure laptop is patched and updated as best you can and that ALL hardware drivers are installed and working.
• Because this is hit and miss and may take a few attempts - create a Windows SYSTEM RESTORE point before you start the new installation and name it 'Prior to Diagbox Install' or similar, so you can always restore the system back to this state if needed.
• Ensure the Network adapter is working, but don't connect to the internet.
• Use Demon or other software to Mount the installation media.
• Run the installation as an Administrator
• When it asks to activate choose the option for MANUAL activation and validate.
• Fill in the relevant Customer code and relevant password that you were given for this installation when requested.
• Allow installation to continue and fill in Customer Info required fields when asked and Validate - it should now be activated.
• Allow any requests for Firewall Exceptions.
• Close Diagbox down immediately - do not attempt to go into any menus.
• Now restart Diagbox - it will start applying the patch automatically - and you will see the robbed screen - no problem.
• Restart your PC and open Diagbox - it should be version 7.01 and should be activated.
• If Activated, copy the APPDIAG file from the C:\AWROOT\BIN\FI location to a folder on the Desktop or somewhere safe.
• You should plug in your Lexia Unit into the USB port and wait until it confirms the driver has been installed. Remove and plug the cable into each USB port in turn on the laptop and wait again until the driver is installed.
  
  Now go and try it out - but keep your internet disconnected. If you have an older Revision B unit - the serial number may be blocked, so it is important to keep the internet deactivated - as if it will deactivate the software if it gets through to the PSA servers.
  
  Good Luck.

[kitchD6C]

Thanks for the advice. I managed to get it working (despite thinking I had Windows XP, when I actually had Windows 7 - DOH!)

Communicating with the car now (Pug 407) with mixed results. I believe it has a dodgy comms unit fitted, and I'm getting airbag and ESP warning lights, preventing an MoT pass. Found a used one off a C5 on eBay so have ordered that, will fit it and scan again, see what happens. I'm guessing I'll need to calibrate it to the car etc?

It is connecting though, and I've so far been able to do things like turn the parking sensors off at least!

[GiveMeABreak]

Thanks for the advice. I managed to get it working (despite thinking I had Windows XP, when I actually had Windows 7 - DOH!)

Communicating with the car now (Pug 407) with mixed results. I believe it has a dodgy comms unit fitted, and I'm getting airbag and ESP warning lights, preventing an MoT pass. Found a used one off a C5 on eBay so have ordered that, will fit it and scan again, see what happens. I'm guessing I'll need to calibrate it to the car etc?
It is connecting though, and I've so far been able to do things like turn the parking sensors off at least!

Great - I'm really glad your Lexia is working now - it made typing that lot out again above worthwhile!
If you are referring to the Comms 200*... unit behind the steering wheel - it will depend. I had a chat with my Citroen Service Manager, as we had issues on the C3 with our auto headlights activating and switching off, which soon started playing up even when switched to manual mode. They got progressively worse and as comms unit errors don't easily show up ion the Lexia if at all - I was going to buy a new unit and fit it myself. My only concern was the software matching up with the vehicle, so on speaking with the Service Manager, he said that it is important that the software version in the comms unit is correct for the car it is going onto, otherwise you may have other issues. I thought about it and for the additional cost, decided to get Citroen to do it. So I guess the sensible thing to do would to try and get one from the same vehicle and model as your car if possible. At the end of the day you could always try and return it if it causes issues or starts playing up. I would always try and match it with a compatible donor - one that has the cruise, auto wipers, auto lights etc as far as possible - according the same spec of your car.

Regarding the Airbag and ESP errors - I've seen this error fixed by just taking off the airbag connectors (after disconnecting the battery and waiting for 10-15 minutes of course) and then reconnecting them after a gentle clean. - The chap was looking to clean up the contacts for the indicator PCB contacts and cured this in the process. Not saying yours will be the same error, but worth a mention. The other issue can be the connector under the carpet on the Passenger side. A good clean up of this can also be a cure - but observe safety precautions too.

[kitchD6C]

Yes, the Comms 2000 unit. I've used the Peugeot software to try and find the correct part number, and found a C5 unit on eBay with the identical number, and it was even manufactured within 3 months of the original (which I guess means it'll last 3 more months!) So the features/stalks etc are all identical.

I don't want to splash out on a brand new one yet, as I don't know if the rest of the car is ok. But if I fit this thing and manage to get it through the MoT, then I'd consider buying a new one at £300 or so later on.

I know the one in it is no good, as I know the guy who fitted it. He said he had a feeling it had been spun round while disconnected, and when he fitted it, he tried to turn round in the yard and there was a cracking sound!

Then I've just got to figure out the DPF rubbish that's going on!

[GiveMeABreak]

Right in that case your abs esp error will very likely be the steering wheel angle sensor out of kilter. I did this when changing a steering wheel on my older C5 years ago. It is important that you don't let the cassette move round when tackling any job arround that area. It should be marked with an arrow. You will need the Lexia to set it back. There are a few videos on the tube that show this IIRC. Best of luck with the job.