So currently this is how it goes: connect using auto/auto baud. It will fail on fast init, go to slow, it will connect then timeout after 2 seconds or so( I can hear the cluster "clicking" too like ME7logger).
Then without turning ignition off connect on auto again(this is the procedure I have to do with me7logger too, connect on 0x00 fail cause of wrong response then connect with slow0x01) and it will connect with fast 0x10 and run on correct baud.
After this it works perfect.
As said before it means your cable does not support one of the parameters, so it can not communicate on KW1281.
Otherwise it would just work.
As per tool and my application I was a little bit surprised it didnt parse all the measurements from the (public) A2l available for this ecu - 018CM 0008 only the same ones ME7logger creates basically.
Would've been nice.
You can create your own custom list from the A2L:
https://docs.vehical.net/logger_customOr in your case you can also try the VAG KWP - Advanced paid protocol (but only if fast init actually works directly with your cluster).
The free protocol is literally the same variables as ME7Logger because ME7Info was used to dump all the bins and then that data used.
It's also why it's free.
Full A2L logging is for newer ECU's (that support fastinit directly) in VAG KWP - Basic.
If you want to add some a2l, you do that the same way as with ME7Logger using a custom measurements file.
