imo, this is not a good indicator if this immo-off patch doesn't work at all. if it works when swapping one a6 transmission into another then it's good enough. I think it was mentioned that in his case, this is likely a powerclass mismatch issue. a6 trans is expecting to see an engine with 3.0"t" powerclass, but he has a 4.0tt which has different powerclass.
To be honest WFS5 is still a mystery to me and the TCU has several variables that seem to be a flag for the immobilizer status as well compliment flags, but I was under the assumption power class was just another piece of the pie that makes up the “immobilizer” and or component protection.
I did find the function that TXs on powertrain bus (to ECU presumably) using can ID 0x12 but there’s no XREFs to the data that makes up the payload so it’s probably written at some offset from another address. Numerous helper functions are simply just returning addresses at some offset from param 1 for example so it’s a bit of a nightmare to track these down manually.
I also found the same function, which calls the immobilizer TX function on the Audi, in a RAM 8HP70 ASW which simply don’t have these function calls and are padded with 0’s (Because there’s no immo in that SW). I tried to mimic this in the AL551 but TCU doesn’t communicate after doing so. Lastly, I haven’t confirmed with Ghidra but there’s also some communication pattern tables listed in the AL551 A2L which I assume monitor processing times of tasks / functions which might be affected by doing so..
Audirama got the immo adapted with ODIS, which he will send me bench read, so I plan to at least compare before after to see what is changed to maybe get a better clue to functions.
