RKS+ CAN Interface: Troubleshooting & KOBD2Check Issues

Hello everyone,

I purchased an OBD2 diagnostic kit some time ago.
I actually only needed the two add-ons for VCDS. But then I decided to get the whole kit for just a little more, about 10 euros.

A few days ago, I wanted to test the cable with KOBD2Check on a non-VAG vehicle and read out its data.
Unfortunately, it's not really working the way I envisioned it.
Vehicle data is always being received. The VIN and information about the control module are displayed.
After that, nothing happens. The application seems to be frozen.
The other buttons, such as "Check" or "Error," are not triggering either.
My Skoda Octavia is only displaying a message that a new software version has been found for the BCM (Body Control Module).
After that, there is nothing more.

I have tested the application on both Windows 10 x64 and x86, as well as on Windows 7 x64.

What am I doing wrong?
Can someone help me?

Best regards and thank you very much in advance.

Hi,

Please upload a screenshot. Then, please tell us what you expect to happen and what you think should happen. Also, please specify exactly which "non-VAG vehicle" you tested (model, year of manufacture, engine).

Best regards, Rainer.

A few weeks ago, I worked on an Opel Combo from 2015 and a Ford Transit from 2009.
Of course, I didn't take any direct screenshots of either.

Today, I had a Skoda Octavia from 2016 on the diagnostic tool, and it had numerous error codes stored in its memory. I also took a screenshot of those error codes.
However, the tool did not display any error messages and also provided no information about the control units installed.

As proof of the existing errors in the vehicle, I performed an autoscan using VCDS. This scan displayed all the error codes. See attachment.

What do I expect from KOBD2Check?
It lists the control units.
It displays the entire error memory of the control units completely and correctly.
That I can clear the error memory.

At least, that's how KOBD2Check is advertised; I understand that it can be used to read data from vehicles other than those manufactured by the VAG group.

Hi.

As I suspected, the engine control unit from the Octavia 3 isn't included in your VCDS text-based scan.
Not because it's not possible, but because you were randomly changing settings within the VCDS program.
Please restore the default settings in the VCDS configuration.

KOBD2Check can read the error memory from the Octavia 3 engine control unit, and your KOBD2Check screenshot proves it. There are zero (no, - ) emissions-related errors stored in the engine control unit.

In principle, only the engine control unit can be read via }OBD2}, and the intended use of KOBD2Check and VCDS is usually different.

Best regards, Rainer.

Hello Rainer,

I am aware that VCDS and KOBD2Check have different purposes.
VCDS is not configured in a "meaningless" way. It simply still had the checkmark enabled for using the K-line.

The description for KOBD2Check includes the following text:

Quote:

Features of this diesel mechanic OBD2 scan tool: Read OBD2 control unit information (control unit part number / software version, VIN, CVN, etc.). Read and clear OBD2 error codes. Read and record sensor data via OBD2. Check the control unit self-tests (readiness).

Since the text uses the plural form, I assumed that it can read out multiple control units accordingly.

Phantomias wrote:

Since the text is written in the plural form, I assumed that it can also read out multiple control units accordingly.

That's because you didn't know what OBD2 is...

You simply didn't read the product description correctly, because there is a link in it that explains it.
https://shop.dieselschrauber.org/en/obd2-diagnose-kit-p-321.php

Best regards, Rainer.