Getting started with reversing P01/P59

[Vetteyog Profile]

Here it is - I spent quite a bit of time scouring various corners of the net, and have a pretty comprehensive list. https://github.com/hkaase/P01P59XDFRepository

At this point, if you are active in XDF development, I would be more than willing to add you to this repository. If you aren't familiar with Git or uncomfortable using it, shoot me a PM, and I will be happy to get you up to speed. That way we can ensure everyone has access to the latest and most cutting edge XDFs.

Once we start seeing more P10/P12 activity, we can also direct development of XDFs for those OSes here to simplify the search process.

I tried to download the XDF from the link and there is no download button. Where can I find more XDF files for a P10. I'm working on a 2004 GMC Envoy XL.

[Gampy]

What OsID ??

GitHub is absolutely worthless as an XDF repository ... IMNSHO!

-Enjoy

[antus]

I dont think there are any XDFs for a P10 yet (happy to be wrong!) use universal patcher, it can find some things.

[Gampy]

Then you'll be happy Antus!

Because thanks to Phoenix there is one: 12587430 OS V.1.2.xdf

-Enjoy

[Phoenix Profile]

Then you'll be happy Antus!
Because thanks to Phoenix there is one: 12587430 OS V.1.2.xdf

-Enjoy

Edit: Changes file name to help with confusion. Added date it was posted to the name.

That is an older version, guess I never got around to posting the latest version as I am still not happy with the way the DTC tables are. Basically instead of a DTC being a byte like in the P01/P59, in this OS every DTC is determined by the individual bit. Basically the only way presently to define them in Tunerpro is to create individual flags that change a bit. I still don't feel like making 621 different flags for an OS that I will likely never use. If I ever need to use it, I'll just define as needed. Also I'm not sure how to calculate the checksum when saving the file, maybe Universal Patcher can?

Either way, I'm attaching it here and just be warned that the XDF is for informational and research purposes only, I would not recommend using it on your daily driver, but maybe playing with it on a bench set up.

[Gampy]

Pheonix,

Could we fix the versions/names please, they are confusing, it appears the older one is newer by version ...
The older one is marked: 12587430 OS V.1.2.xdf
The newer one is marked: 12587430 OS Beta V.1.xdf

Thank you!
-Enjoy

[Phoenix Profile]

Pheonix,

Could we fix the versions/names please, they are confusing, it appears the older one is newer by version ...
The older one is marked: 12587430 OS V.1.2.xdf
The newer one is marked: 12587430 OS Beta V.1.xdf

Thank you!
-Enjoy

No problem. I think I'll just start adding the date of the revision in the file name to avoid confusion. Thanks!

[Vetteyog Profile]

Then you'll be happy Antus!
Because thanks to Phoenix there is one: 12587430 OS V.1.2.xdf

-Enjoy

Edit: Changes file name to help with confusion. Added date it was posted to the name.

That is an older version, guess I never got around to posting the latest version as I am still not happy with the way the DTC tables are. Basically instead of a DTC being a byte like in the P01/P59, in this OS every DTC is determined by the individual bit. Basically the only way presently to define them in Tunerpro is to create individual flags that change a bit. I still don't feel like making 621 different flags for an OS that I will likely never use. If I ever need to use it, I'll just define as needed. Also I'm not sure how to calculate the checksum when saving the file, maybe Universal Patcher can?

Either way, I'm attaching it here and just be warned that the XDF is for informational and research purposes only, I would not recommend using it on your daily driver, but maybe playing with it on a bench set up.

I'm messing around with a P10 and going to build a bench harness this weekend. I'll start diving in and see what happens... on a spare PCM.