Graphing Recorded Sessions in PP2000 - A Solution

Just your normal general chatting in here..

Moderator: Moderators

User avatar
fattail95
2.0 Turbo
Posts: 409
Joined: Wed Jun 24, 2009 6:35 pm

Graphing Recorded Sessions in PP2000 - A Solution

Post by fattail95 »

Evening guys,

UPDATE: I've rewritten this in C++ for cross platform capabilities and performance. Link to the source code is below.

For a while now I’ve known that there was a way to get Peugeot Planet to export a log of all the actions performed during a diagnostics session - this log includes all menu’s navigated, as well as the live data viewed on the journey (see here for more details: http://www.406oc.co.uk/viewtopic.php?f= ... 06#p218830). We all know that it can be tricky (and dangerous) trying to watch this live data while driving, let alone try to interpret it, so in my spare time I’ve been working a piece of software that will take in this log and convert it into a clean, importable file for use in Microsoft Excel for example.

I’ve come across a few issues while trying to clean the Peugeot log file, the main problem being that the way the text file is formatted is absolutely awful. There is no way you’re ever going to be able to import it to any graphing software ‘as-is’, so I spent a lot of time building a program that will take in all these entries, clean them, and then output them to a save file. Below is an example of the log before cleaning:

Code: Select all

===========================================================
Principal parameters 2

Engine speed: 803  Rpm
Diesel pressure regulator current: 705.9 MA
Pre-injection advance: 12 °
Main injection advance: 1 °
3rd piston deactivation: No 
Turbo pressure measured: 1035  Mbars
Turbo pressure reference value: 1129  Mbars
Turbo pressure electrovalve OCR: 88  %
Atmospheric pressure: 1012  Mbars
Coolant temperature: 80  Deg. C
Air temperature: 9  Deg. C
Fuel temperature : 19  Deg. C
Injected flow set point: 7  Mm3/stroke
Frame :
    Q7306C3    R011017000561C3198DD43C01000078783131818100000000FD000001
    Q7306C4    R011017000561C4198DD4813C04000178310000818100FDFD00000001
    Q7306C8    R011016000561C81926001039569681B9A28892766D082EFDE10000
    Q730699    R01100C000561993B0D0000BAA2D4D48025
    Q73069B    R01100C0005619B81858080580012803B2E
    Q7306C3    R011017000561C3198ED53B01000078783131818100000000FD000001
    Q7306C4    R011017000561C4198DD4813B04000178310000818100FDFD00000001
    Q7306C8    R011016000561C8192500123C559581B6A28893776C082EFDE10000
    Q730699    R01100C000561993B0D0000B8A2D4D48025
    Q73069B    R01100C0005619B818580805700127F3C2E

===========================================================
Principal parameters 2

Engine speed: 803  Rpm
Diesel pressure regulator current: 705.9 MA
Pre-injection advance: 13 °
Main injection advance: 1 °
3rd piston deactivation: No 
Turbo pressure measured: 1035  Mbars
Turbo pressure reference value: 1129  Mbars
Turbo pressure electrovalve OCR: 88  %
Atmospheric pressure: 1012  Mbars
Coolant temperature: 80  Deg. C
Air temperature: 9  Deg. C
Fuel temperature : 19  Deg. C
Injected flow set point: 7  Mm3/stroke
Frame :
    Q7306C3    R011017000561C3198DD43B01000078783131818100000000FD000001
    Q7306C4    R011017000561C4198ED4813A04000178310000818100FDFD00000001
    Q7306C8    R011016000561C8192600123B589681B7A28892766D082EFDE10000
    Q730699    R01100C000561993B0D0000B6A2D4D58026
    Q73069B    R01100C0005619B81858080570012803C2E

===========================================================
This is just two frames from the log file, and there are hundreds if not thousands if you have the software going for more than a few minutes. Cleaning these entries manually is not an option, and as we all want to be able to graph this data, as it is much more meaningful and interpretable, I had to find the patterns and reference points within the file. Last night I finally completed the build, and here it is! There’s no UI to it as it doesn’t require one, just a small console executable but trust me there are many hundreds of lines of C# behind it that do a lot of heavy lifting:

Image

This will return a text file wherever the program is run which contains the clean, graphable data. As there are two different menu’s (principal parameters 1, and 2), I’ve had to make two different versions to deal with each data format.

Principal parameters 1:

Image

Principal parameters 2:

Image

And from here a graph takes 2 minutes to make, which makes it far easier to analyse trends and if there is anything wrong anywhere. This is particularly helpful when diagnosing issues like duff MAF meters, poorly high pressure pumps and even diagnosing boost leaks by overlaying measured pressures against reference pressures. Not to mention the advantage of having the ability to use any graphing software you want, and not having to be hampered by the typically poor built-in ones that often come with diagnostics software. The graphs I've shown above still do not show all the data, any variation of the parameters can be plotted, I just demonstrated the most common ones.

Turbocharger Pressure

Image

Fuel Pressure

Image

Mass Air Flow

Image

Turbocharger EV Duty Cycle (Wastegate)

Image

Having studied several logs from both HDi 110s and 136s, the log format seems to be consistent among those models. As such, here is a public release of the program (not guaranteed to work with all cars, however), but should work with most! If you have a different engine, please feel free to modify my source code -- all I ask is that you re-upload it so others can use it too.

Download: https://www.dropbox.com/s/pp41v6rec6trl ... r.cpp?dl=0

All the best,

Ben.
Last edited by fattail95 on Wed Aug 01, 2018 8:43 pm, edited 12 times in total.
2001/Y Peugeot 406 2.0 HDi Saloon
150hp/330nm Powerflow stainless exhaust Kevlar clutch Cat delete EGR & Doser delete Leather interior Windows tinted Cruise control 5 dial cluster Yatour bluetooth Starfish alloys Twin rear fogs
User avatar
jonsowman
3.0 24v
Posts: 1707
Joined: Wed Sep 21, 2011 4:19 pm
Location: Surrey, UK (J9 M25)

Re: Graphing Recorded Sessions in PP2000 - A Solution

Post by jonsowman »

This is superb, I'll have to give it a try. In what way does the data differ on a vehicle-by-vehicle basis?

It's a shame the data is recorded by PP2000 in such an annoying format.

Still, well done! This will certainly come in useful :D
Image
2002 V6 SE Coupé (210bhp) - (Aegean Blue)
2002 D9 2.2 HDi Exec Estate - Samarkand Blue
PM me for PP2000 diagnostics around Surrey
User avatar
fattail95
2.0 Turbo
Posts: 409
Joined: Wed Jun 24, 2009 6:35 pm

Re: Graphing Recorded Sessions in PP2000 - A Solution

Post by fattail95 »

jonsowman wrote:This is superb, I'll have to give it a try. In what way does the data differ on a vehicle-by-vehicle basis?

It's a shame the data is recorded by PP2000 in such an annoying format.

Still, well done! This will certainly come in useful :D
Thanks very much! Should make any fault finding a lot easier now. Here is a log from another Peugeot 406 HDi (this ones a 90):

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 mine:

Code: Select all

===========================================================
Principal parameters 2

Engine speed: 803  Rpm
Diesel pressure regulator current: 705.9 MA
Pre-injection advance: 12 °
Main injection advance: 1 °
3rd piston deactivation: No 
Turbo pressure measured: 1035  Mbars
Turbo pressure reference value: 1129  Mbars
Turbo pressure electrovalve OCR: 88  %
Atmospheric pressure: 1012  Mbars
Coolant temperature: 80  Deg. C
Air temperature: 9  Deg. C
Fuel temperature : 19  Deg. C
Injected flow set point: 7  Mm3/stroke
Frame :
    Q7306C3    R011017000561C3198DD43C01000078783131818100000000FD000001
    Q7306C4    R011017000561C4198DD4813C04000178310000818100FDFD00000001
    Q7306C8    R011016000561C81926001039569681B9A28892766D082EFDE10000
    Q730699    R01100C000561993B0D0000BAA2D4D48025
    Q73069B    R01100C0005619B81858080580012803B2E
    Q7306C3    R011017000561C3198ED53B01000078783131818100000000FD000001
    Q7306C4    R011017000561C4198DD4813B04000178310000818100FDFD00000001
    Q7306C8    R011016000561C8192500123C559581B6A28893776C082EFDE10000
    Q730699    R01100C000561993B0D0000B8A2D4D48025
    Q73069B    R01100C0005619B818580805700127F3C2E

===========================================================
Principal parameters 2

Engine speed: 803  Rpm
Diesel pressure regulator current: 705.9 MA
Pre-injection advance: 13 °
Main injection advance: 1 °
3rd piston deactivation: No 
Turbo pressure measured: 1035  Mbars
Turbo pressure reference value: 1129  Mbars
Turbo pressure electrovalve OCR: 88  %
Atmospheric pressure: 1012  Mbars
Coolant temperature: 80  Deg. C
Air temperature: 9  Deg. C
Fuel temperature : 19  Deg. C
Injected flow set point: 7  Mm3/stroke
Frame :
    Q7306C3    R011017000561C3198DD43B01000078783131818100000000FD000001
    Q7306C4    R011017000561C4198ED4813A04000178310000818100FDFD00000001
    Q7306C8    R011016000561C8192600123B589681B7A28892766D082EFDE10000
    Q730699    R01100C000561993B0D0000B6A2D4D58026
    Q73069B    R01100C0005619B81858080570012803C2E

===========================================================
These are just two frames, but as the software requires anchor points to find beginning and end of frame, any variation would mean it will crash. It's easily fixable but it just takes time to rewrite and restructure the classes in the code.
2001/Y Peugeot 406 2.0 HDi Saloon
150hp/330nm Powerflow stainless exhaust Kevlar clutch Cat delete EGR & Doser delete Leather interior Windows tinted Cruise control 5 dial cluster Yatour bluetooth Starfish alloys Twin rear fogs
User avatar
Doggy
Mod with a 2.2 HDi, De-Fapped!
Posts: 10710
Joined: Mon Oct 13, 2008 11:49 pm
Location: Northants

Re: Graphing Recorded Sessions in PP2000 - A Solution

Post by Doggy »

That does look mighty impressive, well done sir!

I've noticed the on-screen presentation of data differs from car to car, but maybe just maybe it might be consistent across full mux 2.2's.
(Might be quite a few takers if that were the case, both here and in coupe land).
2002 HDi 2.2 Exec Estate, (2008-12) (wonderful)
2003 HDi 2.2 6-speed Exec Estate (2012-19) (also a gem)
2009 Citroen C5 2.0 HDi VTR+ Estate (godawful heap)
2008 BMW E91 330i touring (great fun - murdered by a reversing SUV)
2007 BMW E91 325i touring (slower smoother quieter)
User avatar
fattail95
2.0 Turbo
Posts: 409
Joined: Wed Jun 24, 2009 6:35 pm

Re: Graphing Recorded Sessions in PP2000 - A Solution

Post by fattail95 »

Doggy wrote:That does look mighty impressive, well done sir!

I've noticed the on-screen presentation of data differs from car to car, but maybe just maybe it might be consistent across full mux 2.2's.
(Might be quite a few takers if that were the case, both here and in coupe land).
That is a very good shout. If anyone who own's a 2.2HDi can give me a copy of their log data, and they are consistent, I will build one free of charge for everyone to use. It's very simple, when you are exiting PP2000, and you're back at the first screen, just hit F5 (I think) and it will give you 10 slots. F2 Saves to a slot and then you'll find a .zip file in this directory:

C:\APP\OUTILREP\TRACE\MEMO\

The data log doesn't need to be anything special, just a 10 second view of Parameters 1 and 10 seconds of Prameters 2 will suffice and I can code it. Would be mighty useful for 2.2 owners in particular.
2001/Y Peugeot 406 2.0 HDi Saloon
150hp/330nm Powerflow stainless exhaust Kevlar clutch Cat delete EGR & Doser delete Leather interior Windows tinted Cruise control 5 dial cluster Yatour bluetooth Starfish alloys Twin rear fogs
User avatar
Doggy
Mod with a 2.2 HDi, De-Fapped!
Posts: 10710
Joined: Mon Oct 13, 2008 11:49 pm
Location: Northants

Re: Graphing Recorded Sessions in PP2000 - A Solution

Post by Doggy »

fattail95 wrote:If anyone who own's a 2.2HDi can give me a copy of their log data, and they are consistent, I will build one free of charge for everyone to use. It's very simple, when you are exiting PP2000, and you're back at the first screen, just hit F5 (I think) and it will give you 10 slots. F2 Saves to a slot and then you'll find a .zip file in this directory:

C:\APP\OUTILREP\TRACE\MEMO\

The data log doesn't need to be anything special, just a 10 second view of Parameters 1 and 10 seconds of Prameters 2 will suffice and I can code it. Would be mighty useful for 2.2 owners in particular.
Top stuff!
I'll try at the weekend, (unless someone else gets in first).
2002 HDi 2.2 Exec Estate, (2008-12) (wonderful)
2003 HDi 2.2 6-speed Exec Estate (2012-19) (also a gem)
2009 Citroen C5 2.0 HDi VTR+ Estate (godawful heap)
2008 BMW E91 330i touring (great fun - murdered by a reversing SUV)
2007 BMW E91 325i touring (slower smoother quieter)
User avatar
fattail95
2.0 Turbo
Posts: 409
Joined: Wed Jun 24, 2009 6:35 pm

Re: Graphing Recorded Sessions in PP2000 - A Solution

Post by fattail95 »

I'd like to see at least three 2.2HDi logs before I make a start on it, so if any other have Planet please take the time to do so as others would benefit!
2001/Y Peugeot 406 2.0 HDi Saloon
150hp/330nm Powerflow stainless exhaust Kevlar clutch Cat delete EGR & Doser delete Leather interior Windows tinted Cruise control 5 dial cluster Yatour bluetooth Starfish alloys Twin rear fogs
User avatar
jonsowman
3.0 24v
Posts: 1707
Joined: Wed Sep 21, 2011 4:19 pm
Location: Surrey, UK (J9 M25)

Re: Graphing Recorded Sessions in PP2000 - A Solution

Post by jonsowman »

I'll stick mine on the Coupe at the weekend, no problem 8)
Image
2002 V6 SE Coupé (210bhp) - (Aegean Blue)
2002 D9 2.2 HDi Exec Estate - Samarkand Blue
PM me for PP2000 diagnostics around Surrey
User avatar
fattail95
2.0 Turbo
Posts: 409
Joined: Wed Jun 24, 2009 6:35 pm

Re: Graphing Recorded Sessions in PP2000 - A Solution

Post by fattail95 »

I've put a post up on the coupe club too, as soon as I have a few files I'll let you guys know if they're consistent.
2001/Y Peugeot 406 2.0 HDi Saloon
150hp/330nm Powerflow stainless exhaust Kevlar clutch Cat delete EGR & Doser delete Leather interior Windows tinted Cruise control 5 dial cluster Yatour bluetooth Starfish alloys Twin rear fogs
User avatar
Doggy
Mod with a 2.2 HDi, De-Fapped!
Posts: 10710
Joined: Mon Oct 13, 2008 11:49 pm
Location: Northants

Re: Graphing Recorded Sessions in PP2000 - A Solution

Post by Doggy »

Think I've managed to collect some data as described above.
Can you PM me an e-mail address to send it to, or let me know how I can get it to you?
2002 HDi 2.2 Exec Estate, (2008-12) (wonderful)
2003 HDi 2.2 6-speed Exec Estate (2012-19) (also a gem)
2009 Citroen C5 2.0 HDi VTR+ Estate (godawful heap)
2008 BMW E91 330i touring (great fun - murdered by a reversing SUV)
2007 BMW E91 325i touring (slower smoother quieter)
User avatar
fattail95
2.0 Turbo
Posts: 409
Joined: Wed Jun 24, 2009 6:35 pm

Re: Graphing Recorded Sessions in PP2000 - A Solution

Post by fattail95 »

PM'd! :cheesy:
2001/Y Peugeot 406 2.0 HDi Saloon
150hp/330nm Powerflow stainless exhaust Kevlar clutch Cat delete EGR & Doser delete Leather interior Windows tinted Cruise control 5 dial cluster Yatour bluetooth Starfish alloys Twin rear fogs
User avatar
Doggy
Mod with a 2.2 HDi, De-Fapped!
Posts: 10710
Joined: Mon Oct 13, 2008 11:49 pm
Location: Northants

Re: Graphing Recorded Sessions in PP2000 - A Solution

Post by Doggy »

8)
2002 HDi 2.2 Exec Estate, (2008-12) (wonderful)
2003 HDi 2.2 6-speed Exec Estate (2012-19) (also a gem)
2009 Citroen C5 2.0 HDi VTR+ Estate (godawful heap)
2008 BMW E91 330i touring (great fun - murdered by a reversing SUV)
2007 BMW E91 325i touring (slower smoother quieter)
User avatar
fattail95
2.0 Turbo
Posts: 409
Joined: Wed Jun 24, 2009 6:35 pm

Re: Graphing Recorded Sessions in PP2000 - A Solution

Post by fattail95 »

Eric, your copy is done, check your inbox 8) your output log was identical to mine so no modification needed! Happy graphing.

Yours (one frame):

Code: Select all

===========================================================
Principal parameters 1

Engine speed: 771  Rpm
Camshaft/crankshaft synchronisation: YES 
Measured fuel pressure: 306  Bar(s) 
Difference between fuel pressure measured and fuel pressure recommendation: 2  Bar(s) 
Diesel pressure regulator OCR: 18 %
Injected flow set point: 10  Mm3/stroke
Injector flow correction 1: 0.43  Mm3/stroke
Injector flow correction 2: 1.45  Mm3/stroke
Injector flow correction 3: -0.90  Mm3/stroke
Injector flow correction 4: -1.14  Mm3/stroke
Injectors 1 and 4 voltage: 79.4  Volt(s)
Injectors 2 and 3 voltage: 79.8  Volt(s)
Measured air flow: 588  Mg/impulse
EGR valve electrovalve OCR: 0  %
EGR throttle electrovalve OCR: 0  %
Frame :
    Q7306C4    R011019000561C4188BD58435050001523E0000808000FDFD00000001000E
    Q7306C8    R011016000561C81828001935649C84B9B585719374082DFD860000
    Q73069A    R01100C0005619A5292C40004AA00010800
    Q73069E    R01100C0005619E0404182727CB80967FFD
    Q7306C4    R011019000561C4188AD58434040001523E0000808000FDFD00000001000E
    Q7306C8    R011016000561C81827001934649C84B8B985719274082DFD860000
    Q73069A    R01100C0005619A5292C40004AA00010800
    Q73069E    R01100C0005619E0404122727CB80967FFD

===========================================================
Mine (one frame):

Code: Select all

===========================================================
Principal parameters 1

Engine speed: 1478  Rpm
Camshaft/crankshaft synchronisation: Yes 
Measured fuel pressure: 463  Bar(s) 
Difference between fuel pressure measured and fuel pressure recommendation: -2  Bar(s) 
Diesel pressure regulator OCR: 24 %
Injected flow set point: 21  Mm3/stroke
Injector flow correction 1: -0.12  Mm3/stroke
Injector flow correction 2: 0.35  Mm3/stroke
Injector flow correction 3: -0.82  Mm3/stroke
Injector flow correction 4: 0.43  Mm3/stroke
Injectors 1 and 4 voltage: 79.8  Volt(s)
Injectors 2 and 3 voltage: 69.9  Volt(s)
Measured air flow: 629  Mg/impulse
EGR valve electrovalve OCR: 0  %
EGR throttle electrovalve OCR: 0  %
Frame :
    Q7306C4    R011017000561C42E8DD483560500027A2F0000868600FDFD00170002
    Q7306C8    R011016000561C82E3B4835566BAA83B9A27E858475003C00E10000
    Q73069A    R01100C0005619A7A92C42804FCFF400000
    Q73069E    R01100C0005619E05052E3D400E799F7F00

===========================================================
Any other 2.2HDi owners, please send in your logs too! Doesn't take a minute to do. If they're all the same (which I suspect) I will release a public version.
2001/Y Peugeot 406 2.0 HDi Saloon
150hp/330nm Powerflow stainless exhaust Kevlar clutch Cat delete EGR & Doser delete Leather interior Windows tinted Cruise control 5 dial cluster Yatour bluetooth Starfish alloys Twin rear fogs
User avatar
fattail95
2.0 Turbo
Posts: 409
Joined: Wed Jun 24, 2009 6:35 pm

Re: Graphing Recorded Sessions in PP2000 - A Solution

Post by fattail95 »

UPDATE

Finished copy is now available in the original post, should work with most HDi 110s and HDi 136s! Shoot me a PM if you need any help with it.

Best Regards
Ben.
2001/Y Peugeot 406 2.0 HDi Saloon
150hp/330nm Powerflow stainless exhaust Kevlar clutch Cat delete EGR & Doser delete Leather interior Windows tinted Cruise control 5 dial cluster Yatour bluetooth Starfish alloys Twin rear fogs
vlceon
Newbie
Posts: 1
Joined: Sun Jul 29, 2018 9:26 am

Re: Graphing Recorded Sessions in PP2000 - A Solution

Post by vlceon »

Can someone please reupload this program? Thank you
Post Reply