What interface is required

Hello everyone
What interface do I actually need if I want to use it across different brands but also across different software?

For my old car, my old KKL diagnostic interface is sufficient. (even with RS232 connector)
This, however, makes it impossible to read other older vehicles (e.g., Ford, Mitsubishi, Nissan, etc.) because the aftermarket software does not recognize the interface, and therefore, a connection to the control unit naturally fails.
Only VCDS recognizes my interface, but of course it doesn't work with third-party brands.

Does there exist such a "universal interface" that works with other software?

Second question:
Was was the CAN system compatible with, backwards?
(so, dass mit einem CAN-Interface (KKL) ausgelesen werden kann)

Hi,

Regarding the second question:

http://shop.dieselschrauber.de/vcds-obd2-profi-diagnose-kkl-can-p-46.php

The MicroCAN interface cannot do that.

Best regards,

Jan

Quote:

...This will make it impossible, for example, to read other older vehicles (Ford, Mitsubishi, Nissan, etc.) because the aftermarket software does not recognize the interface, and therefore, a connection to the control unit naturally fails.

Furthermore, with older vehicles, the fact that some parts are {MISSING/NOT AVAILABLE} adds to the difficulty.
Use ISO 9141 (K-Line) as a data interface, which means using completely different hardware.
need.
There are systems (Bosch KTS, Gutmann, Launch, ...) that operate in this direction.
(more or less good); but they are really expensive
Here is a comparison of DEKRA: http://files.vogel.de/vogelonline/vogelonline/files/2230.pdf

Hi Micha

Thank you for the responses.

No, it shouldn't be too expensive either, as I'm using it purely for personal, hobby-related purposes, and I'll never recoup the costs.

I just want to occasionally check older cars (among friends) and sometimes newer ones (e.g., my current car) for errors. (Error diagnosis)

For my old "top-of-the-line" car, I am perfectly familiar with my interface, but this does not work with other software, and therefore also not on other (older) vehicles.

Maybe I should actually go with 2 cheaper interfaces, one for KKL and one for CAN-bus.

For all vehicles that are not VAG, I have been using *** or also **** for quite some time.
So far, I've been able to work on everything, whether it's a Ford, BMW, Toyota, old or new.

Software was intended for Delphi or something similar.
I am satisfied.
Staged diagnosis, training, or real-time data are also no problem.
Greetings




EDIT @Autoservice: As far as I'm aware, the version costs around 2,500 EUR.

Advertising for cloned tableware, please elsewhere, not here

If you aim for 100% diagnostic depth, you can only achieve this with VCDS or, of course, a VAG tester.

@autoservice
That's what I didn't know either. I purchased this item privately.

Autoservice wrote:

If you aim for 100% diagnostic depth, you can only do it with VCDS or, of course, with a VAG tester.

Hello
As already written, for my "old" Renner, I used the KKL interface with the VCDS from Rainer. With this, I am more than adequately equipped for this vehicle.
I am also aiming to be able to read fault codes in other vehicle brands (outside of the VAG group) for people I know.
The goal is not to perform a detailed component diagnosis, or to activate or trigger specific actors.