My DiagBox/PP2000 setup experience

Talk about the 406's electrical system, what wires do what, how to add extra functionality, etc.

Moderator: Moderators

Post Reply
ZilogJones
2.0 16v
Posts: 137
Joined: Sun Mar 27, 2011 12:30 am
Location: Ireland

My DiagBox/PP2000 setup experience

Post by ZilogJones » Thu Feb 20, 2014 1:31 am

There's an awful lot of conflicting information out there regarding PP2000/Lexia, DiagBox and these "clone" diagnostic devices (PSA XS Evolution).

It took me three days but I got there in the end. I couldn't get the older standalone PP2000 or Lexia packages to work properly so gave up on them and tried DiagBox again after a previous failed attempt and it works great now.

Here's what I did anyway:
  1. Did a clean install of Windows XP SP3 on my old laptop (Dell Latitude D630) with all updates (used the XPSP3_QFE_UpdatePack with nLite - much easier than installing hundreds of updates manually afterwards!), with no network connection, no anti-virus and no other software installed. Check all the system's drivers are installed.
  2. Installed 7-Zip (archive tool, like WinRAR but totally free and not "nagware"), Virtual CloneDrive (like DaemonTools Lite but doesn't try to install toolbars and other shite), and SumatraPDF (free PDF reader, much more lightweight than Adobe and doesn't try to check for online updates or anything)
  3. Connect the USB interface, and leave it connected for the whole installation process - my first installation was a complete failure (DiagBox would not detect the device at all) and I suspect it was because I did not do this. If Windows asks to look for drivers then just cancel that for now.
  4. Mount the DiagBox 7.02 ISO and run the setup. At some stage a "new hardware found" window will appear - do not choose to search automatically for drivers, just manually select the driver that should now be available (forget the name exactly but there should only be one choice if it's a fresh install).
  5. Once that's finished, start DiagBox and when prompted for activation choose the "manual activation" option, put in whatever was provided in the instructions for the "customer code" and it should sort itself out. It'll then install more stuff.
  6. Not certain but I think after this stage if you start DiagBox again it'll run the update for 7.02.
  7. Install the other update packages - unfortunately there's six packages to go through to get from 7.02 to 7.33 but they should work. Please note after installing each update you'll need to reboot then run DiagBox for the update to be fully installed. At some stage the drivers will change and you'll get the "New hardware found" wizard again - choose the driver manually as before (the name will be different).
  8. You should have a working DiagBox 7.33 now. Connect the USB interface to the OBD-II port on your car, turn on the ignition, and in DiagBox choose the appropriate car (note: "406R" = D9 or "restyling" in Service Box terminology). You may be prompted for VIN confirmation then you'll be prompted for the DAM - this is the 5-digit build code number, on the sticker in the driver's door pillar on D9's (you can also get it from Service Box)
  9. You're then prompted to select either DiagTool or Peugeot Planet 2000. I'm not sure what DiagTool does yet (wouldn't work for me), but PP2000 is where you can check/clear fault codes, get live readouts, run tests, and configure things.
  10. If you get connectivity issues, try removing the USB cable and inserting it again.


One issue I had was was DiagBox activation failed at first ("Error 0" or something vague like that) - this seemed to be because I had all network interfaces disabled on my laptop. I enabled one of them again (but left disconnected), rebooted, restarted DiagBox and activation worked fine. So if you're trying with a VM I'd imagine you'd need to create at least one virtual network interface, even if you leave it disconnected.

I've seen some people saying these clone devices with a serial no. ending with "B/" will not work with anything newer than DiagBox 5, or they won't work with Siemens ECUs or 307's (I suspect also because of Siemens ECUs) but it's working for me :)
My USB interface has firmware version 4.3.0 and a serial no. ending with "B/". I'm not sure if that's what it came with, or if the DiagBox installation upgraded this at some stage. I didn't run any manual firmware update.

Some questions:
  • Anyone know what DiagTool does, or if it works with these devices or the 406?
  • In PP2000 I tried saving some live engine ECU data, and also the BSI full configuration output. A green dot in the bottom-right turned red each time I tried saving something - but where does it save this data and how do I access this? It would be nice to see some graphs and stuff. I also did the save when exiting PP2000.
2002 2.0 HDi 90 Rapier saloon (for sale)

ZilogJones
2.0 16v
Posts: 137
Joined: Sun Mar 27, 2011 12:30 am
Location: Ireland

Re: My DiagBox/PP2000 setup experience

Post by ZilogJones » Sat Feb 22, 2014 1:12 am

I eventually found where PP2000 is logging things if anyone's interested:

When you go to exit PP2000 it gives you a number of slots (10?) to save to before quitting. If you choose one of these it will save stuff to:
C:\APP\OUTILREP\TRACE\MEMO\

There are XML files (e.g. traces1.xml) which I don't really know how to view in a human-readable way, but there are also ZIP files with both the XML and a TXT version (e.g. traceTXT.TXT) which is somewhat human-readable. It will show a log of absolutely everything you did in PP2000, every menu you went through and every input you put in. However, if you're looking at live data it will also record this, including every time the screen is refereshed. Here's a sample of the file when I was looking at the injection information:

Code: Select all

INJECTION INFORMATION 

Engine speed: 192  Rpm
Camshaft/crankshaft synchronisation: Yes 
Reference fuel pressure : 298  Bar(s) 
Measured fuel pressure: 282  Bar(s) 
Pressure regulator OCR: 23  %
Flow regulator OCR: 36  %
Measured injected flow: 34.75  Mg/impulse
Cylinder injector 1 flow correction: 100.39  %
Cylinder injector 3 flow correction: 100.39  %
Cylinder injector 4 flow correction: 100.39  %
Cylinder injector 2 flow correction: 100.39  %
Injector voltage : 73  Volt(s)
Measured air flow: 294  Mg/impulse
Air flow setting: 294  Mg/impulse
EGR valve electrovalve OCR: 10  %
EGR throttle electrovalve OCR: 10  %
Pre-injection advance: 14 °
Main injection advance: 1 °
Injection time: 1.66  Ms (milliseconds)
Coolant temperature: 10  Deg. C
Fuel temperature : 10  Deg. C
Corrected air temperature: 11  Deg. C
Atmospheric pressure: 1000  Mbars
Frame :
    Q8E07C6    R011011000561C60660805E323332C800000000007F00
    Q8E07C8    R011016000561C80624778B7732727FBF0080808080123A5B001919
    Q8E07CC    R01100F000561CC080A7D32262736360871347E12

===========================================================
INJECTION INFORMATION 

Engine speed: 256  Rpm
Camshaft/crankshaft synchronisation: Yes 
Reference fuel pressure : 298  Bar(s) 
Measured fuel pressure: 306  Bar(s) 
Pressure regulator OCR: 22  %
Flow regulator OCR: 35  %
Measured injected flow: 34.75  Mg/impulse
Cylinder injector 1 flow correction: 100.39  %
Cylinder injector 3 flow correction: 100.39  %
Cylinder injector 4 flow correction: 100.39  %
Cylinder injector 2 flow correction: 100.39  %
Injector voltage : 74  Volt(s)
Measured air flow: 294  Mg/impulse
Air flow setting: 294  Mg/impulse
EGR valve electrovalve OCR: 10  %
EGR throttle electrovalve OCR: 10  %
Pre-injection advance: 14 °
Main injection advance: 1 °
Injection time: 1.66  Ms (milliseconds)
Coolant temperature: 10  Deg. C
Fuel temperature : 10  Deg. C
Corrected air temperature: 11  Deg. C
Atmospheric pressure: 1000  Mbars
Frame :
    Q8E07C6    R011011000561C60860805F323332C800000000007E00
    Q8E07C8    R011016000561C80627778B7735727FC30080808080123859001919
    Q8E07CC    R01100F000561CC060A8032262736360872347F12
And goes on like this for quite a while. I left this running for about 15 minutes or so, so in this file there are about 4500 samples of the injector readouts. The file in this case is about 18 MB uncompressed. Unfortunately, due to the gammy way it formats this text it's not very easy importing it to a spreadsheet. But after a lot of arsing around with regex in Notepad++ I got it into Excel, and with some pretty formatting it's now like this:

[The extension png has been deactivated and can no longer be displayed.]

I've attached the full spreadsheet if anyone's interested.
Attachments

[The extension zip has been deactivated and can no longer be displayed.]

2002 2.0 HDi 90 Rapier saloon (for sale)

User avatar
rwb
3.0 24v
Posts: 2515
Joined: Thu Jun 17, 2010 7:53 pm
Location: Yorkshireman exiled in Salop
Contact:

Re: My DiagBox/PP2000 setup experience

Post by rwb » Fri Apr 18, 2014 10:39 am

I've been using PP2000 under XP for a while, but have just got Diagbox 7.02 going under Windows 7.
This is on a Dell D610 from 2006 (2GHz Pentium M, 2GB RAM).

By comparison Diagbox is unusably slow, so looking to compare experience.

It looks like I shouldn't have put Diagbox on my main (only) machine (which is also my work laptop) since the services it installs sometimes eat RAM and/or CPU.

Is there anything that Diagbox does that PP2k doesn't? (Other than connect to a 508 -- as if I'll need that.)

R-plate 406 1.9 TD LX (1 year) | 02 406 2.0 HDi (90, Siemens) GLX+nav (8 years) | 07 407 2.2 HDi GT (since 2013) | 307cc 2.0 180 | Map of PeugeotForums users offering PP2k

seelaz
Newbie
Posts: 1
Joined: Thu Jan 29, 2015 2:49 pm

Re: My DiagBox/PP2000 setup experience

Post by seelaz » Thu Jan 29, 2015 2:55 pm

Im currently working in a PP2000 log player, thanks to your input on the log files i could write a php script that converts the xml in javascript (WIP). Im still testing it and Im in need of some feedback so when you have some spare time head to http://seelaz.com.br/projects/peugeot/ and have a look. Thanks!

User avatar
Rolebama
2.0 Turbo
Posts: 316
Joined: Wed Dec 04, 2013 3:15 pm
Location: Middlesex (NW London)

Re: My DiagBox/PP2000 setup experience

Post by Rolebama » Fri Jan 30, 2015 1:46 pm

I installed my PP2000/DiagBox to my laptop, but, because of partitioning, I only had a 25GB C partition, and it was a bugger removing stuff to make room for it. I did get it working OK, and one of the things I remember was that it gave me two icons on the desktop to find the drivers, and fire up the unit every time I plugged it in. It all worked fine, although it wouldn't find the Engine ECU because of a broken wire, which was my non-start problem at the time. It was a long process with a multimeter which eventually found the problem. I have since deleted the stuff from my laptop and intend to get a 'dedicated' one in the future.
It may seem that I am knocking PP2000, but I am not, it's just another tool in the toolbox, and as such, does not contain all the answers.
1998 2.1 GLX TD

Liliflower
1.6 8v
Posts: 12
Joined: Thu Jan 29, 2015 6:45 am

Re: My DiagBox/PP2000 setup experience

Post by Liliflower » Mon Oct 26, 2015 8:36 am

rwb wrote:I've been using PP2000 under XP for a while, but have just got Diagbox 7.02 going under Windows 7.
This is on a Dell D610 from 2006 (2GHz Pentium M, 2GB RAM).

By comparison Diagbox is unusably slow, so looking to compare experience.

It looks like I shouldn't have put Diagbox on my main (only) machine (which is also my work laptop) since the services it installs sometimes eat RAM and/or CPU.

Is there anything that Diagbox does that PP2k doesn't? (Other than connect to a 508 -- as if I'll need that.)
PP2000 is older software for old Pug, it DiagBox is newer sw for both Pug and Citroen, it keeps updating, currently released to V7.57 or newer
http://www.obdii365.com/wholesale/lexia ... p2000.html

Post Reply