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 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:
Principal parameters 2:
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.
Mass Air Flow
Turbocharger EV Duty Cycle (Wastegate)
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,