Vag-Com AAT Engine Data Blocks

Hello.

After the Opto version refused to communicate with my MSTG, I built the Maik's MAX-232 version based on an article. Now I can access my MSTG, read the error memory, and display 'single readings,' but not 'measure blocks.' I can display these measure blocks for the automatic transmission, but that also worked with the older Opto version. I've also tried messing around with the settings, but nothing has helped. I've also read here that the 1Z has a similar problem, but I haven't found much information about it from the AAT (presumably referring to a specific system or module).

Is there anyone who has actually managed to read the AAT Meas.Blocks?
And I could probably make an even better adapter than the one Maik made.

Please don't suggest that I could buy one – I'm not exactly flush with cash, and the car is already expensive enough. There's also the Alex Weiss adapter, which only adds galvanic isolation, but that wouldn't really benefit me and might even worsen things due to the optocouplers.

Audi 100 (C4), manufactured in 1993, 2.5 TDI (engine code: AAT), automatic transmission.
Toshiba, very old laptop, 133MHz, 32MB.

With a little searching, you would have found it: /viewtopic.php?t=7694

Quote:

"The AAT with the initial software version only displays measurement block 00."

The measurement block 00 only applies to AAT versions 1 and 2. Starting with version 3, you can also read out other measurement blocks. You can identify whether you have an AAT version 3 by checking if it has an engine cover or if the control unit number ends in 'E' or 'F'.

Hello!

I bought a '92 C4 with an AAT (115 hp) engine.
I am unable to perform a diagnosis using VCDS. I have tried using VW tool and VDS pro as well, but I am not getting any communication.
Ref.: 0281001129.
We have had success with Bosch ESI, which allows us to diagnose a number of issues, but we have had no success with VAG-COM.
Can this type of diagnostic tool be used with VAG-Com?

This forum is really great; I've learned a lot.
Thank you!

Best regards.
David.

Try going to Options -> Start Baud -> 240.

-Uwe-

The baud rate alone didn't help me. If I really need the diagnostic information urgently, I'll probably have to get a smart interface.

Hello!

I tried it, but I had no success.
What kind of intelligent interface are you referring to?
Mine has a dual K/L interface.

Best regards.
David.

What kind of intelligent interface are you referring to?

A HEX interface.

Sure, here's the translation:

"Like this one:"
http://shop.dieselschrauber.de/index.php/cPath/23

Best regards, Rainer.

Will I be successful with this interface?
What is the difference between a normal interface and a Hex interface (besides the registration)?

Best regards.

Hello,

especially the product features, as explained in the respective descriptions .
Let me list the highlights:
- Check if the K/L lines are functioning correctly (vehicle wiring harness is okay, radio installation is okay).
- The diagnostic adapter has its own intelligence, which means that the timing of the diagnostic protocols can no longer be disrupted by the "non-real-time operating system Windows."
- CAN-Bus support.
- Generic OBD2 capability (beta testing, as it's brand new).

The details are in the descriptions, and it wouldn't make much sense to copy them here again.

Best regards, Rainer.

Hello!

Success!
With win98 and a baud rate of 240, I was successful. I spoke with my Audi, and she said everything was OK, no errors. I was good to her, and she loves me too!

Thank you for your help!
Regards,
David.