I've done about as much as I can learn via google and chatGPT so I could use some help...
lol...
Yeah reversing shit like this you either need a very strong existing background or it's gonna take years.
The latest idea I had was to compare the dump from the Audi with a Dodge/Chrysler as they do NOT have an immobilizer.
Waste of time.
Problem is I probably need the Funktionsrahmen or Damos for this TCU to at least point me in the right direction but I can't find it.
hex/a2l is out there.
I guess I'm asking for what you guys think I should do. I need the immobilizer and component protection removed from the ASW due to using this transmission with an aftermarket ECU. I have the Audi Kmatrix (DBC file) which I plan to use in order to make a canbus bridge.
Good luck with that ... you probably won't get very far unless you run something like MoTeC and implement all the torque calculations...
Is there any good reason you want to use this transmission? There are much simpler alternatives.
The DBC file doesn't explicitly mention how the WFS5 immobilizer is implemented nor mention any signals transmitted over CAN 2.0
That's because the WFS5 documentation is a higher level clearance need-to-know basis and there are it's own documents. It is also not part of the ASW in most ECU's, it gets linked in as a library.
I assume it's being done over UDS or K-line perhaps.
Completely wrong. K-Line is not used in over a decade and UDS is a diagnostic protocol that has nothing to do with inter-module communication.
For immo there is a switch in the cal on/off, I have never tried if it actually bypasses it.
Component protection no idea.