That is really cool. Nice work.

There's some Python seed-key code included with the same research paper. It came up with the same key result as Forscan when I tested it against my 2018 instrument cluster. I need to test it against a few other modules in my truck. It's also pretty easy to get the secrets from the module firmware. A...

Could be the same idea, right? Application A needs to read version 1.xx of the message, and application B needs to read version 1.xy of the message.

Could it be the difference between a bump in the CAN database version vs what the OS actually cares about?

Like the CAN handler needs to know a 7 byte message is valid for error checking purposes, but the OS only reads 6 bytes to look for data that's relevant to it.

Good info. I'm not sure what GM actually called this second set of HS GMLAN ID's, but it would helpful to categorize what PCM hardware OS versions ran it. For now, at least ya know what your lookng for in the ID structure for anything in question. If CAN ID's are all dec, it's Corvette / Holden ver...

Love reading this stuff. Thanks for sharing. I wish I had something to add, but all I can offer is gratitude.

I checked my CS+ install and it doesn't have any of the PRM files you're looking for.

PRM is for 78K and V850. PR5 is for RL78.

I've got an old Colorado IPC circuit board I was about to throw away. Let me know if it can be used for destructive testing or something.

I can't believe they even offer programming via ELM type devices. It also blew my mind that Ford thinks it's acceptable to take 9+ hours to program a cluster.

2018 F150 8" cluster in a 2017 truck. I did a quick skim of the code associated with the high range DIDs and it looks like none of them do anything especially interesting.