I didn't try yet, but I guess that TP2.0 and UDS are different enough such that for my new 2013 Audi A4 vag-blocks won't work out of the box, right? If it doesn't, what exactly is needed to get UDS supported?
Best,
Stephan
I looked at your code and I think I do understand the whole picture a bit better now. Sorry for any confusion that I may have caused.
UDS support needs to be implemented as a substitute for KWP2000, they're both defined on the same level. I still have to check wether UDS also uses TP2.0 / ISO-TP as underlying transport layer. Unfortunately, UDS seems to be less specified than KWP2000 and I'm still collecting material now. I already found the ISO 15765 chapters and will check how far that brings me. My hope is that many of the KWP2000 ids can simply be mapped, but it's more likely they changed everything again all over.
The Bluetooth ELM327 that I have works well on the Audi, but only OBD2 so far which gives very limited info. I was in particular interested in the fuel level indicator (FLI), but it always returns "NO DATA" for that. A friend of mine owns an older VW Golf station wagon and he had the same limited info via OBD2, but I'm sure vag-blocks will work on his car, so we'll try it out there.
Best,
Stephan