antus wrote:@dms we should move this part to another thread, one of the existing development ones but to answer the question above: usually you can analyse the DLC code that gives the data pids back to a tool or pc, see what ram that is addressing for a given pid and when you have the ram address see what code is using that ram. The better question is what are you trying to do? Porting a whole OS to another PCM may be technically possible in theory but it'd be a huge and impractical job, difficult to test and validate and especially parts of the code that run anything custom in the proprietary silicon there that we don't know about. You could do the watchdogs and DLC easily enough, but then what? Applying the same patch to different OS based on patterns might be a better approach if that was the aim, or just modifying the most capable OS (like BoostOS
viewtopic.php?f=42&t=7482 ) and using only that. Better to clearly define the question before coming up with the answer.
I'm basically still in the doing stuff to learn it phase so there's not a huge focus on anything directly. You make some good points about the DLC codes and the scan tool side of things. I've never poked around that code, so that will be new area for me to explore lol.
As far as goals, some of the P04 bins sound to be known less than others, so being able to use the way the hardware is read and making a logic path back to different settings might be a reasonable way to make more of a universal detection for a given setting. Doing it based on the actual function's code probably would be better though since I would think GM would reuse at least some code across computer models. I guess it's just a concept I had that could be interesting to explore at some point. Sounds like efforts into the P04 side of things are getting pretty far though so I might have to switch focus to another model that's less worked out. Maybe P11 would be a good one, or the computer I got with the 2005 3500 engine (E something I think?).
For actual goals of my business #1 is being able to disable immo/pats/passkey etc, and secondary is disabling "extra" features that are normally required stock, for the P04 example, it's possible to change the tune so the MAF isn't needed and the engine runs on only the MAP sensor, one less sensor to cause problems in a demo derby. Eventually I'm planning to build a shop and ideally get a dyno to actually tune computers focused on the demo derby logic. Of course never really tuned an engine this way before, I do fine with carb's, but I EFI side of things will bit a bit of a learning curve even though I get the basics well enough and I know the actual signals and such pretty well.
