Engine Diagnostics: Read & Log Issues

Hello there...

I'm having a problem with VCDS (I've tried various versions). Everything works fine when only the ignition is turned on. However, as soon as I try to view live data with the engine running, I get an error message: "unknown protocol (9c?)" or "synchronization error."

Don't downvote if the answer can be found elsewhere... I really did search!

Can you help me with that?

Regards,

Thomas.

...if you had searched for "Synchronization", you would have found the following:

/viewtopic.php?t=3089&highlight=synchronisation*

or

/viewtopic.php?t=2080&highlight=synchronisation*

or

/viewtopic.php?t=2404&highlight=synchronisation*

Best regards, Styrian (hoping to have been of help).

"Of course, I've been searching for synchronization information. Also, this isn't a custom-built interface. Furthermore, everything else works fine except for reading the engine management data while the engine is running. The airbag, ABS, and comfort instrument functions are all working perfectly, even with the engine running!"

By the way, it's a 2003 model with a 1.9L TDI PD engine and 74 kW.

Do you have any other brilliant ideas?

fabiaix wrote:

It is also not a custom-built interface. Furthermore, everything else works except for reading the engine management data while the engine is running. The airbag/ABS/comfort instrument functions perfectly, even with the engine running! Do you have any other brilliant ideas?

Hi.

"How about..."

Claim your (presumably cheap) interface.

buy a reasonable one, e.g., from the local shop.

to build something usable (see linked plans in the first link mentioned above).

Thank you...

[Edit Admin]Link removed, the cable is from the carputer.[/Edit]

It works perfectly in other vehicles. It's also not an opto-isolated interface. And it's not cheap either, costing over €140 when converted from a specialist shop here in Oslo.

So, please stop nagging at me!

No one is messing around here. But if you're looking for support, please contact your manufacturer.
You must surely understand that in a forum associated with a shop that sells OBD tools, support for third-party devices is not to be expected, right?

Anyway. I think it's legitimate if someone has ordered a license. Besides, there were reasons why I didn't order from Germany or the USA (import regulations, import duties, 25% VAT, and it's a non-EU country). Furthermore, it doesn't seem to be a problem with the interface, since it works perfectly fine with other vehicles, but not with mine.
I thought this forum was intended for people interested in engine technology. Otherwise, is it only supposed to be for customers, or not? Even then, I would be in the right place with my VAG license...

I would be very grateful if someone could help me right now!

Regards,

Thomas.

fabiaix wrote:

It works perfectly fine in other vehicles. It's also not an opto interface. And it's not cheap, costing over €140 when converted from a specialist shop here in Oslo.

Well, unfortunately, even the cheapest technology is often sold at an inflated price.
I once had very similar problems (with a self-built interface) that were simply due to the fact that its electrical characteristics didn't meet the standard. So, with the engine stopped and connected to the other ECUs, it only "worked" by chance. As soon as the engine was running, there were constant communication interruptions.

Try running a diagnostic test with a workshop-grade diagnostic tool. If that shows the same problems, then (contrary to expectations) the issue is likely with your car. Otherwise, it's most likely with your interface.
The software should be fine, because otherwise, in my opinion, it shouldn't work even with the engine idling.

Quote:

So, please stop nagging me!

If someone is actually hacking, it reads completely differently.

Hi Thomas,

fabiaix wrote:

... Even then, I would be in the right place here with my VAG license... If anyone can help me right now, I would be very grateful! Regards, Thomas

In simple terms: the money for the license was probably pocketed by the company "Carputer," so they should be the ones to take care of the problem.
That means there is no entitlement to support from my side.
Personally, I suspect the problem, as Ulf already mentioned, lies in hardware specifications that are borderline.
If the interface doesn't work with VAG-COM 409.1, it's almost certain that it won't work.

Best regards, Rainer.

You're welcome.

It's working perfectly fine. The problem only occurs when the engine is running, and then only on my car. It works without any issues on other vehicles!

Regarding the license: It's directly from Ross-Tech. The term "carputer" only includes a link to Ross-Tech.

Ich meine irgendwo gelesen zu haben das es bei neueren Fahrzeugen zu problemen kommen kann, finde den beitrag aber nicht wieder. Could that be possible?

Thomas.

Hello Thomas,

No, it definitely isn't due to "newer vehicles." Is your notebook powered by the vehicle's on-board network?
If so, that would be another potential source of error; if not, it is very likely due to your adapter hardware (USB?).

Generally, it's advisable to obtain the adapter hardware from a distributor listed on the Ross-Tech website.
http://www.ross-tech.com/distributors.html

You can be sure that the hardware and software will work together in that case. Based on the image in the link you provided, your hardware is definitely not a product of Ross-Tech or any other listed distributor. As far as I can tell, it looks very similar to the cheap imports from China that are sold on eBay without the first digit of your price.

Only your seller can really help you with that (or maybe not), as they should know what technology is inside and where the potential problems might be. With that, I'm closing this topic.

Best regards, Rainer.