Series 1.5 3200 has CEL, but codes can't be read

[Robbe]

Hi all,
as I have a CEL, with a car that starts but does not want to run over 1500rpm (does not react to pedal) , I am very anxious to see what causes it.
I strongly suspect the TB as it was behaving badly before (pedal pot has been changed for contactless recently so that should be fine), but before I part with 1500 euro for another throttle body (my present one is already made contactless so can't send that one away for revision), I want to check if it is not some other issue. So I need to read the codes.

But as I have a 2000 year car (series 1.5 ), with 16 pin OBD (not OBD2!!), I can't get my 3 readers (even an Autel of 125 euro) to connect to it.
I read the UniDiag software is the one to go for, but all those postings are from at least 6 years ago, and when I google UniDiag, nothing recent turns up.
So is UniDiag still available, or is there a new alternative? Or any other ideas to retrieve the codes from this intermediate model?
Can I tap into the wires to the connector, feed them into my 3 pin connector that adapts again into 16 and into my reader? But which wires...

My other option is to have the car picked up at my house to have it picked up and brought on a flatbed to one of the 2 specialists in the whole country (Netherlands), and that is what I am trying to avoid as you might understand...

 

[davy83]

my 2001 car works on the KWP 2000 protocol. DO your reader support that one? I have a cheap one I got off e-bay and it works a treat. I also have a wifi ODBII unit that allows me to use my laptop and I am pretty sure this is also KWP 2000. I appreciate the early 3200's were not properly integrated. There are a few threads on here (somewhere) that explain how ot get older cars to talk to code readers you might get some clues from these.

 

[Robbe]

Both the more expensive readers support the KWP2000 protocol fast and slow (as I can see them in the screen trying to connect.) The cheap reader I bought a few months ago does not work either.
I have searched a lot already, and as far as I understand, the UniDiag software was the one to go for, but I am afraid it does not exist anymore.
I am afraid I am clueless now as I do not have the knowledge to dive into those protocols and see why it does not connect.
I had hoped for a more or less plug and play solution, but I understand that it is not that simpel on these series 1.5 cars...

 

[Contigo]

Your car is a crossover car which has the OBD port but uses the old protocol. Get a copy of Unidiag...

 

[Robbe]

Yes, I have tried to contact Sander for that

Update: thanks to member Redsonnylee I now have the UniDiag program. I have ordered the special VAG COM cable with ftdi chip inside, will arrive later this week (I hope).
Will post further updates.