I am sharing this file that I have been compiling since I messaged you last night.
It's work in progress, but hopefully people here will share their information, and we can put together something final and comprehensive.
Edit to add:
My plan is not just to catalog a bunch of setting that people can pull and drop into their cars, although I won't stop you from doing that, but it is actually to do cataloging and explaining what those things are.
The hard part is obviously using used cars for sale to determine what general features a car has or doesn't have that affects the as-built data. I have listed those which I think have an impact at the top of the spreadsheet and literally just used the images of the cars for sale to make that determination. Obviously, I suffer from situations where used cars have been upgraded after being sold since the as-built won't match the options anymore. But for the most part, people tend to NOT upgrade their cars with OEM parts (or do so very infrequently) for me to be worried about how it will impact my data.
The first car in the sheet is my car which I used as a baseline for the dataset to compare against.
WHat you will notice is that the last 2 digits of every data point is moved to the final column, this is because every single final 2 digits represent the checksum of the row. Basically there is a calculation that takes the address (726-01-01) and the data points (0C00, 0000, 01) and does fancy math to them to spit out the final numbers. Essentially this is to make sure you are not putting in something into the car that wholly makes no sense. So if you see one data point that is only 0C38, that means that the actual data is only 0C and the 38 is the checksum to make sure the data is correct. You can practice in the checksum tab. That actually massively cuts down the number of inputs that are needed to be analyzed for differences.
docs.google.com
